Re: [Bug-ddrescue] Strange behaviour at the endof the rescue

[Antonio Diaz Diaz]

David Morrison wrote:
> There are still a lot of files that are damaged on the copy. Sometimes 
> they will not open because the application has detected problems in the 
> data structure, eg, some JPEG files. Other times they open, but contain 
> random data. For example, text files do this.

I have checked the code again and I can assure you that if you are not 
using sparse writes and ddrescue states in the logfile that the whole 
disc has been succesfully recovered, the destination file is an exact 
copy of the data returned by the system library functions.

If the files in the copy are corrupt it means that they were already 
corrupt in the source drive, that the drive is returning bogus data, or 
(very unlikely) that the kernel has a bug.


> It seems odd that it has tried to read a number of blocks in the earlier 
> steps (copy, trim, split, etc) and always got an error. Then at the end, 
> it seemed to have read them all successfully. (I say "successfully", but 
> obviously some of the blocks read do not contain the correct data.)

It really sounds as if your drive or kernel were falsely reporting bad 
sectors as good.


Regards,
Antonio.