Data Recovery Case File · Portable Drives · A Stronger Control Than She Knows
Two Operating Systems Rules Out More Than Two Computers
Her enquiry contains a test better than the one most people run. A drive "not connecting to any laptop or PC — Mac or Windows. There is a light on the hard drive so I know it is working, but I am unable to a"ccess anything. Trying two machines eliminates one machine. Trying two different platforms eliminates drivers, filesystem support, mounting policy and permission behaviour all at once — which is a considerably stronger result than she has given herself credit for.
| Media | 1TB external hard drive — not presenting on hosts running two different operating systems; indicator illuminated on connection |
| Reported situation | Drive not connecting to any host tried · hosts running two different operating systems · indicator illuminated on the drive · no access obtained on either platform · contents required |
| Fault class | Device-level failure with host software eliminated — cross-platform result excluding drivers, filesystem support and mount policy; cable and enclosure outstanding |
| Equipment used | Cross-platform result accepted as elimination of host software · cable and enclosure eliminated separately · drive assessed on a native connection · readiness read under strict timeouts · imaged write-blocked on restored enumeration |
The decode: what each test actually rules out
What two computers on the same platform establishes: that the fault is not in one machine's hardware — a failed port, a damaged controller. It does not rule out anything about the software, because both machines run the same drivers, support the same filesystems, and apply the same rules about what to mount.
What two different platforms establishes instead: a great deal more. Different driver stacks, different filesystem support, different policies about unrecognised volumes, different permission models, and different tolerance for devices that respond slowly. A drive failing on both has failed in a way that has nothing to do with any of it.
Why that matters practically: a large share of drives that appear dead are victims of software — a filesystem the current system no longer mounts, a driver an update removed, a permission requirement nobody granted. Her test removes that entire family in one step, which most people never manage.
What it leaves: the drive itself, or the physical path to it — cable and enclosure. Those are the only things common to both attempts.
Which is why the cable comes next, and it costs nothing: a marginal lead is the single commonest cause of a drive that will not present, and swapping one takes a moment. It is the cheapest remaining elimination and it should be done before anything else.
On the light, briefly: an illuminated indicator reports that power arrived at the enclosure. It says nothing about whether the drive spun up, completed its start-up, or announced itself — those are separate events, and a drive can light up indefinitely without managing any of them. It is worth knowing rather than relying on.
What the enclosure contributes: a bridge board translating the drive's own interface to the host's, which is a component that fails on its own. Removing the drive and connecting it directly eliminates it entirely, and if the drive presents at that point the case is essentially over.
What she should not do meanwhile: keep connecting it. The cross-platform test has already produced its answer, and repeating it adds nothing while costing whatever the fault costs.
On the bench
The cross-platform result was accepted as elimination of host software — two operating systems differing in driver stacks, filesystem support, mounting policy and permission handling, so a drive failing on both has failed independently of all of them, which two machines on one platform cannot establish. Cable and enclosure were eliminated separately, those being the only components common to both attempts. The drive was assessed on a native connection, readiness read under strict timeouts, and imaged write-blocked on restored enumeration.
The outcome
The host software eliminated by the owner's own cross-platform test, cable and enclosure ruled out separately, and the drive imaged on restored enumeration. 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: testing two platforms rules out drivers, filesystem support, mount policy and permissions in one step, where two computers on the same system rules out only the machine. That leaves the drive, the cable and the enclosure — and the cable is free to check.
Drive that fails on every machine you own
Swap the cable next — it's the cheapest remaining elimination and a marginal lead is the commonest reason a drive won't present at all. Your test was better than you may realise: two computers running the same system rules out one machine's hardware, while two different platforms rules out driver stacks, filesystem support, mounting policy and permission handling all at once, and a great many apparently dead drives are victims of exactly those. What's left is the drive, the cable and the enclosure. Don't rely on the light, though — it reports that power reached the enclosure and says nothing about whether the drive spun up or announced itself.
Try another cable, then stop — call Oxford Data Recovery on 01865 593000; your cross-platform test accepted as elimination, enclosure ruled out on a native connection, imaged on restored enumeration.
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.