Data Recovery Case File · Desktop Externals & Aging Drives · One Fault, Two Symptoms
The Message Is a Consequence of the Noise
Her enquiry reports two things and correctly disbelieves the second. An external drive "making an unhealthy sound when plugged in, and now the computer is saying it is not in a format it can read — which I know should not be true." She is right that the format has not changed, and the reason the machine says so is the same reason the drive is making a noise: it cannot read the structures that would tell it otherwise.
| Media | External hard drive previously in normal service — producing abnormal acoustics on connection; host reporting the volume format as unrecognised |
| Reported situation | Drive previously used normally with the same machine · abnormal sound produced on connection · host reporting the volume as being in an unreadable format · owner aware the format has not changed · up to 1TB of content held |
| Fault class | Read failure preventing filesystem interpretation — acoustic symptom and format message arising from a single fault; initialisation prompt present |
| Equipment used | No initialisation permitted at any point · acoustic character established before any conclusion · Atola Insight Forensic error-rate assessment · imaged write-blocked under strict per-sector timeouts · structures rebuilt from surviving copies on the image |
The decode: one fault producing two appearances
What the message actually means: the system went to read the filesystem structures, could not obtain something it needed, and concluded that the volume is not in a format it recognises. It is a report of failure to read, worded as a statement about format — which is why it sounds like an accusation and is not one.
Why her scepticism is correct: the drive was working with that machine, in that format, recently. Formats do not change on their own, and nothing wrote a new one. What changed is the drive's ability to return the structures describing it.
Why the noise explains it: a drive producing abnormal acoustics is a drive struggling to read. The filing structures live in specific regions, and if those regions are among the ones it cannot return, the system gets nothing where it expected a filesystem — and reports exactly what she is seeing. One fault, two symptoms.
What the character of the noise decides: a repeating tone means the motor straining against a stack that will not turn. A click means the head assembly attempting to position and failing. A sustained grinding means contact with the surface, which is the most urgent of the three. Volume matters far less than which of those it is, and describing it accurately is worth more than any other observation available.
Why the message is dangerous rather than merely wrong: it arrives with an offer to initialise the disk, worded as preparing it for use. Accepting writes a fresh filesystem over the region a reconstruction reads, and it will be offered on every connection. That prompt is the single most costly button in this archive.
Why she must stop connecting it: whichever noise it is making, the drive is doing something it cannot complete, and every connection repeats it. A drive that grinds is removing surface material each time, and the position after ten attempts is materially worse than after one.
Why the position is nevertheless reasonable: the content occupies the great bulk of the drive and the structures occupy a small defined region. Content is unaffected by a failure to read a description of it, and reconstruction against a captured image is routine — provided the capture happens before the mechanism deteriorates further.
On the bench
No initialisation was permitted at any point, that prompt writing a fresh filesystem over the region a reconstruction reads. Acoustic character was established before any conclusion — a repeating tone indicating a stalled motor, a click indicating failed head positioning, and sustained grinding indicating surface contact, which is the most urgent. The Atola Insight Forensic assessed error rates, imaging ran write-blocked under strict per-sector timeouts, and structures were rebuilt from surviving copies on the image.
The outcome
No initialisation permitted, the acoustic character established before any conclusion, and the structures rebuilt from a write-blocked image. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: you are right that the format has not changed. That message reports a failure to read, worded as a statement about format — and the noise is why. The drive cannot return the structures describing its own filesystem, so the system finds nothing where it expected one.
Drive making a noise while the computer questions its format
Refuse the offer to initialise, and stop connecting it — those two are the whole of what you can do usefully. You're right that the format hasn't changed: that message reports a failure to read the filesystem structures, worded as a statement about format, and the noise is the explanation. The drive can't return the regions describing its own volume, so the system finds nothing where it expected one. Two symptoms, one fault. Which noise it is matters more than how loud: a repeating tone is a stalled motor, a click is failed head positioning, and sustained grinding is contact with the surface, which can't wait.
Refuse to initialise it — call Oxford Data Recovery on 01865 593000; acoustic character established before any conclusion, error rates measured, imaged under strict per-sector timeouts.
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.