He lost "several years' worth of personal photos" when his WD Blue NVMe SSD failed. The description is very detailed: it "stopped working without warning", is "no longer recognized by any system", and he's tried "different PCs, cables, and interfaces" and still found it "completely unresponsive", the failure arriving "without any prior signs of malfunction". Complete loss of responsiveness across all machines is consistent with a failed controller or firmware rather than worn-out memory; that is the more workable of the two, because the photos are almost certainly intact behind a component that has simply stopped responding.
| Media | WD Blue SN570-class NVMe SSD: sudden complete failure, unrecognised by all PCs, cables and interfaces; targeted data is years of personal photo files |
| Reported situation | No previous indication of problems · drive stopped functioning suddenly and without warning · not responsive on multiple PCs and interfaces · all typical troubleshooting efforts made by the owner · personal photos cannot be replaced |
| Fault class | Failure at the electronic level of the NVMe controller or firmware; the storage media itself is almost certainly intact but can't communicate because its controller has stopped enumerating, as opposed to normal degradation due to wear |
| Equipment used | Profile of power/thermal behaviour using a current-monitored bench supply prior to host connection · PC-3000 SSD with NVMe support and technological modes/loaders of the controller family · safe-mode access where the controller part-responds, firmware and translator structures rebuilt · chip-off via hot-air rework where it does not, noting that WD controllers encrypt their data internally · full image taken at the first stable access, hash verification completed |
Sudden versus gradual failure clearly points at different parts of the drive. Over time, worn-out NAND announces its presence through slowdowns, errors, and files which no longer open. If a drive appears perfectly fine one moment and completely dead the next, it has lost the component which speaks for it (the controller) or the firmware it executes. His emphasis on "no prior signs" fits this pattern of sudden electronic failure rather than slow degradation due to memory wear, and this is the more positive of the two diagnoses.
He has already proven through thorough troubleshooting where the fault lies. Using multiple computers, cables and interfaces, and finding the drive unresponsive everywhere, rules out a problem in the computer, the interface port, the cable, or the connection. Therefore, if every piece of equipment tested cannot see the drive, then the problem exists within the drive itself, and specifically in the part of the drive which allows it to announce its existence, because a drive which never enumerates provides software no basis upon which to search for it.
Because this NVMe never enumerates, it is beyond every consumer method, and that is why everything he tried was useless to him. Enumerating is the first step by the drive itself. Firmware boots, the controller introduces itself and a capacity is reported: this is the handshaking process. Because this handshake never begins, there is no drive for any program to recognise, and therefore it must be accessed beneath the standard interface, through the controller's technological modes on professional equipment.
Firmware failures of NVMe drives are recognised and, on many families, can be resolved. The structures mapping logical addresses to physical NAND become corrupted in known ways, and professional SSD platforms provide loaders and technological modes to wake the controller in a service state, recover those corrupted structures, and bring the drive up long enough to take a complete image. The first stable access is used immediately for a full image, as there is no reason to assume a controller that was previously dead will stay stable.
A WD-specific caveat is made clear up front. WD NVMe controllers typically have internal encryption of NAND as a standard practice, where the key resides in the controller. This provides a reason to revive the controller; if the memory chips surrounding a dead controller were read directly, they would be ciphertext. Therefore, this is why the assessment determines the controller's status early, prior to determining an approach.
A good outcome can be expected, based upon the memory. In this case, if the problem is either the controller or the firmware (as the sudden failure strongly suggests), then the NAND which holds the photographs will still be intact. Thus all that remains to recover the data is to restore access to the NAND. The only exception to this, a real NAND failure, is far less consistent with a drive that dies instantly and cleanly; this condition is established, not assumed.
We measured power and thermal behaviour of the device on a current-monitored bench supply before attaching it to a host. This allowed us to distinguish between a "dead short" printed circuit board and a controller that would allow power to flow through it but could never boot any firmware. The unit was then brought up on the PC-3000 SSD using the loader for its NVMe controller family, safe mode was used wherever possible, and the translator and firmware structures were reconstructed. Once access was stable, we took a complete image of the drive and extracted the photographs from that verified image.
The controller was revived in technological mode and its firmware structures rebuilt, and a full image was captured at the first stable connection to the drive, with the photos then extracted from the image. There are no costs associated with the assessment and the quote will be one fixed amount plus VAT; as this is electronic work, 50% of the fixed quote is due upfront, with the remaining balance only payable if we recover your data. The decode: no warning is a sign of a failed electronic component, and failed electronics can be worked with. Your NAND almost certainly has not been damaged; it has simply lost the controller that presents it, and getting your controller working again will reach your photographs.
Do not continue to power cycle it and do not try another machine: each time you power cycle it or try another machine, you are working the failed controller, on certain families of drives you may damage the firmware further, and software cannot scan a drive that no computer can see. Store it in a cool, dry place and keep it powered off. Record the exact make and model, because NVMe drives use different families of controllers and the family determines the recovery route before the drive is even connected; WD controllers specifically use internal encryption, therefore reviving the controller is the way forward.
Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, and in most cases you only pay if we recover your data. Start now or call the freephone.