NAS Codex › Synology › Synology volume crashed: Synology's four scenarios and what you can still do

Synology volume crashed: Synology's four scenarios and what you can still do

Storage Manager says a volume or storage pool has Crashed. Synology is blunt about this one: "A volume crash caused by drive errors or file system errors cannot be repaired." What you can still do depends on whether the NAS boots and whether your files can still be read. Synology splits it into four scenarios, below, in the order you should check them.

Written against: Synology Knowledge Center articles tagged DSM 7 series, DSM legacy versions and DSM Enterprise (PAS); steps given for DSM 7 and DSM 6.2. Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

First, do not power the NAS off if your files can still be opened in File Station: Synology says to keep it on and copy the data to a computer on your local network straight away. If files cannot be read, Synology says to contact a data rescue company. If the crash came from a drive you pulled by accident, put it straight back; in DSM 7 you can use Online Assemble in Storage Manager > Storage.

What causes a crash, per Synology

Synology lists two groups of causes.

Synology's storage pool help says that once a pool's status is Crashed, "you can no longer repair it by yourself."

Scenario 1: the NAS cannot be powered on

If drive failures stop the system from powering on, Synology points to its article on fixing drive failure and retrieving data from the drives. That article's multi-bay route uses a spare drive in the Drive 1 slot with DSM installed on it (and no storage pool created on it), then puts the original drives back so DSM 7 can offer Online Assemble.

Scenario 2: you can sign in, but data cannot be read

You can power on and sign in, but File Station cannot read the data because of drive errors. Synology's advice for this case is to contact a local data rescue company.

Scenario 3: you can sign in and data can still be read

Synology says: do not power off the system, and follow these steps.

  1. Back up the data to a computer on your local network (map the shared folders from Windows or a Mac).
  2. Warning: the next step erases the crashed volume. Only after your backup is complete and checked: go to Storage Manager and remove the storage pool of the crashed volume.
  3. Run a memory test. If the result is not Normal or successful, replace the memory module; if it is a non-Synology module, Synology says to replace it with a Synology one.
  4. Create a new storage pool and volume.
  5. Restore the backed-up data.

Synology adds: if a file gives an error while you are copying it off a crashed volume, that file is corrupted. Skip it and carry on with the rest.

Scenario 4: a drive was removed by accident

  1. Insert the removed drive back into the NAS immediately.
  2. DSM 7: go to Storage Manager > Storage and use Online Assemble to bring the storage pool back without restarting. DSM 6.2: restart the system.
  3. If that solves it, run data scrubbing.
  4. Back up your data.

Synology's Online Assemble help says a pool shows Crashed when too few drives are installed to assemble it or a drive was removed while the system was on, and Missing when no drives can be detected. It can be assembled once enough drives are installed and their serial numbers match those in Required Drive Info; the status then changes to Can be assembled because drives are detected.

When to stop and get help

Stop and get help if File Station cannot read your data (Synology: contact a data rescue company), if the NAS will not power on and the data is not backed up, or if you are unsure whether a drive was pulled by accident. Never remove the crashed storage pool before your copy of the data is complete.

Questions

Can a crashed Synology volume be repaired?

Synology says a volume crash caused by drive errors or file system errors cannot be repaired. The exception it describes is a drive removed by accident, which can be reinserted and the pool brought back with Online Assemble (DSM 7) or a restart (DSM 6.2).

Should I turn the NAS off after a volume crash?

Not if the data can still be read. Synology says not to power off the system and to back the data up to a computer on the local network first.

What if some files will not copy off the crashed volume?

Synology says an error while copying a file from a crashed volume means that file has become corrupted. Skip it and continue copying the other files.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-14.