Last night I noticed that my plex docker had stopped, and would give me an error message when I tried to start it back up. All other docker apps were working. I looked at the system log and it said something about nchan not having enough memory. I don’t know what that means so, I grab the diagnostic and tried to reboot the server. Now, the Unraid won’t boot even though it’s the 1st thing set to boot in my bios. I tried booting it directly from the bios, but it acts as if it’s not there. I plugged the usb in my Mac and it mounts plus all the files are there, so I’m stuck on how to resolve this issue. I’m going to do a fsck check, but other than that I’m lost. Please help.

tower-syslog-20260408-0352.zip

48 minutes ago, weezysteel said:

I grab the diagnostic

You only posted the syslog. Do you have the diagnostics?

See if you can boot memtest86 on your server.

How is a computer with a public IP address able to login to your server?

Apr  7 16:19:35 Tower webgui: Successful login user root from 100.93.240.74

1 minute ago, trurl said:

public IP address

OK, not public, but also not private

https://en.wikipedia.org/wiki/Private_network#Dedicated_space_for_carrier-grade_NAT_deployment

Sorry, didn’t grab the diagnostic initially. I just ran fsck on my usb, inserted it back into my tower, and now it boots. Plex along with everything else seems to be working again, but I still don’t know what happened. I still see some errors in my syslog. I’ve attached it along with diagnostic below

tower-syslog-20260408-2137.zip tower-diagnostics-20260408-1610.zip

If it's working I guess it's OK. Not unusual to see some "error" lines on bootup as Unraid probes the hardware. The colors are completely based on keywords appearing in the line, such as "error".

Do you have a current backup of the boot flash?

Food for thought: If you continue to run into weird or inexplicable problems, it could be your usb drive (sda) going wonky. All sorts of strange can happen when they start failing.