This disk worked fine for a year and then it suddenly quit being recognized by the PC.

It spins up on power up, but then it sounds like it make one attempt to seek, then just spins - no more noises.

I attached a terminal to it, and then placed an insulator between the 3 signals going to the motor and observed on the terminal:

Reset
4096k x 16 DRAM
NHAWK - 1_Disk S-3E 05-27-08_15:02

Buzz
Buzz
Buzz
Buzz
Buzz
Buzz
Buzz

I hear a periodic chirp or buzz from the drive - after which it prints a "Buzz" on the screen.

Cntrl-z doesn't seem to get the drives attention, nor does Cntrl-c.

Any suggestions? does this look like a familiar problem to anyone?

Thanks

you have the motor STUCK.

not DIY.

_________________
ZeBong
" что случилось в России - останется в России "
" Россия еще раз"

I think that makes sense, as I've got an insulator between the motor drive pins and the PCB.

Once I wait long enough (after more Buzz's go by), I get this on the terminal:


Buzz
Spin Motor Locked
Index found - Spin Held -
Spin Motor Locked
Index found - Spin Held -ERR A2: Boot Adapts

Which I also think makes sense, as the motor can't run and it looks like it figures this out. However after this message is posted, I get an

F>

prompt.

Can't seem to get any commands to work though.

If I reconnect the motor, then this is what I get on power up:


Reset
4096k x 16 DRAM
NHAWK - 1_Disk S-3E 05-27-08_15:02

Buzz HM SFI
!
(P)SATA Reset

After which it seems to just sit there spinning the motor and no seek sounds.

Anybody know what this means?

Seems like maybe Buzz is an indicator when it tries to drive the motor, and maybe "HM SFI" is some kind of status?

and what about "(P)SATA Reset" - normal indication of a reset?

the spindle is not working,

and the solution for that is not with commands by terminal.

_________________
ZeBong
" что случилось в России - останется в России "
" Россия еще раз"

I think you have read one too many DIY repair guide for different Seagate series.

Repairs on Seagates based on F3 architecture do not apply to previous models like yours.

Try posting terminal response without isolating PCB. Then you will get better idea of the problem...

The terminal response without disconnecting the motor was posted 2 posts up. It ends with a reset and no cursor.

I'm new to this forum, and new to Data Recovery (other than software-type), so I wonder if anyone could explain what's puzzling me about this thread.

The OP said that the drive was spinning, but the replies are saying that the motor is stuck.

Is the OP mistaken in thinking that the drive is spinning?

If so, is that an easy mistake to make? Can you tell, by feeling vibrations?

The OP wrote "I attached a terminal to it, and then placed an insulator between the 3 signals going to the motor". As he explains, this means that the motor was disconnected, not stuck as Zebong said.

The "spin buzz" is the motor controller chip's attempt to jolt the motor into action.

As for whether the drive is spinning or not, it is clear from the "Buzz HM SFI" message that the drive is spinning. If it weren't, then there would be repeated "buzz" attempts as in the first instance.

A spinning drive would also be obvious to the OP. The fact that it is connected to a serial terminal interface would suggest that it is not mounted inside an enclosure, in which case the OP could easily detect the spinning by ear, or by feel.

_________________
A backup a day keeps DR away.

It sounds like you are saying that the other replies are incorrect or misleading.

The reason why I looked at this thread, is because I have a similar problem, with a Seagate Barracuda 7200 ES.2 which seems to me to be spinning, but is not detected in POST.

Should I raise my own thread for this?

Yes.


Your drive could be afflicted with the 7200.11 BSY bug. If you contact Seagate Tech Support, you may qualify for free data recovery. Otherwise there is a simple low cost DIY fix.

See this thread for more information:
http://forums.seagate.com/t5/ATA-and-Se ... 036#M19464

This is Seagate's tech bulletin:

Urgent Field Update. Topic: Drive Hang after Power Cycle:
http://support.ironsystems.com/docs/KB1 ... Update.pdf

_________________
A backup a day keeps DR away.

The ES.2 drives that are affected by the BSY bug will respond to the widely publicised 7200.11 DIY fix, but with a slight twist:

http://www.msfn.org/board/topic/129551- ... 0cc-state/

_________________
A backup a day keeps DR away.