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". Now he needs "my files extracting from the failed SSD", a WD NVMe drive. The repair swapped the failing drive for a working one, which got him back up and running, and left his data behind on the removed drive. This is a common and sensible split, as recovering files from a failed SSD is a specialised job separate and distinct from replacing the device, and it is that separate job that now begins.
| Media | WD SN520-class NVMe SSD, 512GB, removed during laptop repair as it had failed; laptop currently operational using a replacement drive, the failed drive retained for recovery |
| Reported situation | Faulty laptop, failure traced to the SSD · original drive replaced during repair, laptop now operational · failed original drive retained · files needed from the removed drive · type and extent of the SSD's failure not yet identified |
| Fault class | Failed NVMe SSD, fault to be determined: most likely a controller or firmware failure, with the memory probably still intact behind the failed logic; a separate data-extraction job from the completed hardware replacement |
| Equipment used | Power and thermal behaviour profiled on a current-monitored bench supply prior to host connection · PC-3000 SSD with NVMe support, with the WD controller family's technological modes and loaders · access via safe mode where the controller part-responds, firmware and translator structures rebuilt · chip-off using hot-air rework where it does not, with the caveat that WD controllers encrypt internally · full image from first stable access, files extracted and hash-verified |
The repair did the right thing, and left the right thing undone. Repairing a laptop that has had its SSD fail means replacing the SSD to get the laptop working properly (the proper fix for a broken laptop). Replacing the SSD allows you to use your computer again; however, it does nothing to recover what was on the original drive. There are two different tasks involved here: fixing the laptop (replacing a drive) and recovering the data. His decision to keep the failed drive for data recovery is a good choice. The laptop has been fixed; now comes the data recovery job.
The reason the SSD failed will determine how to proceed with recovery, and has yet to be identified. Although the fact that an SSD "failed" is sufficient justification for replacement, it does not provide enough information to establish a plan of action for the retrieval of data from the device. A common type of failure, a controller or firmware failure, results in the memory remaining intact behind a component that simply ceased functioning, which allows for potential recovery. However, a genuine memory failure is far less likely to be recoverable. At the time of assessment, the nature of the failure is determined rather than assumed; this establishes the course of action and prognosis.
SSD failures are usually caused by electronic failure, which is the hopeful reading. Failure within solid-state drives is more frequently due to failures at the controller or firmware level versus memory errors themselves; therefore, there is a higher likelihood that the data stored within the SSD remains intact behind a failed controller. An NVMe drive that failed and had to be replaced fits this pattern. In such cases, recovering the data involves restoring access to the memory via the controller's service modes using professional equipment, similar to any other controller-level SSD recovery.
Although a failed SSD was previously used in a laptop, it still requires specialist access to its contents. If the controller can no longer enumerate, the SSD presents no content for standard interfaces to read, which appears to have contributed to why it was considered failed. Access to the SSD is re-established beneath the standard interface (in technological mode) and the firmware structures that map the memory are reconstructed where they were damaged, prior to taking a complete image of all data contained within the SSD.
One specific WD-related limitation is clearly defined. WD NVMe controllers are generally set up to encrypt the memory internally as standard, with the keys held inside the controller; therefore reviving the controller is the only viable method of getting to the data, because reading the memory around a dead controller would only yield encrypted data. This is why we assess the controller's condition early on, before deciding how to proceed.
The expected results are good, based upon what most likely caused the failure. If the failure occurred at the level of the controller or firmware (which is most common) then the memory containing his files remains intact, and the recovery procedure restores access to those files. We establish the exception to this rule (a memory-level failure) rather than assuming it exists, and state it prior to beginning the work, so that he knows which category his drive falls into before anything is committed.
Power and thermal behaviour were tested and documented on a current-monitored bench supply, before the host computer was connected. The drive was loaded on PC-3000 SSD using the WD NVMe controller family's loader, and the safe mode option was employed where available. The translator and firmware structures were rebuilt, and with a stable interface established the drive was imaged in full. All of the files were then extracted from the verified image and hash-checked.
We assess the controller state, restore access in technological mode, rebuild the firmware and take a full image, and the files are recovered from it. We don't charge anything for our assessment and you receive a single fixed price quote, plus VAT. For electronic and chip-level work, 50 percent of our quoted price is payable upfront, with the balance only due if we recover your data. The decode: replacing the drive fixed your laptop and left your data on the removed one: two completely different jobs. Most SSDs fail at their controllers while keeping their memory intact, so restoring access to that memory is how we get to your files.
Keeping the failed drive was exactly right: replacing the failed SSD restored your laptop to working condition, but left your data on the removed drive, and recovering that is an entirely separate specialist job. Do not keep plugging the dead SSD into computers in the hope that it shows up again; if the controller has failed it will never appear anywhere, and continued attempts may worsen the firmware state on some families. Record the make and model, since each family of controllers dictates the route. WD drives are also encrypted internally, so controller-based recovery is the necessary path for them.
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.