Data Recovery Case File · Solid State & Flash · The Number That Rules Something Out
Almost No Wear, and It Still Will Not Start
His enquiry was apologetic about its length and contained a figure most people never look up. "This has been an ongoing issue for over three weeks. I have an SSD with a wear percentage of 2. Windows will no longer start. I would just replace the SSD, but there are a few files on the original that I hadn't had time to back up. I have already tried installing Windows via USB, but there was no way to keep the files — it came up with an error message. I have tried mounting" it elsewhere. That wear figure is genuinely useful and it does something valuable: it rules out the explanation everybody reaches for first. This drive has barely been used, so whatever has failed, it is not worn out.
| Media | Solid-state drive reporting approximately 2% of rated endurance consumed — system no longer starting; unbacked-up files held; multiple recovery approaches attempted over three weeks |
| Reported situation | System failing to start · drive reporting minimal wear · reinstallation attempted from external media without a data-preserving option · mounting attempted elsewhere · attempts continuing over three weeks · unbacked-up files required |
| Fault class | Failure unrelated to endurance — controller firmware or translation-layer state indicated; memory condition favourable |
| Equipment used | Further attempts halted · vendor technological and safe-mode access (PC-3000 portfolio, SSD support) · firmware area and translation-layer assessment · imaging on restored access; contents verified by opening |
The decode: what the number means, and the near miss he had
What wear percentage actually reports: solid-state drives track how much of their rated write endurance has been consumed, and report it as a percentage. A figure of 2 means the drive has used around two per cent of the writing it was designed to tolerate — it is, in endurance terms, nearly new. That matters because "SSDs wear out" is the default explanation people reach for, and here the drive itself has ruled it out. Whatever is wrong, the memory is not exhausted.
What that leaves, and why it is the better outcome: a drive that will not present a usable system while its memory is healthy points at the controller — specifically its firmware state and the translation layer that maps logical addresses to physical flash locations. That is the tractable category, because firmware areas can be assessed and repaired through the manufacturer's own technological modes, after which the drive addresses its media normally and can be imaged. A worn-out drive is the genuinely hard case; a confused one is not.
The near miss worth naming: he tried installing Windows from a USB stick and found no option to keep the files. That is fortunate. The installer offers routes that erase the target drive, and they are not always obviously labelled — people working through an installer at the end of a frustrating week accept them regularly. The error message that blocked him may well have saved the files he is trying to recover. Anyone in this position should stop reaching for the installer entirely until the data is off.
Why three weeks is the real problem: not because the drive degrades from waiting — it does not, in the way a mechanical drive does — but because three weeks of repeated attempts is three weeks of the drive being powered, addressed and asked to do things it cannot. Solid-state drives perform background housekeeping whenever powered, and a drive in a confused firmware state being repeatedly booted is not neutral. The instinct to keep trying one more thing is what stretches these out.
The practical framing for him: he says he would simply replace the drive but for a few unbacked files. That is the right instinct and it suggests a scoped approach — naming those specific files means imaging can be sequenced to capture them first, and the rest treated as a bonus. A scoped recovery on a drive like this is usually quicker and cheaper than a full one.
On the bench
Further boot and mount attempts were stopped, since three weeks of powering a drive in a confused firmware state adds nothing and is not neutral. Access was attempted through the PC-3000 portfolio's SSD support in the drive's vendor technological modes, with the firmware area and translation layer assessed specifically — because a drive reporting almost no wear is describing a management-state problem rather than exhausted memory. Imaging ran on restored access, sequenced to take the named unbacked files first, and the contents were verified by opening.
The outcome
The endurance explanation ruled out by the drive's own reporting, the controller addressed in vendor modes and the required files imaged first. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone with a failed SSD: look up the wear or endurance figure, because a low number rules out the explanation everyone reaches for first and points at the controller's firmware state instead — which is the tractable category rather than the hard one; stop reaching for the operating system installer, whose options erase the target drive and are not always obviously labelled; and name the specific files you actually need, because a scoped recovery is quicker and cheaper.
SSD that won't boot but reports low wear
Take that number seriously, because it rules something out. Solid-state drives report how much of their rated write endurance they've used, and a low figure means the memory is nowhere near exhausted — so "SSDs just wear out" isn't your explanation. What's left is usually the controller's firmware state and the internal map that translates addresses to physical storage, and that's the more tractable category rather than the harder one. Meanwhile, stop reaching for the operating system installer. Its options erase the target drive and aren't always clearly labelled, and people accept them at the end of a frustrating week; if an error stopped you, that may have saved your files. Stop repeatedly booting the machine too. And write down exactly which unbacked files you need, because a scoped recovery is faster and cheaper than a full one.
That number points away from wear — call Newcastle Data Recovery on 0191 406 1051; controller addressed in vendor modes, firmware and translation layer assessed, your named files imaged first.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.