July 23, 201510 yr Had a crash today at 1:23pm PDT. I got the alert from another system that reported it lost contact with the apcups daemon, but it came back after a minute or two. I then got notification from unRAID that it was running a parity check. When I got home I verified the system rebooted today. I've read a few other threads here and looks like some people are having the same problem? I upgraded to 6.0.1 over the weekend, so I've not been on this version very long. Never had a crash before. I have Docker enabled, but I had the CrashPlan containers shutdown while I was still doing some work on them. No other customizations have been made to the system. Since syslog is written to memory, there's no way to get any information on why the crash happened. Wish there was a way to have logs sent somewhere else that was not so volatile.
July 23, 201510 yr Click the Log button on the top right of the unRAID GUI. Leave the Log window open until the server halts. Save a Diagnostics file after opening the Log window. Attach both the diagnostics file and the entire contents of the Log window.
July 24, 201510 yr Author Ah, good point. I could also just ssh into the system and leave a running tail of the log too and leave that running on my desktop. I'll try both of those out in case that crash happens again.
Archived
This topic is now archived and is closed to further replies.