V2V Convert error - Disk encoding error

[davidos]

Hello, I am trying to convert a disk from VMWare to Hyper-V but I am getting error that I couldn't even find on google. I have the latest version of your V2V converter

Log is here:

Code: Select all

The log file name: 'logs\V2V_Log-20220128-113604.log' (PID 15284)
1/28 11:36:04.856 28bc Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
1/28 11:36:04.856 28bc Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
1/28 11:36:04.880 28bc Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
1/28 11:36:04.888 28bc Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
1/28 11:36:04.901 28bc Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 19043
1/28 11:36:04.921 28bc Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 797a0000
1/28 11:36:04.951 28bc Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 797a0000
1/28 11:36:11.189 28bc Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
1/28 11:36:22.943 28bc Facility ???INFO: CPPInputFile::checkFile: Select file: path-to-vmdk-file
1/28 11:36:23.059 28bc Facility ???INFO: VMwareFile::ParseFile: sFilename - path-to-vmdk-file
1/28 11:36:23.106 28bc Facility ???ERROR: VMwareFile::ParseFile: m_VixDiskLib_Open is fail - 16061, Disk encoding error
1/28 11:36:23.106 28bc Facility ???INFO: CPPInputFile::checkFile: ParseFile: 2

What could be the cause of this issue?
The disk boots fine in VMWare Workstation Pro 16. In the VMWare client it says: This is a VMWare Workstation 12 image so it isn't one of the newest but I hope that the problem isn't with the version.

Thanks
David

[yaroslav (staff)]

According to the logs, it cannot reach the file.
Please copy the file to a Windows Server machine and try converting it locally.

[sandman]

Guys,

I have exactly the same problem according to logs, however, my VMDK file is located on a USB-3 drive attached directly to my workstation. VMWare Player runs it from this location without any trouble. I found also an old copy on a secondary internal drive but the result is the same. May it be somehow connected to the internal format of VMDK? How can I troubleshoot that? Is there any way to increase the verbosity of the logs?

BR,
Jacek

[yaroslav (staff)]

Please consider trying local VMDK conversion.
Share the logs here with me if you run into any issues.

[forssuse]

Same issue here. The log looked exactly the same as the OP's version. I was converting a vmdk on the local machine running Windows Server 2019.

Are there any methods to show verbose log?

[yaroslav (staff)]

Please try converting as a local disk.