Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Configure NAS drives for RAID by first confirming your exact NAS model, firmware, supported RAID layouts, drive compatibility, and usable-capacity target. Then choose a layout that matches the number of disks and the failures you must survive, create the storage pool in the vendor’s management interface, and establish a separate backup before putting important data on it. TrueNAS/ZFS, Synology DSM, and QNAP QTS use different terminology and have different rules, so there is no single click path that applies to every NAS.
What RAID does in a NAS
RAID combines two or more physical disks into a logical storage arrangement. Depending on the layout, it can duplicate data, calculate parity information that allows recovery after a disk failure, or combine disks for capacity and speed without protection. RAID is a storage-availability feature, not a complete backup system: a separate, verified copy is still needed for accidental deletion, malware, theft, fire, filesystem corruption, and other failures that can affect every disk in the NAS.
The terms used by NAS products are not interchangeable. TrueNAS uses ZFS pools made from one or more virtual devices (VDEVs). Synology DSM creates storage pools and then volumes on those pools, and offers Synology Hybrid RAID (SHR) as well as conventional RAID types. QNAP presents RAID 1, 5, 6, 10, 50, 60 and other choices depending on the product and use case. A layout that is valid in one system may be unavailable or behave differently in another.
“A data VDEV with a stripe layout irretrievably loses all stored data if a single disk in the VDEV fails.” — TrueNAS SCALE documentation, “Setting Up Storage.”
#1 Best Overall
Seagate IronWolf 4TB NAS Internal Hard Drive CMR 3.5 Inch SATA 6Gb/s 5400 RPM 64MB Cache for RAID Network Attached Storage Rescue Services (ST4000VNZ06/006)
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance
- Store more and work faster with a NAS-optimized hard drive providing ultra-high capacity up to 16TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited warranty protection plan included and three year Rescue Data Recovery Services included
How do I configure NAS drives for RAID? Start with a compatibility check
Before assigning a disk to a pool, record the information below. A pool created with unsupported or mismatched hardware can be impossible to expand, may run at reduced capacity, or may not be accepted by the management software.
- Exact NAS model and bay count: The number of drive bays limits the layouts and future expansion options. External expansion shelves can have separate rules.
- Operating-system and firmware version: Storage wizards, supported RAID levels, and expansion operations can change between releases.
- Disk type: Confirm whether the model accepts SATA hard disks, SATA SSDs, NVMe devices, or a particular combination. Some systems require a pool to contain one drive type.
- Drive compatibility: Use the manufacturer’s current compatibility list and model specification. Synology explicitly directs users to its product compatibility list and states that drives in a pool must be the same drive type.
- Disk health and sector size: Do not add a disk reporting SMART errors, media errors, or an incompatible sector format. A marginal disk can fail during the initial build or resilver.
- Drive capacity: Mixed sizes may be supported, but the smallest disk or vendor-specific allocation rules can determine usable capacity.
Keep the model manual open while planning. Product families often expose different RAID types even when they run the same operating system, and a firmware update can rename a menu or add a restriction.
Which RAID should I use for my NAS?
Choose by balancing four things: the number of disk failures you need to tolerate, usable capacity, workload and performance requirements, and the number and size of disks you have. The table describes the general behavior; the NAS interface may use a different name or impose additional requirements.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Layout | Minimum disks | Failure tolerance | Usable-capacity idea | When it fits |
|---|---|---|---|---|
| Stripe / RAID 0 | 2 or more in many systems | None; one failed disk loses the data set | Approximately the sum of the disks, subject to implementation overhead | Temporary, reproducible data where loss is acceptable; never irreplaceable files |
| Mirror / RAID 1 | 2 | At least one disk, provided the surviving copy is healthy | Approximately the capacity of one disk in a two-disk mirror | Small pools that prioritize simple redundancy and fast recovery |
| RAIDZ1 | 3 in TrueNAS | One failed disk in the VDEV | Roughly one disk-equivalent is used for parity | TrueNAS pools where one-disk protection is an acceptable risk |
| RAIDZ2 | 4 in TrueNAS | Two failed disks in the VDEV | Roughly two disk-equivalents are used for parity | TrueNAS pools needing stronger protection than RAIDZ1 |
| RAIDZ3 | 5 in TrueNAS | Three failed disks in the VDEV | Roughly three disk-equivalents are used for parity | Large TrueNAS VDEVs where three-disk tolerance justifies the capacity cost |
| SHR | Depends on the Synology model and selected protection | Depends on the SHR variant | Synology automatically manages RAID and can optimize volume size when different-size drives are combined | Synology users who want guided mixed-size management, subject to model rules |
| RAID 5/6/10, 50 or 60 | Depends on the QNAP model and level | Depends on the selected level | Parity or mirroring consumes part of raw capacity | QNAP deployments whose hardware and workload support the selected level |
TrueNAS documentation defines RAIDZ1, RAIDZ2 and RAIDZ3 as tolerating one, two and three failed disks respectively in the relevant VDEV. Those counts are not universal labels for every NAS implementation. A two-disk mirror generally has one complete copy available if the other disk fails, but a mirror with more members follows the vendor’s own rules.
Stripe or RAID 0
Striping spreads blocks across disks without duplicate data or parity. It offers the most raw capacity from a set of disks, but a single disk failure destroys the data VDEV. Use it only for data that exists elsewhere and can be recreated. It is not a sensible choice for a family photo library, business documents, or the only copy of backups.
Mirror or RAID 1
A mirror writes identical data to multiple disks. TrueNAS requires at least two disks for a mirror and reports usable capacity equal to one disk in the VDEV. Mirroring is easy to understand and usually has straightforward replacement behavior, but it gives up roughly half of raw capacity in a two-disk arrangement. It does not protect against deletion, ransomware, or a damaged file being copied to every member.
RAIDZ parity in TrueNAS
RAIDZ reserves disk-equivalents for parity. RAIDZ1 uses one, RAIDZ2 two, and RAIDZ3 three. TrueNAS lists minimums of three, four and five disks for RAIDZ1, RAIDZ2 and RAIDZ3. The parity count is also the number of disk failures that the designed VDEV can withstand without data loss, assuming the VDEV remains healthy and the failed devices are replaced according to the documented procedure.
Rank #2
- Store more, compute faster, and do it confidently with the proven reliability of BarraCuda internal hard drives
- Build a power house gaming computer or desktop setup with a variety of capacities and form factors
- The go to SATA hard drive solution for nearly every PC application from music to video to photo editing to PC gaming. Ax. Sustained transfer rate OD: 190MB/s
- Confidently rely on internal hard drive technology backed by 20 years of innovation
- Frustration Free Packaging - This is just an anti-static bag. No cables, no box.
TrueNAS currently recommends RAIDZ generally, and specifically recommends it over dRAID when a dRAID VDEV would contain fewer than 10 data storage devices. Its documentation presents dRAID as a layout for specific very large arrays, not a default choice for a small home NAS. Do not select dRAID merely because it appears in a menu; verify that the array size and recovery goals justify it.
Synology SHR
Synology describes SHR as automated RAID management. It can optimize volume size when drives of different capacities are combined, but the exact benefit, allowable conversions, and expansion path depend on the model and DSM version. Check the model-specific documentation before assuming that a larger replacement disk will immediately add capacity.
QNAP RAID levels
QNAP documentation covers RAID 1, 5, 6, 10, 50 and 60, with additional types depending on product and use. RAID 5 and RAID 6 are parity arrangements; RAID 10 combines mirroring and striping. RAID 50 and RAID 60 combine groups of parity arrays. These choices belong to QNAP’s own storage workflow and should not be translated into a TrueNAS VDEV design.
How many drives do I need for RAID?
The answer depends on the layout and the NAS implementation. For the TrueNAS layouts covered here, RAIDZ1 needs at least three disks, RAIDZ2 at least four, and RAIDZ3 at least five. A TrueNAS mirror needs at least two. A stripe normally needs two or more, but the exact minimum is controlled by the interface.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Count both the disks required today and the disks you may need later. A four-bay NAS filled with four disks cannot add a disk internally without replacing hardware or attaching an expansion unit. If your capacity target will outgrow the initial pool, leave a bay available only if your chosen RAID type and vendor support adding a disk to that pool. Otherwise, plan for a documented expansion or migration procedure rather than assuming that an empty bay guarantees expansion.
Failure tolerance is a planning number, not a prediction. Selecting RAIDZ2 because you want to survive two simultaneous failures does not mean the pool is safe during a long rebuild if another disk develops errors. Consider disk age, replacement availability, rebuild exposure, and the value of the data when choosing between one-, two- and three-disk parity.
Estimate usable capacity before creating the pool
Start with the vendor’s calculator or the capacity estimate shown by the storage wizard. Raw disk labels use decimal units, while operating systems often display binary units, so the number shown in the NAS will not exactly match the sum printed on the disks.
Rank #3
- IronWolf internal hard drives are the ideal solution for up to 8-bay, multi-user NAS environments craving powerhouse performance.date transfer rate:6.0 gigabits_per_second
- Store more and work faster with a NAS-optimized hard drive providing 8TB and cache of up to 256MB
- Purpose built for NAS enclosures, IronWolf delivers less wear and tear, little to no noise/vibration, no lags or down time, increased file-sharing performance, and much more
- Easily monitor the health of drives using the integrated IronWolf Health Management system and enjoy long-term reliability with 1M hours MTBF
- Three-year limited product warranty protection plan and three year Rescue Data Recovery Services included
- Mirror: In a two-disk mirror, usable capacity is approximately the size of one member.
- RAIDZ1: Plan on approximately one disk-equivalent reserved for parity.
- RAIDZ2: Plan on approximately two disk-equivalents reserved for parity.
- RAIDZ3: Plan on approximately three disk-equivalents reserved for parity.
- Mixed sizes: The smallest disk or the vendor’s allocation algorithm can limit the capacity contributed by larger disks. QNAP’s RAID documentation also notes that mismatched capacities affect the resulting array.
Leave operational headroom instead of planning to fill the displayed maximum. Filesystem metadata, snapshots, checksums, reserved space and temporary rebuild requirements vary by platform. Use the NAS’s own estimate after selecting the exact disks, then compare it with your required working capacity and growth over the next few years.
Step-by-step: create a RAID pool on a NAS
The labels differ, but the sequence below maps the common workflow. Do not click through until the backup and compatibility checks are complete.
- Document the hardware. Write down the NAS model, bay numbers, firmware or DSM/QTS/TrueNAS version, disk models, capacities and serial numbers. Mark which disks contain data that must not be erased.
- Check compatibility. Open the manufacturer’s model-specific compatibility list and specification. Confirm drive type, maximum supported capacity, sector format, RAID levels, and whether mixing capacities is permitted. Replace any disk with health warnings before pool creation.
- Define protection and capacity targets. Decide whether the pool must withstand one, two or three disk failures, how much usable space is needed, and whether the workload is general files, virtual machines, media, databases or another demanding pattern. Select only a layout supported by the exact model.
- Create or verify a separate backup. Copy important files to another device or service and verify that representative files can be opened. A hot spare, mirror or parity disk is not an independent backup.
- Open storage management. In TrueNAS, use the pool or storage-management workflow to select eligible disks and create a pool containing one or more VDEVs. In Synology DSM, open Storage Manager, create a storage pool, select the drives and choose the available RAID or SHR type; a volume is created on the pool afterward. In QNAP QTS, open Storage & Snapshots or the equivalent storage utility, choose the available RAID type and select the disks. Menu names vary by release.
- Review the proposed layout. Check the selected bays, RAID level, estimated usable capacity, redundancy, filesystem or pool settings, and any warning that disks will be erased. Stop if a disk with required data appears in the selection.
- Confirm initialization. Accept the create or initialize action only after the selection is correct. Pool creation can erase the selected disks and may take hours or longer while parity is initialized.
- Create the data container. Create a dataset, filesystem or volume as required by the platform. Synology distinguishes the storage pool from the volume placed on it; TrueNAS commonly uses datasets inside a pool. Apply quotas, compression, encryption and snapshot settings only after checking their effects on your workload.
- Create shares and permissions. Add SMB, NFS or other shares, create users and groups, and apply least-privilege access. Test access from a client before copying the full data set.
- Configure protection and monitoring. Set scheduled backups, snapshots where appropriate, email or notification alerts, SMART tests, scrubs or data-integrity checks supported by the platform. Record the replacement procedure and the disk bay order.
- Perform a controlled test. Copy noncritical data, disconnect or simulate a documented failure only if the vendor supports that procedure, and confirm that alerts arrive. Never pull a live disk solely to experiment on an important pool.
What changes when a disk fails?
First confirm which physical disk is reported as failed. NAS indicators, serial numbers and the management interface should agree; removing the wrong disk can turn a degraded but recoverable pool into an unavailable one. Save the alert and pool status before acting.
- Check whether the pool is degraded, offline or already rebuilding.
- Confirm the replacement disk is compatible and at least as large as the disk being replaced under the vendor’s rules.
- Follow the model’s documented replace or rebuild command. Do not initialize the replacement in a separate pool if the system expects a direct replacement operation.
- Monitor the resilver, rebuild or reconstruction until the pool returns to a healthy state. Performance can be reduced during this process.
- Investigate why the disk failed and review remaining disks for health warnings before declaring the incident complete.
RAIDZ1, RAIDZ2 and RAIDZ3’s one-, two- and three-disk tolerance applies to the relevant TrueNAS VDEV, not to every possible pool failure scenario. A second failure during a RAIDZ1 rebuild, for example, can exceed the VDEV’s protection. A pool can also be unavailable because of controller, enclosure, power, firmware or filesystem problems even when no disk has failed.
Expansion and replacement limitations
Expansion is not a universal “add one disk” operation. It can be limited by the RAID type, current health, available bays, disk size, firmware, and whether the system expands an existing group or requires an additional group. Some platforms expand by replacing every member with a larger disk; others add a compatible disk to a supported array; some require creating a new pool and migrating data.
Recommended Free Tools
Before buying larger disks, read the exact expansion procedure for your model. Confirm whether the pool must be healthy, whether all members must be replaced before capacity increases, whether a new VDEV or RAID group is required, and whether the filesystem will automatically grow. Never assume that replacing one disk with a larger disk immediately increases usable space.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.RAID is not a backup
RAID keeps a pool available through certain disk failures. It does not provide a historical copy, undo an accidental overwrite, or protect against an administrator deleting a shared folder. A practical protection plan has at least one separate copy that is not continuously writable from the NAS, plus a way to restore and verify files.
Rank #4
- Available in capacities ranging from 2 to 22TB(1) | (1) 1GB = 1 billion bytes and 1TB = 1 trillion bytes. Actual user capacity may be less depending on operating environment.
- For RAID-optimized NAS systems with unlimited number of bays
- Rated for 550TB/yr workload rate(2) | (2) Annualized Workload Rate = TB transferred x (8760 / recorded power-on hours). The maximum rated workload is specified for operating at typical temperature of 40C. Workload Rate will vary depending on your hardware and software components and configurations.
- Designed to handle the demands of high-intensity 24x7 multi-user NAS environments
- Western Digital partners with a wide range of NAS system vendors for extensive testing to ensure compatibility with most NAS enclosures
- Keep a second copy on another storage system or removable media.
- Maintain versioned backups so corrupted or deleted files can be recovered from an earlier point.
- Use encryption and access controls appropriate to the data.
- Test restoration, not just backup completion messages.
- Document who can replace disks, restore shares and recover encryption keys.
Common configuration mistakes and fixes
Choosing RAID 0 for important files
Symptom: The wizard offers maximum capacity and no warning that a single failure destroys the set. Fix: Select a mirror or parity layout supported by the NAS, or use RAID 0 only for disposable data that has a verified separate copy.
Assuming every four-disk NAS supports the same RAID
Symptom: A planned RAIDZ2, SHR or RAID 6 option is missing. Fix: Check the exact model and firmware. Minimum disk counts and available levels are implementation-specific; TrueNAS RAIDZ2’s four-disk minimum is not a universal requirement for every vendor’s RAID 6, nor does it guarantee that a four-bay device supports it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Mixing incompatible drive types
Symptom: A disk is rejected, the pool cannot be created, or an expansion is blocked. Fix: Use the compatibility list, match the required drive type, and confirm capacity and sector-format rules before replacing or adding hardware.
Expecting larger disks to add capacity immediately
Symptom: A replacement disk is larger but the pool capacity is unchanged. Fix: Read the vendor’s expansion rules. The system may require every member to be replaced, a new RAID group, a pool expansion command, or a migration.
Creating a pool without a verified backup
Symptom: The only copy of files is on disks selected by the creation wizard. Fix: Stop, copy the files elsewhere, verify the copy, and only then initialize the pool. Existing-disk conversion is not universally lossless or supported in place.
Ignoring alerts during a rebuild
Symptom: A rebuild is running while another disk reports errors. Fix: Preserve the pool state, check the vendor’s recovery guidance, and avoid unnecessary reboots or disk removal. A second failure can exceed the chosen layout’s tolerance.
Pre-creation checklist
- Exact model, bay count and firmware version recorded.
- Supported RAID levels and expansion method confirmed in the model documentation.
- Every disk appears on the compatibility list or meets the vendor’s stated requirements.
- Disk health checked and serial numbers mapped to bay numbers.
- Usable-capacity estimate meets the current requirement and expected growth.
- Failure tolerance chosen deliberately rather than by the wizard’s default.
- Important data copied to a separate, verified backup.
- Pool, volume or dataset structure planned before shares are created.
- Monitoring, alerts, integrity checks and a restoration test scheduled.
Choosing among TrueNAS, Synology and QNAP workflows
Use TrueNAS terminology when you are designing ZFS VDEVs: decide the VDEV layout first, then assemble the pool from one or more VDEVs. Use Synology’s Storage Manager terminology when separating a storage pool from the volume that occupies it, and evaluate SHR according to the exact model’s rules for mixed drive sizes and expansion. Use QNAP’s Storage & Snapshots workflow and its published RAID options rather than mapping a QNAP RAID group directly to a TrueNAS VDEV.
Across all three platforms, the safe order is the same: verify compatibility, select a supported layout, confirm capacity and failure tolerance, create the pool only after a backup, then configure volumes or datasets, shares, monitoring and recovery procedures. The implementation details—and whether a pool can later be converted or expanded—remain vendor- and model-specific.
The Bottom Line
Build the pool around the disks your NAS officially supports, the number of failures you need to survive, and the capacity you can actually use. Confirm every destructive step, keep a separate backup, and follow the exact TrueNAS, Synology or QNAP expansion and replacement procedure instead of assuming RAID behaves the same everywhere.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
