To correct the issue I increase the size of this disk to 20 GB, rebooted the appliance, and ran the below command. dev/sda3 has multiple partitions and the actual size of /dev/sda is 12GB for a Tiny VCSA install. I identified that Hard Disk 1 was the correct vCenter disk. vCenter is non-operationalĪttempting to log onto the appliance may also cause intermediate issues.Įrror in method invocation Field messages missing from Structure .rvice_unavailableĬhecking the space usage on my appliance showed that I only had 5% free space which appeared to not be sufficient for an appliance upgrade.Īfter a little bit of troubleshooting and attempting to locate the correct vCenter Hard Disk that /dev/sda3 represented.
The root partition should now have sufficient space for normal operation or upgrades.ĭuring an attempt to update my VCSA from version 6.7 to 6.7 U1 I encountered the following error in the VAMI. usr/lib/applmgmt/support/scripts/autogrow.shĪs its name implies this will auto grow the root partition with the available space just allocated. There’s a few different commands you can run at this point (see my full issue below) but the easiest command to run is below In the example below I have increase it to 20 GB.Īfter the reboot SSH to the VCSA and enter the shell. Increase the size of the disk from 12 GB (for a Tiny appliance deployment). dev/mapper/log_vg-log 9.8G 2.3G 7.0G 25% /storage/logĮdit the settings of the VCSA VM and located Hard Disk 1 (This disk represents device SDA). dev/mapper/imagebuilder_vg-imagebuilder 9.8G 23M 9.2G 1% /storage/imagebuilder The VCSA root partition is at 100% or near 100% with less than 10% free space available.įilesystem Size Used Avail Use% Mounted on See bottom of post for the full description of my issue. I’ve seen this a number of times with Tiny installs of VCSA so I didn’t want to bother troubleshooting a Home Lab problem through the night. While Anthony was adamant in finding the root cause of the issue to free up space my solution was much simpler -just increase the space on the root volume.
Our root partitions on our Tiny install of VCSA 6.7 had either run out of space or near out of space causing upgrade issues to U1. While our problems were slightly different they both had a common issue. Over this past week both Anthony and I upgraded our vCenters from 6.7 to 6.7 U1. It’s somewhat related to a post Anthony published yesterday so I hope he doesn’t mind. Full disclosure, I’m stealing Anthony Spiteri’s ‘Quick Fix’ used in the title of this post.