I am trying to retrieve data from a 1 Terabyte internal hard disk using 'ddrescue'. I give below the info that I got after approximately nine (9) hours of running of 'ddrescue'.

GNU ddrescue 1.22
ipos: 131134 MB, non-trimmed: 3760 kB, current rate: 0 B/s
ipos: 131131 MB, non-trimmed: 0 B, current rate: 0 B/s
opos: 131131 MB, non-scraped: 4064 kB, average rate: 28557 kB/s
non-tried: 0 B, bad-sector: 412160 B, error rate: 256 B/s
rescued: 1000 GB, bad areas: 23, run time: 9h 43m 44s
pct rescued: 99.99%, read errors: 883, remaining time: n/a
time since last successful read: 1h 51m 45s
Scraping failed blocks... (forwards)

This 'Scraping failed blocks... (forwards) is shown for the past two hours approximately. Can I rest assured that the data was retrieved and I can stop 'ddrescue' by running CTRL-c or CTRL-d ?

At the time of that report, ddrescue has successfully rescued 99.99% of the disk, has isolated 23 bad areas which might still contain some recoverable sectors, and is trying to recover more. That is typically a very slow process because the drive can spend quite a long time (seconds, not milliseconds) attempting to read a bad sector. You can look at the mapfile and see what parts of the disk are still unrecovered.

You can stop ddrescue at any time and see if anything important is still missing from the recovered image. Do mount that image read-only so that its current state is preserved should you wish to continue. You can always continue the ddrescue operation from the state last recorded in its mapfile.

1 members found this post helpful.