Data Recovery Case File · Desktop Externals & Aging Drives · So Was It Running?
That Is About as Gentle as a Drop Gets
His enquiry describes an impact at the mild end of everything in this archive. A drive "dropped from a bed to a carpeted floor. The device light comes on when plugged in, and I hear a whirring noise from the device, but it is not recognised on my laptop, television, or projector." Short distance and soft landing should have been survivable — which makes one question worth asking before anything else, because the answer decides whether the fall is the cause at all.
| Media | 1TB external hard drive following a short fall onto a soft surface — powering and rotating; not enumerating on three host types |
| Reported situation | Drive dropped from approximately bed height onto carpet · indicator illuminating on connection · rotation audible · not recognised by a laptop computer · not recognised by a television · not recognised by a projector · absent from both host device consoles |
| Fault class | Failure to complete start-up with rotation achieved — operating state at impact determinative; service area or head reading indicated rather than gross mechanical damage |
| Equipment used | Operating state at the moment of impact established before assessment · rotation confirmed by touch · readiness sequence read directly under strict timeouts · laminar flow bench inspection where head damage was indicated · imaging on restored addressing |
The decode: the question that decides it, and what rotation proves
Why the height and the surface matter less than people think: what damages a drive is deceleration. Bed height onto carpet spreads the stop over a comparatively long distance and transfers a modest force — considerably less than the same drive falling a shorter distance onto tile.
So the question worth answering: was it powered and connected at the time? A drive that is switched off has its heads parked on a ramp at the edge of the platter, mechanically clear of the surface — which is what parking is for, and it is why drives survive being posted. A drive that is spinning has its heads flying microns above the surface, held there by airflow.
Why that single variable outweighs the rest: a gentle knock while running can bring heads into contact; a harder fall while parked frequently does nothing at all. If it was not running, this fall was probably not the cause — and the failure may be coincidental or the drive may have been marginal already.
What his three tests establish, and it is a thorough control: a laptop, a television and a projector are three different kinds of host with three different device stacks. Failing on all of them eliminates host software far more comprehensively than three computers would, and it is more testing than most enquiries contain.
What the rotation proves: a great deal. The board powered up, regulation worked, the controller initialised and the motor drove the spindle to speed. That is the whole electrical front end confirmed working, and it excludes the family of faults where a drive is silent.
So what is left: the drive spins and does not announce itself, which means it is failing to complete its start-up — unable to read the reserved region holding its own firmware and calibration, or unable to position its heads reliably enough to do so.
Why that is consistent with a mild impact: heads do not have to be destroyed to be degraded. A knock can leave an assembly that positions imprecisely, which is enough to fail a service area read while leaving the drive apparently healthy in every other respect.
What must stop: further connection. Each attempt is a full start-up sequence with head movement, on an assembly that may already be marginal.
On the bench
The operating state at the moment of impact was established before assessment — a parked drive having its heads secured clear of the surface while a spinning one has them flying microns above it, which makes the power state a larger variable than either height or landing surface. Rotation was confirmed by touch, and the readiness sequence read directly under strict timeouts, spin confirming the electrical front end while failure to announce indicates a service area or positioning fault.
The outcome
The operating state established first, rotation confirmed by touch and readiness read under controlled timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: bed height onto carpet is a gentle fall, so the question is whether it was running. Parked heads sit clear of the surface; spinning ones fly microns above it. And your drive turning proves the whole electrical front end works.
Drive that failed after a gentle fall
Work out whether it was powered and connected at the time — that matters more than the height or what it landed on. A switched-off drive has its heads parked on a ramp clear of the platter, which is why drives survive being posted; a spinning one has them flying microns above the surface. So a gentle knock while running can do more than a harder fall while parked, and if yours wasn't running the fall may not be the cause at all. Take encouragement from the rotation: the board, regulation, controller and motor all work. Testing on three different kinds of host was a genuinely strong control. Stop reconnecting it.
Stop connecting it — call Oxford Data Recovery on 01865 593000; operating state at impact established first, rotation confirmed by touch, readiness read under strict timeouts.
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.