Read Error on Data Drive... Now What?

[wreck]

So all of a sudden one of my data drives (disk2) is showing 168 read errors. I've never seen this before on any drive I've had, so I don't know what to do. I ran a correcting parity check, but they still show up. I was getting ready for a few projects ( ugrade from 6.3.5 to 6.4.1, xfs conversion and adding 8tb parity and data drives), but I don't know if I should move forward with this disk as-is. Can it be trusted? Should I RMA it (it's less than a year old)? Diagnostics file is attached. Thanks in advance for the help.

tower-diagnostics-20180208-0952.zip

[JorgeB]

It was a disk problem, looks like the offending sectors were reallocated when unRAID wrote the sectors back, the disk might be fine for now, you can confirm by running an extended SMART test, though even if passes reallocated sectors are never a good sign, but it's difficult to predict if you're going to get more in the near future.

 

To clear the current errors you just need to stop and re-start the array.

[wreck]

Thanks for the quick reply johnnie. The extended SMART test came back with no errors, which is a good sign. I know there is no way to tell for sure, but in general that means I should be able to trust the drive, right? I should be able to go ahead with the changes I'm wanting to do with a relative sense of comfort? Obviously if I see more errors on this drive, then the RMA would be a good option, I believe. Is there any other data I could/should provide to help you guys in assessing the situation? Thanks.

[JorgeB]

If the extended SMART passed, as expected since there were no pending sectors, the disk is fine for now, but keep an eye on it, as long as it does't continue to reallocate sectors on a regular base it should be fine.