slcc2c

Another safe mode crash, doesn't have anything interesting in the log. Points to HW failure but having trouble id'ing the weak HW. syslog_safe_crash

@JorgeB appreciate it. Any take on logging I can use during this time to capture what the HW failure might be? All the HW is a few months old and purchased at the same time so no obvious culprits.

I was attempting some troubleshooting in safe mode and got another crash, with no obvious errors. During these "crashes" the CLI and WebUI are unresponsive but the system stays on. syslog_safe

Hi all, thanks in advance for the help. Issue Presented as the inability to connect to my server over the network, I am also unable to login to the CLI with a kb/m+monitor. Unraid appears to be crashing in the background, in my syslogs I'm seeing messages similar to "CPU: 9 PID: 1076 Comm: kworker/u48:14 Tainted" and CPU: 9 PID: 24651 Comm: C1 CompilerThre Tainted: P" across multiple crashes. Memtests are passing, safe mode works fine and I can start my dockers, etc. I am using the latest version of Unraid. Timeline Full rebuild in January and moved my USB to a new machine. Over the last 3-4 months I had noticed instability, pinned down to the USB drive failing, and migrated to a new USB 2.0 32GB drive in early June. Since then I have been experiencing <24hrs of uptime before the server became unreachable, during these times the machine was still on and the CLI was up. Over the last 2 weeks, I have been experiencing the issue above. Files syslog_crash & syslog-previous: both have CPU Tainted error syslog_login_crash: syslog when I was able to login over web interface but system immediately crashed tower-diagnostics-20240625-1718.zip: most recent diagnostic that was successfully written. If it is helpful I can download diagnostics from safe mode as well.