Mixed-Capacity NAS Upgrade Risk Checklist

Eva Wong

IceWhale author

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Mixed-Capacity NAS Upgrade Risk Checklist - Zima Store Online

A larger disk does not automatically create more usable NAS capacity. Before buying or inserting mixed-capacity drives, confirm how the current RAID or pool allocates space, when expansion becomes visible, and what failure exposure each rebuild creates.

Identify the topology and the capacity rule

Record the operating system, pool type, RAID level, vdev or array layout, current drive sizes, sector format, encryption, and free space. Product names such as RAID, hybrid RAID, parity array, mirror, and ZFS do not imply the same expansion behavior.

Traditional RAID groups commonly allocate according to the smallest member. A two-disk mirror may remain at the old size until both members are replaced; a RAIDZ vdev may require every member to grow before the extra space appears.

Do not assume a spare bay can accept any old disk. Check whether the platform supports adding a drive to the existing group, adding a new group, replacing members sequentially, or only rebuilding into a new pool.

Check the drives as a matched operating set

Compare interface, capacity, CMR or SMR recording, rotational speed, error recovery behavior, workload rating, warranty, age, SMART history, and prior power-on hours. A nominally compatible disk can still become the slowest or least predictable member.

Burn in new drives outside the only good copy with a long SMART test and a full read or write verification appropriate to disposable media. Check cables, bays, power connectors, cooling, and controller visibility before beginning the upgrade.

Use the table to turn the proposed mix into an explicit stop-or-proceed decision.

Decision area	Assessment	Boundary
Capacity rule	Document final and per-step usable space	Stop if the platform cannot confirm it
Drive behavior	Prefer compatible CMR drives with known health	Do not mix unknown or failing media
Recovery	Verified copy outside the pool	One rebuild at a time

Model the rebuild and failure window

Estimate rebuild duration from used data and real array throughput, then schedule the work when the server can run continuously. Scrubs, downloads, media scans, databases, and backup jobs can extend the period of degraded protection.

Keep a verified independent backup before the first replacement. A parity or mirror rebuild is an availability operation, not a backup, and another unreadable sector or power interruption can defeat the plan.

A related ZimaSpace NAS drive selection article explains why matching capacity, recording type, and performance simplifies recovery.

An independent mixed-drive overview illustrates how usable capacity and expansion behavior depend on the storage layout.

-15% OFF

ZimaBoard 2 - Mini Home Server for Your Big Idea

Single board computer zimaboard2

Approve the upgrade only with rollback

Write the replacement order, expected degraded states, capacity after every step, commands or interface screens to monitor, and the condition that stops the procedure. Never replace a second member until the first rebuild has completed and health checks are clean.

Preserve the removed drive unchanged until the array has completed a scrub, backup, reboot, and ordinary workload. Label it with its slot and date so it is not accidentally reused or mistaken for the current member.

Proceed when the topology officially supports the sequence, the power and cooling path are stable, the backup restores, and the final usable capacity justifies the risk. Otherwise build a new matched pool and migrate data with both copies intact.