WD with wrong Capacity

Bankole Oladoja

Bankole Oladoja

Member
Can anyone please guide me through this strange WD hard drive ?

When Powered on PC-3000, the drive clicks three times and stops. it been identified as follows

Model : WDC ROM MODEL-HAWK-----
Serial : WDC-ROM SN# XYZ----
Firmware : 10.02E01
Capacity : 7.46 GB(15 650 209) instead of 160 GB

and here is the terminal log

Techno mode key
Techno mode key......................... : Ok

RAM:
HDD Info reading........................ : Ok
Heads number............................ : 4
Cyl Count............................... : 64

Zone allocation table................... : HDDs RAM reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended"

ROM:
ROM reading............................. : Ok
ROM Data size........................... : 128 Kb
ROM Modules:
ROM version............................. : 10.16E
ROM F/W version......................... : 1016E
Overlay F/W version..................... : 10.16E
Servo F/W version....................... : 02.0A

Heads configuration..................... : by map
Heads number............................ : 4
Heads number in use..................... : 4
Switched off heads...................... : No
Heads map............................... : 0,1,4,5

Service area:
Permanent overlay....................... : Not loaded
SA dir reading (ID)..................... : Unknown error code: 435A
Configuration reading................... : Module 02 not found


Can someone please explain whats going on ??
 
Jared

Jared

Administrator
Staff member
Bad heads and/or possibly media damage. The reduced capacity is just the drive going into Kernel mode where you can access ROM etc.
 
Jared

Jared

Administrator
Staff member
It still might be worth trying another PCB just to rule it out for sure, but generally that's a head failure.
 
Jared

Jared

Administrator
Staff member
I thought you said the drive spun down??? If it isn't spinning you're not reading data, that I'm sure of. Unless it's spinning back up after you do something...
 
pclab

pclab

Moderator
Hi

I will share experience with a similar case, with a WD800 which was detected as 5.xx GB.
I tried to do a RAM headmap and head 1 was OK. I could read FW and Tracks.
So, I got a similar drive (same model), wrote tracks from pacient into it. Then I powered it with the pacient PCB, which got detected and ID well. Did a headmap again to head 1, stopped the drive, swapped PCB back to pacient body and imaged data from that head.
Fortunately I was searching for a 100Mb database, which I could get (I even got the full folder ehhheh)
I will give the file to my client tomorrow :D
 
pclab

pclab

Moderator
Hey

So the DB I needed seems to be corrupted...
It's a FDB database. Is there any way to check the integrity of it or a repair utility?

Thanks
 
You must log in or register to reply here.
Top