How to Expand a RAID or ZFS Array: Adding Drives Without Data Loss

If you’re running out of space on your NAS and wondering whether you can simply add a new drive to your existing RAID array without wiping everything and starting over, the short answer is: yes, but only if your RAID controller or NAS operating system explicitly supports Online Capacity Expansion (OCE). This guide walks you through the exact process for expanding a traditional RAID array (RAID 5, RAID 6) and explains why ZFS pools work differently. We’ll cover the critical backup step you must take first, realistic time expectations, and the vulnerable window during a rebuild when your data is at its most exposed.

Does Your RAID Controller or NAS OS Support Online Capacity Expansion?

Before you insert a single drive, confirm that your hardware or software supports expanding an existing array without data loss. This feature is often called Online Capacity Expansion (OCE) or RAID Level Migration.

Full Backup and Integrity Check: A Non-Negotiable First Step

RAID expansion is a high-risk operation. A power failure, drive failure, or firmware glitch during the reshape can destroy your entire array. RAID is not backup — it protects against a single drive failure, not against accidental deletion, ransomware, or a botched expansion.

• Create a full backup of all data on the array to an external drive or another NAS.
• Perform a file system integrity check (e.g., fsck on ext4, scrub on ZFS).
• Verify the backup is restorable — do not skip this step.
• Document your current RAID configuration (drive order, stripe size, filesystem type).

General Expansion Process: Install Drive, Trigger Rebuild, Extend Filesystem

Assuming your system supports OCE, the basic workflow is the same across most platforms.

Why ZFS Pools Work Differently: Adding vdevs vs. Expanding RAIDZ

ZFS is the most common filesystem in homelab NAS builds, especially with TrueNAS. It handles expansion differently than traditional RAID. You cannot add a single drive to an existing RAIDZ vdev to increase its capacity. Instead, you must add an entire new vdev (a group of drives) to the pool.

For example, if you have a 3-drive RAIDZ1 vdev (3x 4TB drives = ~8TB usable) and want more space, you cannot add a single 4TB drive to that vdev. Instead, you add a second 3-drive RAIDZ1 vdev, giving you ~16TB total. The pool stripes data across both vdevs. This means you lose the capacity of one drive per vdev to parity — so adding a second 3-drive vdev costs you 4TB of parity space.

For a deeper comparison of RAID levels, see our guide on RAID 1 vs RAID 5: Which Gives You More Usable Storage?.

Realistic Time Expectations and the Vulnerable Window During Reshape

RAID expansion is not fast. The reshape process reads and rewrites every byte on every drive in the array, which can take hours or days depending on drive size and interface speed.

To minimize risk, follow these guidelines:

• Run a full S.M.A.R.T. long test on all existing drives before starting.
• Ensure your UPS has enough runtime to cover the entire reshape (at least 30 minutes for small arrays, 2+ hours for large ones).
• Do not run any other disk-intensive tasks during the reshape.
• Monitor the reshape progress regularly (e.g., cat /proc/mdstat on Linux).

Power consumption during a reshape is also higher than idle. Expect each HDD to draw 6-10W under continuous load, plus the CPU/controller overhead. For a 4-drive array running for 48 hours, that’s roughly 1.5-2 kWh of extra electricity — about $0.20-$0.40 depending on your rates. For more on managing power, see How to Reduce Your NAS’s Power Consumption (Without Losing Performance).

Which Expansion Method Should You Choose?

Your choice depends on your current setup and future growth plans.

• If you run mdadm or a hardware RAID controller and have RAID 5 or RAID 6, you can add single drives to expand capacity. This is the most cost-effective method for small expansions (1-2 drives).
• If you run TrueNAS or any ZFS-based system, plan your vdev layout from the start. Adding a new vdev of the same type (mirror or RAIDZ) is the only supported expansion path. Consider starting with mirrors if you expect to grow incrementally.
• If you run Unraid, expansion is trivial — just add a new drive to the array and it becomes part of the storage pool immediately, with no reshape required.
• If you run Synology or QNAP, use their native expansion tools. Both support adding drives to existing SHR or RAID groups.

Bottom Line: Plan Ahead or Risk a Long Reshape

Expanding a RAID array is possible without data loss, but it is a slow, high-risk operation that requires careful preparation. The safest path is to always back up before starting, confirm your controller or OS supports OCE, and understand that ZFS does not allow single-drive expansion of RAIDZ vdevs. If you are building a new NAS today, consider whether you will need to expand in the future — starting with mirrors in ZFS or using Unraid can save you days of reshape time later. For CPU recommendations that handle ZFS expansion well, check our guide on the Best CPU for TrueNAS in 2026.