1013

Increase root partition size on existing deployments

Summary

NAbox has grown over time and containers now require more space on the root partition than older releases initially allocated. Newer releases ship with a larger root capacity, but existing deployments may still need a manual disk size increase.

Why this is needed

On older deployments, the root partition (/) can become a bottleneck during normal operations or upgrades, especially when pulling and unpacking container images.

Before making changes, check current root usage:

df -h /

If available space is low, increase the system disk size for the VM and reboot.

VMware procedure

On VMware, this is typically straightforward:

1. Increase the NAbox system VMDK size in vCenter.
2. Reboot NAbox.
3. Validate that root capacity increased:

df -h /

If the new size is visible in df -h /, no additional action is needed.

Other platforms

The same concept applies on other platforms:

1. Increase the VM or instance system disk size using platform tooling.
2. Reboot NAbox.
3. Validate with df -h /.

The exact commands and UI workflow differ by platform (for example Hyper-V, KVM/QEMU, or cloud providers), so use your platform documentation for the disk expansion step.

Validation checklist

• df -h / reports a larger total size than before.
• Root free space is sufficient for upgrades and container image operations.
• NAbox services are healthy after reboot.

If size did not increase after reboot

1. Confirm that the hypervisor/provider change was applied to the correct system disk.
2. Confirm the guest sees the larger disk size with lsblk.
3. If the disk size increased but / did not, open a support request and include df -h, lsblk, and platform details.