Get-VMHostFirmware Internal Error - Can't Backup Hypervisor Configuration

If you're getting an internal error while trying to run the Get-VMHostFirmware command with vSphere PowerCli, chances are the problem comes from a corrupt scratch directory on the hypervisor.

The Get-VMHostFirmware command is one of my favorites if I'm doing any maintenance on the hosts. It saved me hours of configuration multiple times... Very handy! But recently, I needed to run the command on one of my hosts and I was getting an internal error! Nothing more... Even after a reboot and trying all the other methods of configuration backup mentioned here, still no luck!

How to back up ESXi host configuration
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2042141

After hours of research, finally I came across with a blog that mentioned the scratch folder on the host. In the post, the user was suggesting to backup the scratch to another location and recreate it. I took a different approach and just changed the scratch config location from the "Advanced Settings" of the host.

in vSphere Client, select the host and go to "Configuration" tab, than go to "Advanced Settings" and locate the "ScratchConfig" section and enter the new vmfs volume in the ScratchConfig.ConfiguredScratchLocation setting.

You need to reboot the host for this setting to take effect. You should be able to use the Get-VMHostFirmware command now.
Location: Montreal, QC, Canada

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more