Data Recovery Case File · Formatted & Logical Faults · Two Reports of One Event
The Board Code and the Sound Describe the Same Failure From Two Sides
His enquiry pairs a machine's own diagnosis with what he could hear. A start-up code indicating the drive could not be read, alongside "an odd clicking sound which repeated three times", leading him to conclude the read head may have stopped working. Both observations are describing one event — the drive attempting to start, failing three times, and giving up — and his conclusion from them is a reasonable reading.
| Media | 2TB desktop hard drive — host start-up code reporting failure to read the drive; three repeating mechanical sounds at power-up |
| Reported situation | Machine displaying a start-up code indicating the drive could not be read · drive producing a repeating sound three times at power-up · owner concluding head failure from published symptom guidance · duration and cost of recovery queried |
| Fault class | Head positioning failure with bounded retry — repeating sound limited to a fixed count indicating the drive abandoning start-up; firmware and mechanical causes to be separated |
| Equipment used | Start-up code and audible sound reconciled as one event · bounded retry count interpreted as the drive abandoning initialisation · 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 three attempts means, and why the count matters
What the machine's code is reporting: its start-up routine tried to communicate with the drive and could not. That happens before any operating system, so it is a device-level observation and it eliminates every software explanation in one line.
What the sound is: a mechanical action failing and being retried. Heads attempting to reach their position, not succeeding, resetting and trying again — audible because it is physical.
Why the two are one observation: the drive could not read itself, so it could not identify itself, so the machine reported failure. The sound is the drive's attempt and the code is the machine's account of that attempt failing — not two faults, one fault seen from inside and outside.
Why the count of three is genuinely informative: the sound repeats a fixed number of times and stops. That is a drive with a retry limit reaching it and abandoning initialisation, rather than one cycling indefinitely — which tells us the drive's own logic is working and reaching a conclusion.
Why that is mildly encouraging: the board is functioning well enough to run its start-up sequence, count its attempts and stop. The failure is in what the attempts are trying to achieve, not in the drive's ability to attempt.
Why his conclusion is plausible but not established: a bounded retry with no successful start is consistent with a head fault. It is equally consistent with a firmware region the drive cannot read — where the mechanism is sound and the drive still cannot complete initialisation, which needs no donor parts at all.
Why the distinction is worth the assessment: one requires opening the drive and fitting matched donor parts; the other is addressed in the drive's own technological modes without opening it. The difference in cost and invasiveness is substantial, and only inspection settles it.
What determines how long the work takes, since he asks: which of those it turns out to be, and whether donor parts must be sourced. A firmware route is short; a head replacement depends on locating a compatible donor for the specific model, which is the variable part.
What must not happen while waiting: no further start-up attempts to reproduce the sound. Each power-up is another three failed positioning attempts, and where heads are the problem, those attempts are made across the surfaces holding the data.
On the bench
The start-up code and audible sound were reconciled as one event — host firmware reporting failure to communicate at a stage preceding any operating system, while the repeating sound represents positioning attempts failing and retrying, the code being the machine's account of what the sound is the drive performing. A bounded retry count was interpreted as the drive abandoning initialisation, indicating functional board logic reaching a limit. Inspection ran under the laminar flow bench before any spin attempt.
The outcome
The code and sound reconciled as one event, the bounded retry read as abandoned initialisation, 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: those are two views of one failure. The sound is the drive attempting to start and the code is your machine reporting that it did not — and stopping after three tries means the drive's own logic is working and reaching a limit.
A start-up code and a sound from the drive
Treat them as one observation rather than two faults — your machine's code reports that it couldn't communicate with the drive, and the sound is the drive's failed attempt to get far enough to answer. A sound that repeats a fixed number of times and stops is mildly encouraging: it means the drive's own logic is running, counting its attempts and abandoning initialisation, rather than cycling endlessly. Head failure is a fair reading of it, but an unreadable firmware region produces the same picture with the mechanism intact and needs no donor parts. Stop powering it up to reproduce the sound, since each attempt repeats the failure.
Stop restarting it — call Easy Data Recovery on 028 9002 0144; code and sound reconciled as one event, bounded retry read as abandoned initialisation, inspected under filtered air before any spin attempt.
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.