December 10, 20187 yr I wondering if this means the drive should be retired. Error from Fix Common Problems. It is worth noting that this error occured during a parity rebuild. I had another drive with a number of write error. I copied that data off of the failed drive (it was number 14) onto this drive (number 15) using unBalance, then removed the failed drive from the array using instructed here for Shrink array - The "Remove Drives Then Rebuild Parity" Method Quote disk15 (MG03ACA300_SA_94KDK0EYF_350000c900068b5a8) has read errors Quote If the disk has not been disabled, then unRaid has successfully rewritten the contents of the offending sectors back to the hard drive. It would be a good idea to look at the S.M.A.R.T. Attributes for the drive in questionBegin Investigation Here orcrist-smart-20181209-1844.zip orcrist-diagnostics-20181209-1840.zip
December 10, 20187 yr Community Expert Because of the NetApp shelf we can't see the actual SMART report, connect the disk to a SATA port and grab a new one.
December 23, 20187 yr Author Stupid question. I'm out of slots on the unraid box (which is why I'm using the NetApp shelf in the first place). Is there an easily download the SMART report in a windows environment? I have a hot swap drive bay on my windows box that works well.
December 23, 20187 yr Community Expert There are many programs that can read SMART for Windows, including a Windows version of Smartmontools, Google is your friend.
December 26, 20187 yr Author OK, here is the output to the windows version of Smartmontools Drive1.txt Drive2.txt
December 26, 20187 yr Community Expert SMART looks fine for both, you could run an extended SMART test on them just to be sure but most likely the disks aren't the problem, could be cables, power, etc.
Archived
This topic is now archived and is closed to further replies.