Data Recovery Case File · Portable Drives · An Unusually Precise Observation
The Enclosure Introduced Itself and the Drive Behind It Did Not
His enquiry contains a diagnostic step almost nobody thinks to take. A drive that will not appear on either of two machines, where "the drive illuminates and you can feel that it is receiving power. I've been through disk utilities and the disk is not visible, but it is visible under the connection device tree in system information on both machines." Those two lists describe different things — and being in one and not the other places the fault precisely.
| Media | External hard drive — enclosure bridge enumerating on the host connection bus; no storage device presented behind it; rotation confirmed by the owner |
| Reported situation | Drive not appearing in the host disk utility on either of two machines · drive visible in the host connection device listing on both · indicator illuminating · rotation detectable by touch · contents required |
| Fault class | Bridge enumerating without presenting storage — drive not responding to the bridge; enclosure and host eliminated |
| Equipment used | Connection listing distinguished from storage listing as separate layers · bridge enumeration accepted as elimination of cable, port and bridge power · drive removed from the enclosure and assessed on a native connection · readiness sequence read under strict timeouts |
The decode: two lists, two different questions
What the connection device listing shows: everything physically attached that has introduced itself on the bus. For an external drive, the thing that introduces itself is the bridge board inside the enclosure — the small controller that translates between the drive's interface and the connection to the computer.
What appearing there proves: the cable works, the port works, the enclosure has power, and the bridge board powered up, ran its own start-up and completed its introduction. That is a considerable amount of the chain confirmed working, and it is confirmed on two independent machines.
What the disk utility shows: storage devices. For one to appear, the bridge must have found a drive behind it, communicated with it successfully, and passed it on to the system. That is a further step entirely.
So what his pattern establishes: the bridge is present and the drive behind it is not answering. The fault is at the drive or at the connection between drive and bridge, and nowhere else — not the cable, not the port, not the bridge's power, not the host.
Why that is worth so much: those eliminations normally take several tests each. One observation in the right list does all of them at once, and it is available on any machine to anybody who knows where to look.
Why rotation adds to it rather than contradicting it: the drive spins, so it is receiving power from the bridge and its motor circuitry works. A drive that spins and does not answer is failing to complete its start-up — typically unable to read the reserved region holding its own firmware and calibration, or unable to position its heads well enough to do so.
What the next step is: removing the drive and connecting it natively, without the enclosure. That either resolves the case, if the bridge-to-drive connection was the fault, or confirms the drive — and it is one step rather than several.
What must stop: further connection to more machines. Two independent hosts agreeing is conclusive, and each attempt is another start-up on a drive that has failed to complete one.
On the bench
The connection listing was distinguished from the storage listing as separate layers — the former showing devices that have introduced themselves on the bus, which for an external drive is the enclosure's bridge board, while the latter requires the bridge to have communicated successfully with a drive behind it and presented it onward. Bridge enumeration was accepted as elimination of cable, port and bridge power, and the drive assessed on a native connection away from the enclosure.
The outcome
The two listings treated as separate layers, cable and port and bridge eliminated by his own observation, and the drive assessed natively. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: those lists answer different questions. Appearing on the connection bus means the enclosure's bridge introduced itself; appearing in the disk utility means it found a drive behind it. Yours does the first and not the second.
Checking where in the chain a drive is failing
Look in the system information connection listing as well as the disk utility — those two answer different questions, and the difference between them is worth several separate tests. A device appearing on the connection bus is the enclosure's bridge board having powered up and introduced itself, which proves the cable, the port, the enclosure supply and the bridge all work. A device appearing in the disk utility means the bridge additionally found a drive behind it and passed it on. Present in one and absent from the other places the fault at the drive or its connection to the bridge, and nowhere else.
That narrows it precisely — call Oxford Data Recovery on 01865 593000; listings treated as separate layers, cable and bridge eliminated by your own observation, 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.