Seagate Terminal Commands

[BlackST]

The FIRST THING SpinRite does when it starts examining and working with a drive is to completely disable the drive's built-in automatic sector relocation. This way the drive can't whisk the sector away the first time it's not easily read, and SpinRite can study the sector to recover its data as much as necessary. (And as you might guess by now, no other utility is even aware of this problem.)

NOT TRUE.

[Corsari]

I'm wondering why the document Seagate Diagnostic Commands, available for download also on hddguru, is not reporting Level F, safe mode.

Level F is compatible with, which one of the other levels?
I've read through the document and there are not R1 and R2 commands available in level F

Anyway, here you the nice tutorial where I've found about level F
"How to Test Seagate Drives’ Heads for HDD Repair"
http://www.datarecoverytools.co.uk/2011 ... dd-repair/

as you can read it says

F>R1
F>R2

Cor

[queueverte]

Yello,

Thanks you for these many answers.

I have a problem with my Seagate HDD SATA "500 Go ST500DM002 KC45 firmware Barracuda" which can not be recognises by the BIOS , a BSY problem.

When i use the terminal for the resolution of the problem, these line display on the pateform :



Boot 0x10M
Spin Up
FAIL Servo Op=0100 Resp=0003
ResponseFrame FFFF 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 FFFF
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000
LED:000000EE FAddr:0010289C



Please i need help to know what it is.

Sincerly.

[BlackST]

A terminal output could not be more clear.

I'm afraid there's something more than "BSY" problem !

[SAjunky]

Did you clean PCB contacts? Soft pencil eraser.

[queueverte]

Thanks you,

I clean all PCB contacts but nothing.

I Stand....

[SAjunky]

It could be PCB problem, as message points to servo and you would be pointed to head problem on any occassion even with 1% of such possibility.
What happen if you press [CTRL]+z ?
No reaction (terminal frozen) or get prompt F3>T?
It is not typical LED CC firmware corruption, but in case of frozen terminal you can use the same tecniques to bring terminal prompt.
My newbie opinion, look for compatible PC-board, but be aware you would need to transfer ROM to get new board working.

[northwind]

[BlackST]

It could be PCB problem, as message points to servo and you would be pointed to head problem on any occassion even with 1% of such possibility.
What happen if you press [CTRL]+z ?
No reaction (terminal frozen) or get prompt F3>T?
It is not typical LED CC firmware corruption, but in case of frozen terminal you can use the same tecniques to bring terminal prompt.
My newbie opinion, look for compatible PC-board, but be aware you would need to transfer ROM to get new board working.

Yes, sure ? *COUGH !*

FAIL Servo Op=0100 Resp=0003

(It takes 2 minutes with another PCB or 30 seconds with a DDA to rule out....)

[queueverte]

Hi !!!

For "BlackST", when loading terminal for the first time, pressing one of these combinaisons of touch Crtl+z or Ctrl+o give the windows i post before never the famous F3>T.

There is something important : The last line :"LED 000000..." take many time to display (over 5 min) .

Also, after all line displays, any combinaison of seagate command do anything in the terminal.

We have to lock out the terminal and disconnect and reconnect the USB - TTL adapter before anything display newly in the termial.

Otherwise, the terminal freeze after the display of the last line.


Sincerly.

[BlackST]

@queueverte ,

if you are looking for the "INTERNET FIX" of .11 and so on and it doesn't work, keep in mind that "busy" state is a CONSEQUENCE not exactly a symptom of something else.

You get LED xxxx message AFTER "FAIL Servo Op=0100 Resp=0003 /
ResponseFrame 2EA0 0603 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000" !!

Proper diagnose, please.

[SAjunky]

Proper diagnose, please.

I am afraid there will be no proper diagnose unless BlackST gives more details. For now at least BlackST agrees to my opinion that:
1. It is not typical 7200.11 firmware failure.
2. Replacing PCB is a way to go:

(It takes 2 minutes with another PCB or 30 seconds with a DDA to rule out....)

[queueverte]

Hi all !!!

Finally,
I abandoned the HDD and now I install a new one , Western D. 120 Go capacity.

The forum is too rich.

Thanks for all.

[xsoliman]

Another very good list and description of Seagate terminal commands here

www.rom.by/files/yaxsi_rus-ing_seag_bar.pdf‎

Covers up to 7200.7

[fzabkar]

Another very good list and description of Seagate terminal commands here

http://www.rom.by/files/yaxsi_rus-ing_seag_bar.pdf‎

Covers up to 7200.7

Many thanks.

[data-medics]

I know this is a really old thread, but I've put together a list of useful Terminal Commands for F3 drives: https://www.data-medics.com/forum/viewt ... f=26&t=901

Anyone wants to help contribute to it, please feel free to post.

[tkanik]

Does anyone know the commands that cause reading from the disk? I would like to try to read the disk using the Rx / Tx line. Or maybe you know command to set the head in a specific place and start reading so that the bits can be read on the appropriate SATA pins? Maybe someone tried such low-level reading bit by bit?