RAID decision
Synology SHR vs RAID 5: Capacity, Expansion and Recovery
SHR and RAID 5 can both provide one-drive fault tolerance on suitable multi-drive Synology systems, but they differ most when drive sizes change over time. RAID 5 is predictable and portable in concept: usable capacity is based on the smallest member drive. SHR uses Synology automation to combine equal-size regions and can recover capacity that classic RAID 5 would leave unused when drives are mixed.
Quick answer
Choose from your future upgrade path, not the label
For equal-size drives and a stable array, RAID 5 is simple and easy to reason about. If you expect to replace disks gradually with larger capacities, SHR is usually the more flexible Synology-native choice because it can make additional space usable as enough larger regions become redundant.
Live Amazon products
Hardware relevant to this technical workflow
This Sprint 9F catalogue is intentionally focused on current and previous Synology Plus systems. Storage-repair pages can also read compatible third-party NAS hard-drive data from Cloudzat Storage Price Intelligence in read-only mode. Product cards support the decision; they never override current Synology compatibility or model-specific repair rules.
Technical decision
One-drive redundancy is the shared baseline
Neither SHR-1 nor RAID 5 replaces backup. Pick between them according to expansion behavior, portability preferences, administrative simplicity and the exact RAID types supported by your DiskStation.
Interactive technical tool
SHR vs RAID 5 Capacity Planner
Use this as a planning aid. It identifies capacity, redundancy, deployment or repair constraints, but it does not replace the current Synology model manual, DSM documentation or upstream application release notes.
Technical safety checklist
Four checks before changing a production NAS
Protect data before maintenance
A healthy RAID state is not a backup. Confirm an independent restorable copy before repairs, DSM upgrades, RAID migration or major container changes.
Change one layer at a time
Storage, DSM, networking and application changes should be separated so an unexpected result can be traced to one action rather than several.
Record the exact state
Write down model, DSM build, pool type, drive serials, ports, mapped folders and current application versions before modifying a production NAS.
Verify the result
A repair or upgrade is complete only after storage health, services, backups and representative restores behave as expected.
Start with fault tolerance
Start with fault tolerance is central to SHR and RAID 5 on Synology: SHR-1 and RAID 5 normally tolerate one member-drive failure when the array has enough drives, so the meaningful comparison begins after establishing that shared redundancy level. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking start with fault tolerance, compare the one-parity storage path result with that earlier one-parity storage path baseline.
A tested backup protects the one-parity storage path workflow during start with fault tolerance. For SHR and RAID 5 on Synology, recovery of the one-parity storage path state matters more than speed.
Equal-size arrays are the least controversial case
For SHR and RAID 5 on Synology, equal-size arrays are the least controversial case matters because with identical drive capacities, both layouts can produce broadly similar usable capacity before filesystem overhead, so expansion policy and management preferences become more important. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking equal-size arrays are the least controversial case, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Document the one-parity storage path decision around equal-size arrays are the least controversial case. In SHR and RAID 5 on Synology, record why the one-parity storage path state changed and what outcome the one-parity storage path procedure expects.
Mixed drives expose the biggest difference
Inside SHR and RAID 5 on Synology, the practical constraint is this: classic RAID 5 sizes every member contribution around the smallest disk, whereas SHR can create additional redundant regions from larger drives when enough matching capacity exists. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking mixed drives expose the biggest difference, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Keep mixed drives expose the biggest difference separate from other one-parity storage path changes. On SHR and RAID 5 on Synology, isolating the one-parity storage path work makes a failure in the one-parity storage path path easier to identify.
Expansion favors staged upgrades under SHR
The SHR and RAID 5 on Synology reason to study expansion favors staged upgrades under shr is straightforward: Synology documents that SHR can expose additional capacity after enough larger drives form a redundant region rather than waiting for every disk to be replaced. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking expansion favors staged upgrades under shr, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Before buying hardware for expansion favors staged upgrades under shr, decide whether the one-parity storage path target is capacity, redundancy or availability; verify the resulting one-parity storage path outcome directly.
RAID 5 remains easy to model
SHR and RAID 5 on Synology planning can fail here because the planning formula is based on drive count minus one multiplied by the smallest drive, which makes forecasts straightforward even if the capacity efficiency is lower with mismatched disks. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking raid 5 remains easy to model, compare the one-parity storage path result with that earlier one-parity storage path baseline.
In SHR and RAID 5 on Synology, make the one-parity storage path step reversible. Back up the one-parity storage path state; change one variable for raid 5 remains easy to model; verify the one-parity storage path result before continuing.
SHR is Synology-specific automation
A safer SHR and RAID 5 on Synology interpretation starts with one fact: the flexibility comes from Synology management of Linux RAID components, so administrators who value conventional RAID semantics may still choose RAID 5 intentionally. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking shr is synology-specific automation, compare the one-parity storage path result with that earlier one-parity storage path baseline.
If a tutorial conflicts with the one-parity storage path behavior on SHR and RAID 5 on Synology, stop at shr is synology-specific automation; follow the model-specific Synology instructions for the one-parity storage path condition.
Rebuild risk exists in either layout
Rebuild risk exists in either layout is central to SHR and RAID 5 on Synology: a degraded one-drive-protected array has no remaining tolerance for another failure in that redundancy layer while a repair is underway, making backups and drive health especially important. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking rebuild risk exists in either layout, compare the one-parity storage path result with that earlier one-parity storage path baseline.
A tested backup protects the one-parity storage path workflow during rebuild risk exists in either layout. For SHR and RAID 5 on Synology, recovery of the one-parity storage path state matters more than speed.
Replacement drive rules still matter
For SHR and RAID 5 on Synology, replacement drive rules still matter matters because a larger drive is not automatically useful if it cannot satisfy the repair or expansion rules for the existing storage pool. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking replacement drive rules still matter, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Document the one-parity storage path decision around replacement drive rules still matter. In SHR and RAID 5 on Synology, record why the one-parity storage path state changed and what outcome the one-parity storage path procedure expects.
Data scrubbing and health checks are separate
Inside SHR and RAID 5 on Synology, the practical constraint is this: scrubbing, SMART information and storage-pool status each answer different questions and should not be collapsed into a single health indicator. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking data scrubbing and health checks are separate, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Keep data scrubbing and health checks are separate separate from other one-parity storage path changes. On SHR and RAID 5 on Synology, isolating the one-parity storage path work makes a failure in the one-parity storage path path easier to identify.
Application uptime does not prove redundancy
The SHR and RAID 5 on Synology reason to study application uptime does not prove redundancy is straightforward: Plex, Photos or file shares may continue working while the pool is degraded, so service availability should not be mistaken for a healthy protection state. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking application uptime does not prove redundancy, compare the one-parity storage path result with that earlier one-parity storage path baseline.
Before buying hardware for application uptime does not prove redundancy, decide whether the one-parity storage path target is capacity, redundancy or availability; verify the resulting one-parity storage path outcome directly.
Migration cost should include future disks
SHR and RAID 5 on Synology planning can fail here because a layout that looks efficient today can become expensive if every member must be upgraded together before additional capacity appears. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking migration cost should include future disks, compare the one-parity storage path result with that earlier one-parity storage path baseline.
In SHR and RAID 5 on Synology, make the one-parity storage path step reversible. Back up the one-parity storage path state; change one variable for migration cost should include future disks; verify the one-parity storage path result before continuing.
Use backup to make the RAID choice less dangerous
A safer SHR and RAID 5 on Synology interpretation starts with one fact: when a restorable copy exists outside the array, the choice between SHR and RAID 5 can focus on operations instead of pretending RAID is disaster recovery. For SHR and RAID 5 on Synology, record the one-parity storage path baseline before action. When checking use backup to make the raid choice less dangerous, compare the one-parity storage path result with that earlier one-parity storage path baseline.
If a tutorial conflicts with the one-parity storage path behavior on SHR and RAID 5 on Synology, stop at use backup to make the raid choice less dangerous; follow the model-specific Synology instructions for the one-parity storage path condition.
Questions people ask
SHR and RAID 5 on Synology: common questions
Is SHR faster than RAID 5?
Performance depends on workload, drive count, NAS hardware and layout. The primary SHR advantage discussed here is flexible capacity management, not a blanket speed claim.
For SHR and RAID 5 on Synology, "Is SHR faster than RAID 5?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Does SHR protect against one failed drive?
SHR-1 can provide one-drive fault tolerance when configured with enough drives. Confirm the actual storage-pool protection state in Storage Manager.
For SHR and RAID 5 on Synology, "Does SHR protect against one failed drive?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Can RAID 5 use mixed-size drives?
Yes, but classic RAID 5 capacity is constrained by the smallest member drive, so larger portions may be unused.
For SHR and RAID 5 on Synology, "Can RAID 5 use mixed-size drives?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Can I convert RAID 5 to SHR?
Do not assume an in-place conversion exists. Synology supports only specific RAID-type changes; check the current Change RAID Type options for your pool.
For SHR and RAID 5 on Synology, "Can I convert RAID 5 to SHR?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Is SHR proprietary?
SHR is Synology automated RAID management built on Linux RAID technologies, but its management behavior is Synology-specific.
For SHR and RAID 5 on Synology, "Is SHR proprietary?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Which is better for a first NAS?
SHR is often easier for owners who want flexible future upgrades, while RAID 5 suits administrators who deliberately want a classic RAID layout.
For SHR and RAID 5 on Synology, "Which is better for a first NAS?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Does either option replace backup?
No. One-drive fault tolerance keeps a pool available after a member failure; it does not protect against deletion, ransomware, theft or catastrophic device loss.
For SHR and RAID 5 on Synology, "Does either option replace backup?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Do I need equal-size drives for SHR?
No, mixed sizes are one of SHR’s main use cases, although usable capacity depends on the combination of installed drive sizes.
For SHR and RAID 5 on Synology, "Do I need equal-size drives for SHR?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
How many drives does RAID 5 need?
RAID 5 requires at least three drives.
For SHR and RAID 5 on Synology, "How many drives does RAID 5 need?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Should I change a healthy pool just to use SHR?
Usually not without a clear benefit and a tested migration plan. The risk and downtime of changing storage architecture can exceed the theoretical gain.
For SHR and RAID 5 on Synology, "Should I change a healthy pool just to use SHR?" depends on the one-parity storage path: check the exact DSM build for the one-parity storage path, the NAS model, and the current one-parity storage path state.
Official references and methodology
Verify the exact model, DSM build and application state
This SHR and RAID 5 on Synology guide uses primary documentation for the one-parity storage path. Cloudzat evaluates the one-parity storage path capacity, redundancy, deployment and recovery layers separately. Interactive one-parity storage path results support planning; final one-parity storage path changes need exact model guidance and current upstream documentation.
- Synology: What is Synology Hybrid RAID (SHR)?
- Synology: What RAID type is best for my storage?
- Synology: Change the RAID type of a storage pool
- Synology: Repair a storage pool
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, NAS models, drive compatibility, DSM behavior and upstream application requirements can change. Verify the exact DiskStation model, current DSM documentation and application release notes before changing storage pools, replacing drives, exposing network services or upgrading production containers.