Data Recovery Case File · Second Fixes & Trade Handoffs · The Count Is Consistent
The Same Number of Attempts Every Time Means the Drive Fails the Same Way Every Time
His enquiry contains a precise and unusually useful observation. A drive removed from an external enclosure that "fails to register in the firmware during boot up — five clicks can be heard every time the computer boots." The consistency is the informative part. A fixed count repeated identically at every start-up describes a drive following its own retry logic to a limit and stopping, which is a specific and readable failure.
| Media | 2TB hard drive removed from an external enclosure holding approximately 1TB of content — not registering in host firmware; five repeating sounds at each start-up |
| Reported situation | Drive removed from an external enclosure and installed internally · approximately 1TB of content held · drive not registering in host firmware at start-up · five repeating sounds audible at every boot · count consistent between attempts · recovery quotation sought |
| Fault class | Head positioning failure with bounded retry — consistent count indicating retry limit reached and initialisation abandoned; board logic functional |
| Equipment used | Consistent retry count interpreted as bounded initialisation failure · no further boot attempts permitted · laminar flow bench inspection with head and surface assessment before any spin attempt · matched donor assembly as indicated · single controlled read pass and imaging in one supervised session |
The decode: what a fixed count tells you that an unspecified sound does not
Why the number matters: most people report a drive as clicking without noticing how many times. A count that is the same at every start-up means the drive is following a defined sequence and reaching a defined stopping point — it is not failing randomly, it is failing systematically.
What that sequence is: the drive attempts to position its heads and read its own configuration, fails, resets, and tries again — up to a limit set in its own logic. Reaching that limit, it stops and reports nothing, which is why the machine's firmware never registers it.
Why that is mildly reassuring: the board is working well enough to run the sequence, count the attempts, apply the limit and stop cleanly. The electronics and the drive's own logic are functioning — the failure is in what the attempts are trying to achieve.
What the sounds themselves are: the head assembly moving and being reset. Each cycle is heads attempting to reach position, not succeeding, and returning to try again — audible because it is mechanical.
What that narrows the cause to: either a head assembly that can no longer position correctly, or a region of the drive holding its configuration that cannot be read. Both produce identical bounded-retry behaviour, and they require very different interventions — one needs matched donor parts under filtered air, the other does not require opening the drive at all.
Why only inspection settles which: from outside, the two are indistinguishable. The difference in cost and invasiveness is substantial, which is why the drive is assessed before any parts are sourced.
Why the enclosure history is worth noting: the drive was previously in an external case and has been moved inside a machine. Where an external bridge board applied any transformation to the data, reading the drive directly can present differently — though that would not cause the sounds, which are unambiguously mechanical.
Why every boot has a cost: the count repeating at each start-up means five failed positioning attempts each time the machine is turned on. A drive that has been booted many times has performed that sequence many times, and heads attempting to position on a drive that cannot position are heads moving where they should not.
What follows practically: the drive should be disconnected from the machine rather than left installed. Leaving it in place means it repeats the sequence at every start-up, indefinitely — which is a cost paid for no information, since the behaviour is already known.
On the bench
The consistent retry count was interpreted as bounded initialisation failure — an identical number of cycles at every start-up indicating the drive following defined retry logic to a set limit and abandoning initialisation cleanly, which establishes that board electronics and drive logic are functional while positioning or configuration reading is not. Each cycle represents head movement and reset. Inspection ran under the laminar flow bench with head and surface assessment before any spin attempt, distinguishing head assembly failure from an unreadable configuration region.
The outcome
The consistent count read as bounded initialisation failure, no further boot attempts permitted, and the drive inspected 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: the count being the same every time is the useful detail. It means the drive runs its retry logic, reaches its limit and stops — so the electronics work, and the fault is either the heads or the region holding its configuration.
A drive that makes the same number of sounds every start-up
Take the drive out of the machine rather than leaving it installed — every boot repeats the whole failed sequence, and that's a cost paid for information you already have. The consistency is worth noticing: an identical count each time means the drive is following its own retry logic to a set limit and stopping cleanly, so the electronics and logic are working. What's failing is either the head assembly's ability to position, or the drive's ability to read the region holding its configuration. Those need very different work — one requires opening the drive and fitting donor parts, the other doesn't — and only inspection tells them apart.
Disconnect it — call Easy Data Recovery on 028 9002 0144; consistent count read as bounded initialisation failure, inspected under filtered air before any spin attempt, single controlled read pass.
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.