P2V conversion of Linux Server using VMware Converter fails at 99% with an error "No such file or directory"

Products

• Converter

Issue/Introduction

This article provides information about the P2V conversion failing at 99% with an error similar to:

Issue can be further validated as per the log entries mentioned below:

vmware-converter-server.log

YYYY-MM-DDTHH:MM:SS info vmware-converter-server[17600] [Originator@6876 sub=Default] [task,381] [task-1] -- ERROR -- Convert: converter.fault.CloneFault
--> (converter.fault.CloneFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    description = "boost::filesystem::copy_file: No such file or directory: "/mnt/p2v-src-root/boot/grub2/grub.cfg", "/mnt/p2v-src-root/boot/grub2/grub.cfg.old.0""
-->    msg = ""
--> }

vmware-converter-worker.log:

YYYY-MM-DDTHH:MM:SS INFO storage ]:  Got mount table entry: fsname: /dev/mapper/mpathgt1, dir: /boot, type: xfs
[YYYY-MM-DDTHH:MM:SS INFO storage ]:  Got mount table entry: fsname: /dev/mapper/mpathgt1, dir: /boot, type: xfs

Environment

VMware Converter 6.6

VMware Converter 6.4

Cause

The source machine utilizes multipathing for mounting the /boot volume. The VMware Converter deploys a sysinfo utility on the source machine to collect system information. However, this utility did not detect the /boot volume as it was mounted via multipathing and mistakenly treated "/boot" as a directory within "/". As a result, the utility did not attempt to mount the /boot volume, leading to the file /boot/grub2/grub.cfg (and any files under /boot) being inaccessible.

 

Resolution

Linux volumes mounted by Device Mapper multipath is not supported by VMware Converter. This is an expected behavior.

Additional Information

Supported Source Disk Types: https://docs.vmware.com/en/vCenter-Converter-Standalone/6.6/vcenter-converter/GUID-37839EC7-368D-4BAF-8853-46A7FBF0E4DD.html