Taking work now — the first look is freeNAS drives posted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
NDRNAS Data Recovery 0800 6890668 Price my job
NDR / 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 firm, the town, the serial numbers. 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 · NDR-2026-0540JOB LOGGED ✓

A Synology DS920+ in SHR: drive 2 failed, then drive 4 at 38 per cent of the repair, and the pool marked Crashed

The owner powered down when the repair stopped. Drive 4 had unrecoverable read errors and was imaged slowly with its bad areas last; the original drive 2 was read for the stripes the repair had not reached; the healthy pair end to end. The SHR arrays were assembled from the images, the LVM volume mapped, and the Btrfs file system mounted read-only from the virtual volume. Every folder came back.

99.98% of the volume recovered7 days here, and back by post
Illustrative example — replace with a genuine case
UK · NDR-2026-0526JOB LOGGED ✓

A WD My Cloud Home 6TB, dead after a power cut, with a decade of photographs and no other copy

The unit would not start and the app showed nothing. The drive was imaged, the ext4 cloud volume mounted from the image, and the SQLite index recovered intact, so that every content-ID file came back under its own name in its own folder.

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

A QNAP TS-453D in RAID 5 hit by Deadbolt, with snapshots on and a business that did not know it had them

The network cable came out the moment the ransom page appeared. All four drives were imaged, the pool reassembled from the images, and a snapshot from two days before the attack found beneath the encrypted volume. It was mounted from the image and copied out whole.

98% of the share recovered from the snapshot6 days here, and back by post
Illustrative example — replace with a genuine case
UK · NDR-2026-0542JOB LOGGED ✓

A Netgear ReadyNAS 314 whose X-RAID expansion stopped in a power cut, then reported the volume dead

The unit offered to remove the inactive volume; the owner powered it down. All four drives were imaged, the reshape point read from the metadata, the layered arrays assembled with the old geometry before it and the new one after, and the Btrfs volume mounted from the virtual set.

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

A WD My Cloud 4TB with a red light after the OS 5 update, and a family's only copy of everything

The update had failed and the unit would not boot; the owner did not reset it. The drive was imaged, the ext4 data volume mounted from the image, and every folder came back with its name. The board was fine; only its firmware had gone.

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

A Buffalo TeraStation TS3410 in RAID 5 showing E14 after a power cut, and a school's shared drive on it

The manual's next step was a rebuild; the unit was powered down instead. All four drives were imaged, one with bad sectors taken last, the array assembled from the superblocks on the images, and the XFS log replayed on the virtual volume before it was mounted read-only.

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

A TrueNAS SCALE box with six drives in RAIDZ2 that would not import after a power cut, and an import -F that made it worse

Two drives had dropped and the owner had forced the import, discarding the last transactions. All six drives were imaged and the pool imported read-only from the images at the last transaction group before the force. The datasets came back complete, including the one the force had lost.

100% of the datasets recovered7 days here, and back by post
Illustrative example — replace with a genuine case
UK · NDR-2026-0523JOB LOGGED ✓

A QNAP TS-453Be, dead on a Monday morning, with a small firm's shared drive on it

The boot flash had worn out. The four drives were imaged, the QTS storage pool assembled from the images with its thin volume mapped, and the ext4 file system mounted from the virtual volume. The firm was working again by the Thursday.

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

A Synology DS923+ with an encrypted volume, a crashed pool, and a recovery key in a password manager

Two drives had failed in SHR. The saved recovery key decided the job: all four drives imaged, the SHR arrays and LVM volume reassembled, the LUKS volume unlocked on the image with the key, and the Btrfs file system mounted from it.

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

A QNAP TVS-872XT serving a VMware host by iSCSI, with the thin pool full and every LUN offline

The pool had been over-committed and filled. All eight drives were imaged, the pool reassembled, the thin-pool metadata rebuilt from the images, and the three LUNs extracted and their VMFS volumes opened. Every virtual machine came back.

100% of the LUNs recovered9 days here, and back by post
Illustrative example — replace with a genuine case
UK · NDR-2026-0519JOB LOGGED ✓

A My Book Live 3TB reset in June 2021, unplugged that morning, and left in a drawer

Nothing had been written to it since. The drive was imaged, the old ext4 structures reconstructed from the backup superblock groups the reset had not reused, and the file tree rebuilt with names intact for all but a few hundred files, which were carved and sorted by type.

97% of files recovered, most with names4 days here, and back by post
Illustrative example — replace with a genuine case
UK · NDR-2026-0533JOB LOGGED ✓

A Synology DS220+ in SHR whose owner fitted a new drive and watched the repair stop at 41 per cent

The survivor had bad sectors DSM had worked around for a year. Both original drives were imaged, the survivor slowly with its weak areas last, the dropped drive read for the stripes the survivor could not give, and the Btrfs volume mounted from the merged image.

100% of it recovered6 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

Price my jobPacking and posting