Data Recovery Case File · Solid State & Flash · Do You Deal With NVMe?

Yes — NVMe M.2 is handled natively: a randomly-failed laptop SSD imaged on the TaskForce 2's M.2 ports, the cloud-backup gap closed, and the backup question answered in principles rather than brands

His enquiry was a model of useful detail. An NVMe M.2 SSD from a three-year-old laptop: "it randomly stopped working one day and I didn't know why. I went through a bunch of diagnostic tests with the manufacturer of the laptop, which included a lot of rebooting and stuff, in case it wasn't the SSD." He'd since tried it in another device — no response. His stakes, honestly sized: "most of my data is backed up to my Microsoft account; however, there is still some that didn't get backed up, and some important that I would like to recover." And two questions: does this lab handle NVMe M.2 (yes, natively — this page shows how), and could we recommend backup services for afterwards — which gets the honest answer below: principles rather than brands, because the principles are what protect you.

The decode: the failure, the rebooting, and the two questions

The failure, and the diagnostics that preceded it: a random, warningless stop is the signature solid-state exit this volume decodes elsewhere — no moving parts, no audible decline, a controller or firmware event flipping the drive from fine to absent in a step. The manufacturer's diagnostic round was a reasonable process for ruling out the laptop, and it did establish something useful (the fault travels with the drive, confirmed again in his second device). One gentle honest note, offered without criticism: "a lot of rebooting" is, for a marginal SSD, a lot of spent attempts — each power cycle is a fresh demand on a failing controller, and the professional instinct runs opposite: image completely on the first sign of life rather than rebooting toward one. It's the counterintuitive discipline nobody should be expected to know in advance, and it's why the drive's remaining chances now get spent on an imager rather than another boot.

Question one — yes, NVMe M.2 is native territory: his opening question deserves its direct answer: NVMe M.2 drives are handled here natively — dedicated M.2 NVMe ports on the imaging hardware, not adapters improvised onto equipment built for something else. The bench's forensic imager carries native NVMe ports precisely because this form factor is now the mainstream laptop drive, and the discipline for a marginal one is exactly as above: bring it up under stabilised handling, and if it answers at all, image the entire drive in that session — multipass, managed, complete — because a randomly-failed SSD's next silence may be permanent. Where the drive doesn't answer, the work moves to the controller and firmware layer, with the data typically intact in the NAND behind the management fault.

Question two — backup advice in principles, not brands: his request for backup recommendations gets the answer that will still be true in ten years: follow the 3-2-1 principle — three copies of anything important, on two different kinds of storage, one of them off-site (his cloud account already serves well as the off-site leg). The refinements his own case teaches: make the backup automatic, because manual habits are where gaps like his come from; and verify occasionally that what you think is backed up actually is — his "some that didn't get backed up" is precisely the discovery everyone makes one drive too late. Any reputable service or drive can fill the roles; it's the structure, not the brand, that saves you.

On the bench

The blade went onto the Atola TaskForce 2's native M.2 NVMe ports under stabilised handling, with the Atola Insight Forensic profiling its behaviour — and on the drive's response, it was imaged immediately and completely, the full capacity banked in one managed, multipass session rather than gambled on further power cycles. The filesystem stood up from the image, and the recovery then did something his partial backup made efficient: the recovered estate was compared against his cloud-backed set, and the gap — the unbacked and important files he'd described — identified, extracted and verified specifically, alongside the full recovery. What the rebooting rounds couldn't reach, one complete image did.

The outcome

The SSD's data recovered — the cloud-backup gap closed and the important unbacked files verified — and delivered with both his questions answered. Free assessment, one fixed written figure including VAT, no recovery, no fee. Yes to NVMe M.2, natively; and on backups, the durable advice: three copies, two media, one off-site, automated and occasionally verified — so the next random failure, whenever it comes, finds nothing left to take.

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.