I've had drives with similar issues as this, but never this specific error. Originally the drive had no access at all, it was a continuous BSY state and did not show up in the BIOS. This is what the Terminal output looked like:

Rst 0x40M
RW: Disc Ctlr Initialization Completed.

(P) SATA Reset

SIM Error 1009
RW Error 00000080

Then below that, it had something to the effect, Hi Temp or exceeded maximum temperature, something like that. I should have done a screen cap, but I was pretty sure it was PCB related.

I swapped the PCB and ROM, and the drive was able to be fully recognized, and become ready but it would time out on every sector.

Back in Terminal I get the same thing still:

Rst 0x40M
RW: Disc Ctlr Initialization Completed.

(P) SATA Reset

SIM Error 1009
RW Error 00000080

But that's it, it just hangs there and doesn't go any further, and the temperature error is no longer present. Again, this drive is now recognized by every computer that it is connected to, and in DDI it gives you the full model and LBA count, but you just have no ability to read any sectors. Kind of like a translator issue on a WD.

Any ideas on this? Please feel free to PM. There's not much information out there with this specific issue. Thanks.

Hi,

Have you checked defect lists?
Tried to clear smart or translator regen?

I cleared SMART.

I sent a PM.

i have 4 disk that have same problem..

How can i repair it? is there any command or method except

"http://www.dolphindatalab.com/one-click-to-fix-seagate-sim-error-1009-by-dfl-ddp/"

or how can i repair or change 17a and 133 sys file?

http://ts.acelaboratory.com/index.php?/ ... a-sys-file

Could Sediv or Seagate Tools help us?

Did you try to read the two sys files using the F3 terminal commands in the Ace Lab tutorial?

_________________
A backup a day keeps DR away.

How could it be?

i check 17a sys file via "F3 T>r17a"

then i get "DiagError 0000000E" message

obviously r17a file was corrupted.

is there any command for read or write this file?

the solution is here
http://ts.acelaboratory.com/index.php?/ ... a-sys-file

we know that..

but i don't know how program or command solve this issue without any payment.

this is logical error.

sorry my friend
on this planet everything except for air and rocks is gonna cost you

is this for reason Englishman want to say "cost of earth" instead of very expensive.

it is a easy problem. we don't pay to everything.... i.e. training.

r-read
w- write

i read some files from proper same model hard drive. with " r17A" "r133" "r28" "r35"

and after "w" it. w17A, .......

i use Hyperterminal's Y-modem..


http://forum.ru-board.com/topic.cgi?for ... start=1180

if the file is greater than 1 mb USB driver could halt and you'll see blue screen and restart.
You must use USB-TTL adapter.
DKU-5 cable is inefficient.

Thanks..

and you can see, correct, modify this binary files with some Hex Editor programs.
i.e Hex Editor Neo

FYI, not all F3 drives support these commands, mainly the older ones (Moose, Brinks, Wyatt, Holliday perhaps some others as well).

pepe

_________________
Adatmentés - Data recovery