ESXi Patching

SINGLE VIB:
[root@esxi:~] esxcli software vib install -v /tmp/ixgben-1.7.10-1OEM.670.0.0.8169922.x86_64.vib
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: INT_bootbank_ixgben_1.7.10-1OEM.670.0.0.8169922
VIBs Removed: VMW_bootbank_ixgben_1.7.1.16-1vmw.670.3.73.14320388
VIBs Skipped:

ENTIRE ZIP OF VIBs:
[root@esxi:~] esxcli software vib update -d "/vmfs/volumes/RAID5/PATCHES/ESXi670-202004002.zip"
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: [like, the entire ZIP file]
VIBs Removed: [subset]
VIBs Skipped: [subset]

ESXi Patching

SINGLE VIB:
[root@esxi:~] esxcli software vib install -v /tmp/ixgben-1.7.10-1OEM.670.0.0.8169922.x86_64.vib
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: INT_bootbank_ixgben_1.7.10-1OEM.670.0.0.8169922
VIBs Removed: VMW_bootbank_ixgben_1.7.1.16-1vmw.670.3.73.14320388
VIBs Skipped:

ENTIRE ZIP OF VIBs:
[root@esxi:~] esxcli software vib update -d "/vmfs/volumes/RAID5/PATCHES/ESXi670-202004002.zip"
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: [like, the entire ZIP file]
VIBs Removed: [subset]
VIBs Skipped: [subset]

Back-End LUNs in Regards to LVM

For reasons I won't go into here, I increased the capacity of an iSCSI LUN to make more room in a handful of logical volumes. Awkwardly, the parent volume group lost its goddamn mind.

I can't recall if I've ever run into this specific scenario or not before, but I doubt it because I rarely mess around with SAN. Well, until recently anyway. Suffice it to say I was stuck until I could find away to dynamically resize the volume group. Turns out you have to use pvresize as in:

pvresize /dev/sdb

I cannot remember now if I had activated or deactivated the vg prior to doing so, but at any rate it worked.

Back-End LUNs in Regards to LVM

For reasons I won't go into here, I increased the capacity of an iSCSI LUN to make more room in a handful of logical volumes. Awkwardly, the parent volume group lost its goddamn mind.

I can't recall if I've ever run into this specific scenario or not before, but I doubt it because I rarely mess around with SAN. Well, until recently anyway. Suffice it to say I was stuck until I could find away to dynamically resize the volume group. Turns out you have to use pvresize as in:

pvresize /dev/sdb

I cannot remember now if I had activated or deactivated the vg prior to doing so, but at any rate it worked.