The lab is taking new cases · 9am–5:30pm, Mon–Fri Urgent? Ring 0800 6890668
SDR Southampton Data Recovery 0800 6890668 Open a case
SDR / Harder cases / Synology data recovery

Specialist · Synology NAS work

Synology data recovery, Southampton. “Volume Crashed” means DSM has stopped trying. Your files have not moved.

That single frightening looking line shows three completely different faults: RAID members have fallen out; LVM has misplaced its layout (map); or the btrfs tree has gone wrong. They look like they are the same in terms of how it appears on the screen; however, each should receive a completely opposite response. Therefore, the correct action will always be the most mundane: shut down your DiskStation and stay away from Repair.

Only pay if we recover your data, on most jobs Free diagnosis & quote in writing Postal intake across all of Hampshire

Speak to an engineer about it
0800 6890668

What DSM is telling you, message by message.

Not listed? Try the fault finder →
The complaintWhat that tells youFirst step
DSM reports Volume CrashedThree ways one alert can be interpreted: RAID, LVM or btrfs.Switch off and leave Repair alone
DSM reports Storage Pool DegradedOne disk is missing; the pool still runs, but with no protection left.Each further hour adds risk
The DiskStation enclosure has diedYour data is on the disks, not in the chassisAmong the better outcomes
Rebuilding onto a new disk that replaced the failed one has stalled or "crashed".The long read of a rebuild exposed another weak diskStop now; clones will tell
Disks added to a computer that will ask you if you want to format themNormal: Windows does not understand how to access a Linux NAS layoutRefuse every prompt
A ransom demand sitting where your shares used to be.One of the NAS-targeting families got inTake a photo, shut it down, read our ransomware page.
Posting it: first, get a price quotation from us, by phone or with the form. Then send your item to us via tracked, fully insured post to our secure intake laboratory where it will be processed (we pay for return postage). Alternatively, you may also bring it to our Guildford intake laboratory Monday to Friday, 9am to 5:30pm, no appointment needed. Ring us and we would be happy to assist you with packaging, and there are postage details available on the postal details webpage.

SHR explained — and why one-size recovery tools find nothing.

Slices rather than whole disksEach disk is sliced to match up with the smallest member, which lets drives of different sizes all contribute: very neat provisioning that leaves one volume concealing several distinct arrays.
Standard components, odd arrangementThere's nothing proprietary involved. The RAID layer (mdadm) sits atop the slice groups, then those are combined using LVM, and finally ext4 or btrfs will sit at the end. There is no need for the original hardware used by Synology to restore the data because you can just take each layer apart in precisely the right order.
Why single-array tools find nothingFour mixed disks in SHR-1 can amount to three or four mdadm arrays, all beneath the same LVM volume. Aim a tool which expects only one RAID array at it, and there is no such layout to find.
Two repairs never to attemptThe "Repair" control in DSM, which mid-crisis can drop out a working member and overwrite metadata, and btrfs's own "repair" command, which its documentation warns may finish off a tree that is already damaged. Here, both give way to a read-only build from clones of each disk.

How the recovery runs, step by step.

01

Logged in, checked at no cost Free

Your item will have a unique case number assigned to it immediately after we receive it. An engineer will diagnose the issue, tell you what can genuinely be recovered and then provide you with one fixed price in writing. The diagnosis itself is completely at no cost to you. You are under no obligation to allow us to do any work that would incur a charge.

No-cost diagnosisQuote fixed in writingNothing to commit to
02

Clone each disk, nothing written

Each of the disks that were part of your array is cloned along with a map of where all of the bad sectors were located. The DiskStation does not have an opportunity to complete any resumption process. The btrfs root(s) from before the crash are still in the exact state they were when the crash occurred.

Every member imagedEarlier roots kept intact
03

Take the layers apart in sequence

When working on the clone of your data: we first map each piece (or "slice") as described above; after which we reassemble all mdadm arrays using these pieces. Then we read the LVM map. Finally, we mount the ext4 or btrfs file system read-only, one layer at a time, in the order that works.

mdadm → LVM → volumeRead-only assembly
04

Pin down the layer at fault

Each layer is worked through in the order it needs to be rebuilt. A crash at the btrfs, LVM or RAID layer receives its own repair, applied to the reconstruction. The btrfs tree is rolled back to an older working version if the newest one is broken. The shares are then verified before sign-off.

Repair aimed at the layerShares checked on return
05

Checked, returned, signed off

Once you have the complete listing of all the recoverable files back from us, you can "sign-off" and your recovery fee becomes due. Once you've signed-off, all the files will be posted out to you on new media (with postage included) and the case will remain open until you confirm that they can be opened properly at your location.

Sign-off on the file listNew media providedReturn postage on us

First checks on the bench

  • Three possible ailments, one symptom: a broken btrfs tree, missing LVM metadata and a dropped mdadm member all show up as Volume Crashed. Working out which you have means reading the layers, not the banner.
  • btrfs has its own "rewind": btrfs writes to disk in a copy-on-write fashion, so older tree roots are often still on the disk, and dropping back a single generation can restore volumes the current tree had written off.
  • Repairing may damage your system worse than it was originally damaged: when you are stressed in a crisis situation, you could end up throwing away a perfectly fine hard drive or writing on top of the exact same information that would be required to get your system back online. Repairing a disk set should be done for a disk set that is mostly functional rather than completely dead.
  • Ransomware is about exposure, not the brand. It's a consistent story when it comes to the NAS boxes on old firmware; they answer out there and are easily accessible via the Internet. Once you have ensured that your NAS can't be reached and it has been properly updated, you will have successfully defended yourself from the majority of ransomware threats.

The structural point that settles these jobs: an SHR volume made from unequal disks is not a single array; it's a stack of mdadm (RAID) arrays on per-disk slices, pooled by LVM under one filesystem. If you unwind the layers out of sequence, there is nothing to find. But if you unwind them properly, volumes the DiskStation called "crashed" come back routinely.

Out of the casebook.

EX · SDR-2026-0857SIGNED OFF ✓

A four-bay DS of mismatched disks, undone by its own helpfulness

A volume created using two 4TB disks and two 8TB disks had one dead member. An overnight rebuild process ran within DSM which finished in Volume Crashed. Underneath were two separate mdadm arrays. The first array used all four disks (it was still usable although degraded) and the second array used only the two 8TB disks. The arrays were reassembled sequentially outside of the device. After rolling the btrfs tree back one generation, every share came back.

All shares restored5 days on the bench

While it's still with you.

Do

  • Shut the box off as soon as you notice that it is "crashed" or "degraded"
  • Take note of which disk corresponds to which bay before removing it
  • Get a quote first, then post the disks or the whole box in their original state, or drop it off at the Guildford intake lab (no appointment needed)
  • Tell us whether it was on standard RAID or SHR, if you know

Avoid

  • Hit Repair on a degraded or crashed volume.
  • Use btrfs repair on the original drives, ever.
  • Let a PC initialise the disks
  • Shuffle disks between bays to work out which one failed

Bench questions, straight answers.

Volume Crashed in DSM — have I lost the data?

Very unlikely. "Crashed" only means DSM cannot put the stack back together: perhaps there was a loss of RAID members, perhaps corruption of the LVM metadata, perhaps corruption of the btrfs tree. Three separate faults, and mostly recoverable ones, but the message cannot say which. Leave the box powered off and all three stay open.

Is SHR a closed format? Must I have a second Synology?

No. Beneath the surface, SHR is simply basic Linux. The structure is based on mdadm for software RAID across slice partitions, then those partitions are grouped into one large pool (using LVM) and formatted either btrfs or ext4. Rebuilding from a set of drive image files on an average workstation does not pose much of an issue; the only time you'll experience issues is if you're using tools or people who expect a single flat block of data.

Is it safe to let DSM rebuild onto the new disk?

You cannot begin a rebuild until every single member disk has completely been imaged. A rebuild reads every single sector off the tired remaining disks, which is exactly the stress that causes a second failure, and it can write over your old file system roots that recovery relies on. If all member disks are completely imaged before attempting to do a rebuild, there is no risk in doing so.

The NAS was hit by ransomware — any way back?

Often in part, sometimes entirely, depending upon the strain involved. Campaigns targeting NAS devices connected to the Internet go back years; therefore we will review snapshots, replication targets, and what is left in free space. Take a picture of the note, shut down the device, then follow the routes shown on our ransomware page.

Whatever has gone wrong, keep it switched off.

Powering a damaged device up again costs you data. Start by opening a case instead; diagnosis is always free, regardless of your decision.

0800 6890668