Data Recovery Case File · Solid State & Flash · He Stopped After One Step
Being Present and Being Bootable Are Answered at Different Stages
His enquiry separates two things that are usually run together. A machine found sitting at its firmware screen, where the drive "appeared in the firmware but is no longer recognised as bootable media" — and then: "I've replaced the drive and taken no further action, but I would very much like the data off it." Those are two different findings, and the drive still being listed is considerably better news than a drive that has vanished.
| Media | 2TB solid-state drive of high-performance type — enumerating at firmware level, no longer accepted as a startup device; removed from service and preserved |
| Reported situation | Machine left running and found at its firmware screen · drive listed in firmware · drive no longer recognised as bootable · replacement drive fitted · original removed and no further action taken · contents required |
| Fault class | Enumeration succeeding with startup structures unreadable — device-level function retained; boot region or filesystem damage indicated rather than controller failure |
| Equipment used | Firmware presence and bootability distinguished as separate findings · removal from service credited as preservation of state · imaged write-blocked at the block level before any interpretation · boot and filesystem structures examined from surviving copies · files validated by opening |
The decode: what each stage of the start-up asks
What firmware listing the drive establishes: the device answered. To appear at that level, the drive powered, its controller completed its introduction, and it stated what it is — which is the whole of the device-level question, and it passed.
What "not bootable" asks instead: a later and quite different question. Having found a drive, the machine looks at the start of it for a structure describing a startup system — and reports the drive as unbootable when that structure cannot be read or does not describe anything it can start from.
Why the distinction is the good news: the failure is in a small region rather than in the device. Boot structures occupy a tiny fraction of a drive, and their loss says nothing about the rest — the files can be entirely intact behind an unreadable startup record.
Why that differs from the harder cases: a solid-state drive whose controller has failed disappears completely, listed nowhere and reachable only past the controller. His drive is answering normally, which means the ordinary route to reading it is available.
What most likely happened: the machine was running unattended and ended up at the firmware screen, which suggests it restarted. An interruption while startup or filesystem structures were being updated can leave them inconsistent, and the drive then presents itself perfectly while the machine cannot start from it.
Why fitting a replacement was exactly the right first move: it separates two jobs. The machine is back in service and the original drive has been set aside untouched — so nothing further has been written to it, and its state is preserved as it was at the moment of failure.
Why taking no further action matters so much on this fault: the tempting next steps are startup repair, filesystem checking, or a fresh installation. All three write to the drive, and two of them target precisely the structures that would be used to rebuild the volume — so restraint has kept the position considerably better than it would otherwise be.
What the recovery involves: the drive imaged at the block level, and the volume reconstructed from the image using the duplicate structures filesystems maintain. Everything is then answered from the copy, with the original read once.
What must not happen: no reinstalling onto it, no repair utilities, and no initialising. The drive should stay out of service until it has been imaged.
On the bench
Firmware presence and bootability were distinguished as separate findings — enumeration at firmware level requiring power, controller introduction and identification, all of which succeeded, whereas bootability additionally requires a readable startup structure at the drive's beginning, which occupies a negligible fraction of capacity and whose loss does not implicate stored content. Removal from service was credited as preservation of state. Imaging ran write-blocked at the block level before any interpretation.
The outcome
The two findings distinguished, removal credited as preservation, and the drive imaged at the block level before interpretation. 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: still being listed is the good news. Enumeration and bootability are answered at different stages, and a startup structure occupies a negligible part of the drive — so its loss says nothing about your files.
A drive listed by the machine but no longer bootable
Fit a replacement and leave the original alone, which separates getting the machine working from getting the data back. Those are also two different findings: appearing at firmware level means the drive powered, introduced itself and stated what it is, while "not bootable" only means the small structure describing a startup system couldn't be read. That region is a negligible fraction of the drive, so its loss says nothing about your files — and a drive still being listed is in much better shape than one that has vanished entirely. Avoid startup repair, filesystem checks and reinstallation, since all three write to it.
Leave it out of service — call Easy Data Recovery on 028 9002 0144; presence and bootability distinguished as separate findings, imaged at the block level, volume rebuilt from surviving structures.
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.