ZimaOS RAID 5 can grow by adding another drive without recreating the entire array. In the source case, a three-disk 20 TB RAID 5 exposed an Add Drive control once the required conditions were met, and the original poster confirmed the expansion path worked.
Current IceWhale RAID documentation still describes RAID 5 as a layout that can grow by adding drives over time. Expansion is not a substitute for backup: parity protects against a drive failure, while a rebuild/reshape still stresses every participating disk.
The Source Listed Three Conditions for Add Drive
The community reply said the button appears when:
- an empty bay contains an unused disk;
- the new disk capacity is at least as large as a single existing RAID5 member;
- the RAID5 parity check has completed.
The original poster replied that this solved the problem.
Current ZimaOS Still Describes RAID 5 as Expandable
IceWhale's current RAID reference says RAID 5 requires at least three disks and can grow by adding drives over time.
Use the current ZimaOS RAID 5 reference before expanding an older array.
The New Disk Should Not Be Smaller Than Existing Members
If the new disk is smaller than the array member size, ZimaOS cannot use it as a full member of the same RAID geometry. Equal or larger capacity is the safe expectation.
A larger disk does not automatically give extra space beyond the geometry used by the array until the layout/filesystem supports and completes expansion.
Expand Only a Healthy Array
Do not add capacity while the array is degraded, rebuilding, reporting read-only mode, or showing failed members. First restore the array to a healthy state and complete parity/recovery work.
Back Up Important Data Before a RAID Reshape
Adding a drive changes RAID geometry and can require extensive parity work across every member. A second drive failure, cabling problem, power loss, or latent media error during the reshape can turn capacity expansion into recovery.
RAID is not an independent backup.
Expect Large Arrays to Take a Long Time
With 20 TB disks, parity checking and reshape can take many hours or longer depending on disk speed, system load, and the amount of data. Avoid unnecessary shutdowns during the operation and monitor drive health/temperature.
Do Not Reformat Existing RAID Members to Add Capacity
The point of Add Drive is to grow the existing array. Formatting current members would destroy data. Only the unused incoming disk should be prepared/consumed by the managed expansion workflow.
Verify Capacity and RAID Health After Expansion
After ZimaOS finishes, confirm:
- all expected members are active;
- the array reports Healthy;
- usable capacity increased as expected;
- critical shares and apps still read/write correctly;
- the independent backup remains valid.
RAID 5 Expansion FAQ
Can ZimaOS RAID 5 add another drive without reformatting the whole array?
Yes. The source user confirmed the Add Drive workflow, and current IceWhale documentation still describes RAID 5 as expandable.
Why might Add Drive not appear?
The source says the array needs an eligible unused disk and a completed parity check.
Does RAID 5 expansion replace the need for backup?
No. Capacity expansion and parity do not protect against every failure or accidental deletion.
