VxRail: Virtual Machine Cannot Power on After Removal of RecoverPoint for Virtual Machines
Summary: Virtual machine (VM) cannot power on after removing RecoverPoint for Virtual Machines due to IO filter settings in the .vmdk file.
Symptoms
Trying to power on the issue VM gives an error: No host is compatible with virtual machine.
Powering on the VM from the host directly gives the error: Cannot open the disk '/vmfs/volumes/vsan: xxxx/xxx.vmdk' or one of the snapshot disks it depends on
Cause
The .vmdk file has included a wrong IO filter configuration. See below the ddb.iofilters = "emcsplitter" line:
[root@xxxxx:/vmfs/volumes/vsan:xxxxxxxxxxxxxxxxx] cat xxxxxxx.vmdk # Disk DescriptorFile version=5 encoding="UTF-8" CID=8xxxxxx parentCID=ffffffff createType="vmfs" # Extent description RW 440401920 VMFS "vsan://xxxxxxxxxxxxxxxxxxx" # Change Tracking File changeTrackPath="xxxxxxxx.vmdk" # The Disk Data Base #DDB ddb.adapterType = "lsilogic" ddb.deletable = "true" ddb.geometry.cylinders = "27413" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.iofilters = "emcsplitter" ddb.longContentID = "2245a7xxxxx20db48133a838" #ddb.sidecars = "emcsplitter_1,xxxxxxxxxx.vmfd" ddb.thinProvisioned = "1" ddb.toolsInstallType = "1" ddb.toolsVersion = "12421" ddb.uuid = "xx 00 C2 xx xx xx xx xx" ddb.virtualHWVersion = "14"
Resolution
Engage RecoverPoint for Virtual Machines to check issue.
Verify that there is a valid backup of the virtual machine.
Edit issue .vmdk files, Remove the "IO filter provider" line entries from the VMDK descriptor files for virtual machines with more than one VMDK attached.
- Back up the issue
.vmdkfile. - Edit the issue
.vmdkusing vi - Comment out the
ddb.iofiltersline:#ddb.iofilters = "emcsplitter"
Additional Information
For more information, see Broadcom article: "Module 'Disk' power on failed" / "Plugin loading error" when attempting to power on a VM