February 9, 20206 yr I'm trying to figure out why one of my unRAID servers is rebooting. It'll be up for 6-8 days at a time, then reboot. I've gone through the logs (attached) and the only thing I see is that it says "unclean shutdown detected". Nothing about why it's actually doing it. Anyone see anything in the log as to WHY it's rebooting? I've been troubleshooting this for a couple months now and I still have no idea why it's doing this. I moved the RAM sticks into the correct slots on the motherboard, disabled a few plugins, disabled Docker, now I'm going to disable the VM service and see if it still reboots. I'm thinking about starting up the syslog server on the thing to see if I can find out what's going on...anyone have any other ideas? Machine is an HP Proliant DL360e G8 Server with 2x E5-2430 CPUs, 64GB RAM and 2 8TB drives, a 3TB drive, an 8TB parity drive and a 240GB NVMe SSD running version 6.8.0. I have another unRAID install, same version, running on an HP ProLiant DL380p G8 Server with 2x E5-2667v2, 64GB RAM, etc that is rock solid. tower-syslog-20200209-1647.zip
February 9, 20206 yr You should enable the syslog server mirroring to the flash drive temporarily, and then post the resulting syslog and diagnostics after the next reboot. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601
February 9, 20206 yr Author 1 minute ago, Squid said: You should enable the syslog server mirroring to the flash drive temporarily, and then post the resulting syslog and diagnostics after the next reboot. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601 Alright. That's a start. Will do. Thanks.
February 16, 20206 yr Author Machine rebooted again right around 10:20p last night, Feb 14th. Looking through the syslog file, I'm seeing what looks like memory errors around that time. Seem about right, @Squid? syslog
February 16, 20206 yr It actually started at ~8:20pm. But net result is the same. Eventually one snuck through that ECC didn't correct and your system rebooted (although I was under the impression that most systems with ECC would simply halt at that point, but maybe I'm wrong). Either way, your memory definitely doesn't look very good.
February 16, 20206 yr Author 26 minutes ago, Squid said: It actually started at ~8:20pm. But net result is the same. Eventually one snuck through that ECC didn't correct and your system rebooted (although I was under the impression that most systems with ECC would simply halt at that point, but maybe I'm wrong). Either way, your memory definitely doesn't look very good. Time for some MemTest fun! Thanks.
Archived
This topic is now archived and is closed to further replies.