Data Recovery Case File · Desktop Externals & Aging Drives · When the Owner Is Right
Hard Drive Spins but Is Never Recognised
His enquiry arrived with a diagnosis attached, and the diagnosis was correct — which is worth saying, because this archive spends a good deal of its time gently correcting people's guesses. A Western Digital 2TB drive: "the drive is not old. It is spinning up normally when taken out and put in a caddy. It appears the drive controller is not allowing it to be recognised." He reached that from symptoms alone, and it is very likely right. A drive that spins normally and is never recognised has completed the mechanical part of its start-up and failed at the electronic part — which is a specific, well-understood and entirely recoverable class of fault. This page sets out what his controller is actually failing to do, why the caddy test was the right test, and why not old is no protection at all.
| Media | Western Digital 2TB 3.5-inch hard drive — spins up normally when connected via a caddy; never presented to the host; drive relatively recent |
| Reported situation | Drive removed from its original machine and tested independently in a caddy · normal spin-up observed · no recognition on any host · owner attributing the fault to the drive's controller |
| Fault class | Failure to complete initialisation — service-area or firmware fault preventing identification; mechanism and motor confirmed functional |
| Equipment used | Atola Insight Forensic power-on current signature and readiness diagnostics · PC-3000 Express technological-mode service-area access and module repair · Data Extractor head-mapped imaging · volume rebuilt from the image and verified |
The decode: what the controller is failing to do, and why age is no defence
What normal spin-up establishes: a great deal. The motor works, the bearings turn freely, the power delivery is sound, and the board is functional enough to energise the mechanism. That eliminates the seized, stuck and dead-board categories in one observation — all of the faults that produce beeping, silence or a drive that does nothing. His drive has cleared the mechanical hurdle entirely.
What happens next, silently: spin-up is the first act of a longer sequence, and everything after it is inaudible. The heads must unpark and perform calibration seeks against servo patterns on the platters. Then the controller must read the drive's service area — a reserved region, invisible to any operating system, holding the drive's firmware modules, its defect maps and the translation tables that convert logical addresses into physical locations. Only when that has been read successfully can the drive identify itself and address its own media. A failure there produces precisely his symptom: a drive that spins beautifully and never announces itself. So his instinct that "the controller is not allowing it to be recognised" is accurate — the controller is unable to complete the reads it needs before it can speak.
Why the caddy test was the right test: removing the drive from its original machine and powering it independently eliminates the host's motherboard, ports, cabling and configuration in one step, and it also let him observe the spin-up directly, which he could not have done inside a closed machine. Two useful findings from one action. The important qualification is that a caddy tests presence, not health — and that repeated attempts are worth avoiding, because a drive failing to read its own service area is retrying that read every time it is powered.
Why "not old" is no protection: worth saying, because it is a common and reasonable assumption. Firmware and service-area faults are not wear-related. They arise from an interrupted write to the reserved area during a power event, from a defect-list update that did not complete, or from a firmware bug — none of which requires years of service. A drive can develop this fault in its first month. Age affects mechanical wear; it has very little bearing on this class of failure.
Why it is recoverable: nothing described here touches what is written on the platters. Service-area faults are addressed through the manufacturer's own technological modes — the reserved regions read directly, damaged modules repaired or regenerated until the drive will identify itself and address its media. The moment it does, it is imaged completely, and everything else happens on the copy.
On the bench
The Atola Insight Forensic read the start-up sequence electrically rather than by listening to it — power delivery, spin-up, the calibration attempts and their outcome, and the exact point at which progress stopped — which turned his inference into a located finding. Access followed through the PC-3000 Express in the drive's technological modes: the service area read directly and its damaged modules repaired until the drive identified itself and would address its own media. Imaging began immediately under Data Extractor, head-mapped and complete, before the drive was asked for anything further. The volume was rebuilt from the image, verified by opening, and delivered on fresh media.
The outcome
The service area repaired, the drive imaged completely and the contents verified and delivered. 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. His diagnosis, confirmed and expanded: a drive that spins normally and is never recognised has cleared the mechanical stage and failed at the electronic one, because everything after spin-up — head calibration and reading the drive's own reserved firmware area — happens silently; testing it in a caddy correctly eliminates the host and lets you hear the spin-up, though repeated attempts repeat the failing read; and a drive being new is no defence, because service-area faults come from interrupted writes and firmware problems rather than from wear.
Drive spins perfectly and is never recognised
Take the normal spin-up as genuinely good news: the motor, bearings, power and board are all working, which rules out every fault that produces beeping, grinding or silence. What follows spin-up happens inaudibly — the heads calibrating, and the drive reading its own reserved firmware area — and a failure there means it never identifies itself, which is exactly what you're seeing. That's a recoverable class of fault and it doesn't touch what's written on the platters. Testing it in a caddy was the right move, since it eliminates your computer's ports and configuration in one step, but stop repeating it: every power-up repeats the failing read. Don't run repair utilities, don't initialise anything if a machine ever half-sees it, and don't assume a newish drive is safe from this — firmware and service-area faults come from interrupted writes rather than from age.
You have probably diagnosed it correctly — call Leeds Data Recovery on 0113 322 3083; start-up read by current signature, service area repaired in technological mode, imaged and verified out.
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.