Data Recovery Case File · Second Fixes & Trade Handoffs · Return It and Lose It
A Warranty Replacement Requires the Drive Back, and the Drive Is the Data
His enquiry describes a failure early enough to raise a question most people miss. A laptop drive that failed after about a year — "not detected by the system and will not complete any tests", preceded by a stop error and then the firmware screen — already replaced by the shop that fitted it. A drive that fails within its warranty period is usually returnable, and returning it means giving away the only copy of what is on it.
| Media | Laptop solid-state drive approximately one year old — not detected by the host, failing built-in diagnostics; replacement already fitted by a third party |
| Reported situation | Laptop approximately one year old · system stop error observed followed by the firmware screen · drive no longer detected by the system · drive failing to complete diagnostic tests · replacement drive fitted by a third party · original drive retained · content required |
| Fault class | Early-life controller failure — enumeration absent and diagnostics not completing; commercial disposition of the drive determinative of whether recovery remains possible |
| Equipment used | Warranty disposition established before any commitment · device addressed through hardware with imposed timeouts rather than the host stack · controller state assessed in vendor technological modes · chip-level read past the controller with translation layer reconstructed in software |
The decode: the commercial question first, then the technical one
Why the age is the first thing to notice: a drive failing at about twelve months is within warranty on almost any product. The manufacturer will very likely replace it, which is worth something and which comes with a condition.
What that condition is: the failed drive goes back. A warranty replacement is an exchange, and once the drive is posted it is gone — along with the only copy of everything on it.
Why that sequencing trap catches people: the warranty claim is the obvious, cheap, sensible response to a young component failing. It is also irreversible, and it forecloses the recovery entirely — so the order matters more than either decision does.
What the right order is: recover first, return afterwards. The claim is not time-critical in the way the data is, and a drive already read has nothing left to lose by being sent back.
Why it is worth raising even though he has not mentioned it: he has already had the drive replaced by a shop. Whoever supplied the replacement may expect the failed unit for a claim, and that arrangement should be paused until the content is out.
What the technical picture is: a drive not detected and unable to complete diagnostics is not presenting itself. Diagnostics require the drive to respond, so failing to run them is the same finding as not being detected rather than an additional one.
Why the stop error and firmware screen fit: the system lost its storage while running, then found nothing to start from. That is the sequence a system drive failing abruptly produces, and it points at the drive rather than at the software.
Why an early failure is usually the controller: drives failing in the first year rarely do so through wear. The memory has not been used enough to degrade, so the cause is more often a component or firmware fault — which leaves the stored content untouched.
Why that is the encouraging reading: a young drive has a nearly-new memory array behind a failed controller. Reading past it and rebuilding the arrangement in software reaches content that has barely been written over.
What must not happen: no returning the drive under warranty until it has been read, and no firmware update or vendor utility. Both are irreversible in the direction that matters.
On the bench
The warranty disposition was established before any commitment — a failure at approximately twelve months falling within warranty on most products, replacement being an exchange requiring the failed unit to be surrendered, which forecloses recovery irreversibly. Absence from detection and inability to complete diagnostics are the same finding, diagnostics requiring the drive to respond. Early-life failure rarely arises from wear, implicating controller or firmware while leaving memory intact. Chip-level reading was performed past the controller.
The outcome
Warranty disposition established first, the device addressed through hardware, and the memory read past the controller. 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: check what has been agreed about returning the drive before anything else. A warranty replacement is an exchange, and posting the failed unit gives away the only copy — recover first, return afterwards.
A drive that fails inside its warranty period
Pause any warranty claim until the data is out, and check what whoever fitted your replacement expects to do with the old unit. A replacement is an exchange: the failed drive goes back, and once posted it's gone along with everything on it. That trap catches people because claiming is the obvious, cheap, sensible response to a young component failing — and it's irreversible in the one direction that matters. Recover first, return afterwards; the claim isn't time-critical in the way the data is. Early failures are usually the controller, with the memory barely used.
Pause the claim — call Manchester Data Recovery on 0161 871 0788; warranty disposition established before commitment, addressed through hardware with imposed timeouts, memory read past the controller.
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.