“could not open/create change tracking files” error when powering on VM
search cancel

“could not open/create change tracking files” error when powering on VM

book

Article ID: 313074

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

To provide procedure to allow the virtual machine (VM) affected by this error to power on.

Symptoms:
Powering on virtual machine after a storage outage fails with the error:

could not open/create change tracking file vmdk_file_name
 
Note: For additional symptoms and stack entries, see the Additional Information section.


Cause

This issue occurs when the filename-ctk.vmdk file is not cleared.

Resolution

To resolve this issue, move the filename-ctk.vmdk file into a subdirectory or rename it:
 
  1. In the vCenter or ESXi host user interface, right-click the VM and select Edit Settings...
  2. Make note of the SCSI controller type used by the hard disk.
  3. Remove the vmdk_file_name hard disk specified in the error message from the virtual machine.
Warning: Select only Remove from virtual machine, Selecting Remove from virtual machine and delete files from disk will permanently delete the virtual disk.
  1. Follow Using the ESXi command line to find the virtual machine file path and virtual disk information to connect to the ESXi host command line interface and navigate to the directory for the affected VM.
  2. Move the filename-ctk.vmdk file into a subdirectory or rename it. Where the text in italics is replaced by the actual file name of the ctk file in the error:
mkdir deleteme
mv filename-ctk.vmdk deleteme
 
  1. In the vSphere Client, re-add the hard disk back to the virtual machine using the SCSI controller type from step one.
  2. On the ESXi host command line interface, edit the descriptor file (.vmdk) and remove or comment out any references that specify use of a ctk file.
  3. Power on the virtual machine.


Additional Information

  • No CTK variables on the virtual machine configuration (.vmx).
  • When the virtual machine is powered on, you see error similar to:

    invalid signature change in tracking file
For more information about Changed Block Tracking see:
 
Further helpful KBs for VM power on issues:
Failed to power on virtual machine