wd800jd-75msa3 reading as XYZ

[raven4d]

hello all ;

i saw this error when the PCB was damaged and i had to replace the PCB , but this time , the pcb has never changed and the HDD reading 6 Giga and serial number XXXXXXXXXXX-XYZ

**using WDR full version to read the SA modules givving all modules read ok and marked grean and CRC OK.
**using road map >> via enumiration (that provides more modules to check)>> read all ,,givving all modules marked in green and all crc are good unless for module
20 < greean mark + bad crc>

i tried to regen the translator several time , with the same error .

18/04/2013 02:46:32 PM Format Quick With P-List - Start
18/04/2013 02:46:32 PM Format Quick With P-List - 3042=UNKNOWN ERROR 3042


any ideas ? thank you






any hints

[labtech]

Transferred ROM? Or checked the fw ver matched?

[raven4d]

thank you for your reply .

i didn't change the PCB at all , this error is showing on the original PCB

[labtech]

You said "PCB was damaged". So, we need to rule out PCB first if you say it is indeed damaged.

[northwind]

I believe he means that he has seen this error on other cases where pcb was damaged, but now he sees it where pcb is ok.

(ie. pcb is not the culprit for this error).

[labtech]

Yup, I misread that.

[raven4d]

that u all for your input .

yes the problem this time , that no PCB swap was done at all .
drive just started identifing like this .....


i am planning getting a FW repair tool for WD ,
which one do u prefere ? (pc3k is way out of my budget)

WD hd doctor or DFL2 ?

[fzabkar]

**using road map >> via enumiration (that provides more modules to check)>> read all ,,givving all modules marked in green and all crc are good unless for module
20 < greean mark + bad crc>

FWIW, I have a WD2500BB which has no history of problems and whose MOD 20 also has a non-zero checksum.

Could you upload the resource dump for your drive, ie the SA MODs and ROM? Then we could confirm whether your PCB or its ROM really is native.

Could you also tell us the date code on the label and the markings on the MCU, SDRAM, flash memory (aka ROM), and motor controller? This will help us determine if the board was manufactured at around the same date as the drive.

[fzabkar]

Is this article of any help?

Solution for WD XYZ problem:
http://www.salvationdata.com/blog/solut ... z-problem/

[raven4d]

hello again .. and really thank you guys for your input

drive mods and flash
http://www.4shared.com/rar/s_p13reP/backup.html

MCU :
88i6545-tfj1
GN50911A.1
0623 B2P
TW

SDram :
EM6381 65TS-6G
K313208RLE826.1H
ETRONTECH

MOTOR CONTROLLER :
SMOOTH L6283 1.3
9925S VH
MYS 99 630

ROM:
SS725YF010
20-4C-SAE
0626182-AA

thank you for the article , i have read it before , flash operations >> repair , will not work , as it's only for ROYL chips i think , and when tried , the drive powers off . and re-power on .

as for the tool am looking to get , i need a tool that can handle WD FW repaires , especially , being able to edit head map for drives that clicks because of dead head , so i can reach the data available for other heads .
if the drive clicks because of a dead head , and that dead head is the one responsible to read the SA , is there a tool to emulate a drives SA to bypass that head ?

thank you

[fzabkar]

The date codes that I recognise are 0623 630 0626. They're in YYWW / YWW (Year / Week) format. This puts the age of the PCB at around week 30 of 2006 or later. Match this against the date on the label of your drive.

As for your MODs and ROM, sorry but I can't download them. 4shared wants me to login. Why not upload them to HDD Guru's file area instead, or attach them to your next post?

[raven4d]

sorry , the FW and rom backup reuploaded

Attachments

backup.rar

(908.75 KiB) Downloaded 771 times

[Nesa]

Try with another (sure good) PCB with original ROM.

[raven4d]

Try with another (sure good) PCB with original ROM.

drive clicks

flashing the original rom to new pcb will give the same XYZ serial

[fzabkar]

MOD 02 has an internal date of 12-17-2007. That does not match the PCB. What is the date on the label?

The serial number in MOD 02 is "WD-WMAM9YX14662". What is on the label?

[Nesa]

What are the numbers for both pcbs?

[fzabkar]

I extracted the following SMART data from MODs 21 and 22. It doesn't appear to show any hint of bad sectors.

Code:

ID   Typ   Cur  Worst  Raw             Description

1    F    200  200    00000000000000  Read Error Rate
3    3    166  164    00000000000A8C  Spin-Up Time
4   32     96   96    000000000010D2  Start/Stop Count
5   33    200  200    00000000000000  Reallocated Sector Count
7    F    200  200    00000000000000  Seek Error Rate
9   32     77   77    000000000043C1  Power-On Hours
A   13    100  100    00000000000000  Spin Retry Count
B   12    100  100    00000000000000  Calibration Retry Count
C   32     96   96    000000000010B0  Power Cycle Count
BE   22     67   51    00000000000021  Airflow Temperature
C2   22    110   94    00000000000021  Temperature
C4   32    200  200    00000000000000  Reallocation Event Count
C5   12    200  200    00000000000000  Current Pending Sector Count
C6   10    200  200    00000000000000  Offline Uncorrectable
C7   3E    200  200    00000000000000  UltraDMA CRC Error Count
C8    9    200  200    00000000000000  Write Error Rate


[fzabkar]

IIUC, here are your SA MODs sorted by version:

Code:

File        ID      Size      Version

~id37.rpm    0x37    0x1       0100
~id0C.rpm    0xC     0x4       0100
~idB1.rpm    0xB1    0x5       0112
~id04.rpm    0x4     0x9       0200
~id06.rpm    0x6     0xA       0200
~id07.rpm    0x7     0x9       0200
~id05.rpm    0x5     0x9       0200
~id28.rpm    0x28    0x10      0300
~id02.rpm    0x2     0x2       0800
~id17.rpm    0x17    0x1E      109K
~id19.rpm    0x19    0x19      109K
~id11.rpm    0x11    0x11A     109K
~id1C.rpm    0x1C    0x1B      109K
~id1E.rpm    0x1E    0x17      109K
~id25.rpm    0x25    0x101     109K
~id15.rpm    0x15    0xE       109K
~id01.rpm    0x1     0x2       109K
~id29.rpm    0x29    0x5       109K
~id2A.rpm    0x2A    0x5       109K
~id2D.rpm    0x2D    0x11F     109K
~id2F.rpm    0x2F    0x5       109K
~id36.rpm    0x36    0x2       109K
~id26.rpm    0x26    0x81      109K
~id1B.rpm    0x1B    0x5E      109K
~id38.rpm    0x38    0x101     109K
~id39.rpm    0x39    0x11      109K
~id40.rpm    0x40    0x13      109K
~id41.rpm    0x41    0x13      109K
~id42.rpm    0x42    0x13      109K
~id43.rpm    0x43    0x13      109K
~id62.rpm    0x62    0x1       109K
~id61.rpm    0x61    0x1B      109K
~id49.rpm    0x49    0x2       109K
~id53.rpm    0x53    0x2       109K
~id52.rpm    0x52    0x2       109K
~id4A.rpm    0x4A    0x4       109K
~id51.rpm    0x51    0x2       109K
~id50.rpm    0x50    0x2       109K
~id4C.rpm    0x4C    0xD       109K
~id31.rpm    0x31    0xB0      1500
~id32.rpm    0x32    0x8       1500
~id33.rpm    0x33    0x122     1500
~id34.rpm    0x34    0xC       1500
~id21.rpm    0x21    0x40      2107
~id23.rpm    0x23    0x40      2107
~id24.rpm    0x24    0x40      2107
~id22.rpm    0x22    0x40      2107
~idDE.rpm    0xDE    0x73      I340
~idD6.rpm    0xD6    0x71      I340
~idFC.rpm    0xFC    0x4       I340
~idDF.rpm    0xDF    0x83      I340
~idFB.rpm    0xFB    0x20      I340
~idD5.rpm    0xD5    0x70      I340
~idE0.rpm    0xE0    0x1FE     I340
~idB8.rpm    0xB8    0x2       I340
~id35.rpm    0x35    0x1       I340
~idE1.rpm    0xE1    0x1FE     I340
~idD9.rpm    0xD9    0x4A      I340
~idDC.rpm    0xDC    0x45      I340
~idFD.rpm    0xFD    0x40      I340
~idD7.rpm    0xD7    0x71      I340
~idDB.rpm    0xDB    0x7B      I340
~idE3.rpm    0xE3    0x1FE     I340
~idD4.rpm    0xD4    0x4D      I340
~idB9.rpm    0xB9    0x47      I340
~idE4.rpm    0xE4    0x1FE     I340
~idBA.rpm    0xBA    0x54      I340
~idD3.rpm    0xD3    0x43      I340
~idE5.rpm    0xE5    0x1FE     I340
~idBB.rpm    0xBB    0x4F      I340
~idBC.rpm    0xBC    0x47      I340
~idE6.rpm    0xE6    0x40      I340
~idD2.rpm    0xD2    0x53      I340
~idFE.rpm    0xFE    0x80      I340
~idE7.rpm    0xE7    0x20      I340
~idDD.rpm    0xDD    0x71      I340
~idE2.rpm    0xE2    0x1FE     I340
~idE8.rpm    0xE8    0x1AD     I340
~idDA.rpm    0xDA    0x82      I340
~idBE.rpm    0xBE    0x15      I340
~idE9.rpm    0xE9    0x1AD     I340
~idBF.rpm    0xBF    0x8       I340
~idD0.rpm    0xD0    0x43      I340
~idEE.rpm    0xEE    0x4       I340
~idFA.rpm    0xFA    0x100     I340
~idC5.rpm    0xC5    0x3       R.01
~idC1.rpm    0xC1    0x1       R.6U
~idCF.rpm    0xCF    0x6       R.6U
~idC4.rpm    0xC4    0x60      R.6U
~id9E.rpm    0x9E    0x3       R.6U
~idC2.rpm    0xC2    0x2       R.6U
~idCE.rpm    0xCE    0x6       R.6U
~id93.rpm    0x93    0x6       R.6U
~idC7.rpm    0xC7    0x1       R.6U
~idCA.rpm    0xCA    0x6       R.6U
~id92.rpm    0x92    0x1       R.6U
~idCD.rpm    0xCD    0x6       R.6U
~idCB.rpm    0xCB    0x6       R.6U
~id91.rpm    0x91    0x1       R.6U
~idCC.rpm    0xCC    0x6       R.6U

These are the ROM MODs:

Code:

ROM_0D.bin   0xD     0x1       109D  - firmware version
ROM_47.bin   0x47    0x1       R.6U  - adaptives
ROM_0A.bin   0xA     0x1       0000  - head map
ROM_30.bin   0x30    0x2       1500  - RPDList ?


If I understand SalvationData's blog article correctly, ROM MOD 0D is mismatched to SA MOD 11. This would support the conclusion that the ROM code is not native.

[Nesa]

@Franc

Hm, it's confusing! Owner said "the pcb has never changed" and "no PCB swap was done at all, drive just started identifing like this"!

[pcimage]

PCB is NOT original.

SA version is 109K, ROM is 109D