For the second time today on my few-days-old Odroid N2+ build with Buster desktop I have a system-wide freeze.

Blue LED is constantly on and there is no response to keyboard or mouse events.

Was interacting with Plex both times but I only have Plex, Tautulli and Samba server set up.

I'm loath to pull the power but 30mins in to the second freeze (I pulled the plug on the first one).

What should I be looking for when I get it running again?

Enable verbosity and put a serial console to it and check if there is any output to it.

Also create and provide logs with armbianmonitor -u once you rebooted it.

 

Which image did you use?

what's a serial console?

Here's the armbianmonitor output

https://app.box.com/s/np7u3bv3l7fpvzlybdz7xhh63d28ilkj

The best and almost only way to properly debug a SBC.

It is a 3pin UART connector featuring RX, TX and GND. If you handle SBCs you defnitily want to invest in an USB-UART adapter. No worries, they are dirt cheap these days.

Are you using a N2 image on your N2+?

I used the Buster desktop 5.6 image from this page

https://www.armbian.com/odroid-n2/

So you were basically using the wrong image for the board and wonder that it has hickups?

Support for N2+ is in early development. However you can already build a proper N2+ image using the build tools.

"you can already build a proper N2+ image using the build tools."

 

No, because I have no clue how to do this.
Perhaps I should start off with HardKernal's image?

 

4 minutes ago, j___r said:

No, because I have no clue how to do this.

Check out the documentation

https://docs.armbian.com/Developer-Guide_Build-Preparation/

 

Quote

Perhaps I should start off with HardKernal's image?

Sure, give it a try.

If "Support for N2+ is in early development" what hope do I have of building a stable image?

That it may work better since it is at least an image that is designed for that particular board

thanks for the help

On 8/15/2020 at 11:02 AM, j___r said:

Perhaps I should start off with HardKernal's image?

Kernel is the king. You can build an image with old 4.9.y but fairly functional Hardkernel kernel or try to go with bleeding edge 5.7.y ... which works but its overall problematic at this moment. "I only want stability" takes a loooot of time.