June 19, 20179 yr Bought a new 6tb drive, ran thru a pre-clear cycle with no errors. Found out that new 6TB drive was ever so slightly larger than the other 6TB drives I already had in the system. So this new drive would have to replace one of the current two parity drives. During the parity rebuilding process it looks like tons of write errors showed up, the process was automatically halted, and now I have a red X next to the new drive. Unraid is currently unable to read SMART data either. So my question is where do I go from here. Should I reboot the server to see if I can get smart data? Should I try another parity rebuild? Or just give up and get the drive replaced? Please advise on best course of action. Thank you. tower-syslog-20170619-1800.zip
June 19, 20179 yr Author I rebooted the server and SMART data is now showing on the suspect disk. I'm going to try a different SATA cable to see if that is the issue. Do you recommend I run another pre-clear cycle before I try adding it back in as a parity drive again? tower-smart-20170619-1915.zip
June 20, 20179 yr Author Not that anyone cares , but to keep thread updated: Changed SATA cable and a parity rebuild was successful. Currently performing a parity check to make sure all is ok.
Archived
This topic is now archived and is closed to further replies.