There are plenty tutorials available for it and it's fairly simple to use. That prevents anything you try being irreversible and making things worse. However, it appears that I am not able to do this as it appears that the USB interface is connected to the HDD and can not be removed (there appears to be no SATA interface).įrom the description and images (great on both), it appears there are either a lot of bad sectors or a head is not reading.Īs commented, it's possible the USB is hung up on one bad sector making the drive inaccessible.įirst you should clone the drive with ddrescue or similar if you want to work on it yourself. Is there anything else I could do to attempt to recover as many of the files in the hard drive as possible?ĮDIT: I opened up the enclosure to attempt to retrieve the HDD inside it and insert it as an internal drive to my computer as per suggestion from comments. HDD Guardian (a GUI for Smartmontools' smartctl) however, can read the SMART data: Test Error Code: 08-Too many bad sectors detected.
Here is the result when I attempt to run a 'quick test' with it: WD Data Lifeguard is unable to read the SMART data. I tried accessing the drive in two different computers, and the same thing happens in Explorer, Disk Management and Device Manager. It also shows up in Device Manager as 'working properly' and by its proper name (WD Elements 1048 USB Device). The drive's status light works properly when it is being accessed by GetDataBack. I don't hear any clicking sound coming from the drive. The drive is a 1 TB WD Elements, HDD model no: WD10JMVW, not often used and connected (only around 30 minutes every 2 – 3 days, just to move files from my main HD) and not more than a year old.
The log shows messages all looking like: Error 1117 in HD130: duringReadLba: LBA=43569984, CHS=-lx-lx-l, Cnt=64ĭetails: This is on Windows 7. It seems to me from the GetDataBack log that it is not reading any files at all. I ran GetDataBack for NTFS to attempt to recover my files and this is the screenshot of the log ~1 1/2 hours after it was first run:
The drive shows up as Unknown, Not Initialized and Unallocated in Disk Management: I didn't allow it to initialize and clicked 'Cancel'. I opened Disk Management (dskmgmt.msc) to check and it said that 'You must initialize a disk before logical manager can access it': I recently plugged in an external hard drive of mine and noticed that it doesn't show up on the list of drives in Computer.