Data Recovery Case File · Solid State & Flash · Nothing Left to Test
The Cleanest Elimination There Is
His enquiry contained the single best diagnostic step an owner can take, and he had already done it. A 1TB portable SSD that "initially couldn't read, then when restarted the MacBook would not even show the drive in the Finder window, so I was unable to even use Disk Utility or anything to see the drive. Checked cables and ports, as other SSD drives of the same size and make can be seen no problem." The drive is nearly full of video and audio for a project in progress. That comparison — identical drives, same cables, same ports, working perfectly — is a more complete elimination than most benches begin with, and it means there is genuinely nothing left for him to try.
| Media | 1TB portable solid-state drive close to capacity — initially failing to read, subsequently not enumerated at all; identical drives functioning normally on the same cables and ports; project video and audio held |
| Reported situation | Drive initially readable with errors · not presented at all following a restart · unavailable to the system disk utility · cables and ports verified using identical working drives · project material in active use |
| Fault class | Controller failure progressing from partial to complete — no enumeration; vendor-mode access the realistic route; memory typically intact |
| Equipment used | No further connection attempts · vendor technological and safe-mode access (PC-3000 portfolio, SSD support) · firmware area and translation-layer assessment · imaging on restored access sequenced by project priority |
The decode: what his comparison proves, and what the progression means
Why testing with an identical drive is the best step available: most owners test by changing one variable at a time — another cable, another port, another computer — which takes a while and leaves doubt. Substituting a known-good drive of the same make and model on the same cable and port tests everything at once: the cable, the port, the power delivery, the driver, the operating system's handling of that exact device class. All of it works. So the only remaining variable is the drive itself, and no further home testing can add anything.
What the progression tells us: he did not go from working to nothing. It initially couldn't read — meaning the drive was enumerating and failing on access — and then, after a restart, stopped presenting at all. That is a controller deteriorating rather than a single abrupt failure: first unable to service reads, then unable to complete its introduction. Which also means the window in which the drive was partially accessible has closed, and further connection attempts will reproduce the current state rather than the earlier one.
Why total invisibility is the normal solid-state failure: worth saying, because it alarms people who are 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 present a capacity or a model number. Invisibility is the characteristic outcome rather than an exotic one.
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 memory holding his project is normally unaffected by the controller failing. The honest counterpart: where the failure is in the memory 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 project: a nearly-full drive of video and audio in active use means naming which sequences and sessions matter most is worth doing, so imaging is sequenced accordingly rather than running in disk order.
On the bench
No further connection was attempted, since substituting identical working drives had already eliminated every variable except the drive itself — there was nothing a further test could establish. 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 controller that first failed reads and then stopped enumerating is describing a deteriorating firmware state rather than absent memory. Imaging ran on restored access, sequenced by the project material he had named, and the files were verified by playback.
The outcome
The controller addressed in vendor modes, the firmware state repaired and the project material 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 drive: substituting an identical known-good drive on the same cable and port is the best single test available, because it eliminates cable, port, power, driver and operating system in one step — after that, nothing further can be learned at home; a drive that first failed reads and then stopped appearing is a controller deteriorating rather than one abrupt failure; and total invisibility is the normal way solid-state drives fail, because the controller is the entire management layer.
Drive invisible while identical ones work fine
Stop testing — you've done the best diagnostic step there is and nothing further will add to it. Plugging a known-good drive of the same make and model into the same cable and port eliminates the cable, the port, the power delivery, the driver and the operating system's handling of that device class, all at once. The only variable left is the drive itself. Note the progression too, because it matters: a drive that first gave read errors and then stopped appearing at all is a controller deteriorating in stages, which means the window when it was partly accessible has closed and reconnecting will only reproduce the current state. Don't be alarmed that it's completely invisible — on solid-state drives the controller is the whole management layer, so total disappearance is the normal failure rather than an unusual one.
Your testing is complete — call Glasgow Data Recovery on 0141 404 0294; controller addressed in vendor modes, firmware and translation layer repaired, imaging sequenced by your project priorities.
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.