Page 1 of 1

Seagate 7200.12 ST500DM002 no terminal access

Posted: 09.08.13, 04:44
by toto7983
Got a problem with a Seagate 7200.12 ST500DM002 JC4B firmware. Drive spins up and sounds fine but is not recognized. Drive is only several months old, PCB looks pristine, no corrosion or visible burn damage, has not been dropped. Thought this might be a BSY error similar to the 7200.11 series but when connected to terminal and powered on drive only reports:
Rst 0x10M
RW: Disc Ctlr Initialization Completed.
(P) SATA Reset

No response to CTRL-Z, no terminal access.

Any ideas or suggestions?

Thanks

Re: Seagate 7200.12 ST500DM002 no terminal access

Posted: 12.08.13, 16:12
by Nick_TS
There is a method you should follow for getting to terminal with shorting. The contacts must be identified properly.
On the most drives reading channel line is crossed with an element, so it is easy to find two lines that go from pads to CPU on your drive board.
You should short the contacts with a pincers when holding a paperclip with it.
Also, the moment to short is before 2nd recalibration. When shorted properly, drive will start to click and then it will stop. At the same time press ctrl-z within terminal window and check if T> is there.

Re: Seagate 7200.12 ST500DM002 no terminal access

Posted: 12.08.13, 17:19
by dmarques
Hi,

But your drive just reports BSY ?

Re: Seagate 7200.12 ST500DM002 no terminal access

Posted: 20.08.13, 03:56
by hddstudio
toto7983 wrote:Got a problem with a Seagate 7200.12 ST500DM002 JC4B firmware. Drive spins up and sounds fine but is not recognized. Drive is only several months old, PCB looks pristine, no corrosion or visible burn damage, has not been dropped. Thought this might be a BSY error similar to the 7200.11 series but when connected to terminal and powered on drive only reports:
Rst 0x10M
RW: Disc Ctlr Initialization Completed.
(P) SATA Reset

No response to CTRL-Z, no terminal access.

Any ideas or suggestions?

Thanks


ATA register shows DRDY + DSC but on any soft reset/recalibration will show "DWF + ERR" ?
If that is the case, short circuit its read channel as suggested by Dima