Here's what I had to do in a similar situation - in case someone stumbles upon this question like I did. # Command line: ddrescue -direct -retrim -max-retries=3 /dev/sdb1 /media/jump1/1recover/sdb1.img /media/jump1/1recover/ It looks like, from where I'm standing it worked perfectly. Opos: 1536 B, time from last successful read: 3.7 mĠ.00user 0.00system 3:43.56elapsed 0%CPU (0avgtext+0avgdata 4944maxresident)kĨinputs+0outputs (0major+376minor)pagefaults 0swaps Ipos: 1536 B, errors: 1, average rate: 0 B/s Opos: 1536 B, time from last successful read: 1.3 mĠ.00user 0.00system 3:43.95elapsed 0%CPU (0avgtext+0avgdata 4944maxresident)kĢ38inputs+0outputs (3major+374minor)pagefaults 0swaps Ipos: 1536 B, errors: 1, average rate: 13 B/s Rescued: 160039 MB, errsize: 1024 B, current rate: 0 B/s Opos: 3584 B, time from last successful read: 0 sġ2.78user 1060.42system 1:56:41elapsed 15%CPU (0avgtext+0avgdata 4944maxresident)kģ12580958inputs+0outputs (1major+601minor)pagefaults 0swaps Sudo time ddrescue -direct -retrim -max-retries=3 $src $dst $logĮverything looked like it came off without a hitch: ~ $ sudo bash recover1 Sudo time ddrescue -direct -max-retries=3 $src $dst $log Sudo time ddrescue -no-split $src $dst $log

I changed the destination to the external USB drive. I used this script to create an image of the broken hard drive.

sdc - 1T external, contains recovery image.

sdb - 160g internal, BROKEN, contains about 140g of data I'd like.

sda - 160g internal, holds all system files and all computer.

Partition table entries are not in disk orderĭisk /dev/sdb: 160.0 GB, 160041885696 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Wouldn't even load a Live session with the disk installed. The laptop was jarred and the /home disk was broken.

One has the dual boot Win7 / Linux Mint system files. I'm clueless, I'd appreciate if someone had some input for me. I've outlined what I've done so far below. I'm not sure what I'm doing wrong or if I started this process incorrectly from the beginning. media/jump1/1recover/sdb1.img: ~ $ mmls /media/jump1/1recover/sdb1.img It doesn't even give me detailed information on the file I just made, nautilus says it's 160gb. Mount: you must specify the filesystem type Mount: you must specify the filesystem ~ $ sudo mount /media/jump1/1recover/sdb1.img mnt In some cases useful info is found in syslog - tryĭmesg | tail or ~ $ sudo mount -r -o loop /media/jump1/1recover/sdb1.img recover Missing codepage or helper program, or other error Mount: wrong fs type, bad option, bad superblock on /dev/loop0, ~ $ sudo mount -t ext4 /media/jump1/1recover/sdb1.img /mnt I've tried to mount the image multiple ways. I'm having problems mounting the recovery image.

Ddrescue gui windows