spam_nugget

I tracked down the issue - it’s a CPU spike to 100% caused by a deprecated Docker container - Space Engineers - which left nothing for the Unraid OS. Keeping that container off has kept the system stable. The key for me was understanding that the kernel panicking before writing to the syslog (rsyslog on a RPi works well) indicated a hardware-caused lock up but not a hardware error. Although frustrating I’ve learned a lot more about how Unraid operates and how to troubleshoot it, so it’s been very useful.

I'm new to Unraid troubleshooting. If a plugin or a docker caused the crash, would this show in the syslog?

Thanks @JorgeB . I found the grapics card had become unseated, so that could have caused some random fluctuations. That's been fixed. I ran memtest86 for 1.5 hours, with no issues shown; I'm going to run it for 4 hours today and see what happens. Unraid was up for 9 hours last night. Only when I accessed the WebGUI this morning did it crash. I've posted the syslog. It doesn't indicate any errors to me, apart from the php-fpm pool warning. Parity check completed during the uptime last night. syslog

Hi there Unraid (7.1.4) has been very stable for me for months, until the last couple of days. I upgraded to 7.2.0 and started getting instability, with the system hanging after 10-20 minutes. No WebGUI, no SSH, won't respond to a power button press to clean shutdown. I upgraded again to 7.2.1 - no change. I downgraded to 7.1.4 - no change. Same instability. I've added my diagnostics in the hope that someone can tell me what they think is happening. Thanks 😀 Matt usul-diagnostics-20251120-2212.zip