vMotion failed with error:"Migration failed after VM memory precopy. Please check vmkernel log for true error. The VM failed to resume on the destination during early power on. Module Disk power on failed."

Products

• VMware vSphere ESXi

Issue/Introduction

The vMotion task consistently failed with the following error:

"Migration failed after VM memory precopy. Please check vmkernel log for true error.
The VM failed to resume on the destination during early power on. Module Disk power on failed.
Virtual disks /vmfs/volumes/ds_name/firstvm_name/firstvm_name.vmdk and /vmfs/volumes/ds_name/secondvm_name/secondvm_name.vmdk have the same UUID."

This error prevented the VM from powering on at the destination ESXi host during the vMotion process.

Environment

VMware vCenter Server 8.x

Cause

The failure was caused by two virtual disks attached to the same VM having identical UUIDs. VMware requires that each virtual disk (.vmdk) have a unique UUID to ensure proper identification and operation across hosts. Duplicate UUIDs create a conflict during VM power-on, particularly when using vMotion.

Resolution

1. SSH into the ESXi host using root credentials where the VM is located.

2. Identify the virtual disk with the duplicate UUID as per the error message.

3. Run the following command to generate a new UUID for the disk:

   vmkfstools -J setuuid /vmfs/volumes/datastore_name/VM_directory/vm.vmdk

   Replace datastore_name, VM_directory, and vm.vmdk with the appropriate path to the affected virtual disk.

4. Retry the vMotion operation.
   
   Reference:

• Broadcom KB 341653 – Virtual disks with same UUID should not be attached to the same VM