So I'm about a week and a half into a
ddrescue operation. The failing external hard drive is 2TB, with about 1.8TB of data, mostly photos. Here's what
ddrescue is reporting at the moment, still in progress:
> sudo ddrescue -n -v -c 1Ki /dev/disk2s1 /Volumes/ExtraExternalHardDrive/recovered.img ddrescuelog.log About to copy an unknown number of Bytes from /dev/disk2s1 to /Volumes/ExtraExternalHardDrive/recovered.img. Starting positions: infile = 0 B, outfile = 0 B Copy block size: 1024 sectors Initial skip size: 128 sectors Sector size: 512 Bytes Press Ctrl-C to interrupt Initial status (read from mapfile) rescued: 1937 GB, errsize: 0 B, errors: 0 Current status ipos: 1998 GB, non-trimmed: 297795 kB, current rate: 524 kB/s opos: 1998 GB, non-scraped: 0 B, average rate: 8045 kB/s non-tried: 9223 PB, errsize: 0 B, run time: 2h 3m 16s rescued: 1997 GB, errors: 0, remaining time: n/a percent rescued: 0.00% time since last successful read: 0s Copying non-tried blocks... Pass 1 (forwards)
Ok – so my question is: if I have 1.8TB of data on the failing drive, why do I now have 1.98TB of data in the recovery image file? And… how much longer is this thing going to go?
I've stopped the process multiple times during this effort, using the mapfile to restart each time.