I have a WD 120GB Caviar drive in an ADS Pyro case. It has started behaving badly. First it would spin up and down for no reason in the middle of operation. Then it would spin down and cause Finder hangs. Now it will not mount and some computers can see it and some cannot.
When I run system profiler on my PB, it sees the Oxford Chipset, but does not see the drive itself. When I hook it to a friend's ibook, it sees the drive but will not mount it.
Disk Warrior hangs and so does Tech Tool when I try to have them look for the drive.
I get the following report from console log:
Sep 6 13:17:10 Czar /sbin/autodiskmount[195]: Some fsck failed!
Sep 6 13:17:10 Czar /sbin/autodiskmount[195]: disk2s9 hfs yes yes Caviar 120GB [not mounted]
Sep 6 13:17:10 Czar /sbin/autodiskmount[195]: (autodiskmount.tproj/DiskArbitrationServerMain.c:1665) failed to set up death notifications for port -1: {0x4} (os/kern) invalid argument
Sep 6 13:17:10 Czar /sbin/autodiskmount[195]: (autodiskmount.tproj/DiskArbitrationServerMain.c:410) received unrecognized message (id=0x47) on notify port
Anyone know what is happening here? Any ideas? Anything would be appreciated as I have 80GB of data on there that I really want back.
Edit: Data Rescue X has been suggested. It sees the drive, but hangs as soon as it tries to do the recovery. Once the drive is physically turned off, it will respond to the force quit command, but do nothing else. Also, I have managed to trick DiskWarrior into seeing the drive, but it crashes immeidately when I ask it to repair.
As soon as the drive is turned off, the OS shows the standard "OS cannot read volume, do you want to Initialize?" and "Do you want to launch Disk First Aid?" pop-ups.
Additionally, top shows that fsck_hfs hangs when the drive is first plugged in. How is that happening?
Top
