This is at least my third 500GB RE2 drive to fail. :mansad: This one is weird, though. It failed in Windows while doing an automatic backup, and in my confusion after the failure and not realizing I had a dead drive, my backup file got overwritten by a backup without the data I want.
Nothing can read the WD5000ABYS-01TNA0 drive.
- BIOS will usually (With some help, depending on the PC) detect it.
- When I try a recovery program (booting to DOS/Linux CD) that can read MBR and Track 0, the drive always gives read errors and not a single byte seems to be accessible. If the utility uses FreeDOS, it is very slow to boot.
- The SMART data is readable from a LiveCD Linux environment, but Gparted does not see the drive. It appears that the Linux environment does not mount the drive for Gparted to see.
- Spinrite 6.0 cannot read it. FreeDOS spits out errors, so this is slow to boot, but Spinrite exclaims in red text that something is wrong. I have used Spinrite a lot, and I haven’t seen this before.
- WDC diagnostics give an error 0003 I believe. It doesn’t get beyond drive model and serial number and a quick test that fails.
- When I add it to a spare PC, Windows boots slow.
- When I go to Disk Management, Windows will ask to initialize it and says it is unpartitioned.
- Sounds: Yes, it spins, and yes, it makes seek sounds, for example when I run Testdisk for hours as it tries to read every sector looking for an MBR.
I have, in the past, fixed dead hard drives with an embedded controller PCB swap. But I don’t know if this is a candidate for this.
Now for the interesting part. It was partitioned (dynamic disk) with a 30 GB C: drive mirror (RAID 1) and a 270 GB partition that was half of a RAID 0, and then a 200 GB regular partition. So although my mirrored C: drive is working, my RAID 0 is the drive I am concerned about. I would like to get some of the data off my RAID 0 partition if possible, but I cannot even make an image of the dead drive. My other drive is (of course) working fine.
Prior to death, a lot of timeouts were logged by atapi (event id 9) during ntbackup, and then a BSOD. I rebooted, with no clue as to what the problem was because the machine was not being manned. More of the same errors and another Blue screen a few days later during an automatic backup. Manual reboot (still no clue) and then the inevitable “uncorrectable read error” from dmio (event id 35). There were also write errors and delayed write errors. After about 3 hours of these errors, another BSOD occurred. The status code of 0xc0000185 generally means to check the cable or termination. I know the cable is not culprit here.
Question: Anyone know how I might get some data off this drive?