Advice requested for how to continue with clone attempt.
First thanks for the post "How to Clone a Hard Drive With Bad Sectors Using ddrescue".
Now details, attempting to clone troubled 3TB WD HD with GNU ddrescue 1.25
ddrescue -f -n /dev/sdc /dev/sda recover.log (ran until power outage)
When power came back continued with:
ddrescue -f -n /dev/sdc /dev/sda recover.log
After letting it run for a while I found
Intial Status (read from mapfile)
rescued: 2349 GB, tried: 833232 kB, bad sector: 0 B, bad areas: 0
Current status
ipos: 1328 MB, non-trimmed: 1393 MB, current rate: 0 B/s
ipos: 1328 MB, non-trimmed: 1393 MB, current rate: 0 B/s
opos: 1328 MB, non-scraped: 0 B, current rate: 2148 kB/s
non-tried: 498669 MB, bad-sector: 0 B, error rate: 0 kB/s
rescued: 2500 GB, bad areas: 0, run time: 19h 28m 9s
pct rescued: 83.33%, read errors: 8580, remaining time: 17h m s
time since last successful read: 7h 44m 3s
Copying non-tried blocks... Pass 5 (forwards)
Almost 8 hours since the last successful read, that was concerning.
Even more worrying was the 'SMART Status Bad - Disk likely to fail soon' message.
ddrescuelog -t -v -v recover.log
current pos: 1328 MB, current status: copying
mapfile extent: 3000 GB, in 24487 area(s)
non-tried: 498669 MB, in 9289 area(s) ( 16.61%)
rescued: 2500 GB, in 2969 area(s) ( 83.33%)
non-trimmed: 1393 MB, in 12229 area(s) ( 0.04%)
non-scraped: 0 B, in 0 area(s) ( 0%)
bad-sector: 0 B, in 0 area(s) ( 0%)
I stopped the program here, to consider.
I assume now is the time to try -R, but I'm worried about the looming likely disk failure.
Am I wrong to think that the long last successful read time was heating up the disk,
causing the problem to worsen? So is there a way to make ddrescue pause as it works?
What should be added to the -R below?
ddrescue -f -n -R /dev/sdc /dev/sda recover.log
And assuming this works, when do I run the command without the -n?
I installed Fedora, just to try & save data from this HD. And this is my first time using ddrescue.
So please give advice for steps to continue.
First thanks for the post "How to Clone a Hard Drive With Bad Sectors Using ddrescue".
Now details, attempting to clone troubled 3TB WD HD with GNU ddrescue 1.25
ddrescue -f -n /dev/sdc /dev/sda recover.log (ran until power outage)
When power came back continued with:
ddrescue -f -n /dev/sdc /dev/sda recover.log
After letting it run for a while I found
Intial Status (read from mapfile)
rescued: 2349 GB, tried: 833232 kB, bad sector: 0 B, bad areas: 0
Current status
ipos: 1328 MB, non-trimmed: 1393 MB, current rate: 0 B/s
ipos: 1328 MB, non-trimmed: 1393 MB, current rate: 0 B/s
opos: 1328 MB, non-scraped: 0 B, current rate: 2148 kB/s
non-tried: 498669 MB, bad-sector: 0 B, error rate: 0 kB/s
rescued: 2500 GB, bad areas: 0, run time: 19h 28m 9s
pct rescued: 83.33%, read errors: 8580, remaining time: 17h m s
time since last successful read: 7h 44m 3s
Copying non-tried blocks... Pass 5 (forwards)
Almost 8 hours since the last successful read, that was concerning.
Even more worrying was the 'SMART Status Bad - Disk likely to fail soon' message.
ddrescuelog -t -v -v recover.log
current pos: 1328 MB, current status: copying
mapfile extent: 3000 GB, in 24487 area(s)
non-tried: 498669 MB, in 9289 area(s) ( 16.61%)
rescued: 2500 GB, in 2969 area(s) ( 83.33%)
non-trimmed: 1393 MB, in 12229 area(s) ( 0.04%)
non-scraped: 0 B, in 0 area(s) ( 0%)
bad-sector: 0 B, in 0 area(s) ( 0%)
I stopped the program here, to consider.
I assume now is the time to try -R, but I'm worried about the looming likely disk failure.
Am I wrong to think that the long last successful read time was heating up the disk,
causing the problem to worsen? So is there a way to make ddrescue pause as it works?
What should be added to the -R below?
ddrescue -f -n -R /dev/sdc /dev/sda recover.log
And assuming this works, when do I run the command without the -n?
I installed Fedora, just to try & save data from this HD. And this is my first time using ddrescue.
So please give advice for steps to continue.