Storage vMotion failed to initialize copy of disk-specific file.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• Storage vMotion fails for a specific virtual machine with bellow error

Verification:

• Below error are noticed under hostd.logs:

YYYY-MM-DDTHH:MM:SS.MsecZ info hostd[2100707] [Originator@6876 sub=Vcsvc.VMotionSrc.246109079489503988] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.svmotion.fail.internal",
-->          message = "A fatal internal error occurred. See the virtual machine's log for more details.",
-->       },
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.svmotion.mirror.disk.setup.error",
-->          message = "Failed to start SvMotion. Error during disk setup.",
-->       },
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.svmotion.mirror.disk.file.init.cancel",
-->          message = "Storage vMotion failed to initialize copy of disk-specific file.",
-->       }
-->    ],
-->    reason = "A fatal internal error occurred. See the virtual machine's log for more details.",
-->    msg = "A fatal internal error occurred. See the virtual machine's log for more details.
--> Failed to start SvMotion. Error during disk setup.
--> Storage vMotion failed to initialize copy of disk-specific file.

 

YYYY-MM-DDTHH:MM:SS.MsecZ info hostd[2099695] [Originator@6876 sub=Vcsvc.VMotionDst.246109079489503988] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.migrate.waitdata.platform",
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "1",
-->                value = "195887250"
-->             },
-->             (vmodl.KeyAnyValue) {
-->                key = "2",
-->                value = "Migration determined a failure by the VMX"
-->             }
-->          ],
-->          message = "Failed waiting for data.  Error bad0092. Migration determined a failure by the VMX.
--> "
-->       }
-->    ],
-->    reason = "Failed waiting for data.  Error bad0092. Migration determined a failure by the VMX.
--> ",
-->    msg = "Failed waiting for data.  Error bad0092. Migration determined a failure by the VMX.

• From VMkernel logs stats, Migration failure caused due to configuration error on the vmx file.

YYYY-MM-DDTHH:MM:SS.MsecZ cpu0:2106464)WARNING: Migrate: 6480: 246109079489503988 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.
YYYY-MM-DDTHH:MM:SS.MsecZ cpu0:2106464)Migrate: 102: 246109079489503988 S: MigrateState: Failed
YYYY-MM-DDTHH:MM:SS.MsecZ cpu0:2106464)WARNING: Migrate: 253: 246109079489503988 S: Failed: Migration determined a failure by the VMX (0xbad0092) @0x42000ce4fb0f
YYYY-MM-DDTHH:MM:SS.MsecZ cpu0:2106464)Hbr: 3815: Migration end received (worldID=2106465) (migrateType=2) (event=1) (isSource=1) (sharedConfig=0)
YYYY-MM-DDTHH:MM:SS.MsecZ cpu18:154773235)Migrate: 102: 246109079489503988 D: MigrateState: Failed

Environment

VMware vSphere ESXi 8.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 6.x

Cause

• From the VM configuration file, Notice CBT/CKT  is enabled.

ctkEnabled = "TRUE"
scsi0:0.ctkEnabled = "TRUE"
scsi0:0.cvctkSize = "386547056640"

• From the VMware.log file, Notice Storage vMotion is unable to locate the ckt enabled vmdk file for migration and eventually failing the Storage vMotion.

YYYY-MM-DDTHH:MM:SS.MsecZ| worker-154758433| | I005: SVMotionDiskSetup: Adding disk scsi0:0: moveRDMDesc: 0, isRemote: 0, skipZeros: 1.
YYYY-MM-DDTHH:MM:SS.MsecZ| worker-154758433| | I005: OBJLIB-FILEBE : FileBEGetAllocSizeByPath: could not get size for '/vmfs/volumes/########-########-####-############/<VMHOMEFOLDER>/<VMNAME>-ctk.vmdk' : 6
YYYY-MM-DDTHH:MM:SS.MsecZ| worker-154758433| | W003: Disk_SVMotionPrepareCBT: Failed to get CTK file maximum size '/vmfs/volumes/########-########-####-############/<VMHOMEFOLDER>/<VMNAME>-ctk.vmdk': Could not find the file(393218).
YYYY-MM-DDTHH:MM:SS.MsecZ| worker-154758433| | W003: SVMotionPerDiskFileInit: SvMotion failed due to diskInit event callback request failure for fileType 3
YYYY-MM-DDTHH:MM:SS.MsecZ| worker-154758433| | W003: SVMotionPrepareForCopyThread: Failed to start SvMotion. Error during disk setup.

Resolution

1. Disable CBT on the virtual machine [Steps to Enable/disabling Changed Block Tracking (CBT) on virtual machines]

2. Re-initiate the Storage vMotion.

3. Enabled CBT if needed and confirm that the ckt.vmdk file is created under the home folder.

Additional Information

Enabling / Disabling Changed Block Tracking (CBT) on virtual machines

Changed Block Tracking (CBT) on virtual machines

Storage vMotion fails with Error 195887107

VM cloning / Storage vMotion or VM Backup task fails