ST3500320NS Barracuda ES.2 staying busy

[AJ2008]

I currently have the same problem. Same model HDD also (ST3500320NS). I can reach Terminal by shorting read channels, also by connecting PCB alone, bit never terminal with HDA and PCB attached.

I have replaced PCB and performed ROM swap with no change. I am reluctant to replace heads as I am not certain this is the fault.

Anyone have any ideas?

[GURU]

what happens when you send the spin up command after you re-connect the PCB to HDA with unlocked term?

[AJ2008]

With PCB alone attached ID is still the same, but terminal can be reached. I Spin down, attach HDA, then spin up, but recieve LED error and no terminal access.

ROM swapped to donor PCB also gives same results. Is this a problem with ROM maybe?

[GURU]

You could try

Level 2 U: Rev 0011.0000, Flash, SpinUpDrive, U[HoldState],[Hd],[Cyl]

and trying combinations of HoldState and head + cyclinder

I never seen this and I do not have this drive in my hands :O)

[GURU]

if ROM was corrupt the drive would probably no spin-up (bad checksum error) 70% sure but not tried

[AJ2008]

I will try this when I have time to look again.

I have previously recieved HD with damaged ROM, unfortunately I could not recover. Terminal looked like:

TetonST Boot ROM 4.0
Copyright Seagate 2007

Serial FLASH boot code checksum failure!

Boot Cmds:
DS
AP <addr>
WT <data>
RD
GO
TE
BR <divisor>
BT

RET
>


Maybe there is something thst could be done, but had limited time and experience with this one

[steven]

Serial ROM damaged is very seriuos problem... it is verd hard to recover cause ROM content very critical information. such addaptive data, servo infomation and others.. try to read out the serial ROM Data using external Programming device. because I know. until Now No tool can support read serial ROM from this seagate Drive. even PC3K UDMA....

[AJ2008]

Model: ST_M13FQBL
Serial: QNR_BFW
Firmware: 11291209
Capacity: 3.86 Gb

It's the default parameters for that PCB.. Much like WD M when you see something like

Do we know of any reason and solution for this fault yet?

thanks