I've been using my unRaid on the same HW configuration for 2+ years now without incident until recently.  I have unMenu and the monthly parity checker setup.  I always have 0 parity errors when the check runs, but yesterday my server was unresponsive (i couldn't web to it, then when I switched the KVM to it had some errors printed to the screen but I didn't capture them).  I had to to a manual reboot and then it did a parity check.  It had ~360 errors, so i did another parity check right after that and I got ~450 errors.  My shares disappeared once more and I had to do another manual reboot. 

 

How do I troubleshoot this?  Here are some syslog messages from the unMenu GUI.

 

Thanks!

 

Chris

 

syslog-2011-04-19.txt

Start the server and immediately stop the array. Then get SMART reports for your drives and post them.

I've looked around in the forums, but I don't see how to generate a SMART report.  Could you point me in the right direction?

 

Thanks,

Chris

Telnet or from console...

 

smartctl -a /dev/sdf

 

You might need:

 

smartctl -d ata -a /dev/sdc

for older drives...

 

Replace the "sdx" portion with your drive.

 

Shawn

 

the smart reports are in the attachement.  I took them when the array was online (the wife is streaming episodes of tru blood from it as I type) does that matter?  Things seem better now.  My usershares are not disappearing and becoming unavailable.  Sorry if I made much about nothing, but I have lots of data on my server and I've never had soo many parity errors or issues before.

 

Thanks!

Chris

smart_report.txt

The reports look ok. I suspect the errors are due to the manual shutdowns. Are you just holding the power button down?  Use unMenu to install the clean powerdown package. This should let you do a clean power down by quickly pressing the power button.

I had this situation the other day. Not too sure what happened, but after a restart and a parity check with repair, no more errors.

 

It locked up as I started a copy to a drive that was just spinning up. Bought up 250ish errors after the restart, and I ran again and it found 450 errors. One more restart and a parity sync, and it found no errors.

 

Strange..

 

Running 5 Beta5

things have been fine lately I'll mark this as solved and chalk it up to the powerdowns.  Yes I was holding down the power button on the server to power off because it wasn't responding to anything even tty actions.  I'll try that powerdown pkg.  Thanks.

 

Chris