Taking work now — the first look is freeSSDs posted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
SDRSSD Data Recovery 0800 6890668 Price my job
SDR / Every kind of SSD / SSD RAID and NAS

Two or more SSDs · Synology, QNAP, TrueNAS · server RAID · SSD caches

SSD RAID and NAS recovery. Every drive, in order, and nothing rebuilt in the meantime.

An all-flash NAS or an SSD RAID is several SSDs pretending to be one. Each member can fail in any of the ways on this site, and the array adds faults of its own on top: a failed rebuild, a lost configuration, a controller that no longer recognises its own disks, a cache that held data the main pool never received. We image every member first, then rebuild the array from the images, never from the originals. SSD sets start at £500 + VAT and enterprise storage at £1,250 + VAT, with one figure in writing after the free look and no data, no bill on most jobs.

Free first lookOne fixed figure in writingNo data, no bill on most jobsReturn postage paid

Rather talk it through? An engineer answers the bench line
0800 6890668

Array symptoms, and what each one asks of you tonight.

Not listed? Describe it on the form →
Degraded: one member amber or redRecoverable while the others are untouched. Do not start a rebuild.Do not delay
A rebuild began and stopped, or finished and the volume is corruptThe rebuild wrote across the set. Stop now; every member imaged before anything else.Do not delay
Volume crashed, or the NAS says the pool is missingMetadata, usually. The data is generally intact underneath.Do not delay
The SSD cache failed on a hybrid NASA write cache can hold data the pool never received. Send the cache drives too.Do not delay
The NAS itself is dead; the drives are fineOrdinary. Send the drives, labelled by bay.Everyday job
Packing it and posting it: a bare SSD travels in an anti-static bag inside a small padded box, with nothing able to move. Insure it for what the files are worth rather than the price of the drive, and use a tracked service. The posting address is not printed anywhere on this site; it arrives by email in reply to the form, with a booking sheet to print; the sheet inside the parcel is what matches it to your enquiry when it is opened. Or hand the sealed parcel in at the nearest of ten drop-off points, your name on the outside and the sheet inside; say where you are on the form and it comes by email. We pay the postage home either way. The whole of it is written up on the guide to packing and posting.

System by system, and what tends to go wrong.

Synology all-flash and SHRbtrfs on top of mdadm and LVM. A crashed volume is nearly always metadata; a rebuild that ran after a second failure is the danger.
QNAPext4 or ZFS (QuTS hero) on mdadm. Firmware updates and ransomware have both cost QNAP owners volumes; the underlying members are usually readable.
TrueNAS, Unraid and home-built ZFSPools that will not import after a lost member or a wrong-slot swap. ZFS labels on each member let the pool be reconstructed from images.
Server RAID: Dell PERC, HPE Smart Array, LSIA controller's foreign configuration, a failed battery-backed cache, or two members down. Keep the controller and send it with the set.

What the NAS or controller says, and what it means.

Describe yours to us →
What is going on The usual reason for it Where that leaves you
DegradedOne member downImage it; no rebuild
Crashed volume / pool missingMetadata damagedMembers imaged; volume rebuilt in software
Rebuild failed at n%A second weak member, or a stale oneStop; every member imaged
Cache device failedSSD cache held unflushed writesSend the cache drives with the pool
Foreign configurationController metadata out of stepDo not import; send the set
Volume mounts but files are missing or corruptA rebuild from a stale memberImages plus the controller's metadata are used to reconstruct

From the box arriving to your files going back.

Work we have closed →
01

Logged the day it lands, and the first look costs nothing Free

A case number goes on it the day the parcel is opened, and an engineer settles what has actually failed before anything else happens. The drive is read on our own equipment, never in a computer that might send it a TRIM command. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.

Nothing to pay for lookingA single figure, put in writingNo TRIM, no writes
02

Powered on our terms

Each member is imaged on its own, on our equipment, in the controller's diagnostic state where it has stopped responding. Weak members are imaged first and in short passes; the healthy ones read from end to end.

Vendor diagnostic modeNo hopeful reboots
03

Past the fault, to the map

From the images and the array's own metadata — mdadm superblocks, ZFS labels, a RAID controller's configuration — the set is reassembled in software, the volume mounted from the reassembled images, and every share, database and virtual machine checked before anything goes home.

Loader in RAM, never on the flashMapping tables put back together
04

A full image, then the volume

Nothing is worked on live. The whole drive is imaged once, weak pages retried in their own passes, and the file system is put back together on the image. Encrypted volumes are unlocked there too, with the key you supply, and never on the original.

One careful imageThe volume verified end to end
05

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not — and where nothing has come back, most jobs carry no charge at all. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have opened the files on a machine of your own.

No charge until you accept the figureFresh media, supplied with the jobFive to ten days at the bench

What arrives most often

  • Label every bay before a single drive comes out. Order matters. An array put back in the wrong sequence will not assemble, and working the order out from scratch adds days.
  • The rebuild is the enemy. A degraded array is a recoverable array. The rebuild that runs after a second member has quietly gone is what turns it into a hard job.
  • SSD caches are part of the data. A read cache can be ignored; a write cache cannot. On a hybrid NAS with an M.2 cache, send the cache drives with the pool.
  • Send the box only if it is small, or if it holds the encryption key. Otherwise, the drives alone, in a padded box, each in its own anti-static bag.

One job, followed all the way through.

UK · SDR-2026-0394JOB LOGGED ✓

A four-bay Synology on 870 EVOs, one red, one amber, and a rebuild begun regardless

With two bays showing trouble the unit was still entirely recoverable. What did the damage was the rebuild started afterwards, which wrote across the metadata the box holds for itself. Every member came here labelled; the two weak ones were imaged in short passes and the other two end to end. The mdadm and LVM layers were reconstructed from the images and the btrfs volume mounted from them. Every share opened exactly as it had before.

100% of the shares back6 days here, and back by post
Illustrative example — replace with a genuine case

What helps, and what harms.

Do this much first

  • Power the NAS down and leave it down
  • Write each bay number on its drive
  • Send any SSD cache drives with the pool
  • Tell us the RAID level, the file system and whether encryption was on

What sets us back

  • Starting or continuing a rebuild
  • Re-creating the volume or the pool
  • Running a repair on a crashed volume
  • Swapping drives between bays to see what happens

Questions answered before you commit.

Should I rebuild with a new drive?

Not until the data is safe. A rebuild writes across every member, and if a second member is weak, as it often is by the time the first has failed, the rebuild destroys what it was meant to protect.

Do I send the NAS box?

Send the drives, labelled by bay. Send the box as well only if it is small, or if it holds an encryption key you cannot supply separately.

What about the M.2 cache in my NAS?

Send it with the pool. A write cache can hold data the main volume never received.

What does it cost?

Sets start at £500 + VAT and enterprise storage at £1,250 + VAT. One figure for the whole set, written down after the free look.

How long does it take?

Five to ten days at the bench for most sets. Priority handling is quoted when you ask for it.

Begin here if yours is doing the same thing.

U.2 and U.3 enterprise NVMe →SAS SSDs →SATA 2.5-inch →Samsung →Seagate IronWolf →Western Digital Red →

Power it down, label the bays, and send the form.

Every member imaged before anything is put back together. The first look is free, and one figure for the set is written down before any chargeable work.

0800 6890668

Price my jobPacking and posting