Increasing (The Wrong) VMware vCenter Server Appliance 6.0 VMDK

I encountered a Health Message for my VCSA Build Number 5326079.2017-04-26_22-03-40

This led me to Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.0 (2126276) | VMware KB

However, in the process, I noticed a more serious issue with /storage/log (/dev/mapper/log_vg-log). It was at 98% capacity.2017-04-27_0-29-50

According to the KB article and other reliable sources, I needed to increase VMDK5 to resolve the immediate issue with /storage/log. So, I right clicked the vCenter VM, selected “Edit Settings,” clicked “Manage other disks” (on the Virtual Hardware tab), and increased Hard disk 5 from 10GB to 15GB.

Here is the original configuration:2017-04-27_0-36-04

…and here is how it looked after modification (the sizes were grayed out at the time because vCenter was being backed up by a program that utilizes snapshots and you cannot alter disk size when snapshots are present). Anyway, you will see that Hard disk 5 went from 10 to 15 GB.:2017-04-27_0-39-06

Here is the SSH/Shell before and after:2017-04-27_0-41-20

The Wrong Trousers

Notice something unexpected? Apparently, for my implementation, Disk 5 correlates to /storage/db and NOT /storage/log. In fact, based on this result, it appears that Disk 6 is the one that needs to be grown. Again, that does NOT correlate to other documentation as Disk 6 is referenced as /storage/db in those places.

On a whim and a prayer, I repeated the process for Disk 6, hoping to grow the /storage/log VMDK. Disk 6 was initially 10GB. I changed it to 20GB. Annnnd, bingo:2017-04-27_0-15-54

Migrate Option Is Grayed Out

I’ve encountered this problem in a myriad of ESXi host versions and vCenter versions. For unknown reasons, I am able to migrate some VMs and not others. I’ve tried a number of resolutions in various KB articles, but the only approach that has worked thus far is removing the VM from inventory and adding it back.

Symptoms: Migrate, Move To, Remove from Inventory, and Delete from Disk options are greyed out for a powered-on VM.

To resolve this issue, remove the virtual machine from the vCenter Server Inventory and add it back. Note: When removingĀ a virtual machine from the vCenter Server Inventory, the previous performance statistics for the virtual machine are lost.

Caution: Before performing these steps, make a note of the datastore where the virtual machine resides.

  1. In the vSphere Client, right-click the powered-off virtual machine and click Remove from Inventory.
  2. Click Yes when prompted to confirm the removal.
  3. Click Home > Storage
  4. Open the Datastore and folder where the VM’s vmx file is stored
  5. Right-click the .vmx file and click Register VM. This might be “Add to Inventory” in earlier versions.
  6. Follow the steps in the wizard to add the virtual machine back to the Inventory.
  7. Click Home > Hosts and Clusters.
  8. Right-click the virtual machine. The migrate option is now available.

Can’t Delete Inactive ESXi Datastore

I recently encountered an issue where an ESXi host upgrade caused it to lose it’s connection to an iSCSI datastore. I was finally able to get the iSCSI issue resolved, but then I had an issue where I needed to name the newly created connection the same as the previous. The “old” one was still listed as an “inactive” datastore. I couldn’t name it the same as the old one, but there was no option to delete the old datastore reference.

I finally figured out that I had to remove all VMs from inventory that were still dependent on the “old” datastore. As soon as I deleted those VMs from inventory, the “inactive” datastore was automatically removed. Then I could rename my new iSCSI datastore to match the one that the system marked inactive when the original issue happened during the upgrade.