Hi all!

 

So unraid out of nowhere my server went unresponsive. Can't access the GUI nor any docker BUT the Home Assistant VM is accessible and fully working which is really odd. I can ssh into the server and htop shows this.

 

 

CPU 4 pegged at 100% for some reason?

 

trying to reach the UI: 

 

I can't kill sabnzbd docker, doing "docker stop" or "docker kill" just does nothing, just hangs the command forever until I ctrl+c to abort it. Same with df -h for example.

 

Any idea? I don't really want to hard shutdown

Edited February 19, 20242 yr by Sptz87

If df doesn't work then probably diagnostics at command line won't either. I think hard shutdown will be necessary. Then reboot, and

 

Attach diagnostics to your NEXT post in this thread.

 

And setup syslog server.

3 minutes ago, trurl said:

If df doesn't work then probably diagnostics at command line won't either. I think hard shutdown will be necessary. Then reboot, and

 

Attach diagnostics to your NEXT post in this thread.

 

And setup syslog server.

 

Should I just go ahead and hold the power button to force a shutdown?  This was in the middle of a series download. What kind of stuff can get corrupted by doing this? Anything I can do afterwards? Will obviously attach diagnostics!

Can you get syslog from command line?

1 minute ago, trurl said:

Can you get syslog from command line?

Like the old days?

 

I've attached the Diagnostics here now. 

 

I'm also wondering. I'm still on trial and am looking at purchasing, hopefully I won't run into any other issues but this might also be a good time to ask. I'm running it on this flash drive: https://www.amazon.co.uk/gp/product/B077VXV323/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

Should I change it? I have a spare Samsung one: https://www.amazon.co.uk/gp/product/B07FD6D4HJ/ref=ppx_yo_dt_b_search_asin_image?ie=UTF8&psc=1 

 

Or I could just purchase another one if needed anyway. Just hoping this isn't a hardware issue but it was bizarre because I could go into SSH and Home Assistant VM was fully functional and responsive.

AWE Diagnostics Feb 19.zip

 

7 minutes ago, trurl said:

 

Thank you. Hmm I've never seen that option in bios. But I'm wondering if this is definitely related to that because I could see in htop that sabnzbd was knocking out out 100% of the cpu on just one core.

 

I also saw this when booting as I connected a hdmi to the gpu. Mover always works fine, not sure why it's stating that?

 

Same thing just happened whilst SABNZBD was unpacking. But now the entire thing is unresponsive, not even SSH.... Could it be a RAM issue? The server is turned on but nothing is accessible. Just "died".

2 hours ago, Sptz87 said:

Could it be a RAM issue?

Have you tested it? You shouldn't even attempt to run any computer unless memory is working perfectly. Everything goes through RAM, the OS and other executable code, your data, EVERYTHING. The CPU can't do anything with anything until it is loaded into RAM.

6 minutes ago, trurl said:

Have you tested it? You shouldn't even attempt to run any computer unless memory is working perfectly. Everything goes through RAM, the OS and other executable code, your data, EVERYTHING. The CPU can't do anything with anything until it is loaded into RAM.

 

I used to run this even tighter than XMP when it was the gaming rig, and tested thoroughly. Not sure why it'd be a problem now at default XMP. Regardless, I just lowered from 3600mhz to 3200mhz. And so far doing tons of unpacks in sabnzbd without a hitch!