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 / Casebook

Jobs closed · written up after

The casebook. Closed jobs, described exactly as they ran.

Approval governs all of it. Nothing is published until the customer has been through the recovered material and told us to go ahead, and at that point every identifying detail comes out: the person, the town, the serial number. Each entry then points to the page dealing with that class of fault, for anyone wanting method rather than narrative. The entries below are illustrative examples written to show the shape a casebook entry takes; they are marked as such and will be replaced by genuine closed jobs as they are approved for publication.

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

Most recent at the top.

Also shown on the home page →
UK · SDR-2026-0417JOB LOGGED ✓

A 1TB WD_BLACK SN770 that went missing after a Windows update

A Lenovo laptop stopped at a black screen after an update, and the BIOS no longer listed a drive. The stick came out and came here on its own. In the controller's diagnostic state it answered with its map intact but two firmware modules damaged; a temporary loader brought it up read-only and a full image took eleven hours. A decade of a photographer's edits opened first time.

99.6% of files recovered4 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0409JOB LOGGED ✓

A 2TB SanDisk Extreme Pro V2, unreadable the morning after a wedding

A photographer offloaded three cards onto the drive, ejected it, and next morning the Mac said the disk was not readable. Nothing was written to it after that, which mattered. The board showed a solder fault at the bridge; the SSD behind it was separated and read on its own interface, the APFS volume put back together on the image, and every RAW file accounted for.

Every RAW file recovered4 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0402JOB LOGGED ✓

A 480GB Kingston A400 that forgot its own name

A family PC stopped booting, and the BIOS listed the drive as SATAFIRM S11. Nothing had been run against it, which mattered. On the bench the controller took a loader into its RAM, the service area read back cleanly, and the translation table was rebuilt from it. Ten years of photographs and the household accounts came off in one pass.

100% of it recovered3 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0401JOB LOGGED ✓

A Surface Laptop 4 with a dead board, BitLocker on, and the key in a Microsoft account nobody had checked

The laptop died; the 2230 NVMe drive inside was healthy. BitLocker had been on from the day the machine was set up, as it is on most Surfaces, and the owner did not know it. The recovery key was where Windows had put it, in the Microsoft account under Devices. The drive was imaged whole, the volume unlocked on the image, and everything came back.

100% of it recovered3 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0398JOB LOGGED ✓

A Silicon Power A55 from an office PC, showing 0GB and a strange name

The PC lost power during a print job and came back with a drive called SM2258XT at 0GB. The owner declined the initialise prompt, which was the right call. In the diagnostic state the controller took a loader, the service area read back with its map partly damaged, and the rest was rebuilt from the flash. Every document came back; two temporary files did not.

99% of it recovered3 days here, and back by post
Illustrative example — replace with a genuine case
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
UK · SDR-2026-0385JOB LOGGED ✓

A folder of client contracts deleted from a WD_BLACK SN770, with the laptop shut down inside two minutes

A solicitor deleted the wrong folder, emptied the bin, realised, and held the power button down. The laptop came here whole. The drive was imaged read-only in its diagnostic state, with its housekeeping held off, and the NTFS records still named most of the files. Eighty-six per cent of the folder came back by name; the rest had already been trimmed. The client was told which, and why.

86% of the folder recovered3 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0376JOB LOGGED ✓

A Corsair MP510 whose controller had cooked itself in a small case

A compact gaming PC with no airflow over the M.2 slot, and a drive that had run hot for two years before it stopped. The Phison E12 controller was dead; the drive was not hardware-encrypted, so the four flash packages came off and were read directly. The interleave and scrambling were undone, the map reconstructed from the flash, and the game saves, the photos and the tax paperwork came back. Two months of browser cache did not.

98% of user files recovered6 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0371JOB LOGGED ✓

A 2019 MacBook Pro after a glass of water, with a thesis on it

The machine had been dried on a radiator, which did not help, and powered on twice, which helped less. On the bench the board showed corrosion around a power-management chip and a dead rail. The chip was replaced, the rail came up, and the machine reached the point where FileVault asked for a password. With the owner's password entered, the volume unlocked and was imaged whole. The thesis was two chapters further on than the last backup.

100% of the volume imaged5 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0369JOB LOGGED ✓

A 2TB Samsung 980 Pro on 3B2QGXA7, locked read-only mid-project

A video editor's desktop drive stopped accepting writes half-way through an edit, and Magician offered the firmware update. The owner asked first, which was the right call. The drive was imaged read-only in full in six hours, with the project files checked by opening them before anything was invoiced. Only then was the drive retired.

100% of the project recovered2 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0344JOB LOGGED ✓

An Intel 320 out of a workshop PC, at 8MB after a power cut

A joinery's estimating PC, ten years old, on an Intel 320 that had never missed a day until the power went. The BIOS listed 8MB and a serial number of BAD_CTX. Nothing had been run against it. The firmware was put right in the controller's memory on the bench, the map read back intact, and the drive imaged whole. Every quote and every drawing came back.

100% of it recovered4 days here, and back by post
Illustrative example — replace with a genuine case
UK · SDR-2026-0339JOB LOGGED ✓

A six-drive NVMe ZFS pool that would not import after a failed member

A small hosting firm's pool lost one Micron 7450 and, in the scramble, a second was pulled from the wrong slot. Every drive came here labelled, the quiet one was imaged in its controller's diagnostic state, and the pool was imported from the six images with the slot order reconstructed from the ZFS labels. The datasets mounted and the virtual machines started.

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

Yours could be next on the list, or not, as you prefer.

Nothing is published without your say-so. The first look is free either way.

0800 6890668