Myk3_ Posted March 26 Share Posted March 26 I have been fighting my unraid system for the past few weeks. Every night, over night, it goes unresponsive causing me to power cycle the machine, or it has an unclean shutdown on its own. I have attached the most recent diag in the logs directory, it is from a few days ago.. Is there a way to force a new diag? I have already enabled the local syslog and mirrored it to the USB drive. unraid-diagnostics-20240322-0558.zip Quote Link to comment
JorgeB Posted March 26 Share Posted March 26 There's no syslog-previous in the diags, post a screenshot from the syslog server settings. Quote Link to comment
Myk3_ Posted March 26 Author Share Posted March 26 I see the syslog previous in the log directory.. one sec.. syslog-previous Quote Link to comment
JorgeB Posted March 26 Share Posted March 26 There's nothing relevant logged there, does it cover a crash? Quote Link to comment
Myk3_ Posted March 27 Author Share Posted March 27 yeah.. When i woke up this morning unraid showed an unclean shutdown.. I am sure it will happen again tonight, ill post the logs again tomorrow.. Quote Link to comment
Myk3_ Posted March 27 Author Share Posted March 27 looks like it did it before i went to bed.. it also looks like the system did not create a diagnostics file.. here is the most recent syslog-previous file.. syslog-previous Quote Link to comment
JorgeB Posted March 27 Share Posted March 27 Last log entry is from yesterday at 2100, I assume that was before the crash? Quote Link to comment
Myk3_ Posted March 27 Author Share Posted March 27 yeah I think so.. I don't really know when it happens, most of the time I notice since I have a home assistant VM on unraid and my automations aren't running.. It happened again overnight.. I captured the syslog-previous before starting the array./. syslog-previous1.bak Quote Link to comment
JorgeB Posted March 27 Share Posted March 27 Unfortunately there's still nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.