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:
On Sat, Jan 9, 2010 at 11:10 AM, Stroller <strol...@stellar.eclipse.co.uk
> wrote:
On 9 Jan 2010, at 09:23, Neil Bothwick wrote:
On Sat, 9 Jan 2010 07:20:18 +0000, Valmor de Almeida wrote:
Sometimes the "current rate" reads 0 B/s for a long time... and "time
from last successful read" can be 8m.
Would any one know whether this is normal?
Doesn't ddrescue retry on blocks it cannot read? That would explain
the
variable read rate, even the period of zero activity. If your drive is
that badly damaged, dd would have been no use anyway.
I think Valmor is using GNU ddrescue, with which one makes the
multiple passes manually. The "-n" flag on the command line that
Valmor posted (`ddrescue -n /dev/sda /dev/sdc rescued.log`) relates
to the examples given in the GNU manual page [1]. I believe that GNU
ddrescue is the better version - it was inspired by garloff's
original work, and makes improvements, but it operates differently.
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)"
# 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
