Seagate translator issues Topic is solved

[Deuterium]

We have a Seagate ST1500DL003-9VT16L come into us, it has been messed with by a computer shop we think...the HDD spins up and comes ready OK, all mods and sys files, backed up ok, but no access to user data past 70,000LBA, but can read all sectors with utility, the translator recover is very slow, like 1 second per sector, every sector, looks like the Translator has been regenerated with taking into account NRG, any ideas, tricks or tips to take case forward?

Thanks!

[Filipp_TS]

How to manually deal with Translator you can read in these articles:
http://blog.acelab.eu.com/translato ... fects.html
http://blog.acelab.eu.com/pc-3000-h ... edure.html
http://blog.acelab.eu.com/pc-3000-f ... fects.html
or welcome to Technical support dept.: http://ts.acelab.eu.com/

[Amarbir[CDR-Labs]]

Source of the post We have a Seagate ST1500DL003-9VT16L come into us, it has been messed with by a computer shop we think...the HDD spins up and comes ready OK, all mods and sys files, backed up ok, but no access to user data past 70,000LBA, but can read all sectors with utility, the translator recover is very slow, like 1 second per sector, every sector, looks like the Translator has been regenerated with taking into account NRG, any ideas, tricks or tips to take case forward?

Thanks!

Well,
i have asked this several times no answer ,How do you take into account nrg list and recalculate/regenerate translator so that we do not have a partial access issue

[AJ2008]

read 3_028_0, regen translator, write 3_028_0 back to 2B module - this works in many cases.

m0,6,3 - this command should regen translator while preserving (and including) NRG entries

Translator recovery can help to automate restoration of NRG entries. IN the event it tells you to correct manually, there are steps in guides Filipp posted that can help (including guide to deal with 'invisible' or invalid NRG defects).

I see often cases that arrive following attempts to recover from other company who rebuild translator without concerns for NRG defects. I also see some cases with NRG list shows many entries with 0x20 flag which suggests some prior attempt to regen or repair (generally native flags should show 0x0)

Otherwise, raise ticket with Ace TS who can remotely solve for you

[Amarbir[CDR-Labs]]

Source of the post read 3_028_0, regen translator, write 3_028_0 back to 2B module - this works in many cases.

m0,6,3 - this command should regen translator while preserving (and including) NRG entries

Translator recovery can help to automate restoration of NRG entries. IN the event it tells you to correct manually, there are steps in guides Filipp posted that can help (including guide to deal with 'invisible' or invalid NRG defects).

I see often cases that arrive following attempts to recover from other company who rebuild translator without concerns for NRG defects. I also see some cases with NRG list shows many entries with 0x20 flag which suggests some prior attempt to regen or repair (generally native flags should show 0x0)

Otherwise, raise ticket with Ace TS who can remotely solve for you

Thanks AJ ,
I am extremely happy that you replied to this and my question was finally answered after several years/months really .m0,6,3 command i never tried but next time i will try .I was thinking of doing this few times never did and almost every time solved the translator issue automatically and few times filipp also solved it ,but the one he did was too good case