Data Recovery Case File · Desktop Externals & Aging Drives · Count Them
A Repeating Pattern Is a Routine, Not Damage
His enquiry does something almost nobody does: it counts. A portable drive of five years, checked occasionally, which on connection "spins and emits 5, sometimes 6, pulses or knocking sounds, followed by 2, then 2 again." That structure is the most useful thing in the message — because random noise and a repeating sequence mean quite different things, and a drive executing a defined pattern is a drive whose firmware is still in control.
| Media | Portable external hard drive of approximately five years, intermittently used — achieving rotation; producing a structured repeating acoustic sequence on power |
| Reported situation | Drive of approximately five years in occasional use · rotation achieved on connection · repeating sequence of positioning sounds produced · sequence structured in consistent groups · drive not presenting · contents required |
| Fault class | Service area read failure with head positioning functional — firmware retry routine executing to a defined sequence; dormancy effects present |
| Equipment used | Acoustic sequence recorded and grouped before any conclusion · rotation confirmed by touch · readiness sequence read directly under strict timeouts · PC-3000 Express technological-mode service area assessment · imaging on restored addressing |
The decode: why counting matters
What random noise indicates: irregular scraping, grinding, or knocks at inconsistent intervals suggest a mechanism that is not doing what it intends — heads contacting a surface, debris in the assembly, or a bearing failing. There is no routine behind it, and it is the more serious family of sounds.
What a structured sequence indicates instead: firmware. Groups of a consistent size, repeating in a consistent order, is code executing — a retry routine running to a defined number of attempts, then changing strategy, then trying again. Each knock is the head assembly being commanded to a position.
What the drive is trying to do: read the reserved region holding its own firmware, calibration data and defect map. It cannot report a capacity or accept a command until it has. The five or six attempts are positioning tries at the expected location; the pairs that follow are typically recalibration attempts, repositioning against a reference before trying once more.
Why that is the better of the two positions: the heads are moving to command, the motor is turning, and the firmware is running its own error handling. All of that has to work for a pattern to exist at all. The failure is at the read, not at the mechanism — and the reserved region is a small administrative area entirely separate from where his photographs live.
Why the count is worth reporting: different manufacturers use different retry structures, and the shape of the sequence indicates which stage is failing. Nobody else in this archive has counted, and it takes one listen.
Why it must not be repeated: every cycle is another set of positioning movements across the platters. A drive left connected runs the routine indefinitely — several times a minute, for as long as it has power, achieving nothing.
What the five years and the occasional use add: a drive stored between uses has lubricant that has had time to thicken and heads that have rested. Occasional checking is better than none, and it is not the same as regular operation — which is worth knowing rather than regretting.
What is done about it: the reserved region is addressed in the drive's technological modes, where damaged modules can be repaired and addressing restored, after which it images conventionally.
On the bench
The acoustic sequence was recorded and grouped before any conclusion — irregular scraping indicating a mechanism not doing what it intends, while consistent groups repeating in order indicate firmware executing a retry routine, with the initial group representing positioning attempts at the expected location and subsequent pairs typically recalibration. Rotation was confirmed by touch, readiness read directly under strict timeouts, and PC-3000 Express technological-mode assessment performed on the service area.
The outcome
The sequence grouped and characterised, the service area addressed in technological modes 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: counting was the right thing to do. Irregular noise suggests a mechanism failing; consistent repeating groups mean firmware running a retry routine, which requires the motor, the head positioning and the error handling all to be working. Your fault is at the read, in a small reserved area.
Drive making a repeating pattern of sounds
Count them once, then disconnect it — the count is genuinely useful and every cycle costs. A structured sequence is better news than irregular noise: random scraping or knocks at inconsistent intervals suggest a mechanism not doing what it intends, while consistent groups repeating in a consistent order mean firmware executing a defined retry routine, which requires the motor, head positioning and error handling all to be working. Your drive is trying to read the small reserved region holding its own configuration, failing, and retrying to a set pattern. That region is entirely separate from where your files live. Leave it connected, though, and it runs that routine several times a minute indefinitely.
Count it once, then stop — call Oxford Data Recovery on 01865 593000; sequence recorded and grouped before any conclusion, 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.