February 4, 201214 yr UnRAID B14 red-balled drive 2. Performed a short SMART test and clean bill of health. Syslog showed no drive issues so I start a data rebuild for drive 2. Shortly after starting I get constant read errors on drive 5 in syslog. Performed a long 4-hour SMART test and absolutely nothing wrong and zero reallocated blocks. So now what is the next step since disk2 is now apparently wiped out due to an incomplete data rebuild but another drive showing constant read errors by unRAID even though a comprehensive SMART test shows zero errors? This may be the second time an unRAID beta red-balled one drive but the real issues were with a different drive (parity drive last time I believe).
February 4, 201214 yr Author The syslog was just too big (52 MB) so I truncated it to show some of the disk5 errors... But the REAL problem is: What do I do now? I was thinking of replacing all cables and power connections on disk5 and try again. If that fails, I will start the array, cancel parity rebuild, then copy over the network all contents belonging to disk2 and disk5, replace drive 5 entirely with a brand new drive, then rebuild the array with new parity. Is this the basic steps to recreate the array from two "bad" drives? syslog-2012-02-03_snip.txt.zip
February 5, 201214 yr Author Changing out the SATA cables to new ones seems to have done the trick. I also swapped around power connectors (but reutilized the same ones) to see if perhaps issues follow the power cable plug but so far, the data rebuild is still chugging along just fine and much farther along than before the change-out. Crossing my fingers...
Archived
This topic is now archived and is closed to further replies.