
In short
- Degraded: back up now. Crashed: switch off and stop.
- Avoid Repair if another disk shows bad sectors or reconnection errors.
- SHR and Btrfs are rebuilt by hand, layer by layer, on copies of the disks.
What DSM is telling you
| Status | What it means | What to do |
|---|---|---|
| Healthy | Every disk and the volume are fine | Check your backup still runs |
| Degraded | One disk is missing or failed, the volume still works | Copy your important files first, then replace the disk |
| Crashed | The volume cannot be read: too many disks lost, or damaged metadata | Switch the NAS off, do not repair |
| Read-only | Btrfs or ext4 detected an error and protected itself | Copy what you can, do not force a repair |
How a Synology volume is built
Each disk is split into partitions: one small system partition (DSM itself), one for swap, and one or more data partitions. The system partitions of all disks form a RAID 1 called md0, swap is md1, and the data partitions form md2, md3 and so on.
With SHR, Synology creates several RAID sets to make use of disks of different sizes, then joins them with LVM into a single storage pool. With SHR-2, each set has two parity disks, like RAID 6. On top of the pool sits the volume, formatted with Btrfs or ext4.
A crash can come from any layer: two disks lost in one RAID set, an LVM metadata problem after an expansion, or Btrfs metadata damaged by a power cut or faulty memory.
When Repair makes things worse
The Repair button rebuilds the missing disk onto a new one. It reads every sector of the remaining disks. If one of them already has bad sectors, a reconnection count that keeps rising or a "warning" status, the rebuild can push it over the edge and turn a degraded pool into a crashed one.
Before clicking Repair:
- Open Storage Manager, then HDD/SSD, and check every disk: status, bad sector count, reconnection count.
- If anything other than "Healthy" appears on another disk, stop and copy your data first, or have the disks cloned.
Mistakes we see every week
- Reinstalling DSM after a failed update, choosing the option that erases the disks.
- Mode 2 reset done in a panic: it resets the configuration and can make DSM offer to recreate the volume.
- Moving the disks to another Synology to "test" them, which can trigger a migration that rewrites the system partitions.
- Removing a disk to see if the NAS works without it: in SHR with one parity, that is exactly how a degraded pool becomes a crashed one.
How the volume is recovered in the lab
- Each disk is cloned, after repair if needed. The original disks are no longer used.
- The md RAID sets are reassembled from the clones, read-only, using the superblocks to find the most recent members.
- For SHR, the LVM volume group is rebuilt so the RAID sets are joined in the right order.
- Btrfs is opened read-only. If the latest metadata tree is damaged, earlier trees (Btrfs keeps several generations) are used to reach a consistent state.
- Files are extracted, including encrypted shared folders if you have the key.
Older Synology models that will not start
Some Synology models built on Intel Atom C2000 processors are known for boards that suddenly stop booting, with a blinking blue light. In that case the disks are usually fine: the volume is rebuilt from them without the enclosure.
See also Synology NAS data recovery and The complete guide to NAS: how they fail and how to protect them.
Frequently asked questions
Is my data lost if the volume is crashed?
No. In the vast majority of cases the data is still on the disks; the problem is that DSM can no longer assemble them. The layers are rebuilt from copies of the disks.
Can I put the disks in a PC to read them?
Only with a Linux system able to assemble mdadm, LVM and Btrfs, and only read-only. A Windows PC will offer to initialise them: never accept.
Is your data important?
Do not try anything that could make the fault worse. The diagnosis is free and you get a fixed quote before any work starts.



