This help? Should be plain text.
Dale
:-) :-)
Stroller wrote:
Would love to comment on this. Is it possible you could resend this
post in plain text format?
Stroller.
On 10 Jan 2010, at 02:08, Valmor de Almeida wrote:
Indeed I am using GNU ddrescue and the -n flag is supposed to
expedite the recovery of data as posted in
http://www.cgsecurity.org/wiki/Damaged_Hard_Disk
"The best solution - both faster and more efficient - seems to be
Antonio Diaz's 'ddrescue' (ddrescue
<http://savannah.gnu.org/projects/ddrescue/>)"
# first, grab most of the error-free areas in a hurry:
./ddrescue -n /dev/old_disk /dev/new_disk rescued.log
# then try to recover as much of the dicy areas as possible:
./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log
expectation, not a reasoned one. I think the best thing he can do
is hold his breath, wait until its finished and see how if the
results are readable, after running `fsck` on the mounted filesystem.
The first step above finished; don't know how long it took but it was
a long time (maybe 20 hours or more?) and the screen output was
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued: 0 B, errsize: 0 B, errors: 0
Current status
rescued: 58811 MB, errsize: 48909 kB, current rate: 83 B/s
ipos: 58860 MB, errors: 95, average rate: 1365 kB/s
opos: 58860 MB, time from last successful read: 0 s
Copying non-tried blocks...
ddrescue: write error: Input/output error
