Data Recovery Case File · Desktop Externals & Aging Drives · The Silent Half of Start-Up
Drive Spins Up Then Goes Quiet and Never Appears
His enquiry described the start-up sequence better than most technical reports do, and the description contains the diagnosis. A 1TB Verbatim external drive, never dropped: "when switched on it goes through the process, all the lights work, the sound of spinning etc, but then it reaches a point where it goes quiet — but it's like it never reaches the final point where the data or device shows up on my Mac desktop." He has noticed something most owners never articulate: that a drive's start-up has an audible part and a silent part, and that his stops between them. That is exactly right, and it localises the fault precisely — because everything in the silent half is where drives of this kind fail, and none of it touches what is written on the platters.
| Media | Verbatim 1TB external hard drive — powers and spins normally, then falls silent; never presented to the host; no impact history |
| Reported situation | Enclosure lights functioning · audible spin-up completing normally · no further activity · drive never appearing on the desktop · no drop or incident reported |
| Fault class | Failure to complete initialisation after successful spin-up — head calibration or service-area read; mechanism and power confirmed working |
| Equipment used | Drive removed from enclosure and assessed on a native connection · 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 |
The decode: the two halves of a start-up, and where his stops
The audible half: power arrives, the enclosure's board energises — his lights — and the spindle motor brings the platters up to speed, which is the whirr he hears. That much succeeding rules out a great deal: the power path works, the enclosure's board works, the motor works, and the bearings turn freely. Every fault that produces beeping, grinding or silence is eliminated by that sound alone.
The silent half, which is where his stops: once the platters are at speed, three things happen and none of them makes a sound. The heads unpark and move onto the surfaces. They perform calibration seeks, positioning themselves against servo patterns written on the platters at manufacture. And the controller reads the drive's service area — a reserved region, invisible to any operating system, holding its firmware modules, defect maps and the translation tables that convert logical addresses into physical locations. Only when all three succeed can the drive identify itself and report a capacity. A failure at any of them produces exactly what he describes: a drive that sounds perfectly healthy and never appears. So his "it goes quiet and never reaches the final point" is a literal description of a start-up that completed its mechanical stage and failed its electronic one.
Why "never been dropped" is consistent: he offers it as though it undermines the case, and it does not. Service-area and calibration faults are not impact-related. They arise from an interrupted write to the reserved region during a power event, from a defect-list update that did not complete, or from firmware problems — none of which requires mistreatment. A drive that has led a blameless life can develop this.
Why it is workable: neither remaining cause touches the data. Service-area faults are addressed through the manufacturer's own technological modes — the reserved regions read directly and their damaged modules repaired or regenerated until the drive will identify itself and address its media. Calibration failures are met at the mechanism. In both cases the discipline afterwards is identical: the moment the drive answers, it is imaged completely, and everything else happens on the copy.
The one thing to stop: repeated power-ups. A drive failing to read its own service area retries that read every time it is switched on, and there is nothing further to learn from hearing it happen again.
On the bench
The drive was taken out of its enclosure and assessed on a native connection, removing the bridge board his lights had already proved was working. The Atola Insight Forensic read the start-up sequence electrically rather than audibly — power delivery, spin-up, the calibration seek attempts and their outcome, and the precise point at which progress stopped — turning his description 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 own media. Imaging began immediately under Data Extractor, head-mapped and complete, and the volume was rebuilt from the image and verified by opening.
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. The decode, for anyone whose drive sounds fine and never appears: a start-up has an audible half and a silent one, and yours completed the first — power, enclosure, motor and bearings are all proved by that sound; the silent half is head calibration and the drive reading its own reserved firmware area, and a failure there means it never identifies itself, which is exactly the symptom; that class of fault is not caused by mistreatment, so "never been dropped" is entirely consistent; and it does not touch your data. Stop switching it on, because each attempt simply repeats the failing read.
Drive that sounds perfectly normal and never shows up
Take the sound as evidence rather than a puzzle. If it spins up normally, the power path, the enclosure board, the motor and the bearings are all working — that rules out every fault that beeps, grinds or stays silent. What follows spin-up happens inaudibly: the heads unpark and calibrate against patterns on the platters, and the drive reads its own reserved firmware area. A failure there means it never identifies itself and never appears, which is precisely what you're seeing, and none of it touches your files. Don't assume you must have mishandled it either — these faults come from interrupted writes and firmware problems rather than from drops. Stop switching it on, since each attempt repeats the same failing read, and don't run repair utilities or accept any offer to initialise if a machine ever half-sees it.
That's the silent half failing — call Glasgow Data Recovery on 0141 404 0294; read on a native connection, start-up measured by current signature, service area repaired and imaged 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.