ST3500413AS BSY

P

protech

Member
Hi Guys,

I have a ST3500413AS here that remains busy, no clicking noise, doesn't spin down and CTRL Z doesn't get to terminal.
I shorted the pins at the start and it gets to DRD DSC but doesn't ID at all. I also tried to determine if the ROM is original but no luck there either as the output
ROM file is 0kb. Any idea on what to try is greatly appreciated.

Here is the reading.

Thanks

Rst 0x10M
RW: Disc Ctlr Initialization Completed.
LED:000000CC FAddr:000075A5
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:00000054
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:00000054
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:0000004C
LED:000000EE FAddr:00000054
LED:000000EE FAddr:00000054
LED:000000EE FAddr:00000054
LED:000000EE FAddr:00000054
LED:000000EE FAddr:00000054
LED:000000EE FAddr:00000054
 
Jared

Jared

Administrator
Staff member
Have you tried: Tests > Solutions > Solution for the "HDD Lock (LED: 000000CC)" problem ?

I think I would try that first.
 
H

hddguy

New member
LED:CC means there is problem with translator or overlays, LED:EE is usually representative of some media cache error,

Once you reach ready you should try to edit the SMP module. If you have PC3000 (or similar) you should be able to edit it with 'Edit HDD ID (Terminal) to disable reallocation and media cache processes. If LED:CC error is caused by some overlay not loading, then you can use a Loader to patch the RAM allowing it to operate, or if it is translator issue then you would need to regenerate the translator. But you should be very careful in rebuilding the translator incase of the presence of defects in translator that are not in the P-list (NRG).
 
P

protech

Member
Hi guys,

Sorry for the insanely late response, I just thought better late than never. After multiple tries to short the read channel I finally got the following and I was able to access the drive and recover the files just like that....

on Completed.
(DOS) Table Read FAIL
DOS: MAGIC CONFIG NUMBER MISMATCH
(DOS) Table Read FAIL
No HOST FIS-ReadyStatusFlags 2002A185
F3 T>
File Descriptor FD368093
File Size 00001200
Byte Offset 00000000
Bytes to write 00001200
F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 6.015 secs
F3 2>U

HighPowerMode
ExecuteSpinRequest
Spin Up Complete
Elapsed Time 3.787 secs
F3 2>/7

F3 7>X

Head 00 Resistance 00D5
Head 01 Resistance 00D9

F3 7>V40

Invalid Diag Cmd

F3 7>V1

Invalid Diag Cmd

F3 7>v40

Invalid Diag Cmd

F3 7>/T

F3 T>V40
Nonresident GList 0 entries returned
Total entries available: 0
PBA Len Flags Phy Cyl Hd PhySctr SFI

F3 T>V1
User Slip Defect List
log log log phys phys
LBA span cumm cyl hd sctr zn cyl sctr SFI PBA
0 0 0 0 0 0 0 0 0 4 0

Head 0: entries 1 slips 0
Head 1: entries 0 slips 0
Total Entries 1 Total Slips 0

F3 T>
 
You must log in or register to reply here.
Top