Busy - Barracuda LP ST31000520AS fw CC32

[Basco]

Hello i have a barracuda LP ST31000520AS fw CC32 in busy, bios does not detect it.
The pcb is 100536501 (same as for many barracudas 7200.12), heads are not clicking.
When i give smart reset in terminal i get "Init SMART Fail" error, take a look to terminal log:

Code:

ASCII Diag mode

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 525.708 msecs
F3 2>U

HighPowerMode
ExecuteSpinRequest

Spin Up Complete
Elapsed Time 10.139 secs
F3 2>/1

F3 1>N1

Init SMART Fail
LED:000000CC FAddr:0024EE21
LED:000000CC FAddr:0024EE21

What's the problem with this drive?

[northwind]

Grab yer tweezers.

[einstein9]

:idea:

Grab yer tweezers.

even w/o it

[hddguy]

Clear SMART in this model is not possible when stuck in BSY. Also, as terminal is present may be possible to make repairs without short circuit, but I would keep a pair of tweezers handy just in case

[einstein9]

Clear SMART in this model is not possible when stuck in BSY. Also, as terminal is present may be possible to make repairs without short circuit, but I would keep a pair of tweezers handy just in case

chk the log Z & U hddguy. i guess when its U is fine.
right

[michael chiklis]

Explain it better

[Basco]

What should i do with tweezers?

[loki]

What should i do with tweezers?

What is meant is: find the two shorting points on the PCB & use tweezers to short them.

Loki

[Basco]

ok the pcb is 100536501.

Where are the point to short?

[Basco]

hddguy, loki, einstein, northwind please help me

[hddguy]

Post photo of PCB from other side and I will tell you short points if you think this will help

[loki]

A quick use of search on this forums shows this has been asked before by a member called scottly

download/file.php?id=5259&mode=view

seagate-100536501-rev-led-short-pin-location-t23363.html



Loki

[loki]

By matching up the location from the other pic it looks like it's these here
But I would recommend confirming it using a pin in each hole to check

Loki

[Basco]

ok, when i should short those points?
Only when i give the N1 command or since i power on the drive?

UPDATE
I just tried with shorted points since power on, but i still have the SMART init error when i do N1

[hddguy]

I just tried with shorted points since power on, but i still have the SMART init error when i do N1

Shorting of read channels will not help to clear SMART. Primarily it will help to maintain terminal access in cases where it is blocked. I do not think terminal is blocked in your case so probably is no need for short circuit anyway.

It is very difficult helping in this case remotely, without seeing the media. Also, issuing specific terminal commands to the drive could have complications. For example you could successfully build translation system, but secondary defects list not accounted for and access beyond a few million LBA is not possible.

At this stage I would highly recommend you consult a professional. If not, then you can continue attempts yourself and run the risk of complicating this case even more than it already is.

[hddguy]

ok, when i should short those points?

In some series you can apply short circuit prior to powering, in other cases it should be following calibration of heads.

[Basco]

ok, when i should short those points?

In some series you can apply short circuit prior to powering, in other cases it should be following calibration of heads.

How i do calibraton of heads?

If i choose to continue with DIY, what do you suggest to do now?
In terminal can i do some diagnostic test to check what's wrong?

[mr_spokk]

ok, when i should short those points?

In some series you can apply short circuit prior to powering, in other cases it should be following calibration of heads.

How i do calibraton of heads?

If i choose to continue with DIY, what do you suggest to do now?
In terminal can i do some diagnostic test to check what's wrong?

It can be a confusion in language, but was hddguy ment was after the heads done it's calibration...not you!
Anyhow, I must say that if data IS importent don't mess with the drive anymore you CAN brick it.
Check for a local DR service, should not be too much € in this stage.

Cheers
Bosse

[hddguy]

It can be a confusion in language, but was hddguy ment was after the heads done it's calibration...not you!

Thanks I should have been clearer, bu this is exactly what I meant

[Basco]

So it's impossible to fix this in terminal, right?
Need more powerful tools as hd doctor, am i right?