Data Recovery Case File · Desktop Externals & Aging Drives · A Result, Not a Cause
A Built-In Diagnostic Reports That a Drive Failed a Test, Not What Is Wrong With It
His enquiry supplies something most do not: a machine-generated result. A desktop reporting a specific diagnostic code with a validation reference, where "the manufacturer confirms drive failure" and recovery is now needed. The code is genuinely useful and narrower than it sounds — it records that a self-test did not pass, which is a finding about the test rather than a description of the fault.
| Media | Desktop internal hard drive failing a manufacturer's built-in diagnostic — coded result and validation reference issued; drive failure confirmed by the vendor |
| Reported situation | Desktop computer reporting a diagnostic error code · validation reference issued alongside it · manufacturer confirming drive failure on that basis · recovery of content sought · possibilities, cost and timescale queried |
| Fault class | Self-test failure of undetermined underlying cause — read errors, timeouts and mechanical faults all producing the same coded result |
| Equipment used | Coded result interpreted as a test outcome rather than a fault description · no further diagnostic runs permitted · drive addressed with imposed timeouts outside any host storage stack · current draw measured across the start-up cycle on a controlled bench supply · imaged under strict per-sector timeouts with healthy regions taken first |
The decode: what the test does, and why it should not be run again
What a built-in diagnostic actually performs: a read across the drive. It asks for sectors and records whether they return within an expected time and without error.
What a failing result therefore means: something did not return. The test met sectors that errored or took too long, and it reports that outcome with a code.
Why that is a narrower statement than it appears: many faults produce it. Surface degradation, head weakness, a firmware problem and an interface fault can all cause the same failed read.
Why the vendor's confirmation adds little: it restates the result. Confirming drive failure on the basis of a failed drive test is the same finding expressed differently.
Why the code is nonetheless worth supplying: it is specific about the category. Codes distinguish read failures from timeouts from devices that did not respond at all, and that narrows the starting point.
Now the important practical point: the test should not be repeated. A diagnostic reads across the drive, and on a degrading drive that is a full pass of sustained work.
Why that costs more than it seems: it prioritises nothing. The test reads wherever it decides to read, spending the drive's remaining life without retaining a byte of it.
What is done instead: the same reading, kept. Imaging performs comparable work and preserves everything it obtains, with timeouts imposed so difficult regions are abandoned quickly.
Why the ordering differs as well: healthy regions first. A capture takes what reads easily before returning to what does not, so the maximum is secured early.
Why a failed self-test says nothing about the content: it tested reading. Sectors that failed a timed read are a small proportion, and the test does not examine what any of them hold.
On the bench
The coded result was interpreted as a test outcome rather than a fault description — a built-in diagnostic reading across the drive and recording whether sectors return within an expected time without error, so a failure means sectors errored or were slow, which surface degradation, head weakness, firmware faults and interface faults all produce. Repeating it is a full pass of sustained work retaining nothing. Imaging performed comparable reading and preserved it.
The outcome
The code read as a test outcome, further diagnostic runs stopped, and healthy regions captured first under strict timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: the code records that a test did not pass. Useful for narrowing the category and not a description of the fault — and running it again spends your drive without keeping anything.
After a built-in diagnostic fails a drive
Quote the code when you ask for help — it distinguishes read failures from timeouts from a device that didn't respond, which narrows the starting point. But don't run the test again. A diagnostic reads across the drive, which on a degrading one is a full pass of sustained work that prioritises nothing and retains nothing, spending the drive's remaining life for a second copy of the same answer. Imaging does comparable work and keeps everything it obtains.
Don't run it again — call Cambridge Data Recovery on 01223 655015; the code read as a test outcome rather than a fault description, drive addressed outside the host stack, healthy regions captured 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.