Data Recovery Case File · Mac & Apple Systems · One Symbol, Several Faults
That Symbol Says No Startup System Was Found, Not That the Drive Is Gone
His enquiry describes a machine reduced to a single symbol. A laptop with an internal solid-state drive that "failed to boot and shows only a flashing folder with a question mark. I've tried various recovery boot options but none find the drive, and target mode to another Mac doesn't work either." That symbol reports one thing only — no startup system was found — and his two further tests narrow which of several causes is responsible.
| Media | 256GB internal solid-state drive from a laptop of early-2013 vintage — no startup system located, drive not found by recovery options or through direct machine-to-machine connection |
| Reported situation | Laptop failing to start · flashing folder symbol with a question mark displayed · recovery startup options attempted without locating the drive · direct machine-to-machine connection attempted without result · contents required |
| Fault class | Startup volume not located with drive undetected at recovery and direct-connection levels — controller or connection failure rather than a system-software fault |
| Equipment used | Startup symbol interpreted as absence of a bootable system rather than device failure · recovery and direct-connection results used to distinguish software from device causes · drive removed and assessed independently on a matched adapter · controller state assessed in vendor technological modes · chip-level read past the controller with translation layer reconstructed in software |
The decode: what each of his three tests eliminated
What the symbol actually reports: the machine looked for a startup system and did not find one. That is the whole of its meaning — it does not distinguish between a drive that has failed, a drive that is fine with damaged system files, or a drive that has simply been unplugged.
Why the recovery options were the right next test: those start the machine from a separate source rather than from the drive. If they had loaded and shown the drive, the fault would have been the system software with the storage intact — a straightforward and very recoverable situation.
What their failure to find the drive establishes: the problem is not the system software. An independent startup environment looking for storage and finding none places the fault at the device, which eliminates the most benign explanation.
Why the machine-to-machine test was the strongest one: connecting one computer to another as an external device bypasses the first machine's operating system almost entirely. It is close to reading the drive directly, and it is the test that separates a broken computer from a broken drive.
What its failure means: the drive is not presenting itself even under those conditions. Three progressively more direct routes have failed to reach it, which points firmly at the drive rather than at anything above it.
What that leaves as the likely cause: a controller that is no longer completing its introduction. A drive must announce itself before any system can list it, and a controller stuck at start-up never gets that far — which produces exactly this pattern of nothing found at every level.
Why the memory is very likely intact: the failure is in the component that manages and presents the storage. The memory holding his files is separate and unaffected by a controller that cannot start, which is why a route past it exists.
What is worth noting about a machine of this vintage: the drive may use a manufacturer-specific connection rather than a standard one. That affects how it is assessed rather than whether it can be — the right adapter is needed to reach it outside the machine.
Why the laptop's own condition is now a separate question: the drive is the thing holding the data, and it can be assessed independently of whether the computer works. A machine that will not start is not an obstacle to recovering what its drive holds.
What must not happen: no reinstalling a system to make the machine usable, and no disk repair attempted from a recovery environment. An installation writes to the drive it installs onto, which is the one holding everything he wants back.
On the bench
The startup symbol was interpreted as absence of a bootable system rather than device failure — indicating only that no startup volume was located, which does not distinguish failed storage from intact storage with damaged system files. Recovery and direct-connection results were used to distinguish software from device causes, an independent startup environment failing to locate the drive excluding system software, and machine-to-machine connection failing likewise by bypassing the host operating system. Chip-level reading was performed past the controller.
The outcome
The symbol read as absence of a bootable system, the two further tests used to exclude software causes, and the memory read past the controller. 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: the symbol only means no startup system was found. Your two further tests did the real work — recovery options and a direct machine-to-machine connection both failing to see the drive places the fault at the device rather than the software.
A laptop showing a flashing folder with a question mark
Don't reinstall a system to get the machine going — an installation writes to the very drive holding everything you want back. That symbol reports only that no startup system was found, which covers a failed drive, an intact drive with damaged system files, and a disconnected one. Two tests separate them: starting from a recovery environment, and connecting the machine to another computer as an external device. If either shows the drive, the storage is fine and it's a software problem. If neither does, the fault is at the device, most often a controller no longer completing its introduction — with the memory holding your files intact behind it.
Don't reinstall — call Easy Data Recovery on 028 9002 0144; symbol read as absence of a bootable system, drive assessed independently on a matched adapter, memory read past the controller.
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.