Hello there!
I need a loader for ST2000DM001 drive!
PN:9YN164-306
FW:CC4H

I use Mrt Pro tool.

History of the drive:
The drive had a FAIL Servo Op=0100 Resp=0003 errors.
Changed HSA, and after some Servo errors, the drive was identifyable, but reads LBA with many errors.
I did the following commands:

F00A2,00,22
F01E4,00,22
F057C,043C,22

then

i4,1,22

then

N1 on level 1

then

m0,6,2,,,,,22

Now the drive is post this terminal message, and stays BSY state:

Rst 0x40M
MC Internal LPC Process
Spin Up
RECOV Servo Op=0900 Resp=0005
RECOV Servo Op=0600 Resp=0005
RECOV Servo Op=0055 Resp=0005RW subfile error 2045-P1E6-
MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled... PASS
No HOST FIS-ReadyStatusFlags 0002A1A5
ASCII Diag mode

F3 T>m0,6,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max Iterations = 01, Max Certify Rewrite Retries = 000C

SIM Error 1002 LBA 0000000000090DEA FD FC351028
RW Error 00000080
DiagError 0000500D
User Partition Format Failed - Elapsed Time 0 mins 00 secs
R/W Sense 00000002, R/W Error 00000084, File Error 00001002
LBA 530D00D0530D0001, Cyl FFFFFFFF Hd FF, Phy Sec FFFF, Wedge FFFF


The heads are good, because i can read and write files on SA.

Please help!
Thanks for any help.

Hm, it seems to be a big mess now.
the drive obviously had no problem with the translator, nor smart, why did u played with them?
Can you write translator mod back from backup?

I don't know where do you guys get this 'F....,22' stuff from, but this is bullshit.

pepe

_________________
Adatmentés - Data recovery

This is easy to say. If you remember, there was a BSY issue with Seagate drives which bricked them, and these and related lines (e. g. http://www.overclock.net/t/457286/seaga ... h-pics/180 ) made the rounds real quickly. (w/o people understanding WHAT they're doing )
Oh, and these "solutions" are often mistaken as "one-line-to-cure-'em-all" recipes, and that's the reason why even sensitive areas get amateurishly redone or reformatted that have ABSOLUTELY nothing to do with a particular problem.

What about quoting yourself:

Nothing to add to that.

Hi there!
I know this is not a 7200.11 drive, and on Grenada drives the m0,6,2,,,,,22 command always solved the No Host Fis error (like i seen on ACE Lab video posted by jermy), but now something goes wrong with translator module while the drive tried to write it. I think, the drive has some damage on SA. The biggest problem is, i don't have a backup of modules.

you said, it read LBA after MHA replacement, which means the translator was ok.
IMO the very first thing should be backing up the most critical SA resources, they might come handy sometimes.

_________________
Adatmentés - Data recovery

Yes pepe, you are right.
I'm fool cause i skipped this very important step.
Now i have to "visszalapátolni a szart"

yes, 'innen szép nyerni'

pepe

_________________
Adatmentés - Data recovery

Thanks pepe....

So i'm still looking for loader, thanks for any help!

how will a loader help you in this situation?

_________________
Adatmentés - Data recovery

Ohhh....i have an idea!

i was sure about that

_________________
Adatmentés - Data recovery

I have copy of p-list, NRG-list, and translator system files from copy0.
I cannot write the FC351028 / 28h translator system file to copy1 (Sector593171 -593426 Failed to write). So the damaged SA cause that the translator is not loaded.

hello,

these copies are from after messing with the 'm' command i guess, aren't they?

_________________
Adatmentés - Data recovery

Yes, but i think it is not matters, because the p-list and NRG-list is not changed (i can create a new translator sys file on a donor drive using p-list), and the drive failed to wrote the new translator on copy1.
Now the drive can't read copy1 of translator sys file, and this cause the "No HOST FIS-ReadyStatusFlags" error.
I tested several sys files on copy1, and i seen so many read errors (but not all reading attempts finished with error).
If i can change the sys file 28 location in sys file map to a healthy sector, maybe the drive could be read translator again...

you can't simply rebuild translator on a donor because geometry is different, have you ever tried it?

_________________
Adatmentés - Data recovery