Seagate Barracuda 7200.11 - spins but not ready

[killerchip]

Dear Gurus

I have in my possession a SATA Seagate drive with the following characteristics

===
Barracuda 7200.11
1000 GBytes

ST3100033AS
P/N: 9FZ136-568
Firmware: SD35
Data Code: 09157

PCB information
100512588 REV A
DynamicKM-VOE255400
0828-03-11 94V-0
===

When I power-on the drive, I can hear the spindle spin-up and for 1 sec a 'kr-kr-kr' sound.
The drive does not become ready. I run the PC-3000 Utility but I don't get any HDD ID or any other information.

I have connected with both SATA-PATA adapter and the USB-Terminal (COM port), but terminal also does not display anything.

Is there a way (or suggest) that I can look for PCB-related issue? or should I start looking for clean-room?

Thanks in advance for your time and responses.
KC

[labtech]

Is there a way (or suggest) that I can look for PCB-related issue? or should I start looking for clean-room?

Likely neither. Seems like fw issue. Careful here given the risk of screwing up!

Terminal output may help.

[pcimage]

Agree.

Almost certainly a firmware issue.

[HARD RECOVER]

this is the 100% for pcb unmatched

[dobrevjetser]

Yep, first check if pcb is original.

[killerchip]

Dear Gurus

Thank you, all.

About PCB, seems strange. This is a drive that was originally as external drive in a USB case.
And no PCB change was done by the customer. The only thing he tried was to remove it from its USB case, and connect it directly as SATA.

For some reason, I don't anything on the terminal output. Not even when I press '.' ( I use terminal mode from inside PC-3000 utility)

Any further suggestions, would be appreciated.

Thanks again dear Gurus.
KC

[pcimage]

this is the 100% for pcb unmatched

Not really, on 7200.11 series.

If the PCB was not original on this drive then the drive would complain more than the OP says it does, which sounds more like the <1 second calibration noise.

Still bet it's fw.

As I recall, the terminal is blocked on this fw version so you'll need to check in your pc3000 manual for method(s) to circumvent this.

[killerchip]

[northwind]

If it displays text on terminal when you power it on, as i'm sure it will, then your PCB or ROM is damaged.

No.

F/W or "other" problem can block terminal access/output.

[michael chiklis]

Or maybe it's just dirty pcb head connector (oxidation).
You may post a pic of the pcb (component side)?

[killerchip]

Well, it actually seemed that my PC3K has some configuration problem with CH0.

Once I put in CH1, then drive was recognized OK, and started copying. Then MHA seemed to have problems, as the reading would stuck, and needed from time to time power-off-on. It would continue then. Until the problem got more severe, and started hearing 'clack'-sounds.

So stopped the process and now checking with clean-rooms.

Thank you all for your responses

KC