I have a rather odd problem. I have 5 x WD15EARS in use: 4 x in RAID5 and 1 x in a USB dock.
So this is the situation. I bought 4 disks in November 2010. The ones with the green label. They’ve been running since in a server with an Areca 1210 controller in a RAID5 config. Never had any problem until April this year. 1 disk failed. The Areca had problems detecting the disk. I put the disk in another computer and used WD Lifeguard Diagnostics. It showed this: “06-Quick Test on drive 7 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 7!”. So I created a RMA and shipped the disk. The server kept running degraded.
3 days later, another disk fails. And exactly the same error. I created a RMA and shipped the disk. Of course the array failed but I’ve got backups so no harm done.
Yesterday I received 2 brand new disks from RMA. Also WD15EARS but with a normal black label. Finally I could start my server again. I put in the disks, deleted the old array and created a new one with 4 disks. After a few minutes one disk failed. One of the new ones! I tested it on another computer and exactly the same error message as with the original disks! So I put in 5th disk as replacement. That one was bought a bit over 6 months ago. Again, a few minutes later another disk fails. Same error. This time one of the remaining old ones.
Ok, so I started thinking I could be the cabling, the controller,… But in meanwhile I tested all disks in a different computer internally. And also on a 3rd computer in a USB dock. No matter where I put them, the errors are there.
And more, the 2nd new disk that I receive yesterday also has those problems!
In one computer I tried to write zeros with the WD tool. After a while: “Sector #285533696 - 285533952::Write Zeros Error! Continue?” I pressed yes and it popped up that many times that I just gave up.
On this computer with the USB dock I’m running HDDScan.
Short self test: error with read element failed
Extended test: error with read element failed
Both seems to be stopped at 10%
Also running the RD-Read test. That one is showing lots of “Bad block found, start LBA…” messages.
Is this even possible?? In a period of days, not counting the time that the server was off, 5 disks fail with the same error. And 2 brand new disks also fail with the same error?
Am I going crazy or do I have just bad luck?