WD40PURX Module 02 Checksum error. No access to data

[gameboybin]

Hi everyone. Need your help with this case. The drive readies, full access to SA and can read and write to SA normally. However have the Module 02 checksum error. And wont let me access to user Sector

Model : WDC WD40PURX-89T1XY0
Serial : WD-WCC3FTTR0327
Firmware : 00.02C.5
Capacity : 4 TB (7 814 037 168)

Code:

Family:................................. : Giant
Techno mode key......................... : Ok

HDD Status sector....................... : Ok

RAM:
System controller (SoC)................. : 88i9446C0 0x(A5C0)
HDD Info reading........................ : Ok
Heads number............................ : 8
Cyl Count............................... : 256

ROM:
Read ROM................................ : Ok
ROM Data size........................... : 512 Kb
Flash ROM dir reading................... : Ok
Flash ROM dir reading (Ext)............. : Ok (Active)
Modules directory address............... : 402 822
SA regions address...................... : by default
SA regions address (RAM)................ : by default
Module 02 access........................ : Granted

SA SPT.................................. : 2116

SA Translator loading................... : Ok
SA defects assigned..................... : 6

ROM Modules:
ROM version............................. : 00.54C
Module 4F F/W version................... : 00000054
Overlay F/W version..................... : 00.55C
Servo F/W version....................... : 02.49

Heads configuration..................... : by map
Heads number............................ : 8
Heads number in use..................... : 8
Switched off heads...................... : No
Heads map............................... : 0,1,2,3,4,5,6,7

Relocations............................. : 0 (3 065)
Read ROM DCM............................ : Ok

Power up log reading.................... : Ok
Power up load dir data.................. : Yes
Power up load permovl................... : Yes
Power up load CFG data.................. : Yes
----+------+-----------+-------+------+----------------------------------------------
NN | Step |      Time | Flags | Info | Description                                 
----+------+-----------+-------+------+----------------------------------------------
13 | 710A |    672 ms |   501 | 2097 | SET_SOC_POWER_MODE(Unknown error code: 2097)
36 | 710A | 10 621 ms |   501 | 2097 | SET_SOC_POWER_MODE(Unknown error code: 2097)
79 | 710A | 10 311 ms |   501 | 2097 | SET_SOC_POWER_MODE(Unknown error code: 2097)
----+------+-----------+-------+------+----------------------------------------------

Service area:
SA dir reading (ID)..................... : Ok
Dir items loaded........................ : 422

SA Access............................... : Copy 0,Copy 1

Configuration reading................... : Ok
CFG tech mode lock...................... : No
Self encryption drive................... : No
Master Password......................... : has not been set
User Password........................... : has not been set

DCM in module 47........................ : WM
DCM in module 0A........................ : |F|GWMKCGD
DCM in module 02........................ : S|BFLAPQMWHMCKRSVQKTUG

I have tried uploading LDR + Module 2 from different donors. Still have no access to data. Module 2 still has Checksum error

Thanks for the help!

Attachments

[fzabkar]

Upload module 02?

[gameboybin]

Upload module 02?

Yes. I tried. Uploaded many modules 02 both from original file and from the same fw drive. It writes to SA ok. But when checked again. Still has Checksum error

[fzabkar]

Keep a backup copy of the original mod 02.

Write a good mod 02 to the SA and then read it back. Compare the good and bad copies with a hex editor. You can use my Mod02 parsing tool to identify the section(s) where differences are found. Or you could upload the good and bad copies here and I'll check them for you.

If this drive came out of a DVR, perhaps some funny business is going on in the firmware.

[gameboybin]

Keep a backup copy of the original mod 02.

Write a good mod 02 to the SA and then read it back. Compare the good and bad copies with a hex editor. You can use my Mod02 parsing tool to identify the section(s) where differences are found. Or you could upload the good and bad copies here and I'll check them for you.

If this drive came out of a DVR, perhaps some funny business is going on in the firmware.

My guess is only some funny business has been done. Or some problems with PC3k. Im sending you both copies of original Mod 02. and a copy from a donor drive. All of them when uploaded to Rom of the drive and checked back sends Checksum Error

https://drive.google.com/drive/folders/1Ce_0qB62TOL6--N4htsNv9X6-IIEadOi?usp=drive_link

[fzabkar]

All the checksums are 0x00000000.

[gameboybin]

All the checksums are 0x00000000.

Wait? Does that mean good or bad?? How can that be. Even the donor have checksum of 0x0???

[fzabkar]

Your screenshot shows a CS of 0x98AEFAFA whereas your modules report 0x94AEECFA. That's a difference of 0x04000E00.

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 01 00 30 00 02 00 05 00 FA EC AE 94  ROYL............
                                              ^^^^^^^^^^^

00000010  30 30 30 38 30 30 30 30 07 07 07 00 00 00 00 00  00080000

[gameboybin]

Your screenshot shows a CS of 0x98AEFAFA whereas your modules report 0x94AEECFA. That's a difference of 0x04000E00.

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 01 00 30 00 02 00 05 00 FA EC AE 94  ROYL............
                                              ^^^^^^^^^^^

00000010  30 30 30 38 30 30 30 30 07 07 07 00 00 00 00 00  00080000

So do you know how can i fix this??

[fzabkar]

Dump the module when PC3K shows the bad checksum, then compare it against the one with the good checksum. Then maybe we'll understand what is happening.

[gameboybin]

Dump the module when PC3K shows the bad checksum, then compare it against the one with the good checksum. Then maybe we'll understand what is happening.

It is showing Bad checksum with every single module 02. No matter which one it is

Attachments

[fzabkar]

Could there be bad SDRAM on the PCB??? Would it be worth trying a PCB swap???

[gameboybin]

Could there be bad SDRAM on the PCB??? Would it be worth trying a PCB swap???

I conclude this case with no solution to this

- I have tried fixing modules. Writing, reading
- Tried swapping PCB
- Tried changing Heads
=> As Fzabkar said. This drive is totally Chinese wizardry. The Label and the ID on the side of the drive didn't match.

[dkkiran]

fzabkar, please share Mod02 parsing tool

[fzabkar]

fzabkar, please share Mod02 parsing tool

https://www.hddoracle.com/viewtopic.php?p=4267#p4267

[Disk Solution]

I think there is something else cause the problem I can check remotely. pm

[MindMergepk]

have you tried shifting mod 02 to a different location ?
could it be overlapping with any other module?