October 6, 201411 yr This morning disk3 had failed (red ball). I stopped the array, shutdown the server, and replaced with a 3TB EFRX drive. Restarted the server, I selected the new drive in place of the failed one, and started rebuilding. I got a write error in the log very quickly, and the new drive was red-balled as well. I shutdown the server again, and attached the new drive to a different SATA port. When I start the array, the new drive still has a red ball, and if I start the array, it's unprotected. I am like 99% sure this new drive is good, it gets recognized with proper size, and I can't see any errors in syslog. New drive was formatted with NTFS, but that should not have made any difference in this case, right? How do I get unRAID to 'trust' that the new drive is ok, and start rebuilding?
October 6, 201411 yr Author http://lime-technology.com/wiki/index.php/Troubleshooting#Re-enable_the_drive Thank you! It's rebuilding now. I'm sorry I didn't take a note of the original write error. Oct 6 10:52:15 FS1 kernel: mdcmd (51): check CORRECT (unRAID engine) Oct 6 10:52:15 FS1 kernel: md: recovery thread woken up ... (unRAID engine) Oct 6 10:52:15 FS1 kernel: md: recovery thread rebuilding disk3 ... (unRAID engine) Oct 6 10:52:15 FS1 kernel: md: using 1536k window, over a total of 2930266532 blocks. (unRAID engine)
October 6, 201411 yr Did you pull a SMART report from the original disk? It would help key you know if the drive really failed vs a cable working it's way loose. Most red balls are not failed drives but some issue with the connection.
October 6, 201411 yr Author Nope, again, sorry I will check it out once the rebuilding process is done.
Archived
This topic is now archived and is closed to further replies.