What should I do if a VPS resize fails or capacity does not appear?
A resize can involve several independent stages. Determine which stage completed before retrying: provider allocation, virtual-device presentation, guest resource activation and, for disks, partition or filesystem growth. Repeating a command without that distinction can make recovery harder.
Instructions
1. Inspect the provider operation state
Review the service’s final status and Activity record. Record the requested allocation, time and error. A processing request is not proof of failure or completion, so avoid issuing repeated resize operations.
2. Compare the guest view
If the guest is available, inspect visible resources and storage layers.
lscpu
free -h
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS
df -hTThese views distinguish visible CPU or RAM from disk-device capacity and filesystem capacity.
3. Resume only the confirmed incomplete stage
If the provider allocation failed, use support with the operation reference. If the guest needs a documented restart, schedule it. If a disk is larger but the filesystem is not, follow the verified layout’s expansion procedure. Do not shrink the provider disk back after the guest has already expanded into it.
Check the result
- The completed and incomplete stages are identified with evidence.
- Provider allocation, guest resources and usable filesystem capacity agree after the supported correction.
Troubleshooting
- The guest will no longer boot
- Use the recovery console and preserve the exact resize error before any repair attempt.
- Only df shows the old size
- The virtual disk or partition may be expanded while the filesystem remains unchanged; verify each layer before acting.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.