Question: Trying to pull data off a drive with hardware failures

haertig · 04-27-2017, 02:30 PM

I am trying to pull data off of a friend's hard drive. Looks like a hardware error. I pulled the drive out of his Windows 10 box (failed to boot there). Put it into an external enclosure and I'm now trying to pull data off it attached via USB3 to my Linux box. When I attempted to mount it, it complained that the drive was "hibernated" and refused to mount it, so I then mounted it read-only, and that worked.

mount -t ntfs-3g -o ro /dev/sdd3 /mnt/Windows

Data is copying VERY SLOWLY. I'm using the "cp" command on his "Pictures" directory currently, since that is his most important. It will probably take 25 years to transfer the data he has at this rate, if it doesn't just stall out completely and die first. e.g., 15 minutes so far to pull off only 20 JPG's, each about 1.5Mb.

Is there any hope for this drive, or should I just give up?

"dmesg" is showing this:

Code:

[1108890.623816] xhci_hcd 0000:02:00.0: ERROR Transfer event for disabled endpoint or incorrect stream ring
[1108890.623835] xhci_hcd 0000:02:00.0: @000000012963d710 00000000 00000000 1b000000 01038001
[1108890.623929] sd 22:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[1108890.623939] sd 22:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] 
[1108890.623949] sd 22:0:0:0: [sdd] tag#0 Add. Sense: Internal target failure
[1108890.623958] sd 22:0:0:0: [sdd] tag#0 CDB: Read(10) 28 00 01 ad c9 18 00 00 20 00
[1108890.623965] blk_update_request: critical target error, dev sdd, sector 28166424

Now, cp is spitting out the following errors, one after the other mostly, but occasionally a file will successfully copy:

Code:

cp: cannot stat 'Pictures/2015-03-18/029.JPG': Input/output error

Once I killed the cp and tried to unmount the drive (no activity on it at this point), it took over a minute to finally unmount. I didn't try force, not yet anyway, I just let umount run it's course and it finally worked.

I have not tried a raw copy, like ddrescue, yet. Not sure if that would do any better. I was hoping to avoid a 1Tb raw copy when his whole computer - OS, apps and user data - is only using 75Gb. And most of that he doesn't care about. Just the pictures really. I haven't tried something like photorec either, since the directory structure on the disk, at least the parts I have seen, looks OK. I can go into and out of his directories, list files etc., and that all works fine. I just can't seem to pull those files off, after listing them.

Oh no ... I just now powered down the drive, then reconnected it, and now it's not even showing anything in dmesg, so I can't mount it or run smartctl on it.

Oh well, I guess it's dead.

kilgoretrout · 04-27-2017, 03:46 PM

You can try the freezer trick on it:

https://www.pcmech.com/forum/threads.../#post-1078281

BW-userx · 04-27-2017, 08:36 PM

Quote:

Originally Posted by haertig

I am trying to pull data off of a friend's hard drive. Looks like a hardware error. I pulled the drive out of his Windows 10 box (failed to boot there). Put it into an external enclosure and I'm now trying to pull data off it attached via USB3 to my Linux box. When I attempted to mount it, it complained that the drive was "hibernated" and refused to mount it, so I then mounted it read-only, and that worked.

if that is a windows OS no longer in a computer to boot it?
if you can what I do with my dual boot - go into power setting advance and turn off everything that even looks like hibernate, the do a complete shut down --

I read it is because when it is in Hibernate something about their are files do not get closed properly, to be accessed in that state, so Linux will not allow it to be access so it not damage files due to that state windows was left in.

haertig · 04-27-2017, 10:02 PM

Quote:

Originally Posted by BW-userx

if that is a windows OS no longer in a computer to boot it?

The disk WAS in a Windows computer, but would not boot. Usually nothing but black screen attempting to boot (after you saw the POST messages go by). One time there was a screen saying bad things were happening (before boot). I can't remember the wording because it was only once, and went to black screen before I could read it. I was able to get into BIOS, and the disk was recognized there. It was non-bootable for several attempts, so we gave up and I took the HDD out of my friends computer and tried to do with it what I could over at my house. Which didn't amount to much.

BW-userx · 04-28-2017, 09:36 AM

You're I take it using Linux to try and do this. I wonder if you plug it in to another windows PC as an external it'd accept it?

If it does then you have to play with the Windows permissions to over take it as Admin. like Linux Root gets everything.