Data Recovery Case File · Solid State & Flash · Two Unlike Hosts Agree

When a Camera and a Computer Both Stop Seeing It

His enquiry described an elimination most people cannot perform, because most people only own one kind of device. A 1TB external SSD that "has for some reason stopped being able to be read by my Mac or my camera — it doesn't appear in Disk Utility and doesn't show up." Testing across two computers is a useful elimination. Testing across a computer and a camera is a considerably stronger one, because those two devices share almost nothing — different operating systems, different drivers, different power delivery, different filesystem support. When two things that unlike agree, they are describing the drive.

The decode: why the pairing matters, and what invisibility means

Why two computers is a weaker test than it seems: two laptops running the same operating system share drivers, share the same handling of that device class, and often share quirks. A fault that confuses one can confuse both for the same reason. That is why this archive usually asks for a second operating system rather than a second machine.

Why a camera is such a good second opinion: it is about as different as a host can be. It runs purpose-built firmware rather than a general operating system, it has a minimal storage implementation, it supports a narrow set of filesystems, and it delivers power differently. Almost nothing about how a camera talks to a drive resembles how a Mac does. So a drive that both refuse has failed at a level beneath all of those differences — which means the failure is the drive's own, and no further host testing can add anything.

What complete invisibility means on a solid-state drive: reassuring once understood, though it alarms people used to hard drives. On a mechanical drive the electronics usually complete the introduction even when the mechanism has failed, so a drive that vanishes entirely is genuinely unusual. An SSD's controller is the management layer — it holds the address mapping, the wear-levelling state and often the encryption — so when it fails there is nothing left to report a capacity or a model number. Total disappearance is the characteristic solid-state failure rather than an exotic one, and it says nothing about the memory holding his files.

What the route is: vendor technological and safe modes, which allow a drive whose normal start-up fails to be addressed anyway, its firmware area assessed and repaired, and the drive imaged. The honest counterpart, stated before rather than after: where the failure lies in the memory itself rather than the controller's firmware state, reading the packages directly is not the dependable fallback it is on cards and sticks, because the mapping and keys live in the controller.

The practical note about the camera use: an external SSD used as a recording destination gets sustained sequential writing, which is heavy but even wear. If footage on it matters, it is worth naming which shoots or dates take priority so imaging can be sequenced rather than run in drive order.

On the bench

No further connection was attempted, since a computer and a camera share almost nothing and their agreement had already eliminated every host-side variable. Access was attempted through the PC-3000 portfolio's SSD support in the drive's vendor technological modes, with the firmware area and translation layer assessed specifically — because a drive that presents nothing at all is describing a controller that cannot complete its start-up rather than absent memory. Imaging ran on restored access, sequenced by the material he had named, and the contents were verified by opening.

The outcome

The controller addressed in vendor modes, the firmware state repaired and the contents imaged in priority order. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone testing a failed drive: two computers is a weaker elimination than it looks, because they share drivers and device handling — but a computer and a camera share almost nothing, so their agreement rules out every host-side variable at once and no further testing can add to it; and total invisibility on a solid-state drive is the normal failure rather than an alarming one, because the controller is the entire management layer, so when it fails nothing remains to announce a capacity.

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.