"Virtual disks with same UUID should not be assigned to a VM" error adding a virtual disk to a virtual machine
Article ID: 341653
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- If the virtual machine is running and if you save the change on the virtual machine settings, you see a message similar to:
[msg.disk.duplicateUUID] Virtual disks "/vmfs/volumes/<DatastoreName>/<VMName>/<vDiskName.vmdk>" and "/vmfs/volumes/<DatastoreName>/<VMName>/<vDiskName.vmdk>" have the same UUID 12 34 A5 67 89 B0 1C 23-DE 45 6F 78 9A B0 1C 23. Virtual disks with same UUID should not be assigned to a VM since this can lead to problems when the guest boots. Please make sure virtual disks have unique UUIDs. Do you want to continue?
Note: The complete message is visible in the vmware.log file in the virtual machine folder.
- If the virtual machine is running and you answer no, the virtual disk is not added to the virtual machine and the virtual disk gets locked
Environment
VMware vSphere ESXi 8.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 6.x
Cause
You cannot add a virtual disk to a virtual machine that already has a disk with the same UUID.
Resolution
- In order to create a new UUID for the disk:
1. Power off the virtual machine to unlock the disk.
2. Run this command to get the virtual disk UUID.
vmkfstools -J getuuid <vmname>.vmdk
Example:
# vmkfstools -J getuuid
/vmfs/volumes/datastore/VM/vm.
UUID is 12 34 A5 67 89 B0 1C 23-DE 45 6F 78 9A B0 1C 23
3.Run this command to set or modify the UUID
vmkfstools -J setuuid <vmname>.vmdk
Example:
#vmkfstools -J setuuid /vmfs/volumes/datastore/VM/vm.
UUID is 12 34 A5 67 89 B0 1C 23-DE 45 6F 78 9A B0 1C 23
A new UUID is returned after the command executes.
- Alternatively when you clone a vmdk, a new disk will generally have a different UUID (Universally Unique Identifier). This UUID is used by the hypervisor to uniquely identify the disk.
Additional Information
Feedback
Yes
No
Powered by
