Data Recovery Case File · Solid State & Flash · Two Problems, Not One
One Drive May Already Be Readable
His enquiry described a dead machine and, without meaning to, two entirely separate jobs. "I have two disks from a failed PC. One is a 240GB SSD, the other a 1TB hard disk. The PC wouldn't boot, nor would the computer see the SSD in the boot" menu. The natural framing is my computer died and I need my data back. But there are two drives here with different roles and different conditions, and one of them is very probably fine right now — readable today, on any working machine, at no cost. Separating them is the first thing to do and it frequently ends the enquiry.
| Media | 240GB solid-state system drive and 1TB hard disk from a non-booting desktop — solid-state drive not appearing in firmware; second drive condition unestablished |
| Reported situation | Desktop machine failing to boot · solid-state system drive not listed in the firmware boot menu · second internal hard disk present · both drives removed from the machine · contents required |
| Fault class | System drive absent at firmware level; secondary drive to be assessed independently and likely unaffected |
| Equipment used | Secondary drive assessed first on an external connection · system drive addressed in vendor technological modes where firmware detection had failed · both imaged write-blocked · contents verified by opening |
The decode: which drive is which problem, and what to do today
Why the second drive should be tried immediately: in a machine configured this way the small solid-state drive holds the operating system and programs, while the large hard disk holds documents, photographs and media. The hard disk has no involvement in booting — so a machine that will not start says nothing whatever about it. Connected to any working computer through an inexpensive adapter or caddy, it will very often simply appear with everything on it. That is a five-minute test, and for many people in this position it is the entire answer.
Why the system drive is the real fault: not appearing in the firmware boot menu is a specific and serious finding. That menu is produced before any operating system loads, by the machine's own firmware asking the storage bus what is attached. A drive missing from it has failed to identify itself at the most fundamental level — which is different from a drive that appears and cannot be read, and it eliminates every software-level explanation.
What that usually means on a solid-state drive: the controller has not completed its start-up. These drives run their own firmware, and where its internal structures are damaged the controller cannot reach the point of announcing itself. The memory holding the data is usually untouched behind it, and the route is the manufacturer's technological and safe modes — a way to address a drive whose normal start-up cannot complete, repair the firmware area and restore addressing.
Why it is worth knowing what was on each: if everything that matters lives on the hard disk, the failed system drive may not need recovering at all — its contents are an operating system and applications, all reinstallable. That is a genuinely common outcome and it turns an expensive-looking situation into a caddy and an afternoon. The exception is anything saved to the desktop or a user folder, which lives on the system drive rather than the data drive, and which people routinely forget.
What not to do: not put either drive back into the failed machine to test it. If the failure was a power fault, the machine that killed one drive can damage another. Both should be assessed on known-good equipment.
On the bench
The secondary drive was assessed first on an external connection, since it plays no part in booting and a machine that will not start says nothing about it — establishing at no cost whether the material actually needed was already readable. The system drive, absent from firmware detection, was addressed through its vendor technological modes, where a controller that cannot complete start-up can still be reached and its firmware area repaired. Both were imaged write-blocked and contents verified by opening.
The outcome
The data drive read immediately on an external connection, the system drive addressed in vendor modes and both imaged and verified. 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 with a dead machine and more than one drive: these are two jobs rather than one. The large data drive plays no part in booting, so a machine that will not start says nothing about it — connect it to a working computer through a caddy and it will often just appear. The system drive missing from the firmware boot menu is the real fault, and that is a controller failing to complete start-up rather than anything software-level.
Dead computer with more than one drive in it
Try the data drive first, on any working computer, through a cheap caddy or adapter — it takes five minutes and often ends the problem. In a machine set up this way the small solid-state drive holds the operating system and programs while the large hard disk holds your documents, photographs and media, and the hard disk has no part in booting at all. So a machine that won't start tells you nothing about it. Just don't put either drive back into the failed machine to test them, because if the fault was electrical it can damage a second drive. The system drive missing from the firmware boot menu is the genuine fault, and that's its controller failing to finish starting up rather than anything at software level. Remember anything saved to your desktop lives on that drive, not the data one.
Try that one in a caddy first — then call Newcastle Data Recovery on 0191 406 1051; each drive assessed separately, system drive addressed in vendor technological modes, both imaged write-blocked.
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.