Re: [Bug-ddrescue] Bad sectors initially marked as non-trimmed

[Antonio Diaz Diaz]

Hello Scott.

Scott Dwyer wrote:
> I have a drive that has many single sector errors (think the head flew 
> across during a write). So after figuring that out, I used the -d -c1 
> options in ddrescue to read sector by sector so as not to have to come 
> back again. But to my surprise, the rescue log is showing 512 byte 
> blocks as non-trimmed. How can that be? That is the default sector size, 
> so it cannot be trimmed. Please explain this action by ddrescue.

Thanks for reporting this.

Ddrescue does not (yet) treat the -c1 case specially, so it marks the 
failed blocks as non-trimmed, even if the "failed block" contains only 
one sector.

I'll add code to ddrescue so that it marks the failed sector as 
bad-sector in this case.


> I am using ddrescue 1.16 x64 on this, and the recovery is about 15% done 
> after 3 days, so it will take about 20 days to finish. But I am worried 
> that ddrescue will try to read all those "non-trimmed" areas again, and 
> add a bunch more time.

As a workaround, you can stop ddrescue when it begins trimming and edit 
the logfile to mark as bad-sector all the non-trimmed areas with a size 
of 0x00000200.


Best regards,
Antonio.