VMware Cloud Community
kbhowmick123
Enthusiast
Enthusiast

The VM failed to resume on the destination during early power on

Environment vCenter server 5.5, build 1945274, esxi 5.5.0 1892794 - Error Message - #The VM failed to resume on the destination during early power on

VM is not pinging
getting below error while migrating the VM

#The VM failed to resume on the destination during early power on.

#Module DiskEarly power on failed.

#Cannot open the disk '/vmfs/volumes/5579ba99-ad50f0a6-3465-0025b501a021/SDEPAPS284/SDEPAPS284.vmdk' or one of the snapshot disks it depends on.

#Could not open/create change tracking file

#Cannot open the disk '/vmfs/volumes/5579ba99-ad50f0a6-3465-0025b501a021/SDEPAPS284/SDEPAPS284_1.vmdk' or one of the snapshot disks it depends on.

#Could not open/create change tracking file

Datastore block size details:

Formatting:

File system - vmfs 5.60

Block size -1 MB

Please suggest.

0 Kudos
2 Replies
slikrik727
Contributor
Contributor

I had this same issue after moving VMs to new hardware and upgrading to vmx10 vHardware. Here is how I resolved it;

1. Shutdown the VM.

2. vMotion to another host. (Not sure if this step is necessary but I did it)

3. SSH into the host the VM is now on and browse to the Datastore that the VM is on. cd vmfs/volumes/Datastore/VM_name

4. list (ls)

5. look for any -ctk.vmdk. All will need to be renamed. See step 6.

6. mv vmname-ctk.vmdk vmname-ctk.old

7. Power On VM and then try to migrate.

Good Luck

0 Kudos
kbhowmick123
Enthusiast
Enthusiast

This is a known issue affecting vCenter 5.1 and 5.5

The issue is resolved in VMware vCenter server 5.1 Update 3 and VMware vCenter server 5.5 update 3.

For work around please go through this KB articles:

VMware KB: VMware vCenter Server 5.1/5.5 fails after hot-adding a shared VMDK or RDM

0 Kudos