Data Recovery Case File · Portable Drives · Two Different Lists

Enumerating, and Not Mounting

His enquiry did the elimination properly and then noticed the detail that matters. A 4TB portable drive his Mac cannot see: "I have also tried on two other machines and have checked the ports with memory sticks. It comes up in the system information showing there is data on there, and the manufacturer's application sees it but says" nothing useful. Three machines, ports verified with other devices, and a drive that is simultaneously listed and unusable. Those are two different lists reporting two different things, and the gap between them places the fault precisely.

The decode: what each list means, and why the utility seeing it adds nothing

What the system's hardware information records: devices that completed the introduction their interface requires — drew power, announced themselves, and stated what they are. For an external drive, the component doing all of that is the enclosure bridge, the board converting the drive's native interface to USB. So an entry there proves the enclosure is alive, powered and communicating. It says nothing about the drive behind it.

What appearing on the desktop requires: a great deal more. The system must read the volume's partition and filesystem structures and find them coherent enough to mount. Where it cannot, it presents nothing — and the drive vanishes from view while remaining perfectly present underneath.

Why the manufacturer's utility seeing it is not encouraging: worth saying, because it feels like it should be. Those applications talk to the enclosure — reading its identity, its capacity, its status — which is the same layer the hardware information reports. Its detecting the drive confirms the bridge is working, which was already known, and adds nothing about the volume. Both observations are about the same component.

What his gap therefore identifies: the enclosure works and the drive or its filesystem does not. That eliminates the cable, the port, the power arrangement and the bridge board — the cheap and cheerful explanations — and he has additionally eliminated the host by testing three machines and verifying the ports with other devices. Very few enquiries arrive this thoroughly narrowed.

Why the note about data being shown is worth checking rather than trusting: capacity or usage figures reported at that level come from the bridge, and a bridge can report a drive's declared capacity without any of it being readable. It is not evidence that the contents are intact — encouraging, but not a finding.

The thing that must not happen: the manufacturer's utility will very likely offer to format, erase or run a diagnostic that writes. Faced with a drive it can see and cannot use, that is what such applications propose, and it is worded as maintenance. Nothing should be run from it.

What the assessment does: takes the bridge out of the question by reading the drive on a native connection, establishes whether it becomes ready at all, and — if it does — treats this as a filesystem reconstruction against an image rather than anything done to the drive.

On the bench

No repair, format or vendor utility operation was permitted, since manufacturer applications faced with a visible but unusable drive propose exactly those and word them as maintenance. The drive was removed from the enclosure and assessed on a native connection, taking the bridge out of the question entirely, with the readiness sequence read directly under strict timeouts to establish whether the drive itself became ready. It was imaged write-blocked and structures rebuilt on the image.

The outcome

The bridge eliminated on a native connection, the drive assessed under strict timeouts and structures rebuilt from the image. 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, for anyone whose drive is listed but absent: those are different lists. The hardware information records devices that introduced themselves, which for an external drive is the enclosure bridge rather than the drive — and the manufacturer's utility talks to that same bridge, so its seeing the drive confirms nothing new. Appearing on the desktop needs the volume's structures to be readable. Don't run anything from the vendor application.

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.