Skip to main content

Virtual Machine cloning fails with error: Unable to access -000001.vmdk.ctk

  Symptoms

  • You are unable to access a VM that has has a snapshot from the GUI.
  • When trying to clone the VM using vmkfstools -i sourefile.vmdk destinationfile.vmdk, you see an error like this:

    Unable to power on virtual machine <vm name>. Unable to access <vm name>-000001.vmdk.ctk

changed-block-tracking
Resolution
Caution: You can easily lose data if you make a mistake while editing the .vmdk file. VMware recommends backing up your data before attempting these steps.
The safest way to deal with this issue is to disable Changed Block Tracking and to try the operation again. For more information, see Changed Block Tracking (CBT) on virtual machines (1020128).
To work around this issue, edit the snapshot's .vmdk file and place a # in front of the file reference to the .ctk file. This comments out the reference to the .ctk file, and makes it seem as though change tracking has been disabled.
This prevent change tracking, but allows you to clone or otherwise access the disk.
After performing this workaround, the snapshot should be applied if at all possible and, if needed, a snapshot should be taken again.

Comments

  1. Anonymous23 January 2022 at 10:49

    Best Merit Casino In Canada 2021
    Review of the Merit Casino Canada online casino. 샌즈카지노 It is one 다파벳 of many licensed Canadian gaming providers. You are assured that you can earn  Rating: 9/10 · ‎Review by Shootercasino.com 메리트카지노

    ReplyDelete

Post a Comment

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more