The "blue light turns on", the computer plays its connection sound, and then the drive "does not show up" before it "times out" and disconnects. On it are freelance footage and personal files. This is the awkward middle ground: not a dead drive, and not a working one, but a drive that can start a conversation and cannot finish it. Something — weak heads, a struggling controller, a patch of sectors that will not answer — is causing reads to stall, and after a set period the operating system stops waiting and drops the device. Left plugged in, it will do this all afternoon, and each cycle is another run at whatever it is failing to read.
| Media | A 4TB external hard drive that powers up with its indicator and connection chime, never appears, then times out and disconnects. Holding freelance footage and personal files. |
| Reported situation | 4TB external drive · blue indicator on · device-connected sound heard · never shows up · times out and produces a disconnect alert · freelance footage and personal files wanted. |
| Fault class | Unstable reads — the drive powers and is briefly detected but cannot sustain a stable read, whether from weakening heads, a faltering controller or unreadable sectors, so it times out and drops off. Data generally intact and reached by read-only imaging in controlled passes. |
| Equipment used | Read through a hardware write-blocker on equipment built for unstable media · imaged out to DeepSpar with PC-3000 UDMA behind it in controlled passes, cooperative regions secured first and weak regions approached gently with retries capped so the drive is not stressed · the heads assessed and addressed under laminar flow had they proved to be the cause · the filesystem worked through in R-Studio, the footage validated and written to fresh media. |
The connection chime is genuinely useful information. It means the drive powered up, negotiated with the computer and identified itself — which rules out a dead board, a dead motor and a completely failed head stack in one go. What follows the chime is where it falls over: the computer asks for the partition table and the filesystem, the drive stalls trying to read them, and after a fixed timeout the operating system decides the device has gone and disconnects it.
Stalling on reads has a short list of causes. Heads that are weakening will read some tracks and struggle on others. A controller or bridge board that is faltering will drop mid-transfer. And a patch of sectors that has become unreadable will produce very long retries in exactly the place the computer needs to look first, which is why the drive gets past the introduction and no further.
The important part is what ordinary software does with this, which is the wrong thing. Copying tools and imaging utilities ask for the whole device in order at speed, hit the difficult region, retry endlessly and hang — meanwhile the drive keeps working the one area it cannot manage. Bench imaging inverts it: read everything that is cooperating, secure that first, then go back to the awkward regions gently with retries limited. On a four-terabyte drive that is a great deal of footage secured before anything risky is attempted at all.
It went behind a hardware write-blocker in line on equipment intended for unstable media rather than onto a general-purpose imaging tool. Imaging ran on DeepSpar behind PC-3000 UDMA in controlled passes: the cooperative regions were read first and secured, then the weak areas were approached gently with retry counts capped so the drive was never left grinding. The filesystem was worked through in R-Studio from the image, and the footage was played rather than merely listed before it went onto fresh media.
Imaged in controlled passes, the footage and personal files recovered out onto fresh media, with the small unreadable region itemised so the customer knew exactly what was and was not there. The diagnostic cost nothing; the figure that followed was fixed, written and inclusive of VAT. The drive read without needing to be opened, which kept it on no fix, no fee terms; had the heads proved to be the cause, clean-air work would have meant half the quote in advance and that would have been said first.
Unplug it rather than leaving it to keep trying. A drive that gets as far as a connection chime and then times out is reading unstably, and every disconnect-reconnect cycle sends it back at the same region it could not manage last time — which is how a mostly recoverable drive becomes a partly recoverable one. Do not run copy tools or general imaging software at it, because those ask for everything in order at speed and hang on the first difficult patch while the drive keeps grinding away at it. Unstable media needs the good areas secured first and the awkward ones approached last, gently, with limited retries. And if any part of it matters commercially, mention that when you ring so the recovery can be ordered accordingly.
Every case file here is written up from a real enquiry handled for households and businesses across Norwich and Norfolk, anonymised so that nobody is identifiable. Each sets out the reasoning behind the diagnosis and the method used on that particular fault, with the equipment named.
Intermittent is not lucky, it is a countdown — and the silence at the end of it is the motor or the heads
Two noises, two facts: the whir says the motor is fine, the click says the heads are not
Spinning is not the same as ready — a drive with damaged structures never gets as far as introducing itself
Diagnosis costs nothing and takes up to 2 working days from arrival, the quote is fixed in writing, and logical work runs no fix, no fee — start online or ring the freephone.