WD3200BPTV-24JJ5T0 spin well but can't read SA

Hello,

I've a WD3200BPTV-24JJ5T0 drive. it spin well, no clicks.

When I connect it to PC3000, it can't read ID even in Kernel mode:

Code:: Techno mode key Techno mode key......................... : Ok RAM: HDD Info reading........................ : Ok Heads number............................ : 2 Cyl Count............................... : 256 ROM: ROM reading............................. : Ok ROM Data size........................... : 256 Kb ROM version............................. : 65.48K ROM generation.......................... : 65.48K Link table version...................... : 05.0H. Consolidated ROM version................ : 00650048 ROM Modules: Flash ROM dir reading................... : Ok SA regions address...................... : by default SA Translator loading................... : Ok [b][color=#FF0000]SA defects assigned..................... : 2[/color][/b] Heads configuration..................... : by map Heads number............................ : 2 Heads number in use..................... : 2 Switched off heads...................... : No Heads map............................... : 0,1 ROM Firmware version.................... : 00650048

When I try to read modules by ABA, I get the output bellow:

Code:: Module search process started Search method........................... : Search by ABA ABA..................................... : 0 Size in sectors......................... : 168 148 ABA 0 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 1 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 2 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 3 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 4 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 5 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 6 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 7 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 8 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 9 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 10 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 11 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 12 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 13 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 14 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" ABA 15 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended" Modules found........................... : 0 Module search process completed

Could it be a Bad Head that should be replaced?

Kind regards,

Many thanks for your help Spildit.

Yes, I tried a loader from a share that I found on this website (http://files.hddguru.com/download/PC-30 ... ica%204KV/)

I have the save FW version as this file. but unfortunately, I got the same error "ABA 15 reading error - Device Error Detected: "VSCE PERM OVL NOT LOADED. LDR Upload is recomended""

reading by ID, I got the ABR error.

The drive spins very well and very quite. no noise.

The Patient drive is:

MDL: WD3200BPVT-24JJ5T0
DCM: SHMTJAB
DCX: TJ03J975Y
Date: 12 JAN 2012
FW: 01.01A01

The donor drive is:

MDL: WD3200BPVT-24JJ5T0
DCM: HEMTJABB
DCX: 5J04J9456
Date: 05 OCT 2011
FW: 02.01A02

Could this donor be a good one for HOT SWAP even if the FW version is not the same?

I admit it's a weird problem I have:

In PC3000, When I go to "Tests » Service information » Work with service area » Hardware module checking"; it can read modules except modules 11, 33 "P-List (Primary defect list)", 31 "Translator", 43 "Adaptive data" and other not important modules :roll:

.

Code:: Hardware modules checking ---------------------------------------------------------------------- Id : Copy 0 : Copy 1 : Desription ---------------------------------------------------------------------- 0001 : Ok : Ok : Modules directory 0035 : Ok : Ok : SA Defects 006D : Ok : Ok : 0110 : Ok : Ok : Modules directory (base part) 0102 : Ok : Ok : Heads map module image 0103 : Ok : Ok : ROM adaptives SA images 0104 : Ok : Ok : Microprogram version image 0105 : Ok : Ok : ROM translator SA images 0107 : Ok : Ok : ROM module image 0106 : Ok : Ok : ROM module image 0108 : Ok : Ok : IBI packet 0002 : Ok : Ok : Configuration (HDD ID) 0017 : Ok : Ok : Loaded part of microprogram code 001B : Ok : Ok : Loaded part of microprogram code 001C : Ok : Ok : Loaded part of microprogram code 0014 : Ok : Ok : Loaded part of microprogram code 0015 : Ok : Ok : Loaded part of microprogram code 001E : Ok : Ok : Loaded part of microprogram code 002F : Ok : Ok : Loaded part of microprogram code 002A : Ok : Ok : Loaded part of microprogram code 0021 : Ok : Ok : S.M.A.R.T. 0022 : Ok : Ok : S.M.A.R.T. 0023 : Ok : Ok : S.M.A.R.T. Log (reserved) 0024 : Ok : Ok : S.M.A.R.T. Log (reserved) 0013 : Ok : Ok : Loaded part of microprogram code 0011 : Err: 02 : Err: 02 : Loaded part of microprogram code 0019 : Ok : Ok : Loaded part of microprogram code 0012 : Ok : Ok : Loaded part of microprogram code 0050 : Ok : Ok : Parameters table 1 0051 : Ok : Ok : Parameters table 2 0052 : Ok : Ok : Parameters table 3 0053 : Ok : Ok : Parameters table 4 0109 : Ok : Ok : ROM image 0062 : Ok : Ok : 001F : Ok : Ok : Loaded part of microprogram code 006E : Ok : Ok : Loaded part of microprogram code 0116 : Ok : Ok : 0118 : Ok : Ok : AC55 : Ok : Ok : 4002 : Ok : Ok : 0122 : Ok : Ok : 0081 : Ok : Ok : 80FC : Ok : Ok : 0033 : Err: 02 : Err: 02 : P-List (Primary defect list) 0031 : Err: 02 : Err: 02 : Translator 000C : Ok : Ok : Models table 0034 : Ok : Ok : G-List (Grown defect list) 0032 : Ok : Ok : Relo-List (Candidate defects) 0036 : Ok : Ok : T-List Module 0029 : Ok : Ok : Loaded part of microprogram code 0040 : Ok : Ok : Adaptive data 0041 : Ok : Ok : Adaptive data 0042 : Ok : Ok : Adaptive data 0043 : Err: 02 : Ok : Adaptive data 004E : Ok : Ok : Loaded part of microprogram code 0049 : Ok : Ok : Adaptive data 004A : Ok : Ok : Adaptive data 004D : Ok : Ok : Adaptive data 0003 : Ok : Ok : Format Select Data Module 0025 : Ok : Ok : 0026 : Ok : Ok : 0038 : Ok : Ok : Loaded part of microprogram code 0039 : Err: 02 : Ok : Loaded part of microprogram code 0037 : Ok : Ok : Gain Call Data Module 002D : Ok : Ok : Debug Log 002E : Ok : Ok : Loaded part of microprogram code 00B5 : Ok : Ok : WRRO Log Module 006B : Ok : Ok : Loaded part of microprogram code 003A : Ok : Ok : 0028 : Ok : Ok : Factory Self Test script 003B : Ok : Ok : 003C : Ok : Ok : 003D : Ok : Ok : 003E : Ok : Ok : 003F : Ok : Ok : 006F : Err: 02 : Err: 02 : 0119 : Ok : Ok : 0068 : Ok : Ok : 0069 : Ok : Ok : 006A : Ok : Ok : 0121 : Err: 02 : Err: 02 : 0128 : Ok : Ok : 012A : Ok : Ok : 0120 : Err: 02 : Err: 02 : 012D : Ok : Ok : 022D : Ok : Ok : 0004 : Err: 02 : Err: 02 : Family models configuration (Main) 0123 : Ok : Ok : 0124 : Ok : Ok : 0125 : Ok : Ok : 0126 : Ok : Ok : D002 : Ok : Ok : D003 : Ok : Ok : D004 : Ok : Ok : D005 : Ok : Ok : D000 : Ok : Ok : D001 : Ok : Ok : 0127 : Ok : Ok : D006 : Ok : Ok : 0063 : Ok : Ok : 0115 : Ok : Ok : ... ... ... ---------------------------------------------------------------------- 01 : Module has invalid header 02 : Data error reading module 03 : Servo error reading module 04 : Wrong / Incompatible module 05 : The two copies do not match / Checksums Different 06 : Invalid checksum 07 : Module state reading error

Is there any chance that Hot swap procedure will succeed with the donor drive I mention above ?
Anyone who have a compatible loader with the Patient drive I mention above?

Kind regards,

I don't know. The date code on your donor is pretty far off. I personally would look for one with a closer date, otherwise you might be spinning your wheels and getting nowhere.

Op will need to hotswap in order to access modules via ABA and can read in composite. this way you may salvage enough of 31 to be ok. IF not, and dependent on how much is read before errors, you can cut the translator size as long as it header and checksum is is adjusted. After some point module is filled with 00 anyway.

Donor should be good hotswap donor, sometimes modules can have different SA and sizes of modules may vary, if this is the case with your donor find some resource in database with compatible sa and write tracks and rom to make donor compatible for hotswap.

If DIR module is different write patient one to RAM to ensure mods are accessed correctly.

Once you reach good copy of required modules you can make smart hotswap with same donor to reach data.

Also, with each of these steps is the risk of causing more damage to patient and 'brick' your donor. If you are unsure about any of it, it could be best to outsource it

WD3200BPTV-24JJ5T0 spin well but can't read SA

WD3200BPTV-24JJ5T0 spin well but can't read SA

Re: WD3200BPTV-24JJ5T0 spin well but can't read SA

Re: WD3200BPTV-24JJ5T0 spin well but can't read SA

Re: WD3200BPTV-24JJ5T0 spin well but can't read SA

Re: WD3200BPTV-24JJ5T0 spin well but can't read SA

Re: WD3200BPTV-24JJ5T0 spin well but can't read SA