Data Recovery Case File · Desktop Externals & Aging Drives · The Same Failure, Repeated
A Spin-Up Loop Means the Drive Gets Partway Every Time and Abandons at the Same Point
This enquiry is specified with unusual care — model, firmware revision, capacity, original housing — and its most useful line is the behaviour. The drive "spins up, runs for a few seconds with a faint grinding noise, then slows down and retries." A loop is different from a failure: the drive reaches operating speed, attempts something, gives up and starts over, which locates the fault at a specific stage rather than at the beginning.
| Media | 500GB hard drive originally supplied in an external housing — cycling repeatedly through spin-up, brief operation with audible contact, deceleration and restart; not enumerating |
| Reported situation | Drive supplied with full model, firmware revision and capacity details · originally installed in an external enclosure · drive powering on · reaching operating speed and running briefly · faint grinding audible during that interval · drive decelerating and repeating the cycle · not becoming accessible to the host |
| Fault class | Initialisation failing at a consistent stage with audible head-to-surface contact — service area unreadable or heads degraded; repetition extending contact damage |
| Equipment used | Cyclic behaviour interpreted as consistent failure at one stage rather than as intermittent operation · no further power-up permitted · laminar flow bench inspection with head and platter surfaces assessed before any rotation · matched donor head assembly as indicated · service area read under strict timeouts in vendor technological modes |
The decode: what a loop establishes, and why the grinding makes it urgent
What reaching operating speed proves: the motor and its drive circuit work. A drive that spins up has a functioning spindle, bearing and power stage, which excludes a whole category of fault at the outset.
What happens in the few seconds that follow: initialisation. The drive moves its heads to a reserved region and reads its own configuration — calibration values, defect maps and the parameters it needs before it can describe itself.
Why failing there produces a restart rather than an error: the drive has nothing to report to. It has not yet identified itself to the host, so it cannot say anything went wrong — it simply resets and tries the sequence again.
Why the repetition is the informative part: it is identical each time. A drive failing at random points would behave differently on each attempt; one that runs for the same few seconds is failing at the same stage.
What that rules out: an intermittent connection or a marginal supply. Those produce variable behaviour, and this is consistent.
What the grinding indicates, and this is the urgent part: contact. A faint grinding while the platters turn is a head touching the surface, which is not something that improves with repetition.
Why the loop therefore compounds the damage: each cycle repeats the contact. The drive is dragging a head across the reserved region it is trying to read, every few seconds, for as long as it is powered.
Why that region specifically matters: it holds the drive's own configuration. Damage there prevents the drive from ever starting properly, independently of whether user content is intact.
Why the enclosure history is worth knowing: the drive was supplied inside a housing. Some external drives use a controller that encrypts or remaps at the enclosure level, so the original housing should be retained rather than discarded.
What must not happen: no further powering at all. Every minute connected is more contact on the one region the drive must read to work, and the loop will continue indefinitely because nothing stops it.
On the bench
Cyclic behaviour was interpreted as consistent failure at one stage rather than as intermittent operation — reaching operating speed establishing a functional spindle, bearing and power stage, after which the drive reads its configuration from a reserved region before it can identify itself, so failure there produces a silent reset rather than a reported error. Identical timing on each cycle excludes connection and supply variability. Audible contact during rotation indicates a head touching the surface, extended by every repetition. No further power-up was permitted.
The outcome
Cyclic behaviour read as consistent single-stage failure, further powering stopped, and surfaces assessed under filtered air before any rotation. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: a loop is not intermittent operation. Your drive reaches speed, fails at the same point, resets and repeats — and the grinding during each attempt is contact on the very region it needs to read.
A drive that keeps restarting its own start-up
Unplug it and leave it unplugged. A loop repeats the same failure every few seconds for as long as power is applied, and the faint grinding you can hear is a head touching the surface during each attempt — so the damage accumulates while you listen to it. Read the pattern as useful, though: reaching speed proves the motor, bearing and power stage all work, and identical timing on each cycle rules out a loose connection or a marginal supply. Keep the original enclosure rather than discarding it.
Unplug it — call Cambridge Data Recovery on 01223 655015; the loop read as consistent single-stage failure, surfaces assessed under filtered air before rotation, 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.