Data Recovery Case File · Desktop Externals & Aging Drives · The Whole Cycle Repeats
A Drive Spinning Down and Starting Again Is Restarting Its Entire Sequence
His enquiry describes a cycle rather than a noise. A drive not recognised on his laptop, removed and tried in a caddy on another machine with the same result, where "the platter spins then stops and spins and stops." That is a different event from a repeated click: the whole start-up sequence is being abandoned and begun again, which places the failure at a specific and comparatively hopeful point.
| Media | Laptop-format hard drive removed from its host and tested externally — rotation commencing, ceasing and recommencing in a repeating cycle; not enumerating on either host |
| Reported situation | Drive not recognised on the owner's laptop · drive removed and fitted to an external caddy · tested on a second machine · not recognised there either · rotation observed to start, stop and start again repeatedly · content required |
| Fault class | Start-up sequence abandoned and retried — spin-down following failure to complete initialisation; commonly configuration-region or head-related rather than motor failure |
| Equipment used | Spin cycling distinguished from head impulse sounds to locate the failure · current draw measured across successive cycles on a controlled bench supply · service area read under strict timeouts over a diagnostic interface · laminar flow bench inspection where head involvement was indicated · imaging in one supervised session once initialisation completed |
The decode: what the cycle is, and why it is not the motor
What a drive does when it powers: brings the platters to speed, moves the heads out over the surface, reads its own configuration from a reserved area, checks the result, and only then reports itself. Failure at any of those steps aborts the sequence.
What it does when the sequence aborts: spins down and tries the whole thing again. That is designed behaviour rather than a malfunction — a drive that cannot complete initialisation retries from the beginning, which produces exactly the pattern he describes.
Why the motor is very unlikely to be the problem: it is achieving speed each time. A drive with a seized or failing spindle does not spin at all, or struggles audibly and never reaches speed — this one is starting successfully and then choosing to stop.
Why that distinction is worth drawing carefully: repeated spinning looks like a motor problem to anyone watching. The repetition is the drive's own retry logic rather than a mechanism failing, and the actual fault is at whatever step keeps failing.
What that step usually is: reading the configuration from the reserved area. That data lives on the platters in a region the user never touches, and if the heads cannot read it — because the region has degraded or a head is not working — initialisation cannot complete.
Why that is comparatively hopeful: the user data area is not involved. The drive is failing at a step that happens before anything of his is read, so the recording is untouched by the fault.
Why some of these are resolved without opening the drive: where the configuration region is the problem, the drive can be addressed in its own diagnostic modes and the region worked with directly. No donor parts and no entry into the sealed assembly — among the least invasive interventions available.
Why the alternative is worth naming too: if a head cannot read that region because the head itself has failed, the work requires a matched donor assembly. The distinction is made by measurement rather than by observation, and it changes the terms.
What his caddy test contributed: a different host, a different connection and a different power path. Identical behaviour across both means the fault travels with the drive — established at no cost and not worth repeating.
Why the cycling must be stopped now: each cycle is a full spin-up and a head movement across the surface. Leaving it connected repeats that indefinitely, and if a head is involved, every pass is a pass over the recording.
On the bench
Spin cycling was distinguished from head impulse sounds to locate the failure — a drive bringing platters to speed, positioning heads, reading configuration from a reserved area and checking it before reporting itself, with failure at any step aborting the sequence and prompting a full retry, which is designed behaviour. Achieving speed each cycle excludes spindle failure. The reserved configuration region lies outside the user data area. Service area was read under strict timeouts over a diagnostic interface.
The outcome
The cycling distinguished from head impulse behaviour, draw measured across successive cycles, and the configuration region read over a diagnostic interface. Free assessment, one fixed written figure including VAT, with 50% of parts and labour payable upfront where the drive is opened and the balance only on success. The decode: the repetition is the drive's own retry logic rather than the motor failing — it reaches speed every time. What it cannot finish is reading its configuration, which lives outside the area holding your files.
A drive that spins up, stops, and starts again
Disconnect it, because each cycle is another full spin-up and another head movement across the surface. Read the pattern correctly: repeated spinning looks like a motor problem, but the drive is reaching speed every time and then choosing to stop — that's its own retry logic after failing to complete initialisation. A genuinely failing spindle wouldn't reach speed at all. What usually fails is reading the configuration from a reserved region of the platters, which sits outside the area holding your files, so the recording isn't implicated by the fault.
Disconnect it — call Manchester Data Recovery on 0161 871 0788; spin cycling distinguished from head impulse behaviour, draw measured across cycles, configuration region read over a diagnostic interface.
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.