Switch to full style
Discussions related to PC-3000
Please no pirated software here!
Post a reply

need guidance: WD3200AAJS diagnosis

January 22nd, 2013, 5:06

Hello everyone

I have a problematic WD drive (it suddenly stopped and not recognizable from BIOS), and I'm trying to find out the kind of problem it has (an internal heads problem? or a PCB or something that can be fixed without opening it?)

I connect it to PC-3000 (UDMA) board and it is powered on (I can feel it vibrating).

The Hard Drive itself has the following info printed on it:
WD 320 GB Caviar SE
------------------------
WD3200AAJS-00B4A0
DCM: EHNNNT2CB
R/N: 701537
LBA: 625142448
WWN: 50014EE05606307E

on PCB:
-------
on Board: 2060-701537-003 REV A
Sticker on board: 2061-701537-G00AC XW6D05 V78F 6 0005430 8435

I run WDC Marvell Family Utility, and it auto-detects it as Pinnacle.
When I run the Utility I get the following information:
--------------------------------------------------
Techno mode key
Techno mode key......................... : Ok

RAM:
Zone allocation table................... : HDDs RAM reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED"
SA SPT.................................. : 1311

Head number reading..................... : Ok
Heads number............................ : 2

ROM:
Flash Dir reading....................... : Ok
ROM reading............................. : Ok
ROM Data size........................... : 192 Kb
ROM version............................. : 05.6QA
ROM generation.......................... : 05.6QA
Link table version...................... : 04.2K.
Heads configuration..................... : by map
Heads number............................ : 2
Heads number in use..................... : 2
Switched off heads...................... : No
Head map................................ : 0,1

Firmware version........................ : 0005006Q

Service area:
SA dir reading.......................... : Ok
SA Copies avalabled..................... : NONE

Configuration reading................... : No SA copy avalabled

----------
So any-one can guide or 'sniff' what might be the problem? Heads or PCB?

Any suggestions on next steps?

Thank in advance for your suggestions
Costas

Re: need guidance: WD3200AAJS diagnosis

January 22nd, 2013, 7:40

Most likely is bad overlay.

If you have updated to new PC3000 update, you cannot work with SA by ID to check it. Check if you have LDR for 0005006Q , if not request it. If you dont know what Overlay or LDR is, outsource it.

Re: need guidance: WD3200AAJS diagnosis

January 23rd, 2013, 4:12

Thanks a lot :)

Re: need guidance: WD3200AAJS diagnosis

January 23rd, 2013, 4:23

hddguy wrote:Most likely is bad overlay.

If you have updated to new PC3000 update, you cannot work with SA by ID to check it. Check if you have LDR for 0005006Q , if not request it. If you dont know what Overlay or LDR is, outsource it.


Agree, pretty common issue with this model.

Re: need guidance: WD3200AAJS diagnosis

January 31st, 2013, 11:41

These commonly have irreparable bad sectors in SA as well, a lot of times you have to build compatible SA on another matching HDD and then Smart Hotswap/clone.

Re: need guidance: WD3200AAJS diagnosis

January 31st, 2013, 11:47

Thanks a lot :)

Re: need guidance: WD3200AAJS diagnosis

January 31st, 2013, 17:41

Russwinters wrote:These commonly have irreparable bad sectors in SA as well, a lot of times you have to build compatible SA on another matching HDD and then Smart Hotswap/clone.


Bingo!!! :mrgreen:

Re: need guidance: WD3200AAJS diagnosis

February 8th, 2013, 4:51

Hmmm.

I found a compatible LDR which was loaded successfully, but now I get error on reading the Flash Dir.
I start the utility from HDD (not profile or database).

===

LDR Data uploading...................... : Ok
HDD recalibration....................... : Ok
Techno mode key
Techno mode key......................... : Ok

RAM:

Head number reading..................... : Ok
Heads number............................ : 2

ROM:
Flash Dir reading....................... : Access violation at address 023883BC in module 'PCWDCM~1.DLL'. Read of address 00000006
ROM reading............................. : Ok
ROM Data size........................... : 192 Kb
ROM version............................. : 05.6QA
ROM generation.......................... : 05.6QA
Link table version...................... : 04.2K.
Heads configuration..................... : default
Head map................................ : 0,1

Firmware version........................ : Access violation at address 023883BC in module 'PCWDCM~1.DLL'. Read of address 00000006

Service area:
SA dir reading.......................... : Unknown error. Code(0)
SA Copies avalabled..................... : NONE

Configuration reading................... : Module 02 not found
====

Any suggestion how to proceed? I guess there is some 'incompatibility' on LDR and the rest of the flash?

Thanks in advance
Costas
Post a reply