3 ms·
I had two failures on a RAID 6 in the same week. All 3TB WD Red's. I'm slowly replacing all of the drives with Seagate 4TB NAS drives. I definitely do not tr
by e40 6y ago
I had two failures on a RAID 6 in the same week. All 3TB WD Red's. I'm slowly replacing all of the drives with Seagate 4TB NAS drives. I definitely do not trust these drives.
And, I had had failures of some of the drives before, but when I pulled them and did extensive tests of them, they were always OK.
- StillBored 6y agoI'm betting its possible if your drives are sufficiently fragmented and you start a heavy write workload that shotguns sectors all over the disk from multiple TCQs the default write command timeouts on most RAID systems aren't sufficiently long. So the drive may not have failed, the RAID just determined that the command was taking to long, fired a reset at the drive and when it didn't immediately respond marked it bad.