Most of the people who walk in from Balerno, Currie and the wider west Edinburgh edge after an SSD failure say the same sentence: "It was fine yesterday." That is the defining feature of solid-state storage going wrong — it almost never warns you. A spinning hard drive used to click, grind or slow down for weeks before it died. An SSD usually works perfectly until the moment it doesn't, and then the laptop boots to a screen telling you no operating system was found. This is the guide we'd hand the family member or small business owner ringing in a panic, walking through what's actually happening inside the drive and what to do in the next hour so the data can still be saved.
It's written around what we see on the data recovery bench week to week, not the marketing material on the side of the box. SSDs are excellent storage, but their failure mode is genuinely different from the old drives they replaced, and most of the bad outcomes we recover from come from people treating them like spinning disks.
SSDs Don't Get Sick — They Just Vanish
A traditional hard drive is a mechanical device. When it starts to die, you hear it. Bearings whine, the head clicks, files take ten seconds to open. You get a long, noisy warning window. SSDs have no moving parts. They sit silently doing their job until a controller chip, a power circuit or a critical metadata sector gives up — and then they go from "fine" to "completely invisible to the BIOS" in a single restart.
A recent walk-in from a household near Balerno was a textbook example. A two-year-old NVMe drive in a working-from-home laptop. The owner had shut the lid on Sunday evening with a tab still open. Monday morning, the laptop went straight to a UEFI screen that listed no boot device. The drive itself was electrically dead — the controller had failed. There had been no slow performance, no warning popup, no SMART alert. That's the normal SSD failure pattern, not the exception.
The First Hour Matters More Than the Repair
What you do in the first hour after an SSD failure decides what's possible later. The rule on the bench is simple: stop using the machine. If it still boots intermittently, every boot attempt rewrites portions of the drive's internal mapping table — the structure that tells the controller where each file actually lives. Aggressive recovery tools, repeated power cycles and "let's see if it works again" attempts can wipe out the very metadata a professional needs to rebuild your files.
The right sequence is shutdown, set the machine aside, and decide whether the data on it is worth recovering before doing anything else. If it isn't critical — synced cloud documents, a clean reinstall is fine — you can move on to a new drive. If it is critical, stop pressing power buttons. The mistake we adopt the most is a family member who has spent an evening running consumer recovery utilities against a drive that was already partly readable, only to find by morning that the drive is now completely unrecognised.
The Three Ways SSDs Actually Die
From the bench, SSD failures fall into three broad categories, and which one you have determines whether the data is recoverable in software, in firmware, or only by physically reading the memory chips.
Controller failure. The little chip that manages everything on the drive has given up — usually a power-related event or a bad firmware state. The drive vanishes from BIOS entirely, or shows up at the wrong capacity (a 1 TB drive reporting as 8 MB is a classic controller fault). Software recovery is impossible because the operating system can no longer talk to the storage at all.
NAND wear and bad blocks. The actual flash memory has accumulated too many worn sectors and the controller can no longer remap them quickly enough. The drive becomes painfully slow, files disappear in chunks, and writes start failing silently. Often recoverable in software if caught early — but every reboot makes it worse.
Firmware corruption. The drive is electrically healthy but the internal management tables are damaged. The BIOS sees it but the operating system can't read it, or it presents as raw unformatted space. These cases sometimes recover with vendor tools and a controlled reset — but not always, and never with consumer-grade undelete utilities.
When Chip-Off and Microsoldering Are the Only Option
For controller failures and severe board damage on an SSD, the route to the data is physical. The NAND flash chips themselves still contain the bits — the controller in between simply can't read them any more. The recovery path is chip-off: desoldering the NAND chips, reading them on a specialist programmer, and reconstructing the file system using the controller's specific scrambling and wear-levelling algorithm.
It's slow, intricate and not always successful, but for genuinely irreplaceable data — wedding photos, business records that were never backed up, a thesis with no cloud copy — it's often the last route in. This is where our microsoldering work overlaps with data recovery: a steady-handed lift of the NAND, a clean read, then weeks of reconstruction. We don't promise outcomes on chip-off work because nobody honest can, but we are clear about what's possible the moment we open the case.
Backups That Survive a Sudden SSD Death
The lesson every Balerno or Currie customer takes home after an SSD recovery, successful or not, is that the backup strategy that protected spinning drives doesn't protect SSDs as well. A spinning drive gave you a week or two to act. An SSD gives you no time at all. The backup needs to be running already, before anything goes wrong, because the day you notice the problem is usually the day you've already lost the chance to copy anything off.
For homes, an automatic cloud backup of the documents and photos folders is the bare minimum. For small businesses, the 3-2-1 idea still holds — three copies of the data, on two different types of media, with one of them off-site. We often pair the SSD upgrade itself with a backup setup as part of our hardware upgrades work, because a new fast drive is the natural moment to also set the safety net behind it. The new drive will outlast the old one in performance; it won't necessarily outlast it in years.
Frequently Asked Questions
Common questions we hear from customers around Balerno, Currie and the west of Edinburgh when an SSD has stopped responding.
- Can a dead SSD really be recovered? Sometimes — it depends entirely on which part has failed. Firmware issues and worn NAND can often be read in software. A dead controller usually needs chip-off work, which is slower and never guaranteed.
- Is it worth running recovery software myself first? Only if the drive is still readable and you have a target disk to write the recovered files onto. Running recovery tools against a drive that's in trouble can finish off the damage and make professional recovery harder.
- Why didn't my SSD warn me before it failed? SSDs don't have the gradual mechanical decline that hard drives did. SMART data tracks wear, but a controller or firmware fault can happen with the SMART counters reading completely healthy.
- Do you collect drives from Balerno and the surrounding villages? Yes — we cover Balerno, Currie, Juniper Green, Ratho and the wider west Edinburgh area for drop-off, collection and home visits, with the workshop in central Edinburgh.
Getting an SSD Recovered Around Balerno
Short version: if your laptop or PC has decided overnight that its drive doesn't exist, don't keep restarting it. Don't run undelete tools against a drive that's already in trouble. Bring it in — or send a photo of what the screen is doing — and we'll tell you honestly whether it's a quick firmware reset, a software-stage recovery, or chip-off territory before any work begins. Our data recovery team covers Balerno, Currie, Livingston and the rest of west Edinburgh from the workshop, with collection where the drive is too risky to move twice. Book a consultation online and we'll take a look the same week.
Last updated: 20 June 2026