I’ve been using ddrescue to try and recover a failing 2 TB HDD. It’s been
running for close to three weeks now and it’s still only in pass 3 of copying.
It’s recovered all but about 32 GB, and at the rate it’s going I may just be
willing to write that data off and/or regenerate it. I’d be a lot more
comfortable with that if I knew what files would be affected, though. What I
would like to do is have it just finish where it’s at and mark everything
non-tried as bad-sector, or give up a *lot* quicker, and then use fill mode to
try and figure out which files are incomplete, as described in the
documentation. Is there a way to do this?
Here’s what ddrescue currently looks like:
$ sudo ddrescue -v -f -c 512 -T 60 -R /dev/sdb1 /dev/sda2 mapfile
GNU ddrescue 1.23
About to copy 2000 GBytes from '/dev/sdb1' to '/dev/sda2'
Starting positions: infile = 0 B, outfile = 0 B
Copy block size: 512 sectors Initial skip size: 39168 sectors
Sector size: 512 Bytes
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 1968 GB, tried: 0 B, bad-sector: 0 B, bad areas: 0
Current status
ipos: 1810 GB, non-trimmed: 0 B, current rate: 1424 B/s
opos: 1810 GB, non-scraped: 0 B, average rate: 2733 B/s
non-tried: 32206 MB, bad-sector: 0 B, error rate: 0 B/s
rescued: 1968 GB, bad areas: 0, run time: 31m 58s
pct rescued: 98.38%, read errors: 0, remaining time: 88d 2h 27m
time since last successful read: 0s
Copying non-tried blocks... Pass 3 (backwards)
—
jason laughman
