Blocks are read manually and not selected chains

[jojo2012]

Hi Guys,
I am reading as many sectors as I can from a Rosewood and have now only yellow and red blocks.
By increasing the timeouts (PIO mode) and the number of retries the red blocks are read manually (i.e. lba by lba) but not by selecting the chains of these blocks.
It is obvious that I cannot manually read the 428MB sectors one by one.

I cannot understand why I have this problem.

Thanks for any help

[SGdata]

Those read sectors are good or have m.o.l.d.?

[jojo2012]

Those read sectors are good or have m.o.l.d.?

sorry m.o.l.d?

[SGdata]

Yes, sometimes when Rosewoods are not reading good and you set long timeouts it reads garbage. It's recognized by m.o.l.d in first line of read sector.

[d_d_recovery]

Its caused by corrupted secondary translator bands. Occasionally a head swap can help.

[jojo2012]

Yes, sometimes when Rosewoods are not reading good and you set long timeouts it reads garbage. It's recognized by m.o.l.d in first line of read sector.

This i.e. m.o.l.d. has never happened to me, and in any case the read sectors are OK.
Maybe I have not explained myself well.

I select the map with the red blocks. I go to read them manually one by one and it reads them.
If I select all chains it refuses to read them. I have attached some screenshots.

[jojo2012]

Source of the post Yes, sometimes when Rosewoods are not reading good and you set long timeouts it reads garbage. It's recognized by m.o.l.d in first line of read sector.

You're right by increasing the retries or the timeout to 2000 I get the sectors with m.o.l.d in the header.

About reading the red sectors merged in the map and rejected when I selected the relevant chains, I solved this with change legend.
Unfortunately I am still getting a few red sectors and these sound files must be perfect for a professional SW in the field.

[osity]

jojo2012, How did you end up resolving your m.o.l.d issue?

[300ddr]

You can try different heads, but [I think] often these sectors are not repairable.

[Freakazoid]

I see this post is old but i have a question? did you enable Skip sectors at loss of readiness? if yes take them of....

[osity]

Freakzazoid, Did you see an improvement when you unchecked those two?

[Freakazoid]

Yes. i did imag the drive with Skip sectors at loss of readiness active and got a lot of Skip sectors at loss of readiness.... then when it was finish reading i turn it of and reread and now it read most of those sectors...

[jojo2012]

Source of the post I see this post is old but i have a question? did you enable Skip sectors at loss of readiness? if yes take them of....

Yes I removed that flag.
Now I know that in the case of a cloning that has already been done and that has those sectors there is a tool that identifies those "moldy" sectors so that you can do a second pass

[jojo2012]

Source of the post jojo2012, How did you end up resolving your m.o.l.d issue?

Unfortunately I had to check all the files with that header and read the red blocks manually. The maps were messed up.

[Freakazoid]

Source of the post

Source of the post jojo2012, How did you end up solving your m.o.l.d problem?

Unfortunately I had to check all the files with that header and read the red blocks manually. The maps were messy.

It happened to me too now.. a seagate... a lot of red that I also had to read manually