Data Recovery Case File · Portable Drives · Two States, One Casing
The Indicator Reports the Enclosure, and It Carries On Reporting After the Drive Stops
His enquiry separates two things happening in the same object, which most descriptions do not. A drive that powers up, produces sounds "for thirty seconds to a minute and then stops and never connects" — and the detail that "the light also turns on when it begins powering on and then stays on even after the powering on stops." Those are two different components behaving differently, and the persistence of one while the other quits is the finding.
| Media | External hard drive — mechanical activity for thirty to sixty seconds followed by cessation; indicator remaining illuminated afterwards; no volume presented |
| Reported situation | External drive ceasing to function · drive powering up on connection · audible activity continuing for approximately thirty to sixty seconds · activity ceasing · indicator illuminating at power-up · indicator remaining illuminated after activity ceases · no connection established to the host · photographic and work content held |
| Fault class | Drive abandoning initialisation with the enclosure remaining powered — bridge board functional; failure bounded and self-terminating rather than continuous |
| Equipment used | Persistent illumination attributed to the enclosure independently of drive state · no further connection permitted · drive removed from the enclosure and addressed directly with imposed timeouts · current draw measured across the start-up cycle on a controlled bench supply · service area read under strict timeouts in vendor technological modes |
The decode: what each component is doing, and what the interval means
Why the indicator and the drive are not reporting the same thing: different components drive them. The indicator is lit by the enclosure's bridge board, which has its own power and its own state.
Why it stays lit after the drive quits: nothing told it to stop. The bridge is still powered and still connected to the host, so it continues to indicate that.
What that establishes: the enclosure is fine. A bridge board that powers up, lights its indicator and remains stable is working.
Why that is genuinely useful: it removes a whole layer. A failed bridge is a common and cheap fault, and this one is demonstrably not failed.
Now the interval, which is the more interesting half: thirty to sixty seconds is a long time. A drive spends that period attempting something rather than failing immediately.
What it is attempting: to read its own configuration. Before it can report a capacity or accept commands, it must retrieve calibration values and parameters from a reserved region.
Why the attempt takes that long: retries. A drive struggling with that region attempts it repeatedly, and each attempt costs a full rotation plus repositioning.
Why it stops rather than continuing indefinitely: the firmware limits it. A drive that cannot complete initialisation abandons the attempt rather than running forever.
Why stopping is a mercy rather than a failure: continuing would cost more. Repeated seeking on a region it cannot read is wear with no prospect of success.
What none of it says about his content: nothing at all. The reserved region holds the drive's own parameters, and it is separate from where photographs and work are stored.
On the bench
Persistent illumination was attributed to the enclosure independently of drive state — the indicator being lit by the bridge board, which retains its own power and connection to the host and therefore continues indicating after the drive quits, establishing that the enclosure is functional. The thirty to sixty second interval represents repeated attempts to read the reserved region holding calibration values, each costing a rotation and repositioning, before firmware abandons the sequence. Service area was read under strict timeouts.
The outcome
Illumination attributed to the enclosure independently of the drive, further connection stopped, and the service area read under strict timeouts. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery where the drive is opened. The decode: the light and the drive are two separate components. The indicator staying on proves your enclosure is fine — and the minute of activity before silence was the drive trying to read its own configuration.
An indicator that stays lit after the noise stops
Report both behaviours separately, as you have — they're different components. The indicator is lit by the enclosure's interface board, which keeps its own power and connection, so it carries on reporting after the drive itself quits. That's useful: it proves the enclosure works, removing a common and cheap fault from consideration. The interval before silence matters too — half a minute or more means the drive was attempting something repeatedly rather than failing at once.
Two components, two states — call Cambridge Data Recovery on 01223 655015; illumination attributed to the enclosure, drive addressed directly, service area read under strict 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.