1TB 7200.11 ST31000333AS FW:SD35.

Drive spins up, starts to calibrate and then spins back down. This repeats endlessly, and I'm pretty sure it's a firmware problem.

Terminal shows:

LED:000000CC FAddr:0024CDC9 (drive spins down)
(drive spins up)
Rst 0x20M
(P) SATA Reset

LED:000000CC FAddr:0024CDC9 (drive spins down)
(drive spins up)
Rst 0x20M
(P) SATA Reset

LED:000000CC FAddr:0024CDC9 (drive spins down)
(drive spins up)
Rst 0x20M
(P) SATA Reset

I've tried everything I can think of to get to the command prompt, but nothing I do seems to work. I've tried the standard method of blocking off the heads on the PCB, and I've tried the method used on the HP24 drives. I've also heard of shorting the read channel, but I'm not real excited about trying that. Has anyone else here had a problem with these getting to the command prompt? You can PM if you like.

I would say heads are bad.

It should be noted that when I isolate the PCB, terminal hangs at: Rst 0x20M

To get the command prompt, try to type the command repeatedly and as fast as you can.

Good luck!

Man I have used every ounce of my stellar old school arcade skills trying to Control Z that thing fast enough to show the prompt to no avail.

Yes, and Im sure you can make the repair in the 3 second window you get...

The problem is fw.

Agree

Try to isolate the motor connector with a business card.
Then type "^z", "/2", "Z" to stop spindle, reconnect motor, type "U" to start spindle. Now you should have firmware access. If not, the pre amp is most probably damaged.

Hi to all the forum.

I have here the same drive with the same defect.

Let's suppose that trying and re-trying I get the access to the firmware.

Next?

Which are the suggested commands and or solutions?

Thank you for any tip.

Follows the output
Thank you
Corsari

---------

ASCII Diag mode

F3 T>
(P) SATA Reset

LED:000000CC FAddr:0024CDC9
Rst 0x20M
(P) SATA Reset

LED:000000CC FAddr:0024CDC9
Rst 0x20M

see here: http://sites.google.com/site/seagatefix/Home

I know that page and it does contain a bunch of errors.

Anyway, if you read carefully my post, the issue is a bit different.

I had the access to terminal, but when I issue the m0,22... command, the motor immediatly shuts off.

...then wait, until the motor turns on again!
This can take up to 10 minutes.

I know, this site is not perfect. But it works. For more special details we should open a new thread...