Data Recovery Case File · Portable Drives · Not Merely Unmounted
Missing From Both Lists Is a Different Finding
Her enquiry rules out more than most in two sentences. An external drive "not detected by laptop or PC. Light flashes as if there is power when connected. The device does not appear in the data management or device manager. It is not believed that the cable or powe"r supply is at fault. Most drives in this archive are absent from one view and present in another. Absent from both, while visibly powered, is a stronger and more specific finding — because those two consoles answer different questions and both have said no.
| Media | External hard drive — indicator active on connection; not listed in the host device inventory or the disk management console; behaviour reproduced across machines |
| Reported situation | Drive not detected on either a laptop or a desktop machine · indicator flashing on connection indicating power reaching the enclosure · absent from the device inventory · absent from the disk management console · cable and power supply not suspected · contents required |
| Fault class | Failure to enumerate at bus level — bridge or drive not completing introduction; below filesystem and volume layers entirely |
| Equipment used | No repeated connection attempts · drive removed from the enclosure and assessed on a native connection · current draw measured on a controlled bench supply · readiness sequence read directly under strict timeouts · imaged write-blocked on restored enumeration |
The decode: what each absence rules out
What the device inventory lists: hardware that completed its introduction on the bus — drew power, announced itself, and stated what it is. That is the lowest level at which anything appears. A device absent from that list has not introduced itself at all, which is a far more fundamental failure than a volume that will not mount.
What the disk console lists: storage the system can address as a disk, including disks it cannot read and disks with no usable filesystem — it shows those and marks them accordingly rather than hiding them. Absence there is consistent with the first absence rather than adding to it.
Why both together is the useful reading: most cases in this archive sit in the gap between those two views — present as a device, absent as a volume, which places the fault in the filing structures. Absent from both puts the fault below all of that, at the point where the device should be announcing itself. No filesystem work applies, because nothing has got far enough for a filesystem to exist as a question.
Why the flashing light does not contradict it: the indicator reports power reaching the enclosure and, on many designs, the bridge board's own activity. It illuminates because electricity arrived, not because anything succeeded. A light is a statement about a supply, not about a conversation — which is why so many people take it as evidence that a drive is fine.
What that leaves: two candidates. The enclosure's bridge board may have failed, in which case the drive inside is untouched and reads directly — one of the cheapest outcomes available. Or the drive itself is not becoming ready, so the bridge has nothing to introduce.
Why removing the drive settles it: connecting it natively takes the bridge out of the question entirely. If it appears, the enclosure was the fault and the case is essentially over. If it does not, the fault is the drive's own readiness — and the assessment moves to reading its start-up sequence under strict timeouts rather than letting a host wait through repeated retries.
What she has already eliminated: two machines and, by her own assessment, the cable and supply. That is a proper elimination and there is nothing further to try at that level.
On the bench
No repeated connection attempts were made, two machines having established the position. The drive was removed from the enclosure and assessed on a native connection — absence from both the device inventory and the disk console placing the fault at enumeration rather than at volume level, and a failed bridge board being the cheapest of the two remaining explanations. Current draw was measured on a controlled bench supply, the readiness sequence read directly under strict timeouts, and the drive imaged write-blocked on restored enumeration.
The outcome
The bridge eliminated on a native connection, draw and readiness characterised 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: most drives here are absent from one view and present in another, which places the fault in the filing structures. Absent from both means nothing introduced itself on the bus at all — below the filesystem entirely. And the flashing light reports power arriving, not a conversation succeeding.
Drive missing from the device list as well as the disk console
That pairing is more specific than it feels. The device inventory lists hardware that completed its introduction on the bus — drew power, announced itself, stated what it is — which is the lowest level at which anything appears at all. So a drive absent from there hasn't introduced itself, which is a more fundamental failure than a volume that won't mount, and it means no filesystem repair applies because nothing has got far enough for that to be a question. The flashing light doesn't contradict it: an indicator reports power arriving at the enclosure, not a successful conversation. What's left is either a failed bridge board in the case, with the drive inside untouched, or a drive not becoming ready.
Call Guildford Data Recovery on 01483 901310; bridge eliminated on a native connection, current draw measured on a controlled supply, readiness 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.