I'm running 6.x and while I still haven't diagnosed a drive gone missing a few weeks ago...  I swapped disk locations and was waiting for it to go missing again.

 

After rebuilding parity, I had my drives spun down...  Last time a problem happened my Supermicro drive cage went ballistic (loud buzzer).  I disabled it because it was really quite loud - but planned on checking every day or two to see if the problem recurred.  (NO reboot last time, just the config became invalid, array stopped, loud buzzer)

 

So today I go to use the server, and find out that 3 hours ago it apparently rebooted.  I have it on a UPS, and my main computer's UPS shows no events (power loss) nor are any of my digital clocks reset.

 

It seems for some reason - the machine crashed / rebooted on it's own.  Of course the syslog is not saved after the reboot, right...  So I'm wondering if there's any way to "capture" any crash logs for next time?

 

By the way - my IPMI console doesn't show any memory faults or anything in the logs.  I did have one of those about 3 years ago, but nothing since.

 

I'm really perplexed.

See Fix Common Problems plugin - Troubleshooting.

 

What is the exact model of your power supply?

Thank you - I have a Seasonic X650.

 

All disks up now - because for some reason I'm unable to spin down disks if the array isn't started???  Anyway, 97W total, and at the time of reboot the machine should have had all 8 HD's spun down.

 

I installed the fix common problems script, and configured notifications.

 

The only errors right now is that the array is not started and the powerdown plugin is not installed.  There's a warning that community applications is not installed.

 

I wish I could spin down my HD's - I don't want to start the array and do a parity check as it will take 20 hours and it's pretty warm in that room right now.  (Again, the HD's were not powered up at the time, system temperature is normal according to my IPMI readings and would have been lower this morning when the problem occurred)

 

Thanks for your interest and help

What about FCP Troubleshooting Mode? Powerdown will save your syslog when you intentionally shutdown or reboot, but it won't help if something else is causing reboot. Go to Fix Common Problems Settings and turn on Help to see what Troubleshooting Mode does.