Data Recovery Case File · Desktop Externals & Aging Drives · A Counted Sequence
A Bounded Number of Attempts Is the Firmware's Own Limit, Not the Drive Wearing Out
His description is unusually exact and the exactness is what makes it readable. A drive from 2008 that "will not spin up — when power is initially applied it spins for approximately five seconds, the heads move three times across the platter, then the drive spins down" and nothing recognises it. Three is a programmed number rather than a coincidence: the drive is making a fixed set of attempts at something and then stopping deliberately.
| Media | Desktop hard drive of 2008 manufacture — spinning for approximately five seconds, performing three positioning attempts, then powering down; not enumerating |
| Reported situation | Drive of 2008 manufacture ceasing to function · rotation commencing on power application · rotation continuing for approximately five seconds · three positioning movements observed · drive powering down thereafter · not recognised by the host |
| Fault class | Initialisation failing at a bounded retry limit — service area unreadable or head degradation preventing configuration retrieval; sequence terminating by design rather than by failure |
| Equipment used | Bounded retry count interpreted as a firmware limit rather than as progressive failure · no further power-up permitted · current draw measured across the start-up cycle on a controlled bench supply · service area read under strict timeouts in vendor technological modes · laminar flow bench inspection with head condition assessed before sustained rotation |
The decode: what the three attempts are, and why counting them matters
What a drive does in its first seconds: reads about itself. Once at speed, it moves its heads to a reserved region to retrieve calibration values, defect maps and the parameters it needs before it can describe itself.
Why the head movements he counted correspond to that: each is an attempt. A positioning movement followed by a return and another movement is the drive trying the same read again.
Why the number is fixed rather than variable: the firmware decides. Drives are programmed to attempt initialisation a set number of times and then stop, rather than continuing indefinitely.
Why stopping is deliberate and sensible: continuing would do harm. A drive that cannot read its configuration gains nothing from trying forever, and spinning with heads repeatedly seeking costs wear.
Why that distinguishes his drive from a worse case: a bounded sequence is controlled. A drive cycling endlessly is repeating damage; one that tries three times and powers down has protected itself.
What the failure to read the reserved region indicates: two possibilities. Either that region has become unreadable, or the heads are no longer capable of reading it.
Why the drive's age is relevant to which: it is old. A drive manufactured in 2008 has had many years for head degradation and for the reserved region to weaken.
Why reaching speed at all is encouraging: the mechanics work. Five seconds of rotation establishes a functioning motor, spindle and power stage.
Why the user content is untouched by any of this: the reserved region is separate. A drive unable to describe itself has said nothing about the state of the recording.
What must not happen now: no further attempts. Each one is three more head movements over the region the drive is struggling to read.
On the bench
The bounded retry count was interpreted as a firmware limit rather than as progressive failure — a drive at speed moving its heads to a reserved region for calibration values, defect maps and parameters, with each observed movement an attempt at that read, and firmware programmed to make a set number before stopping rather than continuing indefinitely. A bounded sequence is therefore self-protective. Service area was read under strict timeouts in vendor technological modes.
The outcome
The retry count read as a firmware limit, further powering stopped, and head condition assessed before sustained rotation. 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: counting them was the useful part. Three is a programmed limit — your drive attempted to read its own configuration a fixed number of times and then stopped itself, which is protection rather than collapse.
Counting what a drive does before it gives up
Describe the sequence precisely, as you have — how long it spins and how many movements you hear before it stops is genuinely readable. Each movement is the drive attempting to read the reserved region holding its own configuration, and the count is a programmed limit rather than the drive wearing out mid-attempt. Stopping deliberately is self-protective. Reaching speed at all establishes the motor and spindle work, and none of it says anything about your files.
That count is deliberate — call Cambridge Data Recovery on 01223 655015; the sequence read as a firmware limit, draw measured across the start-up cycle, service area 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.