Synology SHR recovery

A crashed SHR pool requires member and RAID-layout preservation before DSM repair actions.

Synology Hybrid RAID can combine Linux md RAID layers, LVM, filesystems, SSD cache, and encryption. A Crashed state may follow excessive drive failures, unreadable sectors, enclosure problems, interrupted repair, or incorrect migration.

Understand the symptom

SHR data protection depends on its actual RAID groups and the history of each member.

WHY

What is happening

Synology distinguishes Degraded pools that may be repairable from Crashed pools requiring troubleshooting. SHR layouts can include different-size disks and multiple RAID components. Replacing, assembling, or repairing the wrong disk can change md metadata and LVM state before the strongest source set is known.

What you may see

Symptoms that change the recovery path.

01

Storage pool status is Crashed

DSM cannot provide the volume through the current member set.

02

Pool appears Missing or Available for Assembly

The NAS sees metadata but has not mounted the previous pool normally.

03

Repair stopped or failed

Another disk, bad sector, connection, or replacement problem interrupted reconstruction.

04

Shares disappeared after migration

Bay order, model compatibility, encryption, or incomplete members may affect assembly.

Protect the source

Actions that can make the situation worse.

01

New pool creation overwrites metadata

DSM writes fresh RAID, LVM, and filesystem structures.

02

Repair generates broad writes

A rebuild can stress weak disks and propagate an incorrect source.

03

SSD cache changes the state

Dirty or missing cache devices may contain data not committed to the array.

Do this now

Safe steps before evaluation.

01

Export DSM evidence

Save Storage Manager screens, logs, md state, SMART details, alerts, and repair history.

02

Label all devices

Record bay, serial, size, role, failure date, replacements, and SSD cache members.

03

Preserve the NAS enclosure

Keep power supply, backplane, cables, model, DSM version, and encryption keys.

04

Stop pool operations

Do not create, remove, repair, scrub, expand, or assemble the source set casually.

NEPFOSYS process

How a data-first evaluation proceeds.

01

SHR topology review

NEPFOSYS maps md components, LVM, filesystems, member history, and cache state.

02

Independent disk acquisition

Readable members are imaged before virtual assembly.

03

Volume reconstruction

Candidate layers are assembled from images and priority shares are extracted.

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 SHR the same as RAID 5?

Not always. SHR can build one or more RAID components based on drive count and sizes, so the exact layout must be read from metadata.

Should I click Repair?

Only after expected members and their health are known. Repair writes across the pool and is unsafe with multiple uncertain disks.

Why preserve SSD cache devices?

A write-back cache can contain recent data not yet committed to the main pool.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case