Open, and taking cases in · 9am–5:30pm, weekdays In a hurry? Call 0800 6890668
CDR Cardiff Data Recovery 0800 6890668 Book it in
CDR / The things we recover / SSD & NVMe

Devices · SSD & NVMe drives

Cardiff SSD and NVMe recovery. Gone with no warning; the files are almost always still on the flash.

No sound, no warning light. It shuts down fine on Friday; by Monday the BIOS has no idea the drive exists. Three causes cover nearly all of it — a controller that has died, firmware that has corrupted itself, or the power going during a write. Most of what reaches us from Cardiff carries a Western Digital or a Crucial label. We work at the flash, and the sooner it arrives the better.

No files back, no fee on most jobs One fixed price, after a free diagnosis It comes to us by post from Barry, Pontypridd or Newport

Describe the symptoms to an engineer
0800 6890668

This comes in most weeks — routine work for the bench.

Nothing matching? Try the triage →
Posting it to us: post it tracked and fully insured to the intake lab, and the journey back is on us; ring first if you would like an engineer to check how it is packed before you seal the box. Every stage is set out on the posting guide.

The SSD and NVMe makes that arrive most often.

Western DigitalThe Blue SA510 on SATA; the Black SN770 and SN850X on NVMe; SanDisk badges over identical silicon.
SeagateSATA BarraCuda SSD · FireCuda 530 on NVMe · the One Touch SSD.
Crucial & MicronSATA is the MX500. NVMe: P3, P5 Plus, T500.
Phison under other namesPNY CS900 · Kingston A400 · Patriot Burst and many more — one controller sold under a dozen badges, and it fails the same way behind every one of them.

Decoding the error messages.

Not seeing yours? →
What shows upWhat has gone wrongDo this now
The drive reports itself as SATAFIRM S11Just one cause — a Phison controller that has reverted to its ROMDo not run the maker's utility
The BIOS lists nothingNearly always the controller or the firmware; the NAND behind it is fineWork at the chip level
It shows 0GB, or some capacity that is plainly wrongThe flash translation layer, the FTL, has collapsedNo more reboots
SMART health collapses overnightGenuine cell wear, or a controller reporting rubbishCheck the maker's notice, then take an image
Reads fail with 0x800701E3The fault sits in the hardwareImage it, and run no repair tools
After a firmware update: Boot device not foundThe firmware write stopped part-way, leaving nothing bootableLeave the power off

From the parcel to your files coming back.

Cases we have logged →
01

A case number, and a diagnosis at no cost Free

The diagnosis costs you nothing. Every item that arrives is logged under a case number of its own, and an engineer works out what has actually failed — then tells you plainly which files can come back and which cannot. The price follows that: one fixed figure, in writing, and no work begins until you have read it and said go ahead.

Diagnosis at no chargeOne fixed figure in writingNothing owed yet
02

Powered up on our terms

A drive in trouble loses a little more ground every time it is switched on. We bring it up in a controlled service mode instead, so the flash answers to the bench directly rather than to firmware that has stopped coping.

Brought up in service modeNo trial-and-error reboots
03

Going round the controller

If the controller stays silent, we lift the flash contents directly and rebuild the translation table in software. On its own a raw dump is just noise. Restore the table and your folders come back into view.

NAND read directlyTranslation tables rebuilt
04

Back into the right sequence

Wear levelling scatters a single document across every die on the board; that is exactly what it is there for. We reassemble the pieces in order, rebuild the volume, and tick each entry off against the listing.

Wear levelling reversedThe whole volume checked
05

You approve it, then it goes back

Nothing is billed while you are still deciding. A complete listing of what came off the drive reaches you first, and the invoice only follows your yes. Files travel back on media bought new for the job, return postage ours, and we do not close it here until every one of them opens on the machine you will use.

The file list is yours to approveBack on media bought newThe postage back is on us

What we usually find first

  • SATAFIRM S11 belongs on a bench, not on the kitchen table — the name shows up once a Phison controller has dropped into its ROM. The utility the forums recommend calls it a repair, but what it actually does is regenerate the drive, and that throws away the map of where every block used to sit. The proper route is to write working code into the controller, then rebuild that map.
  • Treat a health percentage as a claim, not a reading — the software only repeats a figure the controller gave it, and once those tables are broken the figure means nothing. Firmware from more than one maker has been caught undercounting the wear on its own cells.
  • Every controller lays its flash out differently — the XOR mask and the page order have to be solved first, or a raw dump tells you nothing at all. Lifting the chips off the board is the fast bit, and on its own it hands nobody a single file back.
  • Deleted really is deleted on flash: TRIM gets to work on those blocks within hours, unasked and with nothing on screen to show for it. Lose a file off an SSD and your window is an afternoon, not a fortnight.

One risk worth knowing about: a firmware update rewrites the area that records where each file lives, and if the power goes mid-way there is no earlier copy underneath to fall back on. Nearly all updates go through cleanly. Copy the drive off before you start one, and if it is already misbehaving, leave the update well alone.

Straight out of the casebook.

CF · CDF-2026-0754LOGGED ✓

A firmware update stalled and the NVMe went silent

The laptop's system SSD stopped part-way through a firmware update and would not read afterwards. Working in technical mode, an engineer rebuilt the translator tables, and ten years of one photographer's edited catalogues came back intact.

99% came back5 days after arrival

Before you send it off.

Start with these

  • Power it down fully — sleep will not do
  • Write down the full model number
  • Deleted something? Ring us that day
  • Send the bare drive or M.2 card, not the caddy

What to avoid

  • Rebooting over and over in the hope it appears
  • Pushing a firmware update onto an ailing drive
  • Running any tool that writes to the drive
  • Keeping the machine in use after files went missing

What we get asked, week in, week out.

I deleted something off an SSD an hour ago. Can it come back?

Maybe, if you shut the machine down in the next few minutes rather than tonight. An SSD runs TRIM on its own initiative: the blocks behind a deleted file get scrubbed while the drive sits there powered up, and no spinning disk behaves that way. This is the rare case where pulling the plug is the right move.

Not one machine will show the drive. Is it finished?

Seldom. When a drive goes quiet, the controller or the firmware has failed, and the NAND sitting behind them is generally untouched. Read those chips on the bench and the bulk of it turns up again.

Is an SSD harder work than a spinning disk?

Different, rather than harder. A hard disk fails in the parts that move; an SSD fails in its controller and the tables that controller keeps. As long as TRIM has not already swept through, your chances are good.

What about soldered-down flash?

We take those too. They run alongside the Mac and laptop jobs: the same work on the flash, only with the chips read where they sit.

An unplugged drive keeps whatever it still holds.

A failing drive has only so many starts left in it. Spend none of them. Keep the power off, and the free diagnosis will tell you what is still readable.

0800 6890668