January 31, 201412 yr My 4TB WD Red drive recently had a red ball next to it ( assigned as a parity drive ). I assumed the drive as not heathly so i decided to stop the array and re-do a preclear on the parity drive. The results were no errors. I tried to reassign the same drive a parity drive once more. After the preclear step, I did not format the drive or create a partition to it. I believe a parity drive does not need a filesystem. Correct me if I am wrong, I'm new to this. After starting the array, to recreate a new parity, after a few minutes I get a red ball next to the parity drive again. The temperature indicator on the drive changes to *. What could go wrong? The array is now unprotected without parity. How do I solve this?
January 31, 201412 yr Try a couple of things to get more information needed to help: If the array is still running and hasn't been shutdown since the drive redballed, copy out and post the full syslog. If you have shutdown/restarted, then attempt to assign the parity as parity again, and save out the full syslog after the error occurs. Run SMART report on the parity drive and post the results. See syslog and SMART at: http://lime-technology.com/wiki/index.php/Troubleshooting
February 1, 201412 yr Author Here is the Syslog and the Management console just after starting the array. syslog.txt
February 1, 201412 yr Unplug and reseat the SATA and power connections on that drive. Be sure to reseat the SATA connection at the motherboard as well.
February 1, 201412 yr Author I removed and reseat the power and SATA cable for that drive. Problem solved. Thanks.
Archived
This topic is now archived and is closed to further replies.