[Bug-ddrescue] Re: ddrescue Version 1.11

[Antonio Diaz Diaz]

Hello Arno,

Meger.Arno wrote:
> Instead I find 
> #      pos        size  status
> 0x00000000  0x00000200  -
> 0x00000200  0x00010000  *
> 0x00010200  0x1F303E00  +

Did ddrescue show something like "input file disappeared"? This could 
explain why ddrescue stopped before the trimming pass. (See example 5 in 
the manual's tutorial).


> I last tried the option -T "ddrescue -d -v -T /dev/hdd ./hdd/cf.img 
> ./hdd/cf.log" in an additional call of ddrescue.
> Now the log-files looks even more wrong:
> #      pos        size  status
> 0x00000000  0x00000200  -
> 0x00000200  0x00000200  +
> 0x00000400  0x00000200  -
> 0x00000600  0x0000FC00  *
> 0x00010200  0x1F303E00  +
>
> But the second sector (position 0x200) is definitive defect.

If the kernel reports it as a successful read, there is nothing ddrescue 
can do to verify it. This applies to all versions of ddrescue as well 
as, I suppose, to dd.

IIRC, someone already reported about usb device drivers reporting false 
positives in case of hardware errors.


> This E-Mail and any files attached are confidential and may contain privileged 
> information. If you are not the intended recipient, do not forward or disclose 
> this E-Mail, open any attachments, make any copies or save this E-Mail 
> anywhere. Please delete this E-Mail from your system and notify the sender (as 
> applicable also by phone +49 2166 266-0). Thank you very much.

Please see this reference.

  http://goldmark.org/jeff/stupid-disclaimers/

If you can't avoid your company from putting those onto your email then 
please sign up for one of the many free email providers on the net and 
use those accounts for sending questions and reporting bugs.


Regards,
Antonio.