WDS100T3B0A - WD Blue SA510

[signalq]

Hi all,

I am hoping someone can assist guiding me on what is possible to recover data on the below drive:
WDS100T3B0A
WD Blue SA510

The data on the drive is not very critical to me but would save me about 8 hours of work to recreate. I am a DIY technical guy and have recovered a few HDD previously with help from this forum. Thanks. I would like to try to recover the data frlym this drive. I suspect it is panic/busy mode. It is not detected by BIOS in any computer. It died very suddenly. I did not realize that WD had released urgent firmware update that may have prevented this issue.

I read there are at least 2 different hardware versions of this drive. I suspect I have the newer (problematic) version, but am not 100% certain. Is there a way I can determine it?

I believe the newer version has the following controller? A101-000125-B0 (SANDISK) S220-TGYT77.0001 Am I correct?

If so, is there a way to user terminal software to recover the contents of the drive? I don't have PC 3000 but I can use terminal program and solder wires to the PCB if needed, etc.

I appreciate any guidance or help that can be provided. Thanks.

[Lardman]

I believe the newer version has the following controller? A101-000125-B0 (SANDISK) I don't have PC 3000...

It wouldn't make any difference if you did, it's an unsupported controller https://blog.acelab.eu.com/pc-3000-ssd- ... dated.html AFAIK if it's not something simple like an electrical fault they are currently unrecoverable.

[signalq]

I believe the first generation of the SA510 had the Marvell 88SS1074. If I had this model I would be supported by PC 3000 based on the below link, correct? Thanks.

https://blog.acelab.eu.com/pc-3000-ssd- ... l-cpu.html

[Lardman]

Marvell 88SS1074. If I had this model I would be supported by PC 3000

Supported yes, but recovery is never a certainty. Either way you're going to need to send it to a dr lab, they will tell you which controller you have and if recovery is possible or you can open the casing and check yourself.

[signalq]

The drive is still under warranty and I plan to have them replace it. If I open the casing to see the controller does it break any seal that would be an indication it was opened and void my warranty? Thanks.

[Lardman]

You'd have to check the warranty status as consumer rights are different in each country. I believe over there in the states the concept of a warranty void if removed sticker is covered in magnuson-moss but I'm 4000 miles away so a call to WD should resolve it.

It's a budget drive is recovering your data not worth the cost of a replacement.

[fzabkar]

I would think that the firmware version would tell you which drive you have.

WD Blue SA510 SATA SSDs Critical Firmware Update:
https://support-en.wd.com/app/answers/detailweb/a_id/50208

Code:

Product                 Model Number Starting With                            Affected Firmware

WD Blue SA510 250GB     WDS250G3B0A, WDS250G3B0B                              52008100, 52015100
WD Blue SA510 500GB     WDS500G3B0A, WDS500G3B0B, WDBB8H5000, WDBB8G5000      52008100, 52015100
WD Blue SA510 1TB       WDS100T3B0A, WDS100T3B0B, WDBB8H0010, WDBB8G0010      52008100, 52015100

[zound]

Does anyone have this firmware for WDS100T3B0A version 52046100 as a separate file? Support can not give the firmware. The firmware is downloaded via the dashboard. But my ssd is also not seen by the dashboard. maybe I would flash this firmware directly.

[pepe]

having the data reproduced in 8 hours sounds far more reliable and cheaper solution than relying on recovery of such device especially if you want to have it replaced in warranty.

pepe

[yoitisbrian]

Hey, Zound...

I got a stack of these drives from work, they didn't try to update them and were going to throw them out lol. Half of them I was able to update using dashboard, attached is the firmware file (I think).
When I updated the 4 drives that worked, each drive had a folder named as its serial number in the software's directory... each drive had a 52046100 Folder with a device_properties.xml and had this in it:

Code:

<ffu version="1.0">
<model>WD Blue SA510 2.5 500GB</model>
<fwmode>mode3</fwmode>
<fwversion>52046100</fwversion>
<fwfile>52046100.fluf</fwfile>
<dependency model="WD Blue SA510 2.5 500GB">52008100</dependency>
<dependency model="WD Blue SA510 2.5 500GB">52015100</dependency>
<dependency model="WD Blue SA510 2.5 500GB">52020100</dependency>
</ffu>

That leads me to believe it is the correct firmware file.

How would I use that file to flash the drives that won't show up in dashboard?

[datarecoveryexpert]

For WD BLUE SA 510 there are some problems with this type of SSD. This YODA model
To fix the SSD if it is still recognized, use the firmware update tools.
And then do a secure erase or full wipe of the SSD. After this it will work well. I can give you a link to this utility if it necessary. Also ossible download it from manufacture FTP.
If it is not recognized by the computer or is identified as a SSD device, there only one way, use production tools with new firmware to begin the production process by testing the controller and NAND chip and forming a translator. The SSD will be like brand new.
If need resover data - there is a completely different approach for data recovery.
This is reqire t otesting the controller and restoring the translator modules in the NAND memory chip. But this is a more difficult path.

[SOSdonnees]

I am hoping someone can assist guiding me on what is possible to recover data on the below drive:
WDS100T3B0A
WD Blue SA510

The more accurately the model is specified, the more accurate the answers can be.
I would suggest specifiying the whole model name (also with chars after the hyphen), manufacture date, a.s.o.

This model, which is the 500GB equivalent of your 1TB SSD

Code:

    WDS500G3B0A-00AXR0
    Manufacture date: 13 juin 2022
    R/N: 2YBSA1
    Made in Malaysia

has E007-012020-3 circuit board, with the following controller:

Code:

  SanDisk
  A101-000122-B0
  S210-TGPF00.0000
  SDC1
  TAIWAN

The SA510 SSDs uses the SATA protocol, but exists in two variants: classic 2.5'' SATA form factor, and M.2 (NGFF form factor).
Some SA510 (M.2 variant) use the SanDisk A101-000125 controller: https://forum.acelab.eu.com/viewtopic.php?t=11096

Native Sandisk controllers are currently not supported by the PC-3000.

One additional major issue with those disks is that their NAND uses LDPC (Low-density parity-check code) error correction, which to my knowledge is, as for now, not supported by the available tools (Rusolut VNR, PC-3000 Flash, Flash Extractor). This means that, even with a chip-off, these tools won't be able able to recover the data.
For more details, watch Amabir's video from August 2022 about LDPC, where he explains the problem at timing 9'40", and summarizes the situation at timing 10'50".

LDPC error correction, seems possible using Perl and Python scripts available on GitHub:

• How to use: https://www.youtube.com/watch?v=z93vdLnfoDs
• Download: https://github.com/thesourcerer8/drresearch/