Data Recovery Case File · Second Fixes & Trade Handoffs · The Groundwork Was Done
Everything Testable Without Specialist Equipment Had Already Been Tested
This enquiry arrives from someone who has done the work first. An external drive that "spins up and shows activity on the indicator but is not detected or visible on any system", submitted on behalf of a colleague by someone who has "already tested with multiple cables, ports, different computers and across different operating systems." That eliminates the entire host side, and the question he closes with — what information would you need — is the right one.
| Media | External hard drive — rotation achieved with indicator activity present, not enumerating on any host; cables, ports, machines and platforms eliminated by the submitter |
| Reported situation | External drive spinning up · indicator showing activity · drive not detected or visible on any system · multiple cables tested · multiple ports tested · multiple computers tested · multiple operating systems tested · enquiry submitted by a technical colleague on the user's behalf |
| Fault class | Device-level failure with host variables excluded — rotation and activity present without enumeration; fault below the level any host-side test can reach |
| Equipment used | Prior elimination accepted without repetition · indicator activity distinguished from successful enumeration · current draw measured across the start-up cycle on a controlled bench supply · service area and firmware state read under strict timeouts · laminar flow bench inspection where rotation was affected |
The decode: what his testing settled, and what genuinely remains
Why the breadth of his testing matters: he varied four things independently. Cables, ports, machines and operating systems are separate variables, and changing all of them without changing the behaviour removes the entire host side from consideration.
Why testing across platforms is the strongest part: two operating systems share almost no software — different drivers, different device handling, different volume support. A drive invisible to both has a problem beneath all of it, in the exchange where a device announces itself.
Why that means his testing should not be repeated: the answers will be the same. Re-running eliminations that have already been performed costs time and, on a marginal drive, costs power cycles — so the useful next step is different equipment rather than more of the same.
What the rotation and indicator activity establish: a good deal. Power reaches the drive, the motor runs, and something is happening internally — which places the fault after those stages rather than at them.
Why indicator activity is not the same as enumeration, and this is the distinction worth drawing: a flickering indicator shows the drive doing something. It does not show the drive successfully introducing itself to a host, and a drive can attempt its start-up repeatedly — producing activity — without ever completing it.
What that narrows the fault to: the drive reading its own configuration, or the electronics that complete the introduction. Both sit after rotation and before enumeration, which is exactly the gap his observations bracket.
Why his belief that the data is recoverable is reasonable: a drive that spins and shows activity has not failed catastrophically. The surfaces have not been implicated by anything he describes, and faults in this bracket frequently leave the recording untouched.
What genuinely requires different equipment: current draw across the start-up cycle, whether the drive completes its internal initialisation, and what it reports when addressed at a level the operating system does not use. None of those is observable from a host connection, which is why the next step is not another computer.
What is useful to supply, since he asks: the drive itself, and the observations he already has. The sequence of what was tried, whether anything was written to the drive, and how many times it has been powered — that last one matters more than people expect on a marginal device.
What is worth confirming with the user rather than the technician: what the drive holds and which of it matters. Scope is the user's question rather than the intermediary's, and it shapes the work if the drive turns out to be difficult.
On the bench
Prior elimination was accepted without repetition — cables, ports, machines and operating systems being independent variables whose variation without change of behaviour removes the host side entirely, with cross-platform absence placing the fault beneath all driver and volume handling. Indicator activity was distinguished from successful enumeration, a flickering indicator showing internal activity while a drive may attempt start-up repeatedly without completing it. Current draw was measured across the start-up cycle on a controlled bench supply.
The outcome
Prior elimination accepted without repetition, indicator activity distinguished from enumeration, and the drive assessed on a controlled bench supply. 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: your testing removed the entire host side, and it should not be repeated. Rotation and activity place the fault after spin-up and before enumeration — which needs different equipment rather than another computer.
What is worth supplying with a drive
Bring your observations as well as the device. The most useful things are the sequence of what was tried, whether anything was written to the drive, and how many times it has been powered — that last one matters more than people expect on a marginal device. If you've varied cables, ports, machines and operating systems without any change, you've removed the host side entirely and it needn't be repeated. Note one distinction while you're testing: indicator activity shows the drive doing something, not that it has successfully introduced itself, since a drive can attempt start-up repeatedly without completing it.
That is the right groundwork — call Easy Data Recovery on 028 9002 0144; prior elimination accepted without repetition, draw measured across the start-up cycle, firmware state 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.