Data Recovery Case File · Desktop Externals & Aging Drives · The Cycle Names the Stage
It Is Getting Further Than a Drive That Gives Up
His enquiry describes a loop with three distinguishable steps in it. A drive that has failed: "the disk spins up, I hear the arm moving, and then it cuts out and starts again ad infinitum." Each of those steps is a stage of start-up that succeeded — and reaching head movement before aborting places the fault later in the sequence than a drive that spins and simply stops, which is both more informative and more expensive per minute.
| Media | Hard drive cycling continuously through failed initialisation — rotation achieved, head movement audible, sequence aborting and restarting indefinitely |
| Reported situation | Drive achieving rotation on power · head assembly movement audible following spin-up · sequence terminating shortly afterwards · cycle repeating continuously without intervention · contents required |
| Fault class | Service area read failure with head positioning functional — initialisation aborting after head movement; each cycle repeating positioning attempts |
| Equipment used | No further power-up · cycle timing and stage reached recorded per iteration · readiness sequence read directly under strict timeouts · PC-3000 Express technological-mode service-area assessment · imaging on restored addressing |
The decode: what each step in the cycle confirms
Rotation achieved: the board powered up, regulation worked, the controller initialised, and the motor circuitry drove the spindle to speed. That is the whole electrical front end confirmed working, and it eliminates the family of faults where a drive is silent.
Head movement audible: the drive unparked its heads and began positioning them. That is a further stage — it means the positioning circuitry works and the assembly is capable of movement. The drive has reached the point of trying to read.
What it is trying to read: the reserved region holding its own firmware, calibration parameters and defect map. Every start-up requires that read before the drive can report its capacity or accept a command. Head movement followed by an abort means it went looking and did not find what it needed.
Why cycling rather than stopping: the firmware, having failed, restarts the whole sequence rather than concluding. Some designs give up after a few attempts and power down; others loop indefinitely, which is what he is hearing.
Why this costs more per minute than a simpler failure, and it is the reason to act: a drive that spins and stops does nothing to the surfaces — the heads never leave their parked position. A drive that unparks, positions and retries is moving heads across the platters on every loop, several times a minute, indefinitely. Where the surfaces are damaged or the heads are marginal, that is cumulative.
So the instruction is more urgent than usual: disconnect it. A drive left cycling overnight has performed thousands of positioning attempts for nothing.
Why the position is nevertheless reasonable: the reserved region is entirely separate from where user data lives. A drive that cannot read its own configuration still holds every file — the fault is in a small administrative area, addressed in the drive's technological modes, where damaged modules can be repaired and addressing restored.
What is worth reporting: the cycle length. A loop of two seconds and a loop of fifteen describe different amounts of work being attempted before each abort, and it costs nothing to observe once.
On the bench
No further power-up was attempted, a cycling drive unparking and positioning its heads several times a minute indefinitely, which a drive that simply stops never does. Cycle timing and the stage reached were recorded per iteration — rotation confirming the electrical front end, audible head movement confirming positioning circuitry, and an abort after that placing the failure at the service area read. The readiness sequence was read directly under strict timeouts, with PC-3000 Express technological-mode service area assessment and imaging on restored addressing.
The outcome
The cycle characterised per iteration, the service area repaired and the drive imaged on restored addressing. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: your cycle has three steps and each confirms something. Rotation proves the electrical front end. Head movement proves the positioning circuitry. An abort after that means the drive went looking for its own configuration and did not find it — and every loop repeats the positioning, which a drive that simply stops never does.
Drive cycling through the same start-up repeatedly
Disconnect it now — this failure costs more per minute than most. A drive that spins up and simply stops never moves its heads, so it does nothing to the surfaces. Yours is unparking, positioning and retrying on every loop, several times a minute, and left overnight that's thousands of positioning attempts for nothing. What the cycle tells you is encouraging in itself: rotation proves the board, regulation, controller and motor circuitry all work, and audible head movement proves the positioning circuitry works too. The abort after that means it went looking for its own configuration in a reserved region and didn't find it — and that region is separate from where your files live.
Disconnect it now — call Guildford Data Recovery on 01483 901310; cycle timing recorded per iteration, readiness read under strict timeouts, service area repaired in technological mode.
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.