WD SMR drive cant't write DATA

[Homayoun Hassan Zadeh]

Hello friends 

I have a problem with this HDD (WD22PURZ-85B4ZY0). I can access stored data in any LBA address with maximum speed, but when I try to write to any LBA address, it goes into error. 

The head test in the utility shows all heads are OK.

PCB number: 2060-810051

Do you have any solution to refurbish this HDD?

You can download all resources here. 

[Luke Coughey]

If you can read, copy the data off and replace the drive.

Luke Coughey

CEO

Recovery Force Inc

866-750-3169

http://www.recoveryforce.com

This e-mail is intended solely for the person or entity it is sent to and may contain confidential and/or privileged information.  Any review, dissemination, reproduction or other use of this e-mail by persons or entities other than the intended addressee is prohibited.  If you have received this e-mail in error, please contact the sender immediately and delete and destroy this message, all attached material and all electronic reference from all computing based devices.

--
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/707ad9ce-4c5e-434d-a774-3079474f8f73n%40googlegroups.com.

[Homayoun Hassan Zadeh]

I said that the data is not important, I just want to repair this HDD.

[Luke Coughey]

I fail to see where you made the statement that the data is not important. Seeing that this is a data recovery forum, it seems to be off topic and a waste of time.

Luke Coughey

CEO

Recovery Force Inc

866-750-3169

http://www.recoveryforce.com

This e-mail is intended solely for the person or entity it is sent to and may contain confidential and/or privileged information.  Any review, dissemination, reproduction or other use of this e-mail by persons or entities other than the intended addressee is prohibited.  If you have received this e-mail in error, please contact the sender immediately and delete and destroy this message, all attached material and all electronic reference from all computing based devices.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/2d756292-fabc-43da-b84f-9cc4dab531dan%40googlegroups.com.

[pbzcbf...@gmail.com]

Can you write to a test region in the SA? If not, are all heads affected?

[Homayoun Hassan Zadeh]

I test writing in some module in both copy by head 1 and 0, and it can be written correctly. This is a strange problem. I have never seen this issue before.

[pbzcbf...@gmail.com]

Module check  (some results may be OK)

  IDfil ROYL  IDhdr checksum  size(fil/hdr) stat  filename
  ----  ----  ----  --------  -----------   ---   --------

    24  ....  ....  CD66583E   128   ....   BAD   24.rpm
   123  ....  ....  777F8790     1   ....   BAD   123.rpm
   124  ....  ....  777F8790     1   ....   BAD   124.rpm
   125  ....  ....  777F8790     1   ....   BAD   125.rpm
   126  ....  ....  777F8790     1   ....   BAD   126.rpm
   190  ....  ....  B8248281  3A23 / A238   BAD   190.rpm
  D002  ....  ....  1CC3219A     1   ....   BAD   D002.rpm
  D003  ....  ....  A6BEAC3E     1   ....   BAD   D003.rpm


  IDfil    -- ID of module as reported in its file name (should be the same as ID in SA module 0x01)
  IDhdr    -- ID of module as reported in module's header, or .... if same as IDfil
  checksum -- actual checksum of module if not 0x00000000, or ........ if 0x00000000
  size     -- size of file in sectors / size as reported in module's header if different, or .... if same
  stat     -- status of module is BAD if inconsistency found
  ****     -- "ROYL" signature was not found in header, or .... if "ROYL" found
  xxxx     -- size of file is not a sector multiple
  !!!!     -- IDfil cannot be inferred from filename, or filespec not supported
  ??????   -- the parameter is not applicable for this case
  ......   -- the parameter's value is as expected

SMART attributes

21.rpm

 ID  Flg   Cur  Wor  Thr  Raw             Description
-----------------------------------------------------------------------------
  1   2F   200  200  200  00000000000000  Raw Read Error Rate
  2  *A4   100  253    0  00000000000000  Throughput Performance
  3   27   182  171    0  00000000000763  Spin Up Time
  4   32   100  100    0  00000000000321  Start/Stop Count
  5   33   200  200    0  00000000000000  Reallocated Sector Count
  7   2E   200  200  200  00000000000002  Seek Error Rate
  8  *A4   100  253    0  00000000000000  Seek Time Performance
  9   32    73   73    0  00000000004D72  Power-On Hours Count
 10   32   100  100    0  00000000000000  Spin Retry Count
 11   32   100  100    0  00000000000000  Drive Calibration Retry Count
 12   32   100  100    0  00000000000101  Drive Power Cycle Count
 16  *A2   100  253    0  00000000000000  Unknown Attribute
180  *AF   100  253    0  00000000000000  Unknown Attribute
183  *B2     4    4    0  00000000000060  SATA Downshift Error Count
184  *B2     1    1    0  00000000002651  End to End Error Det/Corr Count
187  *B2     1    1    0  000000000004C4  Reported Uncorrectable Errors
188  *B2     1    1    0  0000410062FFFF  Command Time Out
189  *BA   100  100    0  00000000000000  High Fly Writes
190  *A2    81   49    0  00000000000013  Airflow Temperature
191  *B2     1    1    0  0000000000012B  Shock Sense
192   32   200  200    0  000000000000E5  Emergency Retract Cycle Count
193   32   200  200    0  0000000000023B  Load/Unload Cycle Count
194   22   124   92    0  00000000000013  HDA Temperature
195  *B6   200  200  200  00000000000000  ECC on the Fly Count
196   32   200  200    0  00000000000000  Reallocated Sector Event
197   32   200  200    0  00000000000000  Current Pending Sector Count
198   30   100  253    0  00000000000000  Offline Uncorrectable Sector Count
199   32   200   90    0  00000000000205  UltraDMA CRC Error Rate
200   08   100  253    0  00000000000000  Multi Zone Error Rate
206  *A2   106    0    0  0000000000002C  Flying Height
240  *B2    74   74    0  00000000004B87  Head Flying Hours
241  *B2   200  200    0  00001B077E18B9  Total LBAs written
242  *B2   200  200    0  000000492C4D77  Total LBAs read
243  *B3   100  100    0  000000003623BB  Unknown Attribute
253  *B2   100  253    0  00000000000000  Unknown Attribute
254  *B2   100  253    0  00000000000000  Free Fall Sensor

     * = hidden attribute


24.rpm  -- File checksum is non-zero: 0xCD66583E

 ID  Flg   Cur  Wor  Thr  Raw             Description
-----------------------------------------------------------------------------
  1   2F   200  200  200  00000000000000  Raw Read Error Rate
  2  *A4   100  253    0  00000000000000  Throughput Performance
  3   27   191  171    0  00000000000599  Spin Up Time
  4   32   100  100    0  000000000002C7  Start/Stop Count
  5   33   200  200    0  00000000000000  Reallocated Sector Count
  7   2E   200  200  200  00000000000002  Seek Error Rate
  8  *A4   100  253    0  00000000000000  Seek Time Performance
  9   32    74   74    0  00000000004A2E  Power-On Hours Count
 10   32   100  100    0  00000000000000  Spin Retry Count
 11   32   100  100    0  00000000000000  Drive Calibration Retry Count
 12   32   100  100    0  000000000000D0  Drive Power Cycle Count
 16  *A2   100  253    0  00000000000000  Unknown Attribute
180  *AF   100  253    0  00000000000000  Unknown Attribute
183  *B2     4    4    0  00000000000060  SATA Downshift Error Count
184  *B2     1    1    0  00000000002651  End to End Error Det/Corr Count
187  *B2     1    1    0  000000000004C4  Reported Uncorrectable Errors
188  *B2     1    1    0  0000410062FFFF  Command Time Out
189  *BA   100  100    0  00000000000000  High Fly Writes
190  *A2    65   49    0  00000000000023  Airflow Temperature
191  *B2     1    1    0  00000000000129  Shock Sense
192   32   200  200    0  000000000000B4  Emergency Retract Cycle Count
193   32   200  200    0  00000000000212  Load/Unload Cycle Count
194   22   108   92    0  00000000000023  HDA Temperature
195  *B6   200  200  200  00000000000000  ECC on the Fly Count
196   32   200  200    0  00000000000000  Reallocated Sector Event
197   32   200  200    0  00000000000000  Current Pending Sector Count
198   30   100  253    0  00000000000000  Offline Uncorrectable Sector Count
199   32   200   90    0  00000000000202  UltraDMA CRC Error Rate
200   08   100  253    0  00000000000000  Multi Zone Error Rate
206  *A2   104    0    0  0000000000002C  Flying Height
240  *B2    75   75    0  00000000004843  Head Flying Hours
241  *B2   200  200    0  00001B077E1898  Total LBAs written
242  *B2   200  200    0  0000004883F3FA  Total LBAs read
243  *B3   100  100    0  00000000362397  Unknown Attribute
253  *B2   100  253    0  00000000000000  Unknown Attribute
254  *B2   100  253    0  00000000000000  Free Fall Sensor

     * = hidden attribute

[pbzcbf...@gmail.com]

Warranty Expiration Date -- 20-Apr-2025

You just missed out.

[Abdur Rahim Sopon]

Did you disable update 190 before? 

Best Regards

Abdur rahim sopon

Data Recovery expert

Founder of Data Recovery BD™

WP/call:+8801912881685

--
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/17d4f9eb-f65d-4149-bd3b-1bc925fd28f6n%40googlegroups.com.

[Homayoun Hassan Zadeh]

Thanks for the analysis. I believe that is a problem with module 0x190. Unfortunately, MRT can't open this module in T2 Editor.

[Homayoun Hassan Zadeh]

No, I never disabled module 0x190 before. 

Writing problems happened before I unlocked the ROM.

[Data Recovery Guru]

I would recommend reaching out to MRT for remote support. In my experience, they are good with 190 problems. In one of my cases, they were able to solve a case with a damaged 190 that Ace could not.

DATARECOVERYGURU TEAM

(617) 571-9172

www.datarecoveryguru.com

Offices are open Mon-Fri 9AM to 4:30PM. 

Available by appointment outside business hours.

Boston: 100 Massachusetts Ave, Suite 500 (5th Floor), Boston, MA 02155
Cambridge: 1 Mifflin Place, Suite 400 (4th Floor), Cambridge MA 02138
Dedham: 3 Allied Drive, Suite 303 (3rd Floor), Dedham, MA 02026

Burlington: 1500 District Ave, 1st Floor, Burlington, MA 01803

Framingham: 945 Concord St., 1st Floor, Framingham, MA 01701

Providence: 10 Dorrance St., Suite 700 (7th Floor), Providence, RI 02903

New Hampshire: One Tara Blvd., Suite 200 (2nd Floor), Nashua, NH 03062

https://www.linkedin.com/company/data-recovery-guru

https://www.facebook.com/datarecoveryguru

https://www.instagram.com/datarecoveryguru

https://www.youtube.com/c/Datarecoveryguru1

https://twitter.com/DataRecoverGuru

https://rumble.com/

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/36a491b0-178c-4f7e-8b96-1e29d801a1cbn%40googlegroups.com.

[pbzcbf...@gmail.com]

190  ....  ....  B8248281  3A23 / A238   BAD   190.rpm

Sorry, this is a bug in my program.

I have checked the module's size, and it's OK.

The checksum is genuinely bad, but I think that's a benign error.

Sorry again.

[t...@desertdatarecovery.com]

My understanding is that 190 is not actually a system file as such, so doesn’t have a checksum.

--

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/fb6ceb93-0780-4b55-a8dd-14665114e7e1n%40googlegroups.com.

[pbzcbf...@gmail.com]

Header of module 0x190

Offset(h) 00   02   04   06   08   0A   0C   0E

00000000  524F 594C 0183 1E00 9001 38A2 A439 F0DA  ROYL............
                       ^           ^^^^
                       size is 0x3A238 sectors

00000010  3030 3031 3030 3030 0917 1500 0000 0000  00010000........

WD now uses a spare nibble to store the most significant nibble of those modules whose size exceeds 0xFFFF sectors.

Sorry for derailing this thread.

As for the checksum, there is a checksum dword at offset 0x0C, but I suspect that it was only valid when the module was built and not recalculated thereafter. In fact, recalculating the checksum for this enormous module after every change would create a big overhead, so I guess it makes sense to ignore it.

[Homayoun Hassan Zadeh]

I appreciate your help, I solved the problem by regenerating the translator using P-LIST. After that, it can read and write with proper speed.

--
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/8e9f5bbb-3f85-4f22-9d4f-1d88f880cfc6n%40googlegroups.com.

[pbzcbf...@gmail.com]

Does regenerating the translator also initialise module 0x190? I saw a recent post at HDD Guru where someone was able to read the user data on a different WD model, but in that case both copies of 0x190 were unreadable.

[Homayoun Hassan Zadeh]

In this case, the data wasn't valuable for the customer, so I took the risk and regenerated the translator. For data recovery cases, I never try to regenerate the translator to solve the problem of module 0x190. But I guess it must have a direct impact on module 0x190.

On Thu, May 29, 2025 at 3:02 AM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:

Does regenerating the translator also initialise module 0x190? I saw a recent post at HDD Guru where someone was able to read the user data on a different WD model, but in that case both copies of 0x190 were unreadable.

--
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/fce66961-d362-4598-a101-a08464f21b6bn%40googlegroups.com.

[t...@desertdatarecovery.com]

I stand to be corrected, but I think regenerating the translator only works if 190 can be read.

 

 

From: datarecovery...@googlegroups.com <datarecovery...@googlegroups.com> On Behalf Of Homayoun Hassan Zadeh
Sent: Thursday, May 29, 2025 8:21 AM
To: datarecovery...@googlegroups.com
Subject: Re: WD SMR drive cant't write DATA

 

In this case, the data wasn't valuable for the customer, so I took the risk and regenerated the translator. For data recovery cases, I never try to regenerate the translator to solve the problem of module 0x190. But I guess it must have a direct impact on module 0x190.

To view this discussion visit https://groups.google.com/d/msgid/datarecoverycertification/CAGSRz1-6%3D73MJXHFJb66cDJgkH_P4Js7zUeS8tAg_yPP0Und_A%40mail.gmail.com.