Seagate Barracuda recovery

[terminator2]

I have following hard disk. It stays busy but is not making clicking noise nor getting spin down.
Its not coming to terminal as well. I have tried to change PCB (by swaping rom) but symptoms does not change.
Does this disk belongs to Grenada which needs to unlock (patch) first.

Family -- Seagate Barracuda 500 GB
Model :- ST500DM002
Firmware :- KC45
PCB Rev. :- 100535704 Rev . C
Can someone pls. give shorting points

Attachments

[michael chiklis]

This drive belongs to Pharaoh family.
Check terminal output, what does the log report when powering on?

[terminator2]

This drive belongs to Pharaoh family.
Check terminal output, what does the log report when powering on?

Yes Michael Sorry
This is pharaoh family . Terminal shows following --

Attachments

[Lardman]

Does it come ready and then go busy when you try to ID or is it always busy?

[terminator2]

some how I must get access to terminal first whithout which I can't do anything.

[michael chiklis]

It might be a issue with sys 346.
Can you read sys in serial mode?

If you can access to sys in binary mode, you should first backup those, expecially the most important as 1B 28 35 93

[michael chiklis]

You can try to load Virtual LDR, you can get it from sys 20D of a good donor drive.

[michael chiklis]

Check translator uploading in ram, you can do it with command V1 on level T.
If it returns any entries in slip list then it means that translators are not loaded.

In this case you can regenerate them with command m0,6,2,,,,,22 (but first you should backup sys).
If translator regeneration returns "Init SMART fail" with led CC error it would mean that smart module is corrupted.
Get sys 135 from a good donor drive and overwrite it to fix smart issue.

[michael chiklis]

CORRECTION


Check translator uploading in ram, you can do it with command V1 on level T.
If it DOESN'T return any entries in slip list then it means that translators are not loaded.

In this case you can regenerate them with command m0,6,2,,,,,22 (but first you should backup sys).
If translator regeneration returns "Init SMART fail" with led CC error it would mean that smart module is corrupted.
Get sys 135 from a good donor drive and overwrite it to fix smart issue.

[terminator2]

It might be a issue with sys 346.
Can you read sys in serial mode?

If you can access to sys in binary mode, you should first backup those, expecially the most important as 1B 28 35 93

Hi Michael
Thank you so much for most comprehensive explanation which might be useful for other newbees as well.
I will give it a try as you said and report.

[terminator2]

Does it come ready and then go busy when you try to ID or is it always busy?

No it doesn't get ready and stays busy all the time.

[terminator2]

You can try to load Virtual LDR, you can get it from sys 20D of a good donor drive.

I Think first step needed for this drive is to gain access to terminal first. I can't read sys files ,loader is also of nouse.

Terminal is giving new message now. I think head transplant is needed.

Attachments

[higgsboson]

It might be a issue with sys 346.
Can you read sys in serial mode?

If you can access to sys in binary mode, you should first backup those, expecially the most important as 1B 28 35 93

Thanks Michael
This will really help me as well. Now first thing I will do while working on seagate drives is to copy these files .

[pepe]

To the list above:
93 is not unique and fairly much replacable from donor. 030A is more important to have... not to mention 1D2 and 346 or 348 on recent drives. I would also back up 0_0...

pepe

[terminator2]

To the list above:
93 is not unique and fairly much replacable from donor. 030A is more important to have... not to mention 1D2 and 346 or 348 on recent drives. I would also back up 0_0...

pepe

Wo Thanks a lot pepe
This information is very much critical and is not available in ace manuals as well. It comes from you guys own experimentation , experience ,time and hardwork .
Now for all seagate drives my first step will be to backup
1) 030A
2) 1D2
3) 346/348
4)93 - can be replaced from donor
5) 1B
6)28
7)35

update to case ---- all efforts failed so far and drive is not giving sector access. I think pathching rom could be the issue.
There is difference between original rom and patched rom. I am attaching both copies --
download :-https://drive.google.com/file/d/1XdMojoPF-q68VNQfqSy84H41zLwClWmC/view?usp=sharing
finally I am transplanting heads as only that is left.

Attachments

[terminator2]

Guys Finally Heads were to blame , After replacing heads drive got detection and 100% data was recovered without single bad sector.Happy ending of the story.
I think patching rom might not have caused this issue but weak /filed heads were responsible .
Thanks a lot for all your help particularly michael ,pepe and ddd123.

[pepe]

pepe