Open, and looking at it costs nothing · 9am–5:30pm, Mon to Fri Ring instead, it is quicker: 0115 8220606
NDR Nottingham Data Recovery 0115 8220606 Get my quote
NDR / Hardware we take in / SSD and NVMe drives

Devices · SSDs and NVMe drives

Nottingham SSD and NVMe recovery. Almost always, the flash is fine; it is the controller that stops.

An SSD gives you no noise. The machine shuts down as usual, and in the morning the BIOS lists no drive at all. There are essentially three reasons: the controller fails, the firmware becomes corrupted, or the power goes during a write. We see the same three in an instrument PC from a lab on Pennyfoot Street, Nottingham, and in a home machine in Sherwood, and WD and Crucial badges reach us more than any others. Work happens at the flash level, sooner rather than later. One drive: £300 + VAT, once the free look is done.

Only pay if we recover your data, on most jobs Free diagnosis first, then a single price, in writing Parcels come in from Derby, Lincoln and Loughborough

Ask an engineer and the first look is free
0115 8220606

SSD symptoms, and how much time each leaves you.

Yours not here? Open the finder →
How to pack and post it: ring us on 0115 8220606 for a quote, or use our quote form. Then pack it so that nothing can move inside the box, insure the parcel for what the files are worth to you (not what the drive cost), and send it tracked to the intake lab in Manchester. We pay for the return. Would you like to talk the packing through with an engineer before closing the box? Please ring first. The details are in our packing and postage guide.

The makes we see, and how each one fails.

Western DigitalOn SATA, the SA510 Blue. On NVMe, the SN770 and SN850X Black. The same silicon turns up again under the SanDisk badge.
SeagateFireCuda 530 for NVMe, BarraCuda SSD for SATA, and the One Touch.
Micron, and CrucialMX500 for SATA; P3, P5 Plus and T500 for NVMe.
Phison, wearing other badgesPatriot Burst, Kingston A400, PNY CS900 and plenty more: a dozen badges over one controller, and all of them stop the same way.

What that message about the SSD is telling you.

Say what yours is doing →
What is happeningWhat usually causes itWhat that means for you
It gives its own name as SATAFIRM S11Only one cause: a Phison controller running from its ROMLeave the vendor utility alone
Nothing appears in the BIOSController or firmware failure almost always, usually with the flash left intactThat is chip-level work
Reported as 0GB, or at some plainly wrong sizeThe flash translation layer, which records where all the data sits, has failedStop restarting it
SMART health drops away overnightGenuine cell wear — or a controller talking nonsenseRead the maker's advisory, then image the drive
0x800701E3 on every readThat one is hardwareImage it; run no repair tool of any kind
Boot device not found, and it began with a firmware updateA firmware write that finished half-way, and nothing bootsKeep the power off it

From the parcel arriving to the files going home.

Jobs already finished →
01

Booked in the day it arrives, and the first look is on us Free

Your case number is assigned when the item is received. Then an engineer works out what went wrong (no charge). At this point, you receive a basic summary of which parts are recoverable and which are not. You also receive a single written quote for the price of the recovery. Accept the quoted price or turn it down, and there is no obligation to pay anything.

The first look is freeOne fixed figure, in writingNo charge at this point
02

Brought up on our terms

Each power-up costs a failing SSD some life. On this bench we start it in vendor service mode instead, which lets us talk directly to the flash and keeps worn-out firmware out of the conversation.

Started in the vendor's service modeNo hopeful restarts
03

Behind the controller, chip by chip

If the controller does not answer, each chip is addressed individually, and software rebuilds the translation table. On its own, a raw dump is worth nothing. Hand the table back and your folder structure comes with it.

Flash addressed directlyThe translation tables rebuilt
04

Back into order

Wear levelling is meant to spread a document across every die fitted, and it certainly does. The sequence is put back together piece by piece, the volume is reassembled, and each entry is checked against the list sent out with the job.

The wear levelling unpickedThe whole volume verified
05

The file list comes before the bill

A complete file list will be provided before any invoicing. Simply say "yes" or "no" to what we found: yes means it is billed, no means it is not, and in most cases you only pay if we recover your data. What we find is posted to you on media purchased specifically for your case, at no additional cost to you. We consider the process complete once you have opened those files yourself on your own computer.

Nothing is charged until you agree the figureNew media, bought in for your jobWe pay to send it home

What comes in most often

  • SATAFIRM S11 is bench work. A Phison controller running from its ROM identifies itself as SATAFIRM S11. Forums will point you at a tool described as a repair. In reality, it regenerates the drive and throws away the record of where each block was. Done properly, working code goes onto the controller first, and the record of where each block sat is rebuilt afterwards.
  • Health percentages are claims made by the controller, not actual measurements. Whatever number shows on screen is the one the controller decided to give you, and once its tables break, it means nothing. Firmware has more than once been caught understating wear on its own maker's cells.
  • Flash layouts vary from controller to controller. The page order must be worked out and the XOR mask removed before a dump means anything. Getting the chips off takes an hour on the bench; decoding what they contain takes far longer, and it happens controller family by controller family.
  • On flash, deleted means deleted: unasked, and with nothing shown on screen, TRIM will have been over those blocks within hours. Delete a file on an SSD and you have that day, not that month.

Before you take an update: firmware re-maps the physical location of your data, and if the power drops during the process there is no previous version underneath. Most updates complete without issue, so none of this argues against updating; simply back up your files first. What should never be updated is a drive that is already malfunctioning.

One of these, from start to finish.

NG · NTG-2026-1904ON THE LOG ✓

An NVMe that quit mid-update, with ten years of edits on it

Halfway through a firmware update, the laptop's system SSD stopped answering, and nothing would come off it. Technical mode let an engineer reach the translator tables and rebuild them, so the controller could map the flash beneath it again. A photographer's ten years of edits opened at the first try.

99% of the files back5 days between arrival and return

What helps, and what does damage.

Worth doing first

  • Shut the machine down properly: not sleep, not hibernate
  • Take down the full model number
  • If you have deleted something, ring the same day
  • The drive or M.2 card travels on its own, without a caddy

What makes it harder

  • Restarting again and again in the hope it appears
  • Pushing a firmware update to a drive that is already failing
  • Running anything whatever that writes to it
  • Going on using the machine once files vanish

Answers before you spend anything.

Files went off an SSD this morning. Is there any chance?

Possibly, though the window is usually hours, not days. Blame TRIM: if left powered, an SSD keeps clearing the blocks that held deleted files, on a schedule nobody asked for. No spinning disk has ever done anything like this. Normally, pulling the plug is the wrong instinct; for this one fault, it is exactly right.

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

Rarely. Silence usually means the firmware or the controller has failed, and the flash behind both is untouched. Reading those chips is bench work, and most of what they hold comes back.

Is an SSD a tougher job than a spinning disk?

Different, not harder. A hard disk fails at its moving parts. An SSD fails at its controller, or in the tables the controller keeps. Provided TRIM has not cleared those blocks yet, the chances of recovery are good.

The flash is soldered to the board. Then what?

Soldered storage, as found in T2 and Apple silicon Macs and certain laptops, is not something we take on. If you are unsure whether yours is soldered, ring us first.

Switched off, a drive cannot get any worse.

The look costs nothing. It gives you a file listing of what opened and what did not, along with the cost of finishing the job, in writing, before anything chargeable begins. In most cases you only pay if we recover your data. Do not switch the drive on until you have that listing.

0115 8220606