Replace drives when bay count is scarce and existing disks are due for retirement; add an enclosure when the current set still has useful life and the host supports clean expansion.
The next 20TB is a usable-capacity target, not a shopping quantity. Parity layout, filesystem expansion rules, current disk sizes, replacement order, backup space, controller ports, and power all determine how much new storage either route actually delivers.
Calculate the Usable Gain for Your Existing Layout
Write down the current vdev, RAID group, or mirror geometry and calculate the smallest replacement sequence that can expose 20TB of additional usable space. Some layouts expand only after every member of a group has been replaced; others let you add a complete new group.
Replacing four small drives with denser models may create little visible capacity until the final replacement finishes. Adding a new enclosure may expose capacity sooner, but only after buying enough disks for a valid redundancy group.
Reject any plan that quotes raw disk labels without parity, filesystem overhead, spare policy, and the required free-space margin. The winning route is the one that reaches the usable target with a valid protection layout.
Treat Every Replacement as a Risk Window
Serial drive replacement repeatedly reads the surviving members of the current array. That can be acceptable with healthy disks and a verified backup, but it creates multiple rebuild windows before the larger geometry is complete.
Adding a new group avoids retiring healthy drives, yet it introduces a new backplane, power supply, cable, and controller path. A representative four-bay JBOD evaluation shows that an enclosure can preserve a direct disk path while still adding power and cooling considerations.
Choose replacements when the old disks are already near retirement. Choose a new enclosure when the old set is healthy enough that discarding it would dominate the cost and the new fault domain is supportable.
Price the Ports and Power, Not Only the Disks
An enclosure quote is incomplete without the host adapter, cable, UPS outlet, rack space, fan acoustics, and a spare or replacement plan. A drive-replacement quote is incomplete without the temporary backup or migration capacity needed to protect the process.
If electricity and noise are expensive in the room, drive density can win even at a higher purchase price. If disks are the expensive asset and power is acceptable, preserving the old set in an added shelf can win.
| Cost or constraint | Higher-capacity drives | Another enclosure |
|---|---|---|
| Disk purchases | Replaces existing capacity | Adds capacity beside existing disks |
| Required bays | No extra bays | Needs shelf bays and space |
| Controller path | Existing ports | External HBA or supported link |
| Power | Similar drive count | More drives, fans, and PSU |
| Future headroom | Depends on final density | Depends on remaining shelf bays |
Check the Host's Expansion Boundary
Confirm the host exposes the disks in the way your storage stack expects. Hardware that hides individual drives, uses an unsupported bridge, or consumes the last PCIe lanes needed for networking can turn a nominal expansion into a platform replacement.
Large-fleet hard-drive reliability datasets are useful for comparing model populations, but your local boundary remains controller compatibility, cooling, SMART visibility, and restore readiness.
If adding the enclosure also forces a motherboard, HBA, PSU, and rack change, compare it against a larger integrated chassis rather than pretending it is a small accessory.
Use the 20TB Decision Rule
Choose higher-capacity drives when replacing the oldest or smallest members reaches 20TB usable, preserves a simple topology, and leaves a credible next step. Schedule one replacement at a time and verify array health between each operation.
Choose another enclosure when current drives have meaningful remaining life, expansion can add a complete protected group, and the host has a verified data path. After capacity is settled, use the SMB and NFS client-fit comparison to ensure access design does not become the next bottleneck.
Stop if neither route leaves a verified backup, a manageable recovery time, and one clear monitoring path. Twenty terabytes of new space is not useful if the expansion makes the system harder to restore than to rebuild.
Product Comparisons
More to Read

LXC vs Docker on Proxmox for App Updates and Rollbacks
Docker gives app-level version control; LXC gives guest-level rollback. The better fit follows the smallest state unit you can restore safely.

Docker vs LXC Security Boundaries for Privileged Home Services
Docker fits narrowly packaged apps; LXC fits fuller Linux services, but neither replaces a VM when shared-kernel risk is unacceptable.

Turnkey NAS OS vs Modular Linux for a First-Time Builder
Choose turnkey NAS software for guided storage operations; choose modular Linux when learning and explicit control justify more ownership.

