Page 1 of 1
One vhdx image failing to open
Posted: Tue Dec 21, 2021 7:35 am
by nzimm
I've used V2V to successfully convert 16 of 17 servers from Hyper-V to VMWare. The remaining system is erroring right away when opening the system .vhdx while the data disk seems fine. Error to open image and file. Logs are showing the following error...
???ERROR: CVHDXFile::ParseFile: Log header signature is fail - 1635017060
Pulling my hair out on this one...to come so close to finishing and get stuck here is tough. Any indication of what the problem might be?
Thanks in advance for any assisatance.
Re: One vhdx image failing to open
Posted: Tue Dec 21, 2021 8:05 am
by yaroslav (staff)
Hi, where do you see the error?
Re: One vhdx image failing to open
Posted: Tue Mar 15, 2022 2:33 pm
by asavchenko
Hello,
have same Problem, when i convert VM (Windows 2012 R2) from Hyper-v to VMware
full LOG
Code: Select all
3/15 15:14:06.250 26a0 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
3/15 15:14:06.250 26a0 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.1.268
3/15 15:14:06.250 26a0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
3/15 15:14:06.250 26a0 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
3/15 15:14:06.265 26a0 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 10, MinorVersion 0, BuildNumber 17763
3/15 15:14:06.265 26a0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 95ef0000
3/15 15:14:06.265 26a0 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - 95ef0000
3/15 15:14:15.389 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHYPERVConnection
3/15 15:14:24.387 26a0 Facility ???INFO: WrapperHyperV::connect: Host - \\**********\root\virtualization\v2
3/15 15:14:24.496 26a0 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.14393
3/15 15:14:24.496 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eInputVM
3/15 15:14:47.063 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
3/15 15:14:48.422 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eESXConnectionTo
3/15 15:15:28.369 26a0 Facility ???INFO: WrapperESXI::connect: m_url - https://**********/sdk
3/15 15:15:28.447 26a0 Facility ???INFO: WrapperESXI::connect: fullName - ********** **********, key - 52dffebd-1dc0-b9f3-2291-8967147b6be7
3/15 15:15:28.447 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eVMSettingsESX
3/15 15:15:28.494 26a0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
3/15 15:15:28.494 26a0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
3/15 15:15:28.494 26a0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
3/15 15:15:28.494 26a0 Facility ???INFO: VMConverter::ESXIConverter::GetHostListInfo: ESX version: 7.0.3
3/15 15:15:52.958 26a0 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
3/15 15:15:52.958 2a78 Facility ???INFO: CPPConverting::Convert: InConvertType: 8, OutConvertType: 6
3/15 15:15:53.395 2a78 Facility ???INFO: VMConverter::ESXIConverter::CreateVM: createVM is true, vm-4
3/15 15:15:53.395 2a78 Facility ???INFO: CPPConverting::ConverterESX: Create VM vm-4
3/15 15:15:53.583 2a78 Facility ???INFO: CPPConverting::ConvertImage: pathInput: C:\**********\**********\**********\**********.vhdx, pathOutput: [**********] **********/***********.vmdk
3/15 15:15:53.630 2a78 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 1.
3/15 15:15:53.630 2a78 Facility ???INFO: CVHDXFile::getCurrentHeader: Read header 2.
3/15 15:15:53.630 2a78 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 1.
3/15 15:15:53.630 2a78 Facility ???INFO: CVHDXFile::getCurrentHeader: Check correct header 2.
3/15 15:15:53.630 2a78 Facility ???ERROR: CVHDXFile::ParseFile: Log header signature is fail - 1635017060.
3/15 15:15:53.630 2a78 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 2
3/15 15:15:53.645 2a78 Facility ???INFO: WrapperHyperV::connect: Host - \\**********\root\virtualization\v2
3/15 15:15:53.724 2a78 Facility ???INFO: WrapperHyperV::init_version: HyperV version: 10.0.14393
3/15 15:15:53.724 2a78 Facility ???ERROR: CPPConverting::Convert: FAILED
Re: One vhdx image failing to open
Posted: Wed Mar 16, 2022 4:11 am
by yaroslav (staff)
Greetings,
Will disk conversion work?
Re: One vhdx image failing to open
Posted: Wed Mar 16, 2022 7:59 am
by asavchenko
sorry but what you mean?
Re: One vhdx image failing to open
Posted: Wed Mar 16, 2022 8:52 am
by yaroslav (staff)
Could you try converting the disk alone, please?
Re: One vhdx image failing to open
Posted: Wed Mar 16, 2022 2:10 pm
by asavchenko
Yes, thanks, just only the disk is converted!
Re: One vhdx image failing to open
Posted: Wed Mar 16, 2022 4:33 pm
by yaroslav (staff)
Greetings,
Please try converting disks and creating VM using those disks as a workaround.
Re: One vhdx image failing to open
Posted: Fri Mar 18, 2022 3:13 pm
by asavchenko
Hello
again the same error but already when trying to convert only the disk separately
Re: One vhdx image failing to open
Posted: Fri Mar 18, 2022 3:27 pm
by yaroslav (staff)
I have escalated this case to my colleagues in R&D. We will be checking the logs. As a temporary workaround, please try converting the file locally if possible.
Will keep you posted.
Re: One vhdx image failing to open
Posted: Fri Mar 18, 2022 3:44 pm
by asavchenko
sorry was a snapshot after deleting everything is fine
Re: One vhdx image failing to open
Posted: Fri Mar 18, 2022 3:46 pm
by yaroslav (staff)
Great to read this! Please let me know if more assistance is needed.
Re: One vhdx image failing to open
Posted: Sun Jun 11, 2023 7:02 pm
by jjurak
Happen similar to me, while i did not figured what it caused, workaround follows:
In log there are happen one non-fatal error, fatal happen only for vhdx.
(1) nonfatal one
2023-06-11T18:24:26.934ZE [37836:NonCelloThread] crash.cc:84:HandleCrashpadLog [41224
20230611,202426.933:ERROR crashpad_client_win.cc:531] CreateProcess: The parameter is incorrect. (87)
(2) vmdk fatal one leads to app crash and error message cryptic number 2:
6/11 19:26:15.876 3b8 Facility ???ERROR: CVHDXFile::ParseFile: Log header signature is fail - 1635017060.
so for that particular case just convert in hyper-v vhdx->vhd is workaround.
Re: One vhdx image failing to open
Posted: Tue Jun 13, 2023 12:13 pm
by yaroslav (staff)
Greetings thanks for sharing the workaround!
20230611,202426.933:ERROR crashpad_client_win.cc:531] CreateProcess: The parameter is incorrect. (87)