Data Recovery Case File · Mac & Apple Ecosystem · The Machine Works
Recovery Mode Loading Proves the Machine, and the Drive Is Not There
This enquiry contains a test most people never run and it settles a great deal. A 2013 laptop showing a flashing folder on start-up: "in Recovery Mode, the internal drive is not detected in the disk utility — only the recovery image and external drives appear. The files on the internal drive are very important work documents and not backed up." Recovery Mode loading at all is a working machine, and the internal drive being absent from a list that shows everything else is a much more specific finding than a computer that will not start.
| Media | Proprietary blade solid-state drive from a 2013 laptop — not enumerated by the host recovery environment; external devices and recovery image listed normally |
| Reported situation | Machine displaying a flashing folder on start-up · recovery environment loading successfully · internal drive absent from the disk utility · recovery image and connected external drives listed normally · work documents held with no backup |
| Fault class | Storage not presenting to the host with the machine functional — device-level failure; drive of removable proprietary format |
| Equipment used | No reinstall or repair permitted · storage module removed and read on a generation-matched adapter · initialisation state read directly under strict timeouts · imaged write-blocked on restored readiness · files validated by opening |
The decode: what each observation eliminates
What the flashing folder means: the firmware looked for a system to start from and did not find one. That alone is ambiguous — it covers a damaged operating system, a corrupted volume, and a drive that is not there at all.
What Recovery Mode loading resolves: a great deal. That environment runs from a separate source, so reaching it proves the machine powers correctly, its board works, the display works, and the firmware is functioning. Every question about the computer is answered, and whatever is wrong is not the machine.
Why the drive's absence from that list is decisive: the disk utility enumerates devices before it considers volumes — it shows disks it cannot read, disks with no partitions, and disks whose filesystems are damaged, listing them as unreadable rather than hiding them. So a drive with a corrupted volume would appear, greyed out or unnamed. Not appearing at all means the drive is not presenting itself as a device, which places the fault below the filesystem entirely.
Why the external drives appearing matters: the utility is working and enumerating correctly. It is not that nothing is listed; it is that everything except the internal drive is listed. That distinction rules out the utility, the environment and the enumeration process itself.
What that combination points at: the drive's controller failing to complete its initialisation, or a connection fault between the drive and the board. Both are device-level, and neither is a filesystem problem — which means no amount of repairing, reinstalling or disk-utility work can help, because there is nothing there to work on.
Why the generation is fortunate: a 2013 machine carries storage on a module that unclips from the board and reads on an inexpensive matched adapter. So the drive can be assessed entirely independently of the machine — and if the fault is the connection rather than the drive, it may simply read. Machines only a few years newer are soldered down and encrypted to the board, where this same fault is a far harder proposition.
What must not happen: no reinstall. The recovery environment he is already in offers exactly that, and it offers to erase as part of it — which on a drive that is not appearing would achieve nothing anyway, but the option is one keystroke away.
On the bench
No reinstall or repair was permitted, the recovery environment offering both and the erase path being adjacent. The storage module was removed and read on a generation-matched adapter — that model year carrying a proprietary blade format that unclips, allowing assessment entirely independently of the machine, and resolving the case immediately where the fault lay in the connection rather than the drive. Initialisation state was read directly under strict timeouts, and imaging performed write-blocked on restored readiness.
The outcome
The machine eliminated by its own recovery environment, the module read independently on a matched adapter and imaged on restored readiness. 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: Recovery Mode loading proves the machine entirely. And a disk utility lists devices before volumes — it shows disks it cannot read, greyed out — so a drive absent from a list containing everything else is not presenting itself as a device at all. That is below the filesystem, so no repair applies.
Internal drive missing from the disk utility in recovery mode
Don't reinstall — the option is right there in the environment you're looking at, and it offers to erase as part of the process. Read what you're seeing as a precise finding rather than a bad one. Recovery Mode loading at all proves the machine powers correctly, its board and display work, and the firmware is fine, so nothing about the computer is in question. And the disk utility lists devices before it considers volumes: a drive with a damaged filesystem still appears, greyed out or unnamed. So a drive absent from a list that shows your externals isn't presenting itself as a device at all, which puts the fault below the filesystem where no repair can reach. On that generation the storage unclips and reads on an adapter.
Don't reinstall — call Guildford Data Recovery on 01483 901310; module removed and read on a generation-matched adapter, initialisation read under strict timeouts, imaged on restored readiness.
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.