Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

ST31000524AS terminal error translator table damage

November 26th, 2021, 1:48

Hello,
I have a hard disk ST31000524AS 7200.12 with JC4B firmware, it has too slow problem. without knowing i apply 7200.11 translator regeneration command and clear smart command. after that i apply sys 93 files command like disable media cache and other command. now hdd in partial sector problem. please guide me how to solve problem? sorting pins with twizzer, sim error 2044 and No HOST FIS-ReadyStatusFlags 2002A185 Error coming. please help me to short out my problem. attach images for your refference. i havn't expensive tools like PC3000 or MRT.
Attachments
WhatsApp Image 2021-11-24 at 3.58.36 PM.jpeg
22.jpg
11.jpg

Re: ST31000524AS terminal error translator table damage

November 26th, 2021, 3:08

This happened because your drive's NRG list was not empty. The translator has been recalculated without taking into account those entries.
Now you will have to re-create the translator manually.
To do this, you will have to find the first unreadable sector and add it to defect list, then regenerate the translator and then again and again.

Alternatively, you can contact member Amarbir who is from your country and is able to handle this.

Re: ST31000524AS terminal error translator table damage

November 26th, 2021, 7:03

Case Solved.

I copy sys file 35 from same model and same firware healty hdd and write to faulty hdd. regenerate translator....and quick scan with r studio and partition found and data extract.
Thank you Northwind to reply my post.

Re: ST31000524AS terminal error translator table damage

November 26th, 2021, 9:57

I copy sys file 35 from same model and same firware healty hdd and write to faulty hdd. regenerate translator....and quick scan with r studio and partition found and data extract.


The above cannot be considered as a solution, coz 35 is unique if it has entries. In your case it was probably empty and the new one was empty as well.
And the reason the translator got screwed up comes from a different mistake.
There's a long way ahead of you to become a dr man, experimenting on client drives is not a very good habbit, at least without knowing what you are doing and without the ability to revert to the initial state.

pepe
Post a reply