Seagate Barracuda 2TB, not recognized, recovery terminal stu

[jeena256]

Hello everyone,

I have a 2000GB Seagate Barracuda HDD, that suddenly stops working. I try to repair it with terminal and USB->TTL connection, but the terminal always stuck on SATA Reset.
Then I try to find another board with same ID and REV, swapped bios chip, but the problem persists. If I Put the bios chip from donor HDD to Board from faulty HDD and this combination insert into donor HDD, the donor HDD works, so error is not in board, but deffinitively in bios chip. What can I do? I included log from terminal and images, the drive on the left is the bad drive.

Thanks for any suggestions and sorry for my bad english.

Images:






Log from some attemps in terminal:

Boot 0x40M
Spin Up[LBA=0x000042F9]N01010C10o0o0o0o0o0o0o
Trans.

Spin Up
SpinOK
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

Boot 0x40M
Spin Up[LBA=0x000042F9]N01010C10o0o0o0o0o0o0o0o0[LBA=0x000042F9]NO11
Trans.

Spin Up
SpinOK
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

Boot 0x40M
Spin Up[LBA=0x000042F9]N01010C10o0o0o0o0o0o0o0o0
Trans.

Spin Up
SpinOK
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

Boot 0x40M
Spin Up[LBA=0x000042F9]N0
Trans.

Spin Up
SpinOK
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

Boot 0x40M
Spin Up[LBA=0x000042F9]N01010C10o0o0o0o0o0o0o0o0
Trans.

[northwind]

so error is not in board, but deffinitively in bios chip.

Nope.
Is the data important?
If yes, stop what you're doing and consult a pro. It shouldn't be expensive at this point.
If not, then you need to at least work with sysfile 93. Search this forum for that.

[jeena256]

Hello, thanks for your reply.
All data on drive I have backed up, but I want to determine, what’s happend to the drive? I want to learn something new. Drive is still spinning and sounds like it is normally working, but it can’t be seen in bios and the terminal stuck, everytime...

[northwind]

OK

If you don't care about the data, then you need to gain access to SMP (file 93). To do this, you could perhaps short the read channel and gain access to terminal. You can search the forum for additional info, it has been explained plenty of times.

Good luck!

[jeena256]

Yes the method with shorting read channel I tried before, it was start typing to terminal something like LED: and stuck again. So I going to try it again with a new board.

THX

[rogfanther]

You didn´t mention it :

The "faulty" board with "faulty' eeprom chip work in the donor ? Or which are the symptoms ?

[jeena256]

No, the “faulty” board with chip from donor HDD, works in donor HDD. It also works in faulty HDD, but only cca 4 gigabytes. And the symptoms is: drive can’t be seen on devices or bios, also the terminal connection does not accept any commands. Drive spins and sounds normally.

[jeena256]

When I short it, it still repeating this:

Boot 0x40M
Spin Up
Trans.
Retry delay
Retry delay
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
Retry delay
(P) SATA Reset

As stated you need to short channel in PCB to gain access to TTL prompt in order to backup and patch sysfile 93 ... Then you can try to clone the drive ...

[jeena256]

Still not works, after shorting its doing this:
I doing it just as described in tutorial on this forum, short read channel after trans message apeared.
What terminal program are you using for this?

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
Retry delay
Retry delay
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
Retry delay
(P) SATA Reset

[labtech]

You get good terminal output, so the terminal software is fine. No need to worry about that.

[jeena256]

On the donor disk it works like this, but on this, CTRL+Z does nothing:

Spin Up
SpinOK
Retry delay
SnapshotEventOccurred( SNAPSHOT_INITIAL_VALUES ).
(P) SATA Reset

ASCII Diag mode

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 11.578 secs
F3 2>U

LED:00000067 FAddr:003E2002
Rst 0x40M
Spin Up
SpinOK
LED:00000067 FAddr:003E2002
LED:00000067 FAddr:003E2002
LED:00000067 FAddr:003E2002
LED:00000067 FAddr:003E2002

[jeena256]

Am only testing funktionality of terminal on good board.
On the patient board I don´t even get reaction to CTRL + Z...
Its doing nothing, I let it ran overnight and still nothing, only SATA RESET message.

[jeena256]

Soory for confusing you.

On the patient is only diference when shorted (on Healthy drive Ive never seen this):
Boot 0x40M
Spin Up[LBA=0x000042F9]N01010C10o0o0o0o0o0o0o0o0
Trans.

And when not shorted:
Boot 0x40M
Spin Up
Trans.

And what about to use healthy board with healthy bios to get SMP 93 from patient drive? Is that a way or not?

[magnetepazzo]

I have the same problem, have you solved ?

[magnetepazzo]

I have the same problem, have you solved ?

Patch sysfile 93 and try to clone the drive ?

Send the drive to a data recovery pro (outsource) ?

Hi Spildit, thanks for reply. I have tryed to enter in T level but the disk not responding, remain in BSY. I have connected to MRT but nothing, I have try to adapt the rom with mrt adapt utility but nothing same problem. I have tryed virtual start in MRT but nothing, after upload stay in BSY. Have suggestion ?
Thanks