His laptop broke, and fixing it left a loose end. "After getting it fixed the SSD was taken out" — because "it had failed it therefore had to be replaced" — and now he needs "my files extracting from the failed SSD", a WD NVMe drive. The repair swapped the failed drive for a working one, which got him a functioning laptop and left his data behind on the removed drive — a common and sensible split, because recovering data from a failed SSD is a specialist job entirely separate from replacing it, and it is that separate job that now begins.
| Media | WD SN520-class NVMe SSD, 512GB, removed from a laptop during repair because it had failed — the machine now running on a replacement, the failed drive retained for data extraction |
| Reported situation | Laptop failure traced to the SSD · drive replaced during repair, laptop now working · failed original retained · files needed from the removed drive · nature of the SSD's failure not yet characterised |
| Fault class | Failed NVMe SSD, fault to be determined — controller or firmware failure the common cause, with the memory likely intact behind it; a data-extraction job distinct from the completed hardware replacement |
| Equipment used | Power and thermal behaviour profiled on a current-monitored bench supply before host connection · PC-3000 SSD with NVMe support and the WD controller family's technological modes and loaders · safe-mode access where the controller part-responds, firmware and translator structures rebuilt · chip-off by hot-air rework where it does not, with the caveat that WD controllers encrypt internally · full image at first stable access, files extracted and hash-verified |
The repair did the right thing and left the right thing undone. A laptop repair that identifies a failed SSD replaces it to restore the machine — that is the correct fix for a broken laptop. But replacing a drive gets the computer working again; it does nothing to recover what was on the old one. The two are separate jobs, and his keeping the failed drive for extraction is exactly the right instinct. The laptop is fixed; the data recovery is a distinct task that starts now.
How the SSD failed determines everything, and it has not been characterised yet. "It had failed" is enough to justify replacing it, but not enough to know the recovery route. The common cause — a controller or firmware failure — leaves the memory intact behind a component that stopped working, which is workable. A genuine memory failure is less recoverable. Which applies is established at assessment, not assumed, and shapes the approach and the prognosis.
Most SSD failures are electronic, which is the hopeful reading. Solid-state drives most often fail at the controller or firmware level rather than in the memory itself, so the odds favour the data being intact behind a failed controller. An NVMe drive that failed and had to be replaced fits that pattern, and the recovery then turns on restoring access to the memory through the controller's service modes on professional equipment — the same class of work as any controller-level SSD recovery.
A failed drive that once ran in a laptop still needs specialist access. If the controller no longer enumerates, the drive presents nothing for ordinary methods to read — which is presumably part of why it was deemed failed. Access is re-established beneath the standard interface, in technological mode, and the firmware structures that map the memory rebuilt where they are damaged, before a full image is taken.
One WD-specific caveat is stated plainly. WD NVMe controllers commonly encrypt the memory internally as standard, keyed within the controller — so reviving the controller is the viable route, since reading the memory around a dead controller would yield ciphertext. The assessment establishes the controller's state early for exactly this reason, before committing to an approach.
The realistic outcome is good, framed by what the failure most likely is. If the fault is the controller or firmware, as is most common, the memory holding his files is intact and the recovery restores access to it. The honest exception — a memory-level failure — is established rather than assumed, and stated before the work, so he knows which category his drive falls into before anything is committed.
Power and thermal behaviour were profiled on a current-monitored bench supply before host connection. The drive was brought up on PC-3000 SSD using its WD NVMe controller family's loader, safe-mode access used where available and the translator and firmware structures rebuilt. With stable access, the drive was imaged in full and the files extracted from the verified image and hash-checked.
Controller state assessed, access restored in technological mode, firmware rebuilt and a full image taken with the files extracted. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: replacing the drive fixed your laptop and left your data on the old one — different jobs entirely. Most SSDs fail at the controller with the memory intact, so restoring access to that memory is what reaches your files.
Keeping the failed drive was exactly right — replacing it fixed the laptop but left your data on the removed drive, and recovering that is a separate specialist job. Don't keep plugging the failed SSD into machines hoping it appears; if the controller has failed it will show nowhere, and repeated attempts can worsen the firmware state on some families. Note the make and model, because the controller family sets the route — and WD drives encrypt internally, making controller recovery the necessary path.
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, no fix no fee — start now or call the freephone.