Hello,
Drive in topic was dropped and after replacing heads it takes some time to get ready with full model, capacity, SN and FW but no user area access.
SA checked and there's bad sectors in critical tracks (Translator 31, P-List 33 and S.M.A.R.T).
I have managed to get full backup by tracks (composite reading).
MRT not supported module redirection with this FBlite.

Any suggestions?

Thanks in advance.

Test a non important module to write to...if its write, you can write back the read ones thats were bad...try one head at the time.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Already tried this, sir.
Heads are perfectly reading and writing. Tried to write to module then re-read to see the changes and it already write.
Thanks for trying to help. I appreciated

Ok, so you can write modules back...and confirmed they write good?
And you know that you got the critical modules to 100% when you read them?

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Yes.
Yes by both ID and composite by tracks. 31 and 33 backed up with 3 bad sectors in tracks 255 and 256.
I see that almost every track has the same bad sectors in the same location ( sectors 972,1154, 1155 and 1156 )
The drive was dropped, I believe it's scratches to the surface because of the defective heads. I'm sure that the customer tried to power on the drive several times.

Go to sector edit and check different location to reach different Lba's.
If not reached any lba and you got 100% of p-list, then try to regenerate translator.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

No user area access.
I will try and post the results.
I remember I had a similar case that I figured out to access user area, but I can not remember what I have done to solve the issue.

Always document your findings and what you do, memory can a pain sometimes.

_________________
Data Recovery in the Dominican Republic
https://www.recuperamidata.com/

Agree.
But sometimes for hard cases when I try several methods to workaround the problem and figure out to access the user data, the only thing I think of, is to hurry to take an image then I forget all I have done to solve the issue.

ohh yes i have been there.

_________________
Data Recovery in the Dominican Republic
https://www.recuperamidata.com/

Have you tried to record the translator selecting by RAM and try to see if you have access through the sector viewer?

_________________
Is Earth an intelligent being?

I have a HDD just like yours. I have broken the mod 0x31 and then after several attempts I have managed to record in RAM and I have access. I do not know if it will work for your particular case.

_________________
Is Earth an intelligent being?

Can you upload modules 01, 31 and 33? I believe that most modules have 4 copies.

_________________
A backup a day keeps DR away.

The problem is not with modules. The problem is with scratches to the surface ( too many bad sectors in SA in several positions)
Also hot swap is not working with this family.

Thanks for your inputs.

Have you checked if the mod 0x31 in RAM matches the one you have saved?
A greeting.

_________________
Is Earth an intelligent being?

ISTM that all the bad sectors are in the zero-filled area at the end of each module. Therefore modules 31h and 33h should be easy to repair. I was wrong about the number of copies, though -- there are 2, not 4.


As for module redirection, I think it might be possible to do this manually, if necessary.

Would the drive still operate correctly if you were to truncate the sizes of modules 31h and 33h? You would need to edit the corresponding directory records in module 01h as well.

_________________
A backup a day keeps DR away.

Can you corroborate something?
If I turn on the HDD and it has bad 0x33 and 0x31, it starts but does not have access, but if we load the 0x31 in RAM when I want to read sectors I already have access, because the firmware no longer reads these modules from the SA and works with the copy in RAM. Then I do not care as this 0x33 if I have the 0x31 well.

_________________
Is Earth an intelligent being?

Too many modules loaded to RAM are gives errors ( 33,31..etc)


I know that the damaged sectors are in zero filled sectors. But MRT neither relocate or downsize modules.
Also I have checked several tracks to relocate translator and P-list, but almost all tracks have bad sectors in the same place (0,1)
Sectors (972,1154,1155 and 1156) are damaged in all critical tracks.
Thanks for trying to help

Try this if you want.
Boot the disk in kernel mode to free memory from RAM.
Read the module 0x11. You must read 0x01 from the disk.
Select read / write RAM.
You must let the translator write in RAM. And if the translator is fine, you should have access.

It's just a suggestion.

I'm going to break the module 0x01 to also do the test.

_________________
Is Earth an intelligent being?

Would you be interested in testing my ideas? If yes, then could you upload your 01, 31 and 33 modules?

_________________
A backup a day keeps DR away.