Error Converting VMDK to VHD

[hlejeune]

errors at 33% - "file read error! Unknown error" Logs below

Code: Select all

The log file name: 'logs\V2V_Log-20220628-102809.log' (PID 15816)
6/28 10:28:09.528 38f0 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
6/28 10:28:09.528 38f0 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
6/28 10:28:09.531 38f0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
6/28 10:28:09.531 38f0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
6/28 10:28:09.535 38f0 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 19043
6/28 10:28:09.543 38f0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 8e950000
6/28 10:28:09.543 38f0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\WINDOWS\system32\wbem\wmiutils.dll - 8e950000
6/28 10:28:19.290 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputFile
6/28 10:28:22.322 38f0 Facility ???INFO: CPPInputFile::checkFile: Select file: C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vmdk
6/28 10:28:22.411 38f0 Facility ???INFO: VMwareFile::ParseFile: sFilename - C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vmdk
6/28 10:28:22.438 38f0 Facility ???INFO: CPPInputFile::checkFile: ParseFile: 0
6/28 10:28:22.438 38f0 Facility ???INFO: CPPInputFile::checkFile: File type: IDS_IMAGE_CONVERTER_FORMAT_NAME_VMDK_SPARSE  File size: 125829120 sectors
6/28 10:28:23.341 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
6/28 10:28:26.446 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eFormat
6/28 10:28:28.606 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOptionsHyperV
6/28 10:28:33.736 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOutputFile
6/28 10:28:34.973 38f0 Facility ???INFO: CPPOutputFile::onNext: Out path: C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vhd, Out format 7
6/28 10:28:34.973 38f0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
6/28 10:28:34.979 4ed8 Facility ???INFO: CPPConverting::Convert: InConvertType: 4, OutConvertType: 4
6/28 10:28:34.980 4ed8 Facility ???INFO: CPPConverting::ConvertImage: pathInput: C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vmdk, pathOutput: C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vhd
6/28 10:28:34.980 4ed8 Facility ???INFO: VMwareFile::ParseFile: sFilename - C:\Virtual Machines\Windows 10 x64 - VPLink\Windows 10 x64-cl1.vmdk
6/28 10:28:35.006 4ed8 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
6/28 10:28:35.007 4ed8 Facility ???INFO: CVHDSparseExtent::New: Write Footer1
6/28 10:28:35.007 4ed8 Facility ???INFO: CVHDSparseExtent::New: Write Header
6/28 10:28:35.011 4ed8 Facility ???INFO: CVHDSparseExtent::New: Write BAT
6/28 10:28:35.011 4ed8 Facility ???INFO: CVHDSparseExtent::New: Write Footer2
6/28 10:28:35.011 4ed8 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 0
6/28 10:29:13.947 4ed8 Facility ???ERROR: VMwareFile::Read: m_VixDiskLib_Read is fail - 1, Unknown error
6/28 10:29:13.947 4ed8 Facility ???ERROR: CPPConverting::ConvertImage: Read 3

EDIT: Managed to figure it out. had to do a disk repair using vmware because the disk was apparently corrupted even though the VM ran just fine. once that repair was completed the conversion completed successfully.

[yaroslav (staff)]

Hi,

Welcome to StarWind Forum and thanks for your update! Good to know it worked.
Was the VM responsive via RDP or SSH? ESXi sometimes shows the VM as up even though that effectively it can be down.

[hlejeune]

it was actually a workstation VM. it was fully functional. very strange.

[yaroslav (staff)]

That's weird how it was working. Did you try running chckdsk for that VM?

[hlejeune]

I did run one after doing the repair to make sure there weren't any lingering issues, but it didn't find anything.

[yaroslav (staff)]

Thanks for letting me know.
It can be that there was an issue on VMware layer, but not inside the VM. Glad to know anyway that you fixed it!