WDC WD40NDZM-59A8KS1 Module 02

[Mike - USBRecovery.co.uk]

Can someone explain to me like Im a 5 year old, how only the first 512 of a both copies of module 02 can be completely damaged and unreadable. 

Perhaps I'm misunderstanding the process flow but isn't the point of have 2 copies to prevent exactly this ?

[t...@desertdatarecovery.com]

I don’t know. Probably the most corrupt mod I see on SMR drives apart from 190. At least it can be replaced with a donor.

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/6f301609-6091-4226-ad29-8bc50805fb96n%40googlegroups.com.

[Artem Rubtsov]

It's related to glitching PCB, usually some debug modules are damaged (2D,2E,12D,12E) in addition to 02, sometimes 190 is damaged. More often than not it's a USB-C PCB. Sometimes CPU is damaged. 

[Mike - USBRecovery.co.uk]

That must be a very specific kind of glitch for both copies to get damaged in the same manner. You're right though, it's a mac USB-C 810033 only one copy of 190 is damaged but both copies of 21,24 and 12E .

It's another "it just stopped working" drive so you know the client is going to ask how it happened and what they can do to prevent it from happening again. 

[pbzcbf...@gmail.com]

If this is a common problem, what common ATA command would provoke the drive to write to module 0x02?

[Alandata Recovery]

I have this exact situation.

I took the mod02 from a same fw version.

The serial number was different to I patched it and recalced the CS

is that the correct procedure?

I rebooted and it seems ok.

I can read data - weird even though the 190 module has areas.

it reads fine with the AREAS reading.

On Sat, Sep 6, 2025 at 2:28 PM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:

If this is a common problem, what common ATA command would provoke the drive to write to module 0x02?

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/643eb8d5-2921-4295-8567-1389e45046a3n%40googlegroups.com.

--

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

www.alandata.com   www.alandataRecovery.com

[t...@desertdatarecovery.com]

Personally I don’t change the SN.

But wherever possible I try to use the same FW and the exact same model.

Sometimes even through it’s the same FW it will appear encrypted with a different model.

 

Tim Homer - Lead Engineer

Desert Data Recovery

+1 (602) 686 2622

t...@desertdatarecovery.com

www.desertdatarecovery.com

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of Alandata Recovery
Sent: Tuesday, September 23, 2025 1:39 PM
To: datarecovery...@googlegroups.com
Subject: Re: WDC WD40NDZM-59A8KS1 Module 02

 

I have this exact situation.

I took the mod02 from a same fw version.

The serial number was different to I patched it and recalced the CS

is that the correct procedure?

I rebooted and it seems ok.

I can read data - weird even though the 190 module has areas.

it reads fine with the AREAS reading.

 

 

 

On Sat, Sep 6, 2025 at 2:28 PM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:

If this is a common problem, what common ATA command would provoke the drive to write to module 0x02?

 

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/643eb8d5-2921-4295-8567-1389e45046a3n%40googlegroups.com.

 

--

Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

www.alandata.com   www.alandataRecovery.com

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAH-%2BjWSXNuHn92A5HrwuzA0DrPy5NdMwfr60CVg0TJVPjE55ZQ%40mail.gmail.com.

[Alandata Recovery]

it cloned a few hours then

DID IT AGAIN

02 bad...

again

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/00ea01dc2ccb%24f7d70780%24e7851680%24%40desertdatarecovery.com.

[Alandata Recovery]

ok so now it corrupted 02 again

and it wont write now

So I am trying to write the module somewhere else

then use the dir editor to remap it

but looks like heads wont write eiher

tried loading a loader

that didnt help

I got 95%

still sounds good

dont know why it wont write now