good evening ;

i have this wd800jd-00lsa0 , pcb # 2060-701335-005 rev a
which has a burned PCB , simple pcb swap with the same model had made the drive spins ok , but detected as


wdc rom model UNICORN
sn WDC-ROM SN:xyz

in bios , after swaping the rom , drive recognised just it was before doing the swap .
swapped the rom to another 2 diff boards wit the same pcb# and the drive just read the same .

what is the problem ?
is this a drive reading from pcb rom only and not from SA ?

thank you

Had one of these same issue. Finally got it working with donor ROM. What tools do you have? If using SD tools find a donor ROM and write to the PCB and see if you can make it work. I had to use 4 or 5 different donor ROM files before I got one that worked good for me. Also if this one is giving XYZ check the forum on SD for this repair. I know they had a case study on this one before. Look it up on their forum and if not on their forum go to their blog and search for this one. Should help you out on this. Good luck.

_________________
Iorana Haraharaini

I know this person and he has the tools from SD already. He does not need this one. He just needs to find the case study and follow this one and he can get the data off the drive. This one is well documented from SD on forum and case study.

_________________
Iorana Haraharaini

thank you all for your help .

unfortunatly , i donut have SD tools right now , and llooking to get pc3000 UDMA soon .
i am trying to get around this problem "thanks to all people who is contacting me"

thank you again

good evening ;

after testing the modules (I/O >> check all by id) i found out that those have defects .

17 - FM_ERR_COMPAT
4C - FM_ERR_COMPAT
1C - FM_ERR_COMPAT
1B - FM_ERR_COMPAT
19 - FM_ERR_COMPAT
1E - FM_ERR_COMPAT
11 - FM_ERR_COMPAT
2F - FM_ERR_COMPAT
15 - FM_ERR_COMPAT

my drive is
wmam9u135722
wd800jd-00lsa0

and i did find 1 similar FW located here
http://www.datadonor.net/HD%20Western%2 ... 00LSA0.zip

extracted and now in the module window , i do right click on the bad modul >> I/O >> write multi selected and i choose the same module from the donor downloaded FW "with extension .mod" to get
No Module: 0 in Map

a friend has sent me his backup ".rpm" and each time i select replace my module by the donor one , i get
Write Module: **

where ** is the module name

after finishing i repower the drive and re do all the previous to find that the bad modules are still there !


can any 1 of these drive's modules replace the bad onces on my drive ?


thank you

hello again , i am attaching photos .

I would like to suggest that you go to the SD Blog site and search on WD drives case studies. In there is a good case study for why this drive has XYZ and how it can be repaired. You might want to read this one before offering a lot more help on this to the guy. Understand you need SD WD Doctor tool to do it but you will get the idea on this one.

_________________
Iorana Haraharaini

XYZ is a symptom of some failure, not a fault in itself. Your problem is somewhere else. Assuming ROM is OK and is transferred to known good compatible PCB, and no other faults with the disk, then you should reach ID, which you dont, meaning you very likely have other problem elsewhere.

My 128k wd patient shows also something like: BUCCANER WDC-ROM SN# XYZ----

It's the default way to identify when the rom firmware is good but there are some problems with the SA modules (cannot read SA..or modules corrupted..or incompatible versions of modules etc)

The header of each module has a flag...which shows that the module should be checked against the rom firmware. I have no idea what this means...but if it fail the checking it throws that FM_ERR_COMPAT ...perhaps it looks at the versions (rom vs module). I have to investigate since I must implementthis at some point in my app. So any ideea what it means that cheking would be nice

The CRC it's ok..but the module it's not for this rom version (or reverse). And the kernel shows WDC-ROM SN# XYZ---- and stops.

If the SA is damaged for some sectors..then there will be another type of errors...when reading those modules. The same for writing. If the write doesn't throw errors then there are no defects on that region of the platters.

LE:
open those mods with a hexeditor and look for bytes 5-8..and 9....


I assume that the byte 9 it's set somehow..then the version bytes must match the rom version.

I opened some modules from a 128k rom. it seems that byte 9 it's 0x3F ("?") most of the time...and 0x4A ("J") (ie. mod 0x19, 0x1E). but the versions are not the same. so..what the heck it checks? does the rom has a built in table with all version of compatible modules?

maybe raven4d could tell us what's in his 9'th byte for incompatible modules.

then why doesn't rapport anything in the log window? usually when you can't write...the corresponding VSC command throw an error which should be interpreted by the software and shown to the user. those red dots are just for fun.

btw, wdr 3..gives me ok on all 4 heads with "read test" on SA. in fact..i just discovered that head 1 is dead. so it suckz. and booted again in xp..to test again. definitely show ok ok ok ok an all 4. but see the image I've posted.

I explained what FM_ERR_COMPAT means. I have doubts that the firmware will report this err...having behind a read problem. because a bad sector means problems when reading..bad crc...so it should report error_reading...not the result of a compatibility test which assume that the reading was ok...but the check against rom failed.

read my topic. the new drive...which in fact proved to be 25% dead. 1/4 heads dead.

very grateful for your dedicated answers and ideas .

will try to get a working donor tomorrow , do a hot-swap and report the results ..

Hello anyone, probably I'm wrong but I want to suggest you a try/ask for an opinion:
I had something similar on my drive (WD10TMVW recognized USB, but no drive!). The drive spin-on, than hangs with ERR and ABR flags. I cannot even read ANY module from SA using WDR or nazyura tools.. BUT after Recalculating Tranlsators the drive started working!! It seems that wrong/damaged translators was preventing me from reading SA.. may be because the drive whas blocked on loading translator operation? I don't know, but since I don't think that a Translators Recalc should brake anything why don't try?

Please let me know what did you think about it!
Regards
Paolo

Hi raven4d.

Very usefull info here.

I think your problem maybe bad secs in SA.
You must test hotSwap but i think win not success, but testing needed.
Waiting your report.

Bye.

Sorry, i readed badly.