Synology System Partition Failed: Fix Guide

DSM system-partition recovery

Synology stores its system partition redundantly across drives, so a System Partition Failed message on one disk does not automatically mean your user-data volume has failed. Current Synology guidance separates a degraded system partition, where at least one copy remains accessible and a Repair action can be available, from a crashed system partition where all copies are inaccessible and DSM may need to be reinstalled.

See current NAS options Use the diagnostic tool

Quick answer

Read the Overview status before replacing drives

When only part of the mirrored system partition is inaccessible, DSM can often repair it. When the system partition is crashed, Synology instructs users to back up data and use Mode 2 to reinstall DSM.

Current Amazon listings

Replacement and migration DiskStation options

Product cards are supporting purchase references only; they do not determine whether your failed drives are recoverable or whether a specific migration pairing is supported.

Checking the dedicated recovery and migration catalogue…

Technical decision

System Partition Failed is a platform warning with its own repair logic

Do not treat it as identical to storage-pool degradation or volume crash. The system partition is mirrored separately, and DSM may remain usable even while one disk reports a failed system partition.

Interactive recovery tool

Synology Failure Triage Tool

This tool routes the symptoms you select to a safer next step. It does not issue destructive commands. Before initializing a disk, deleting a pool, reinstalling DSM or moving the only copy of important data, verify the exact live Synology procedure for your model and DSM build.

Recovery safety checklist

Four rules before you change a failing Synology system

Preserve readable data first

If unique files can still be opened, copy or back them up before changing storage metadata, reinstalling DSM or running stressful diagnostics.

Record drives and bays

Capture drive serial numbers, bay positions, health states and DSM messages before swapping disks or moving them to another chassis.

Match the action to the failure layer

A degraded pool, crashed volume, failed system partition, bad drive and failed bay have different supported recovery paths.

Keep a rollback path

During migration or recovery, do not erase the source system until the destination data, permissions, applications and backups have been verified.

The DSM system partition is mirrored

Synology protects the system partition across drives with RAID 1-style mirroring. That architecture explains why one inaccessible copy can produce a degraded state while the NAS continues operating from another healthy copy.

For a system-partition incident, the dsm system partition is mirrored must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Degraded and crashed require different responses

A degraded system partition means at least one copy is still accessible and DSM can offer repair. A crashed system partition means all copies are inaccessible, the system cannot repair it in place and reinstalling DSM becomes part of the documented recovery path.

For a system-partition incident, degraded and crashed require different responses must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Use Storage Manager Overview as the primary status

The Overview page tells you whether the system partition is degraded or crashed and whether another higher-priority problem must be solved first. Do not infer the whole system state from one drive-row label alone.

For a system-partition incident, use storage manager overview as the primary status must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Repair degraded system partitions promptly

When the Repair link is available, follow the Synology workflow and then revisit HDD/SSD status. Drives that continue to show System Partition Failed may be defective and should be evaluated for replacement.

For a system-partition incident, repair degraded system partitions promptly must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Replace defective disks one at a time

If several drives need attention, changing them simultaneously can remove remaining healthy system-partition copies and storage redundancy. Synology’s procedure emphasizes sequential replacement and repair.

For a system-partition incident, replace defective disks one at a time must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

A crashed system partition calls for backup first

If DSM is still accessible enough to copy data or use existing backups, secure the dataset before the Mode 2 reinstall path. Reinstalling DSM clears system configuration even though the normal reset is designed to preserve stored user data.

For a system-partition incident, a crashed system partition calls for backup first must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Mode 2 is not the same as erasing the whole NAS

Synology describes Mode 2 as clearing system configurations and reinstalling DSM. It is different from a full secure erase, but configuration loss and package effects are significant enough that backups and keys should be prepared in advance.

For a system-partition incident, mode 2 is not the same as erasing the whole nas must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Drive health still matters after DSM returns

After reinstalling DSM following a crashed system partition, inspect every disk. A drive that remains Failed, Critical or System Partition Failed should not be trusted simply because DSM booted again.

For a system-partition incident, drive health still matters after dsm returns must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Encryption requires preparation before reset

Encrypted storage can depend on keys and key-vault behavior. Confirm recovery keys and understand the DSM 7.3+ option to lock encrypted storage entities during reset before starting a recovery that changes system configuration.

For a system-partition incident, encryption requires preparation before reset must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

System partition errors can be symptoms of broader faults

Drive failures are a common trigger, but repeated errors across disks can also justify checking bays, backplane behavior, memory and chassis stability. The same system should not be rebuilt repeatedly without asking why the partition failed.

For a system-partition incident, system partition errors can be symptoms of broader faults must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Do not format healthy data volumes unnecessarily

A system-partition problem and a data-volume problem are separate layers. Follow the exact Synology procedure so a recoverable user-data volume is not destroyed merely because the DSM system area needs repair or reinstall.

For a system-partition incident, do not format healthy data volumes unnecessarily must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Escalate when all drives show critical system status

When every disk reports system-partition failure and DSM is unstable, the risk of configuration and access loss is high. Preserve available data, record the current drive order and involve Synology support if the documented Mode 2 path does not restore normal operation.

For a system-partition incident, escalate when all drives show critical system status must be read against DSM's separate status for the mirrored system area rather than the user-data volume. Determine whether at least one system-partition copy remains accessible and whether Overview offers Repair. If the state is crashed instead of degraded, preserve data and configuration material before following the documented DSM reinstall route. This checkpoint is designed to prevent a platform-level warning from triggering unnecessary formatting of otherwise recoverable user storage.

Questions people ask

Synology System Partition Failed questions

What does System Partition Failed mean on Synology?

DSM cannot access the system-partition copy on that drive. If other mirrored copies remain healthy, the system partition can be degraded rather than completely crashed.

System Partition Failed should be interpreted as degraded or crashed at the DSM system layer. Do not assume the user-data volume has the same status.

Can I keep using the NAS when the system partition is degraded?

Synology says normal use can continue, but recommends repairing the partition as soon as possible.

What if the system partition is crashed?

Back up data and follow Synology's Mode 2 DSM reinstall procedure. A crashed system partition cannot be repaired in place.

Will Mode 2 delete my files?

The documented reset clears system configurations and reinstalls DSM without intentionally erasing stored user data, but backups are strongly recommended before proceeding.

Why do all drives show System Failed?

When all mirrored system-partition copies are inaccessible, multiple drives can show failed or critical system status. Check the Overview page for the crashed classification.

Should I replace every drive showing System Partition Failed?

Not automatically. Repair the system partition first when possible, then replace drives that remain unhealthy, one at a time.

Is this the same as a crashed storage volume?

No. The DSM system partition and user-data volumes are separate storage structures and have different repair procedures.

Do I need my encryption keys before Mode 2?

Yes. Preserve recovery keys and understand the key-vault behavior for encrypted volumes or folders before resetting DSM.

Can a bad bay cause system partition errors?

Connection or hardware faults can contribute to drive access problems. Persistent slot-specific errors justify drive-versus-bay diagnosis.

When should I contact Synology support?

When repair or Mode 2 does not restore normal status, multiple drives show unexplained errors, or the system is unstable enough that further changes risk data access.

Official references and methodology

Verify the live DSM state before any destructive recovery step

This system-partition guide is limited to DSM's mirrored system area and does not equate that warning with a user-data volume failure. It distinguishes degraded system-partition copies from a fully crashed system partition, explains why defective drives should be replaced one at a time, and reserves DSM reinstall/reset steps for the conditions Synology documents. Backups should be current before repairing system metadata or reinstalling DSM.

As an Amazon Associate, Cloudzat may earn from qualifying purchases. Failure states, DSM behavior, migration compatibility and recovery options can change by model and DSM build. Preserve readable data and verify Synology's current Knowledge Center instructions before initializing drives, deleting pools, reinstalling DSM or changing the only copy of important data.