April 26, 201412 yr This morning I tried to watch a movie on PLEX and my server was unresponsive. When I checked, the parity drive was red balled and 4 additional drives had many errors but no red ball. I did a SMART check and the drives were not online. I had to reboot using the server power button, Now the server is running but the parity drive has an orange ball. I am doing a parity check under maintenance mode currently but the check is stuck at 0%. Any ideas? I have attached the syslog before the reboot. syslog1.txt.zip
April 26, 201412 yr Author And now I am panicking because all the drives report empty (even the cache drive). The user shares are gone too. Please help.
April 26, 201412 yr Author Another reboot and now all the drives report having data and the shares are back too. The parity drive is orange balled so parity sync is taking place.
April 26, 201412 yr How is your hardware configured? How many drives total, how many controllers? How are they wired\grouped?
April 26, 201412 yr Author I have 11 drives plus the parity drive. The parity is connected to the motherboard SATA port. The other drives are connected to two LSI controllers. Most of the drives are connected to one of the LSI controllers including the failed ones. The mother board is a Supermicro - X9SCL-II/X9SCM-II.
April 27, 201412 yr Author I have also attached the smart reports from all the drives and they have all passed. smart_report.zip
April 27, 201412 yr Does the parity check work now? Start one and if it hangs collect and post a syslog. Do not reboot the server.
April 28, 201412 yr Author Yes the parity sync finished successfully and no errors are reported. All drives are green now. I do not think any data was lost. Is there anything I need to watch out for?
April 28, 201412 yr Remember - maint mode - no shares are mounted - hence why they were not there until you rebooted out of maint mode .... Am not sure you can do a parity check/sync in maint mode because of this.... Myk
April 29, 201412 yr Author Ok thanks. Still curious what caused multiple drives reporting errors. In the syslog it seems there were all read errors.
Archived
This topic is now archived and is closed to further replies.