Data Recovery Case File · Desktop Externals & Aging Drives · A Structured Verdict
The Machine Tested Its Own Drive and Reported a Result
His enquiry contains something almost no enquiry contains: a reference number produced by a test. A drive believed failed, where "I ran through the diagnostics on the machine and received an error code. I have plugged the drive into another computer but it doesn't recognise the drive, and you can't hear the platter spinning properly." A diagnostic code is a structured finding rather than an impression — and it is worth quoting exactly, because it says which test failed and how.
| Media | 500GB internal hard drive — failing the host's built-in storage diagnostic with a specific reference; not enumerating on an alternative machine; rotation reported as abnormal |
| Reported situation | Machine's built-in diagnostic executed against the internal drive · specific failure reference returned · drive connected to a second computer · not recognised there · rotation audibly abnormal · contents required |
| Fault class | Drive-reported self-test failure with abnormal rotation — mechanical or service area fault indicated; host eliminated by second machine |
| Equipment used | Diagnostic reference interpreted against the test it names · rotation confirmed by touch rather than by sound · no further power-up once abnormal rotation was established · laminar flow bench inspection before any spin attempt · imaging in one supervised session |
The decode: what a built-in diagnostic actually does
What those tests are: not the machine guessing. The firmware instructs the drive to run its own internal self-test — a sequence built into the drive by its manufacturer, which exercises the mechanism, reads from reserved areas, checks its own recorded statistics, and returns a pass or a specific failure.
Why the code matters: different references identify different stages. A failure during a read test means something quite different from a failure to become ready, or from a failure reported because the drive's own monitoring has already crossed a threshold. The reference distinguishes them, and it is the drive's verdict on itself rather than the computer's opinion.
Why it is worth quoting exactly in an enquiry: because it is a fact rather than a description. "It doesn't work" covers everything; a specific reference covers one thing — and it arrives without anybody having to interpret what a noise sounded like.
What his second observation adds, and it is the more urgent one: the platter is not spinning properly. That is a mechanical finding, and it is consistent with a drive failing a self-test at the readiness stage — because a drive that cannot achieve stable rotation cannot complete anything that follows.
Why the second machine matters: the drive not being recognised there eliminates the original computer entirely. The fault travelled with the drive, which is a proper control and one many people skip.
How to check rotation properly, since sound is unreliable: a hand on the drive detects the faint vibration of platters at speed. That is more dependable than listening, particularly inside a machine where fans and other drives contribute noise of their own.
Why the diagnostic having run is worth noting for a different reason: a self-test is sustained activity on a drive that is failing. It is not a free observation — it exercised the mechanism for the duration of the test, which on a drive with abnormal rotation is not nothing.
What must stop: further diagnostics. The test has produced its result, and running it again produces the same one at the same cost.
On the bench
The diagnostic reference was interpreted against the test it names — built-in diagnostics instructing the drive to execute its own manufacturer self-test, which exercises the mechanism, reads reserved areas and checks recorded statistics, returning a specific failure identifying the stage reached. Rotation was confirmed by touch rather than by sound, platter vibration being detectable through the casing where listening is unreliable amid other machine noise. No further power-up was attempted, and inspection ran under the laminar flow bench.
The outcome
The reference read against the test it names, rotation confirmed by touch and the mechanism inspected before any spin attempt. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: that code is the drive's verdict on itself, not the computer's opinion — the firmware instructs the drive to run its own manufacturer self-test, and the reference identifies which stage failed. Quote it exactly; it says more than any description of a noise.
Built-in diagnostic that returned an error code
Write the code down exactly and quote it — it's a fact rather than a description, and it identifies which stage of the drive's own self-test failed. Those diagnostics aren't the computer guessing: the firmware instructs the drive to run a test built in by its manufacturer, exercising the mechanism, reading reserved areas and checking its recorded statistics. So the result is the drive's verdict on itself. Check rotation by putting a hand on the casing rather than by listening, since fans and other drives make listening unreliable. And don't run the diagnostic again — it has produced its result, and a self-test is sustained work on a failing drive.
Quote it exactly — call Oxford Data Recovery on 01865 593000; reference read against the test it names, rotation confirmed by touch, mechanism inspected before any spin attempt.
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.