still not the end of the world
upload a pic. from the front label

Ok,
It might be that the initial factory ROM was masked on MCU and that would match the stored copy on SA. Then a ROM chip is applyed with updated version and the copy on SA might still be the "old" initial one, so there is the chance that if you get ROM from platters the copy will not be the same as used on ROM chip (updated) and so it might not match module 11. It would make sense. I never attempted to do this on drives with external chip. What i've already done was to write the contents of the external rom to internal masked MCU ROM space and it worked, but unless you have a way to know for sure what version of module 11 you are using and unless you get a ROM code that match that version and you patch the other ROM modules to it you might have some trouble with getting this to work as well.

For now i would try to backup all the modules on both patient and donor. I would write translator from patient to donor and attempt again the HOT SWAP. This time with donor drive already booting patient translator. See if it clones at all.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Maybe i have a backup of the first time putting the disk in...
but i'm not sure. - and it also initilaize as a 18GB drive, but i think i have done the backup...

the only thing for getting the disk up normally is pressing "Spin UP"
spin up OK, but after that i can not load ldr and so on

autodetect always showing the empty FW with demo serial... of course.

SA dir reading tries a few times to start, but it's same...

picture is attached.

Ok, if you plug the donor, place it to sleep, swap pcb to the patient, wake it up. You should be able to read patient modules.

Then place PCB back to original drive, backup firmware of donor/original drive and write to it module 31 that you have read from patient.

Power it off. Powr it on, put it to sleep, swap pcb to damaged drive, wake it up. Try to clone.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

yeah... that was everything... i can directly access data... - not really neccessary to clone.

i don't know why they (ACE support) did not told this to me...

MANY MANY MANY Thx...

after translator was written - nearly everything is fine for reading... some bad sectors but its OK.

It can be so easy - but i did not got such a case, and because i could see the mainfolders, i thoght it's not neccessary to change something else, thought weak heads or something...

Just ask the Oracle

Nice !!!!

Happy that i could be of some help !!!

I'm getting the feeling that i'm improving allot as well and getting good at this.

I think that i know why the rom regen fails with drives with external rom as well. But of course it might still be a simple "fix" if you can read overlay - mod 11 and check version, get ROM compatible with it on database and patch the adaptives assuming they can be retrieved from SA, etc ...

In any case the important is that you can now get the data out of the drive !!!

Please do ask if you have further questions.

Regards and happy learning !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

congrats

Yeah - learning DR will take some years, i'm not new on computers and servers, but i'm new on DR...
Just recovered about 30 disks... but such a thing till today i did not.

Thx

If you want to understand better why this happened please read the article that i've just wrote :

Understanding translator "shifts" :

This will exemplify a "shift" on a translator for just 2 sectors that renders the user data almost inacessible (and RAW recovery provides very poor results as well). Now imagine what would do a "shift" of multiple sectors in multiple directions (on my case i've just added 2 sectors to the P-List but on a completly different translator like yours you also have sectors that are removed as both translators will be completly different).

Hope this helps to clarify why it is necessary to be aware of the defect lists and translator of patient drive when attempting a recovery, because those defect lists are EXCLUSIVE to the drive and without them correctly placing the sectors on the correct order to match LBA (Logic Block Adressing) to internal PBA (Physical Block Adressing) your data will be ... a mess

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

For me the word "Shift" was enough, i also can not set a piece of a puzzle 2 pieces more left, it won't match

Yeah, but you might want to learn about this to use virtual translators and for example to understand and deal with the problem of the non-resident g list on all modern seagate drives !
Regards and have a nice day.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.