Data Recovery Case File · Portable Drives · Which View You Look In
They Are Not Contradicting Each Other — They Are Describing Different Things
His enquiry lists four observations that seem impossible together. A drive that "powers on, light flashes constantly. The system detects the drive in the file browser but hangs or crashes when trying to access it. It does not appear in the partition manager. It appears in the device manager." All four are true simultaneously, because each console reports a different layer of the same stack — and read in order they describe exactly where the failure sits.
| Media | Portable external hard drive — enumerating at device level; no partition structure presenting; stale volume entry causing host stalls on access; indicator cycling |
| Reported situation | Drive powering on with indicator flashing continuously · appearing in the device manager · not appearing in the partition manager · appearing in the file browser · host hanging or crashing on access attempts · consistency check unable to run · contents required |
| Fault class | Device-level enumeration succeeding with no readable partition structure — file browser entry stale; access attempts blocking on unanswered reads |
| Equipment used | Each console reading interpreted against the layer it reports · no consistency check permitted · drive removed from the enclosure and assessed on a native connection · readiness read under strict timeouts · imaged write-blocked with partition structures recovered from surviving copies |
The decode: four views, from the bottom of the stack upward
The device manager, which is the lowest: it lists hardware the system has enumerated — things that announced themselves on the bus and identified themselves. Appearing there means the drive completed its introduction: it powered up, became ready, reported its identity. That is the most encouraging of his four observations.
The partition manager, one layer up: it lists disks and the partitions on them, reading the structure at the very start of the drive that says where volumes begin and end. Absence there means that structure could not be read — either unreadable or invalid. So the drive is answering and one specific small region is not returning usable data.
The file browser, higher still: it shows mounted volumes. An entry appearing there for a drive with no readable partition table is generally stale — a remembered mapping from when the drive worked, or a placeholder the system created optimistically. It is not evidence that anything is mountable.
Which explains the hang: clicking that entry issues reads to a drive that cannot answer. Requests are issued and never completed, holding system resources while the drive retries internally for seconds per sector. The system is not crashing; it is waiting, and eventually running short.
Why the consistency check cannot run: that tool operates on a recognised volume, and there is no volume — which is why it declines rather than failing. Its refusal is a correct report, not another symptom, and it is fortunate: on a drive with read failures the tool would have written conclusions drawn from partial information.
What the flashing indicator adds: a pulsing light on a drive that is nonetheless enumerating suggests the enclosure's activity indicator following repeated internal retries rather than a start-up loop.
So the position, assembled: the drive works well enough to introduce itself and not well enough to return the region describing its own layout. That places the fault at read level in a specific small area, with everything behind it untouched — and partition structures have backup copies elsewhere on the disk, which is what a reconstruction reads.
On the bench
Each console reading was interpreted against the layer it reports — the device manager listing enumerated hardware, the partition manager reading the structure describing volume boundaries, and the file browser showing mounted volumes, so appearing in the first and not the second places the fault precisely, while an entry in the third is a stale mapping rather than evidence of mountability. No consistency check was permitted. The drive was assessed on a native connection and imaged write-blocked with partition structures recovered from surviving copies.
The outcome
Each console read against its own layer, the enclosure eliminated natively and the partition structures recovered from their surviving copies. 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 four observations agree. The device manager says the drive introduced itself. The partition manager says the structure describing its layout could not be read. The file browser entry is stale, and clicking it is what hangs the machine.
Drive that shows in one place and not another
Those views aren't contradicting each other — they report different layers, and reading them in order tells you where the fault sits. The device manager lists hardware that enumerated and identified itself, so appearing there is the most encouraging thing on your list. The partition manager reads the small structure at the very start of a disk describing where volumes begin and end, so absence there means that specific region isn't returning usable data. The file browser shows mounted volumes, and an entry for a drive with no readable partition table is usually a stale mapping — which is why clicking it hangs the machine. Your consistency check refusing to run is correct rather than another symptom.
Stop clicking the stale entry — call Oxford Data Recovery on 01865 593000; each console read against its own layer, enclosure eliminated on a native connection, partition structures recovered from surviving copies.
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.