Home / Case Studies / Trust, Practice & Honest Limits
Trust, Practice & Honest Limits · case file

Not Recovery, but Proof It Can't Be Recovered

His request is the opposite of the usual one, and entirely reasonable. An m.2 NVMe drive has failed; the seller will refund him but requires the drive back. It "was an un-encrypted backup of my drive, so I don't need data recovery" — instead he wants to "know that the drive can't be accessed" before it leaves his hands, asking whether we can "see if you can access it/wipe it, and then send it back". This is a legitimate data-security question rather than a recovery one: an unencrypted drive returning to a manufacturer carries a real risk that someone could read it, and the responsible answer is to assess accessibility honestly and secure the data where possible.

SSD / NVMeDead / No Power
// case at a glance
MediaFailed m.2 NVMe SSD holding an unencrypted backup — being returned to the seller for a refund; the owner wants assurance the data cannot be accessed before it leaves.
Reported situationDrive failed and to be returned for a refund · data was an unencrypted backup, so recovery not wanted · concern that the data could be accessed by others · request to check accessibility and wipe if possible before return · turnaround and process queried.
Fault classNot a recovery case — a data-security assessment of a failed drive: determining whether its data is reachable in its failed state, and rendering it inaccessible where the drive still responds enough to allow it.
Equipment usedDrive assessed on PC-3000 SSD for controller responsiveness on a current-monitored bench supply, behind a hardware write-blocker during read-only checks — establishing whether the data is reachable at all in its failed state · where the controller responds, a secure erase issued through it, or the mapped data overwritten, to render it inaccessible · where the controller is dead, chip-level inspection under stereo microscope to gauge the realistic risk that anyone could recover data from it · a clear written statement of what was done and the residual risk, the drive returned with the data secured as far as its failure allows.
// the decode

The decode

The concern is valid: an unencrypted drive is readable by whoever ends up with it, if it can be read at all. Because the backup was not encrypted, its data is not protected by any key — anyone who can access the drive can read the files. Sending such a drive back to a seller or manufacturer, where it may be inspected, refurbished, or resold, is a genuine exposure. His instinct to secure it first is the right one, and it is a question worth taking seriously rather than waving away.

Whether the data can be reached depends on the same fault that made it fail, which is the first thing established. A drive that failed may or may not still expose its data. If the controller is dead and the drive is completely unresponsive, the practical risk of anyone recovering the data is low — reaching it would itself require laboratory-level work. If the controller still responds enough to be read, the data is genuinely accessible and should be secured. So the assessment begins by determining which of those is true.

Where the drive still responds, it can be securely erased. If the controller answers, a secure-erase command can be issued through it, or the mapped data overwritten, rendering the backup inaccessible before the drive leaves. That directly addresses his concern — the data is not merely deleted but made unrecoverable, so returning the drive carries no exposure.

Where the controller is dead, the honest answer is an assessment of residual risk, not a false guarantee. If the drive is truly unresponsive, it cannot be commanded to erase — but that same unresponsiveness is what makes casual access impossible. The responsible service here is a straight assessment: whether the data is realistically reachable by anyone without specialist equipment, stated plainly, rather than a hollow promise that it has been wiped when the drive would not accept the command.

The forward lesson travels with it. The whole exposure exists because the backup was unencrypted. Encrypting backups means a drive can be returned, discarded, or lost without concern, because the data is unreadable without the key regardless of who holds the hardware — the simplest protection against exactly this situation next time.

// on the bench

On the bench

The drive was assessed on PC-3000 SSD for controller responsiveness, establishing whether the data was reachable in its failed state. Where the controller responded, a secure erase was issued through it, or the mapped data overwritten, to render it inaccessible. Where the controller was dead, an honest assessment of the realistic recovery risk was made. A clear written statement of what was done and any residual risk accompanied the drive, returned with the data secured as far as its failure allowed.

// the outcome

The outcome

Accessibility assessed, the data securely erased where the drive allowed, and an honest statement of residual risk provided for the return. The assessment costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the work turns out not to be possible, no charge is made. The decode: this was a security question, not a recovery one — and it deserved a real answer. Where the drive still responded, the backup was securely erased; where it didn't, that same failure is what keeps the data out of reach. Either way, you return it informed.

Returning a failed unencrypted drive for a refund or warranty

Take the exposure seriously — an unencrypted drive is readable by whoever receives it if it can be read at all, and sellers may inspect, refurbish, or resell returned hardware. If the drive still responds, it can be securely erased before it leaves; if it's truly dead, that unresponsiveness itself limits the risk, and an honest assessment is more useful than a false wipe guarantee. Encrypt your backups in future, so a returned or lost drive carries no exposure regardless of who holds it.

Sending this in from Swansea? Every case opens with the free diagnostic — completed within 2 working days of your media arriving — and one fixed written quote before any work: logical jobs run no fix, no fee; invasive drive-opening work takes 50% of the quote upfront; forensic-classed work is payable upfront in full. If the data is inside a laptop, PC, Mac or server, remove the hard drive or SSD and send us just the drive; we don’t provide an internal drive-removal service, and we don’t recover storage soldered to a motherboard (e.g. Apple Silicon Macs) — only drives that can be removed and sent to us. Post or courier tracked and insured to Bristol Data Recovery, Castlemead, Lower Castle Street, Bristol, BS1 3AG — full sending instructions and the shipping form are here.
Start a free diagnostic

Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.

// related case files

More cases like this one

Browse all case studies →

Got a device with a story like this?

Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.