- It is always recommended to find the files consuming the space and remove them before manually increasing the size of root as per KB: 92978
- To manually increase the root '/' partition check the workaround section.
Workaround:
- Pre-requisite : Take backup (clone of the appliance)
- Power down the vRLCM
- Extend the "Hard disk 1" from standard 10GB to 15GB
- Power on the vRLCM
- Login to ssh session and check current space
Run this command to check that the space has been extended on the /dev/sda drive :
lsblk
From above you see sda size is increased but partition /dev/sda4 still on default 8.9G
- Now we need to change the root partition to take advantage of the extended disk space.# fdisk /dev/sda
# p will print the current setup
# d will prompt for which partition to delete and default to the last created number 4 - delete the partition
# n will prompt to create a new partition - accept all defaults and you should now have a partition 4 which has consumed the extra space you added. When asked about removing the signature choose ‘Y’
You can enter ‘p’ again to print the results which should look like below :
# w will WRITE the partition table changes - if you do q to quit - no changes will be applied
- Update the boot UUID as the above process creates a new one
First run 'blkid' command to confirm the current UUID of /dev/sda4
From above new partition UUID = "a6657eb2-0279-b648-8fca-07d96fb35478"
Update the /boot/grub2/grub.cfg file with the new partition UUID for sda4
vi /boot/grub2/grub.cfg
To check the current grub.cfg file looks like:
Scroll down to line with this entry:
set rootpartition=PARTUUID=x
from the above screenshot currently its :
set rootpartition=PARTUUID=61e317c0-2d91-486a-b915-037ddc4abbb4
Replace with updated value from the blkid command ran earlier : a6657eb2-0279-b648-8fca-07d96fb35478
The /boot/grub2/grub.cfg should now have the updated UUID for root partition, confirm by running a cat on the file :
- Now run reboot command to reboot the appliance :
reboot
Check the status of the appliance in vCenter web console, once up, confirm the space is now available