Trying to increase the root partition of a vcsa 6.5 but getting hiccups. Following https://kb.vmware.com/s/article/2145603 doesnt seem to work for vcsa6.5. Any help?
The URL below is the technique that I used to extend the /dev/sda3 partition in VCSA ESX v6.0.
https://content.pivotal.io/blog/increasing-the-size-of-a-vcsa-root-filesystem
However, this technique doesn’t work in ESXi v6.5. It appears that the version of FDISK in VCSA ESXi v6.5 has changed. It no longer recognizes the partition properly and there is no option ‘a’ to toggle the bootable flag on /dev/sda3. See attached screenshots.
After increasing the size of vmdk1 for the VCSA in the vCenter, I’ve tried running both of the following commands:
- vpxd_servicecfg storage lvm autogrow
- /usr/lib/applmgmt/support/scripts/autogrow.sh
Both commands complete without any errors, but the size of /dev/sda3 never changes.
-chris
- P.S.
I’m growing to grow /dev/sda3 to 24G.
root@localhost [ ~ ]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.9G 0 7.9G 0% /dev
tmpfs 7.9G 16K 7.9G 1% /dev/shm
tmpfs 7.9G 704K 7.9G 1% /run
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
/dev/sda3 11G 6.3G 3.8G 63% /
tmpfs 7.9G 1.5M 7.9G 1% /tmp
/dev/mapper/netdump_vg-netdump 985M 1.3M 932M 1% /storage/netdump
/dev/mapper/dblog_vg-dblog 15G 102M 14G 1% /storage/dblog
/dev/mapper/seat_vg-seat 25G 327M 23G 2% /storage/seat
/dev/mapper/autodeploy_vg-autodeploy 9.8G 23M 9.2G 1% /storage/autodeploy
/dev/mapper/db_vg-db 9.8G 108M 9.2G 2% /storage/db
/dev/sda1 120M 27M 87M 24% /boot
/dev/mapper/updatemgr_vg-updatemgr 99G 74M 94G 1% /storage/updatemgr
/dev/mapper/log_vg-log 9.8G 417M 8.9G 5% /storage/log
/dev/mapper/imagebuilder_vg-imagebuilder 9.8G 23M 9.2G 1% /storage/imagebuilder
/dev/mapper/core_vg-core 50G 52M 47G 1% /storage/core
root@localhost [ ~ ]#
