Re: [Bug-ddrescue] Algorithm of skipping bad blocks is not fully described in the 'info' file

[Antonio Diaz Diaz]

Hello Alexander.

Alexander Sashnov wrote:
> I have found it tryes to read small block inside bad area instead of 
> going to a next cluster.

The --cluster-size is just a measure of how many sectors to copy at a 
time. Ddrescue does not divide the drive into "clusters".


> Other problem here is log file blow up. Instead of 3 records after first 
> --no-split pass:
>
> cluster_0   cluster_2  +
> cluster_3   cluster_5  *
> cluster_6   cluster_7  +

This is not the expected logfile after a --no-split run.


> This is serios problem for me. I am trying to rescue data from a 1Tb HDD 
> with strange
> defect: it have everywhere ~700Mb readable and unreadable areas.

Have you tried to increase --skip-size to, say, 700MB?


> instead of:
> ...
> mb_offset_0     mb_offset_700    +
> mb_offset_700   mb_offset_1200   *
> mb_offset_1200  mb_offset_1800   +
> mb_offset_1800  mb_offset_2400   *
> ...

Ddrescue would need really good AI to produce a logfile like this. :-)


Regards,
Antonio.