dave_the_nerd
Lifer
Have an HD (WD Blue WD10EXEZ 1TB) I bought last week. Dropped it into a pre-existing NAS. NAS seemed fine.
Few days later, drive drops out of RAID.
No SMART errors. Reboot, it's fine.
Yesterday, drive drops out of RAID. Then the RAID drops. Then the other RAID drops. NAS seizes up. Console throws a bunch of errors saying the drive is timing out and that the port multiplier is dead. Errors are looping looping looping looping. NAS wouldn't reboot.
So unplug everything, plug everything back in, boot, it's fine. Run a ZFS scrub, it seizes up. The first error message is specific to that drive, so I pull it, reboot, and everything's fine again. Scrub completes, etc. NAS is fat and happy, even if one of my zpools is is degraded.
Plugged the drive into another computer and it's behaving itself. Surface scan was good, etc. SMART status good. Can't find anything wrong.
So should I just call it cradle death, and say whatever I need to say to exchange the HDD (presumably for a different brand, since if the drive's not actually defective, it could be a firmware problem or something?) or should I pursue/troubleshoot this more?
Few days later, drive drops out of RAID.
No SMART errors. Reboot, it's fine.
Yesterday, drive drops out of RAID. Then the RAID drops. Then the other RAID drops. NAS seizes up. Console throws a bunch of errors saying the drive is timing out and that the port multiplier is dead. Errors are looping looping looping looping. NAS wouldn't reboot.
So unplug everything, plug everything back in, boot, it's fine. Run a ZFS scrub, it seizes up. The first error message is specific to that drive, so I pull it, reboot, and everything's fine again. Scrub completes, etc. NAS is fat and happy, even if one of my zpools is is degraded.
Plugged the drive into another computer and it's behaving itself. Surface scan was good, etc. SMART status good. Can't find anything wrong.
So should I just call it cradle death, and say whatever I need to say to exchange the HDD (presumably for a different brand, since if the drive's not actually defective, it could be a firmware problem or something?) or should I pursue/troubleshoot this more?