Data Recovery Case File · Portable Drives · What Each Fact Rules Out
The Light Belongs to the Enclosure, Not to the Drive
This enquiry came from an organisation and contains the most thorough software elimination available. A drive "no longer being detected in any computer. We have tried three different operating systems with no success. It lights up when plugged in, but we can go no" further. Three unrelated systems failing is conclusive about the software layer — and the light, which looks like reassurance, reports something narrower than it appears.
| Media | External hard drive — indicator illuminating on connection; not enumerating on hosts running three different operating systems |
| Reported situation | Drive not detected on any host tried · hosts running three different operating systems · indicator illuminating on connection · no further response obtained · contents required |
| Fault class | Failure to enumerate with enclosure power confirmed — software layer comprehensively eliminated; bridge board and drive both outstanding |
| Equipment used | Cross-platform result accepted as elimination of the software layer · indicator interpreted as enclosure power rather than drive state · drive removed from the enclosure and assessed on a native connection · current draw measured on a controlled bench supply · readiness read under strict timeouts |
The decode: two observations that narrow it from opposite directions
Why three systems is the strongest possible software test: each has its own driver stack, its own filesystem support, its own rules about what to mount, its own permission model and its own tolerance for devices that respond slowly. They share almost nothing but the physical connector. A drive failing on all three has failed independently of every one of those.
Why that matters more than testing several machines: a large share of apparently dead drives are victims of software — a filesystem no longer mounted, a driver an update removed, a permission nobody granted. Testing on similar machines cannot rule any of that out. This does.
Now the light, which is doing less work than it appears to. On an external drive, the indicator is generally wired to the enclosure's power stage rather than to the drive inside. It illuminates when the enclosure receives power, and it will keep illuminating whether the drive spins up, fails to spin up, or is not connected at all.
So what it actually establishes: that power reached the enclosure. That is genuinely useful — it eliminates the cable and the adapter — and it says nothing whatsoever about whether the drive completed its start-up or announced itself.
What the two facts together leave: the software layer is gone, the supply to the enclosure is confirmed, and the device is not presenting. That leaves the bridge board inside the enclosure, or the drive itself, and nothing else.
Why that is a good position to be in: a failed bridge board is the cheapest outcome in this archive. The drive inside is untouched, and connecting it directly resolves the case entirely — which is why removing it from the enclosure is the next step rather than more host testing.
What to listen for while it is connected, since nobody has mentioned it: whether the drive spins. A hand on the enclosure detects the vibration of platters at speed, and that single observation separates a bridge fault from a drive that is not becoming ready.
What must stop: further host testing. The answer will be the same on a fourth system, and every connection is another start-up attempt on a device that has not managed one yet.
On the bench
The cross-platform result was accepted as elimination of the software layer — three operating systems differing in driver stacks, filesystem support, mount policy and permission handling, sharing almost nothing beyond the connector. The indicator was interpreted as enclosure power rather than drive state, external indicators generally being wired to the enclosure's own power stage and illuminating regardless of whether the drive within responds. The drive was assessed on a native connection with draw measured on a controlled bench supply.
The outcome
The software layer eliminated by your own testing, the indicator read correctly, and the enclosure separated from the drive on a native connection. 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: three operating systems is the most thorough software test there is, and it rules out everything above the device. The light is narrower than it looks — it reports that the enclosure received power, not that the drive did anything.
Drive that fails on every system with its light on
Stop testing more machines and put a hand on the enclosure to feel whether it spins — that single observation is worth more than a fourth operating system. Your testing was already conclusive about software: three different systems share almost nothing but the connector, so failing on all of them rules out drivers, filesystem support, mount policy and permissions together. The light means less than it seems, though. On an external drive the indicator is usually wired to the enclosure's power stage, so it illuminates when the enclosure has power and keeps illuminating whether the drive inside spins up or not. What's left is the bridge board or the drive.
Feel for rotation, then call Oxford Data Recovery on 01865 593000; cross-platform result accepted as elimination, indicator read as enclosure power, drive assessed on a native connection.
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.