February 8, 20179 yr After being down for a few months, I finally got my array back up and running. However, I noticed that one of my 8 drives was reporting a failing attribute (End-to-End_Error is FAILING_NOW). I have a couple other spare drives, so I swapped the failing drive out with the spare. The funny thing is, my spare drive also began reporting the same failing attribute (End-to-End_Error is FAILING_NOW). I then moved the 2nd failing drive to a new bay and unRAID seemed to be fine with it then. It allowed me to do a data rebuild on the spare. I've run 2 parity checks since then and have found 0 errors. However, both drives have the End-to-End_Error attribute as FAILING_NOW in their SMART reports. I've done some reading it sounds like this attribute has to do with the HDD's cache becoming corrupted. It sounds like I should get these drives replaced, but I just want to make sure that this failing attribute couldn't be caused by some other component (SATA cable, motherboard, etc). From the attribute description, it sounds self-contained to the HDD itself, but I'm not very familiar with how SMART is implemented. I would surely rather replace a $5 cable than a $160 drive.
February 8, 20179 yr General rule of thumb: If a drive's smart report is telling you that its failing, then its probably failing. End to end is where the drive has detected an internal error where the CRC generated at one end of the circuit board for data didn't match the CRC generated at the other end of the drive for the same data. IE: Bad cache memory, what not on the drive. It can't be trusted... Definitely not the cable...
Archived
This topic is now archived and is closed to further replies.