Translator problems

[avalanche]

Hello,

I have been working on a WD2500JS. It has bad sectors in the SA. I was able to hotswap, read most of the SA, set up a task in DE and start imaging. It took several days image but it was possible to get nearly a 100% clone. However, before cloning I did not transfer module 31 (Translator) or 36 (T-List) from patient to donor. This meant that the catalog (HFS+) would not rebuild correctly. If I scan for structures it finds the inode entries and creates a folder/file name structure, but of course they point to the wrong LBA so all files are corrupt! It has been a long time since I worked in a WD2500JS series and I don't ever remember having to transfer module 31 previously!

I have now corrected the SA of the donor for hotswap to use patient mod 31 and 36 and it is possible to get working translator with correct catalog / HFS+ filesystem and working data. However, I now have to image the entire HDD again. I want to avoid this if possible as it took a very long time on the first occasion and the drive was unstable.

Does anyone know of a method to take the existing disk image, created using the donor translator module, and some how manipulate this for use to get working data. Or am I going to have to image the entire HDD again now with correct translator in SA?

Best regards,
J

[avalanche]

I ended up re-imaging the HDD with correct translator. Heads are stable so just patience required.

[Amarbir[CDR-Labs]]

Source of the post I ended up re-imaging the HDD with correct translator. Heads are stable so just patience required.

Hi,
its been a while i came here you did good this was the only way to solve this issue ,Great work and good patience boss