SHR vs Traditional RAID

SHR, or Synology Hybrid RAID, is a vendor-managed RAID layout designed to use mixed-size drives more efficiently than many traditional RAID arrays. Its main advantages are easier expansion and less wasted capacity when drive sizes do not match.

Traditional RAID remains attractive when you want broad compatibility, predictable layouts, or a specific RAID level such as RAID 10, RAID 5, or RAID 6.

The short answer is:

• Choose SHR when you want flexible drive upgrades, may mix drive sizes, or prefer simpler capacity expansion within a compatible NAS platform.
• Choose traditional RAID when you want a standard layout that can be moved or managed across a wider range of systems and tools.
• Choose RAID 1, SHR, RAID 5, or RAID 6 according to your failure-tolerance needs—not as a substitute for backups.
• Confirm the NAS manufacturer’s drive, expansion, and migration rules before buying. SHR behavior is vendor-specific.

What SHR and traditional RAID do

RAID combines multiple drives into one storage pool or volume. Depending on the RAID level, it can provide:

• More usable capacity than a mirrored pair
• Protection against one or more drive failures
• Better sequential performance in some workloads
• A single logical volume instead of several independent disks

SHR is not a completely different form of redundancy. It is a vendor-managed system that can divide drives into groups of usable capacity and apply RAID underneath. This allows a NAS to use some portions of larger drives even when other drives are smaller.

Traditional RAID normally expects a more uniform drive layout. In a conventional array, usable capacity is often constrained by the smallest drive in the array.

SHR is most closely associated with Synology NAS systems. Other vendors may offer different flexible or hybrid RAID systems. Do not assume that an SHR array can be imported into a non-Synology NAS or recreated with identical behavior elsewhere.

Failure tolerance and usable capacity

SHR and SHR-2 failure tolerance

The common SHR choices are:

• SHR: usually tolerates the failure of one drive
• SHR-2: usually tolerates the failure of two drives

The exact implementation, supported drive counts, and expansion rules depend on the NAS platform.

SHR-1 is broadly comparable to single-parity RAID for failure tolerance. SHR-2 is broadly comparable to dual-parity RAID for failure tolerance. That does not mean their internal layouts or migration behavior are identical.

Traditional RAID failure tolerance

RAID level	Typical drive-failure tolerance	Usable-capacity concept	Practical notes
RAID 0	None	Sum of all drives	No redundancy; one failed drive can destroy the array
RAID 1	Usually one drive in a two-drive mirror	About the size of one drive	Simple and widely supported, but capacity-efficient only with small arrays
RAID 5	One drive	Roughly (number of drives - 1) × smallest drive	Single parity; rebuild risk and rebuild time increase with drive size and workload
RAID 6	Two drives	Roughly (number of drives - 2) × smallest drive	More failure tolerance than RAID 5, with additional parity overhead
RAID 10	Depends on which mirror members fail	Often about 50% of raw capacity	Good random-I/O behavior; can survive multiple failures if they are not in the same mirror

These formulas are planning estimates. Filesystem metadata, reserved space, parity layout, vendor overhead, and decimal-versus-binary capacity reporting reduce the space available for files.

Why mixed drive sizes matter

Traditional RAID usually bases each drive’s contribution on the smallest drive. For example, adding larger drives to a RAID 5 array may leave the extra space unused until every drive has been replaced or the array is expanded according to the controller’s rules.

SHR can divide drives into capacity sections. It may use:

1. A common-size section across all drives, with redundancy applied to that section.
2. Additional sections from larger drives, where enough matching capacity exists to create another redundant group.

This can reduce wasted capacity when drive sizes are mixed. However, the result is not unlimited free capacity. Larger drives must provide enough matching capacity for the SHR layout to use their additional space.

Worked example: four mixed-size drives

Consider a hypothetical NAS with:

• Two 4 TB drives
• Two 8 TB drives
• Four total drive bays
• A single-drive-failure protection requirement

The following figures are simplified raw-capacity estimates. They exclude filesystem overhead, reserved space, and vendor-specific implementation details.

Traditional RAID 5

A conventional RAID 5 array is generally limited by the 4 TB drives:

(4 drives - 1) × 4 TB = 12 TB

The two 8 TB drives contribute only 4 TB each to the common RAID 5 layout. Their remaining capacity is not automatically available to that array.

SHR-1

A simplified SHR-1 layout could use:

• Four 4 TB sections in a single-parity arrangement: approximately 12 TB
• The remaining 4 TB section on each 8 TB drive in a mirrored arrangement: approximately 4 TB

Estimated total:

12 TB + 4 TB = 16 TB

That is approximately 4 TB more than the simplified RAID 5 estimate.

This example demonstrates the capacity advantage of SHR with mixed-size drives. It is not a guarantee for every SHR configuration. The NAS model, number of drives, drive sizes, SHR version, filesystem, and expansion state can affect the result.

SHR-2 and the same drive set

With only four drives, SHR-2 applies two-drive redundancy. Its usable capacity would be lower than SHR-1, and the exact result depends on how the vendor lays out the capacity sections.

The important planning principle is:

• SHR-1 trades one drive’s worth of redundancy for more usable capacity.
• SHR-2 trades two drives’ worth of redundancy for greater failure tolerance.
• More redundancy does not create more storage capacity.

Use the NAS vendor’s storage calculator for a final estimate. Treat the result as a planning figure rather than the exact free space visible to applications.

Expansion flexibility

Adding larger drives to traditional RAID

Traditional RAID expansion varies by controller and software implementation. Common patterns include:

• Adding a drive to an array and expanding the RAID layout
• Replacing drives one at a time with larger models, then expanding after enough replacements
• Requiring all drives to reach a particular size before the extra capacity becomes usable
• Requiring an offline migration, backup-and-restore process, or a new array

The smallest-drive limitation remains important. Replacing only one 4 TB drive with an 8 TB drive normally does not provide the full benefit of the 8 TB capacity, because the other drives still constrain the array.

Adding larger drives to SHR

SHR is designed to make mixed-size expansion easier. A common upgrade pattern is:

1. Replace one existing drive with a larger drive.
2. Allow the array to rebuild or repair.
3. Repeat the process for the required number of drives.
4. Expand the storage pool or volume once enough additional capacity is available.

The extra space on one larger replacement drive may remain unused until another drive is also large enough to form a redundant capacity group. This is a key point: replacing one drive does not necessarily increase usable capacity immediately.

For example, if a pool contains several 4 TB drives and you replace one with a 12 TB drive, the array may still use only the equivalent of 4 TB from that replacement until other drives are upgraded. The precise threshold depends on the SHR implementation and drive layout.

SHR expansion advantages are strongest when:

• You expect to upgrade drives gradually
• You cannot buy a complete matched set at once
• Your drive sizes will change over time
• You want to avoid discarding usable capacity from larger drives

Traditional RAID may be preferable when:

• All drives will remain the same size
• You need a standard layout usable on multiple platforms
• You are building a fixed-capacity array and do not expect gradual expansion
• Your backup and migration tools are designed around a conventional RAID level

Rebuild behavior and risk

A rebuild restores redundancy after a failed drive is replaced. During a rebuild, the NAS reads data and parity or mirror information from the surviving drives and writes the reconstructed data to the replacement drive.

SHR rebuilds

An SHR pool may contain multiple underlying RAID sections. As a result, a rebuild can involve more than one layout or RAID group. The exact behavior depends on the vendor’s implementation and the affected sections.

SHR is not automatically faster or safer than traditional RAID. Rebuild duration depends on factors such as:

• Drive capacity
• Drive speed and sustained workload
• RAID level and parity calculations
• Amount of allocated data
• NAS processor and storage software
• Background services such as Plex scanning, file indexing, snapshots, and surveillance recording
• Whether another drive develops errors during the rebuild

Traditional RAID rebuilds

Traditional RAID rebuilds are often easier to reason about because the layout is more uniform. However, uniformity does not eliminate risk.

Large-capacity RAID 5 arrays can be exposed to a second failure or an unrecoverable read error while rebuilding. RAID 6 provides an additional drive of failure tolerance, but it still requires time and sustained drive activity to restore redundancy.

RAID 10 rebuilds generally reconstruct a failed mirror member from its surviving mirror partner rather than recalculating parity across the entire array. This can be advantageous for some workloads, but RAID 10 uses more raw capacity for redundancy.

Plan for degraded operation

During a degraded state:

• Protect the NAS from power loss with a suitable UPS where practical.
• Avoid unnecessary heavy workloads.
• Check drive health, logs, and alerts before starting a replacement.
• Confirm that the replacement drive is supported and at least large enough for the failed drive’s usable capacity.
• Keep an independent backup available in case the rebuild exposes another problem.
• Do not assume that a completed rebuild verifies every file or replaces a backup.

RAID is not backup

RAID protects availability against certain drive failures. It does not protect against:

• Accidental deletion
• Ransomware or malware
• File corruption synchronized across the array
• Theft or fire
• Water damage
• NAS failure
• User-account compromise
• Incorrect permissions or configuration
• A failed upgrade or administrator mistake

A mirrored or parity array can faithfully preserve a corrupted or deleted file across all members.

Use a separate backup system with version history where possible. A practical approach may include:

• A second NAS or external drive for local backup
• Cloud or off-site backup for important data
• Versioned backups to recover from accidental changes or ransomware
• Periodic restore tests
• A documented recovery process

RAID and backup solve different problems:

• RAID: keeps storage online or recoverable after some drive failures.
• Backup: provides an independent copy for recovery from data loss.

If a file exists only on the RAID array, it is not backed up.

Choosing drives for SHR or traditional RAID

Match drive capacity to the expansion plan

For SHR, mixed capacities can be useful, but the arrangement still determines how much space is usable. For traditional RAID, matching capacities are usually simpler and more predictable.

Before buying drives, list:

• Current usable capacity
• Expected data growth over three to five years
• Number of drive bays
• Drive replacement budget
• Desired failure tolerance
• Whether future upgrades will happen one drive at a time
• Whether the NAS supports the planned expansion path

Consider drive health and workload

Do not select drives only by capacity. Consider whether the NAS will handle:

• General file storage
• Large media libraries
• Multiple simultaneous users
• Virtual machines or containers
• Plex metadata and transcoding workloads
• Surveillance recording
• Frequent snapshots
• Database or application data

Surveillance and other write-heavy workloads may require different drive endurance and retention planning than a mostly archival media library. Check the NAS vendor’s compatibility guidance and the drive manufacturer’s intended workload category.

SSD cache is not a substitute for array capacity

An SSD cache may improve certain repeated or random-access workloads, but it does not change the fundamental failure tolerance of the storage pool. It also does not replace backups.

For a media server dominated by large sequential reads, adding capacity, network bandwidth, or correctly organizing the storage may be more useful than adding cache. Cache requirements are workload-specific, so do not assume an SSD cache will improve Plex streaming or every NAS application.

Migration and vendor lock-in

SHR can simplify expansion inside a supported Synology environment, but it can also tie your storage plan more closely to that platform.

Before committing to SHR, verify:

• Whether the pool can be moved to another compatible NAS
• Whether the destination model supports the same SHR version and filesystem
• Whether drives can be read by standard Linux or recovery tools
• Whether the vendor supports migration between product lines
• Whether replacing the NAS requires a same-platform migration or backup-and-restore process

Traditional RAID is not automatically portable either. Hardware RAID metadata, software RAID metadata, filesystem choices, encryption, and volume managers can all affect migration. Standard RAID levels generally offer a more familiar conceptual layout, but portability still requires planning.

If long-term platform independence is important, maintain a tested backup and document the array, filesystem, encryption, and recovery procedures.

RAID decision table

Your priority	Usually the better fit	Why	Main caution
Gradual upgrades with mixed-size drives	SHR	Can use larger drives more efficiently as the layout grows	Extra capacity may require upgrading more than one drive
Two-drive failure tolerance in a compatible NAS	SHR-2 or RAID 6	Provides dual-drive redundancy	Lower usable capacity and longer, heavier rebuilds
Standard, broadly understood layout	Traditional RAID	Easier to describe, document, and compare across tools	Expansion can be less flexible with mixed drive sizes
Simple two-drive protection	RAID 1 or SHR	Straightforward mirroring	About half of raw capacity is used for redundancy
High random-I/O performance and mirror-based redundancy	RAID 10	Avoids parity calculations and can provide strong I/O behavior	Usually about half of raw capacity is usable
Maximum capacity with no failure protection	RAID 0 or independent disks	Uses capacity efficiently	A drive failure can cause data loss; not suitable for the only copy
Large array with one-drive protection	SHR-1 or RAID 5	Better capacity efficiency than mirroring	A second failure during recovery can be serious
Important data requiring recoverability	Any suitable RAID plus independent backups	RAID handles some hardware failures while backups handle broader data-loss events	RAID alone is not backup

Bottom line

SHR is most compelling when you expect mixed-size drives, gradual upgrades, or a long-lived NAS that will grow over time. Its capacity advantage comes from using drive space in flexible sections rather than forcing every drive to contribute only the smallest common size.

Traditional RAID is often the better choice when you want a standard layout, predictable behavior, or easier comparison across platforms. It can also be the right answer when all drives will be matched and the array will not change frequently.

Choose the redundancy level first, then calculate usable capacity, rebuild exposure, expansion steps, and backup requirements. If you are ready to compare hardware that supports your storage plan, use Browse NAS or review NAS and storage servers.