Data Recovery Case File · Mac & Apple Ecosystem · Fitted, but Not Speaking

MacBook Air SSD Not Detected: Fitted, but Not Speaking

His enquiry showed initiative at every step and reached a conclusion one stage too early. A MacBook Air of around 2011: "when it was frozen, I forced shutdown. Then I lost all data, even the hard drive. When I tried to turn it on, a flashing question mark appeared. I removed the SSD from the Mac Air, put it on an external adaptor and connected it to another Mac. But I did not see any hard drive icon come up. I think the SSD is damaged." He may be right — but the test he ran cannot establish it, and that matters because the conclusion changes what happens next. A third-party adapter that a blade module fits is not the same as an adapter that can bring that module up correctly, and a silent result through one proves considerably less than it appears to. This page covers what the question mark meant, what the forced shutdown could have interrupted, and why the adapter is the weakest link in his evidence.

The decode: the question mark, the forced shutdown, and the adapter's silence

What the flashing question mark means: precisely one thing — the machine looked for a bootable system and did not find one. It is a statement about bootability, not about the drive's health. A Mac shows it when the drive has failed, certainly, but equally when the system files are damaged, when the boot record is corrupt, or when the volume simply cannot be mounted. On its own it is not evidence that the SSD is broken; it is evidence that the machine could not start from it.

What a forced shutdown can interrupt: holding the power button on a frozen machine cuts power without letting the system finish what it was doing. On an SSD that has two consequences worth knowing. The obvious one is filesystem structures left half-written, which produces an unmountable volume on a perfectly healthy module. The less obvious one is that an SSD's controller maintains its own internal mapping tables — the records that translate logical addresses to physical flash locations — and an abrupt cut during a table update can leave the controller unable to complete its start-up. That produces a module that powers on and never presents itself. Notably, neither of those is damage to the stored data; both are recoverable states, and the second is exactly what a specialist platform exists to address.

Why the adapter proves less than he thinks: the crux. Apple's blade SSDs of this era are proprietary in both connector and protocol, and third-party adapters vary considerably in which generations they properly support. An adapter can mate physically, supply power, and still fail to bring up a module whose protocol it does not correctly implement — producing precisely his result: no icon, no error, nothing. Add that a marginal module may need cleaner or better-regulated power than a generic adapter provides, and the silence becomes even less conclusive. His test was worth running and it narrowed things usefully, but it cannot distinguish the module is dead from this adapter cannot speak to this module. Only a generation-matched interface can do that, and that distinction is the difference between a recovery and a write-off.

Why the era is on his side: a module of this generation is removable, which he has already proved, and the corresponding professional interfaces are well established. If the module answers on the correct connection, the road is short: bring it up, image it completely in that first session, and rebuild the volume from the copy — including whatever the forced shutdown left half-finished.

On the bench

The adapter was set aside and the blade was brought up on a generation-matched proprietary interface through the Atola Insight Forensic's Apple support — its own protocol, its own voltages, and a platform able to distinguish a module that is not responding from one that is merely not being addressed correctly. The module answered. A complete image was taken immediately in that first session, on the standing rule for proprietary modules, and the volume was then reconstructed from the copy: the structures the forced shutdown had left half-written were repaired where nothing was at risk, and the system's contents stood back up. His files were verified by opening and delivered on fresh media.

The outcome

The blade read on a generation-native interface, imaged and the volume rebuilt from the copy, verified and delivered. 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. Three things worth carrying: a flashing question mark means no bootable system was found, which is a statement about booting rather than about the drive's health; a forced shutdown can leave both filesystem structures and the SSD controller's own mapping tables half-written, and neither is damage to your data; and a third-party adapter that physically fits a proprietary blade may still be unable to bring it up, so silence through one is not a diagnosis — it is an untested question.

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.