Synology system partition recovery

A failed Synology system partition is not the same as an empty data volume—but unsafe reset steps can endanger both.

DSM places mirrored system partitions on member drives separately from storage pools and volumes. A degraded system partition means at least one copy remains; a crashed system partition means DSM cannot access the system copy across the drives.

Understand the symptom

DSM system recovery and data-volume recovery are separate but interdependent tasks.

WHY

What is happening

Synology documents repairing a degraded system partition and, for a crashed system partition, reinstalling DSM after backing up data. Those steps assume the storage pool and disks are sufficiently healthy. When multiple drives show errors, cloning and pool reconstruction should precede write-heavy repair or reinstall activity.

What you may see

Symptoms that change the recovery path.

01

System Partition Failed appears

DSM cannot access its system partition on one or more drives.

02

All drives show system failure

The mirrored system partition may be crashed across the set.

03

DSM will not boot normally

The operating system is unavailable even though pool data may remain.

04

Drive status is also Critical or Failed

The incident may extend beyond the DSM system partition.

Protect the source

Actions that can make the situation worse.

01

DSM reset writes to member disks

Reinstall activity changes system areas on the same physical media.

02

Multiple replacements stress the pool

Repair and rebuild reads can expose additional weak drives.

03

Reinitialization can erase data

QNAP- or Synology-style initialization prompts are not recovery actions.

Do this now

Safe steps before evaluation.

01

Record every bay

Photograph disk serials, order, LEDs and Storage Manager status.

02

Stop if multiple drives are unhealthy

Avoid repair or restart loops until member health is assessed.

03

Preserve configuration and keys

Keep DSM backups, encryption keys, package context and logs.

04

Clone unstable disks first

Protect weak members before system-partition repair or pool rebuild.

NEPFOSYS process

How a data-first evaluation proceeds.

01

System-and-pool assessment

NEPFOSYS separates DSM system damage from RAID, filesystem and drive faults.

02

Member preservation

Unstable disks are imaged and array metadata is reconstructed away from originals.

03

Controlled DSM recovery

System restore is attempted only after the data pool and required keys are protected.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Is my volume deleted when the system partition fails?

Not necessarily. DSM system partitions are separate from data volumes, but the underlying drive health must be evaluated.

Can DSM repair a degraded system partition?

Synology provides a repair workflow when at least one healthy system copy remains; protect data first when drive health is uncertain.

Should I use Mode 2 reset?

Only after preserving data and understanding storage-pool health. A reset writes to system partitions and is not a substitute for recovering failing disks.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case