WD800AAJS-75M0A0 with Firmware Issues?

[Dizidago357]

All,

We received a Western Digital drive with model WD800AAJS-75M0A0. The drive spins up fine and goes ready in DDI/HD Doctor, but when you try to load from the drive it errors out. Using a load file found on here, we were able to load the drive in HD Doctor and extract SOME of the firmware modules (we are unable to read in 73 out of 367 modules) along with the ROM. Anyone have any suggestions on what modules we can and can't overwrite. And does anyone care to weigh in if this model drive is likely to have firmware issues only, or other issues with those?

Dizi

[Dizidago357]

Nobody at all?

Dizi

[drc]

FW issues are very common with this drive

[hddguy]

DRC is right, I would guess this has some Overlay error, though proper diagnosis is required.

[Dizidago357]

Thank you drc.

Suggestions on how to go about repairing it (other than send it to a pro)? Are there many modules we could transplant from a donor to the patient and remedy the FW issues? If I were to post a list, would/could you confirm/deny which ones we could transfer and which we cannot?

Dizi

[hddguy]

Replacement of certain SA modules is not as simple as simply replacing as they are often dependent on the specific SA version.

If you do not know how to handle this, maybe sending to a pro is not such a bad idea...

[Dizidago357]

So assuming I were to match up the specific firmware revisions (02.03E02, etc.), is it doable? We haven't done many WD firmware fixes in the past (mostly bad board/corrupt ROM fixes, never anything like this) and we send out many of our more tricky WD headswaps.

We do okay with other manufacturers, and wish to learn some about how to go about the WD FW repairs. We have the tools for some of the repairs, and wish to begin learning how to do those. We're well aware that you can't just replace any module with one from any other model of WD drive, but we were hoping to gain some insight as to which revisions are compatible with which for scenarios like these. We've gotten a few of these in the past, and as the number seems to be rising (slowly, but also steadily - we still only get a few a year) it'd be nice to learn how to do these in-house.

Dizi

[hddguy]

You have a list of the 73 SA modules you could not read?

[Dizidago357]

@hddguy:

Code:

ERR_0003.MOD
ERR_0011.MOD
ERR_0013.MOD
ERR_0023.MOD
ERR_0024.MOD
ERR_002D.MOD
ERR_0031.MOD
ERR_0033.MOD
ERR_0038.MOD
ERR_0039.MOD
ERR_0042.MOD
ERR_0043.MOD
ERR_004A.MOD
ERR_0066.MOD
ERR_006F.MOD
ERR_0080.MOD
ERR_0091.MOD
ERR_0096.MOD
ERR_00A1.MOD
ERR_00A6.MOD
ERR_00A9.MOD
ERR_00AA.MOD
ERR_00BD.MOD
ERR_00BE.MOD
ERR_00C8.MOD
ERR_00D0.MOD
ERR_00D1.MOD
ERR_00D2.MOD
ERR_00D4.MOD
ERR_00D7.MOD
ERR_00D8.MOD
ERR_00DB.MOD
ERR_00DC.MOD
ERR_00E0.MOD
ERR_00E8.MOD
ERR_00FA.MOD
ERR_00FE.MOD
ERR_0115.MOD
ERR_0121.MOD
ERR_0122.MOD
ERR_1100.MOD
ERR_2000.MOD
ERR_2001.MOD
ERR_2002.MOD
ERR_2003.MOD
ERR_2004.MOD
ERR_2005.MOD
ERR_2006.MOD
ERR_2007.MOD
ERR_2014.MOD
ERR_2015.MOD
ERR_2016.MOD
ERR_2030.MOD
ERR_2031.MOD
ERR_2032.MOD
ERR_2033.MOD
ERR_2034.MOD
ERR_2035.MOD
ERR_2037.MOD
ERR_2042.MOD
ERR_2043.MOD
ERR_2045.MOD
ERR_2046.MOD
ERR_2060.MOD
ERR_2061.MOD
ERR_2063.MOD
ERR_2064.MOD
ERR_2067.MOD
ERR_3300.MOD
ERR_3411.MOD
ERR_3500.MOD
ERR_3501.MOD
ERR_801D.MOD


Dizi

[hddguy]

@hddguy:

Code:

ERR_0011.MOD

ERR_0031.MOD

ERR_0042.MOD

ERR_0043.MOD

ERR_004A.MOD




Dizi

You have some damage to important modules. Overlay is bad, Translator is bad, PLIST is bad, Adaptive modules are bad also. Maybe more, I did not check full list.

You have donor for hotswap?

[Dizidago357]

Not yet, we just have the modules we were able to find on HDD Guru's repository.

Dizi