ESX Server mounts the storage using UUID. With the hard disk changed, UUID changes too. Hence, ESX fails to mount
Symptoms
- You boot an ESX host machine from Acronis Bootable Media;
- You back up the machine's hard disk;
- After that you replace the hard disk in the machine with an identical one;
- You restore the backup to the new disk;
- You boot the ESX host machine from the restored disk;
- Guest Operating Systems fail to boot and ESX Server cannot recognize the restored disk.
Cause
ESX Server mounts the storage using Universally Unique Identifier (UUID). With the hard disk changed, UUID changes too. As a result ESX Server fails to recognize the restored hard disk and mount the storage. Hence, Guest Operating Systems fail to boot.
Solution
To migrate ESX Server to new hard disks you need to do the following:
- Restore an existing image of ESX Server to new hard disks;
- Boot ESX Server and hit Alt-F1 to enter the command-line interface. Log in under root;
- Issue the following command:
esxcfg-advcfg -g /LVM/EnableResignature
There will be either 1 or 0 value output. If the value is 0, then ESX will not automatically update the VMFS header with new LUN and UUID. Therefore this value should be set to 1:
esxcfg-advcfg -s 1 /LVM/EnableResignature
- Reboot the ESX Server:
shutdown -r 0
- After the reboot you should connect to the ESX Server from the Console and check if the data storage has been mounted properly.
(!) The Guest Operating Systems will remain in the unknown state. So, you should reinitialize guest virtual machines:
- In the left menu of ESX Server Console right-click on the guest machine name and click Remove from inventory;
- Choose host ESX server-> Configuration;
- Under the Hardware section choose Storage and right-click on it (it should contain a list of virtual machines;
- Click Browse Datastore;
- Choose the .vmx of the machine that was removed from inventory;
- Click on the Add this virtual machine to inventory option.
After this the ESX Server should work properly and Guest Operating Systems should boot.
More information
See also: