This is not a bug, but I'm new to ddrescue and am trying to recover data from a 250GB WD2500JD-75GBB0. I am using ddrescue to save an image file to an already ntfs partitioned 750GB drive with plenty of free space. I believe my drive may be going offline after reading some bad sectors. Or maybe i am doing something wrong. I identified the partitions using: sudo lshw -C disk -short cat /proc/partitions
Then used the following to run ddrescue: sudo mkdir mnt sudo mount /dev/sda1 mnt cd mnt sudo mkdir recovery cd recovery sudo ddrescue -r 3 /dev/sdb image log Press Ctrl-C to interrupt Initial status (read from logfile) rescued: 0 B, errsize: 0 B, errors: 0 Current status rescued: 547581 kB, errsize: 249 GB, current rate: 0 B/s ipos: 10404 MB, errors: 21, average rate: 4131 B/s opos: 10404 MB, time from last successful read: 1.2 d Retrying bad sectors... Retry 3 Interrupted by user Restarting ddrescue produces the same result as above. The drive is still apparent with:sudo lshw -C disk -short & cat /proc/partitions, but sudo fdisk -l correctly shows my 750 GB drive/partition but has: Error: /dev/sdb: unrecognised disk label I power cycled and was able to read using -d -r 1 -c 10 --initial--position=30GB. It read ~3GB then had 0 successful reads for an hour before i interupted. if i change the start position it will read some data then stop. Is there a something different i should be trying? any advice is appreciated. Any suggestions -- View this message in context: http://old.nabble.com/ddrescue%2C-hard-drive-stops-succesfully-reading-after-547MB-tp31047351p31047351.html Sent from the Gnu - ddrescue mailing list archive at Nabble.com. _______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
