Data Recovery Case File · Desktop Externals & Aging Drives · A Failure in Stages

It Failed Mid-Transfer and Never Came Back

His enquiry recorded a sequence rather than a symptom, which makes it readable. A 3TB Seagate Barracuda used as a second drive in a PC: "I was copying files from it and noticed it kept stopping and the transfer would fail. It made a noise once and is now not being recognised. I tried transferring to another PC but it was not recognised there either. The drive does feel and sound like it is spinning but is not being recognised." Three stages in order — stalling transfers, one noise, then nothing — and the order tells you more than any single stage would. This drive announced itself before it stopped, and the stalling copies were the announcement.

The decode: what each stage was, and what spinning still proves

Stage one — stalling transfers. A copy that keeps stopping and failing is a drive failing reads. Each stall was the operation waiting on a sector that would not answer, and each failure was it giving up. That was the drive telling him it had developed unreadable regions, in the clearest way available — and it was the window in which a prioritised copy would have saved the most. Nobody is told to read it that way, which is why this page exists.

Stage two — the single noise. One audible event during a period of read failures is consistent with the head assembly attempting a recovery action — a recalibration, or a retract and reload — which drives perform when reads are failing badly. It is the mechanism intervening rather than a new fault appearing.

Stage three — no recognition. After that, the drive stopped presenting itself. Combined with the fact that it still spins, that places the failure in a specific place: the motor and bearings are fine, so what has failed is one of the silent stages that follow spin-up — head calibration against the servo patterns, or reading the reserved region holding the drive's firmware and translation tables. A drive that cannot complete those never reports a capacity and so never appears, which is exactly what two computers now show.

Why the second computer mattered: he tested elsewhere, which eliminates the original machine, its ports and its drivers in one step. The behaviour is the drive's, consistently, and there is nothing further home testing can establish.

Why the reserved region is the likely culprit: it is not merely a guess. That region contains, among other things, the defect list the drive updates as it retires bad sectors — so a drive that has been actively failing reads has been writing to it. An update to that area interrupted or written to a degrading surface is a common way for a drive to go from struggling to silent, and it explains the progression precisely.

Why the outlook is reasonable: none of that touches the user area. His files sit where they were written, waiting for a drive that can address them. Service-area faults are worked through the manufacturer's own technological modes, and the surface damage that caused the original stalling is handled by patient imaging with timeouts.

On the bench

The Atola Insight Forensic read the readiness sequence and surface condition directly — establishing how far the drive progressed after spin-up and where its reads were failing, which converts his three-stage account into a located finding. Access followed through the PC-3000 Express in the drive's technological modes, with the service area read directly and its damaged modules repaired until the drive identified itself and would address its media. Imaging then ran under Data Extractor with strict timeouts, the healthy expanse captured first and the regions that had stalled his copies revisited on later patient passes.

The outcome

The service area repaired, media addressing restored and the contents imaged with losses named per file. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone whose drive failed in stages: stalling transfers are a drive failing reads, and that is the announcement — the window in which a prioritised copy saves the most; a single noise during that period is usually the mechanism attempting a recovery action rather than a new fault; and a drive that still spins but is no longer recognised has a working motor and a failure in the silent stages after spin-up, commonly the reserved firmware region, which a drive actively retiring bad sectors has been writing to. None of that touches your files.

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.