Unable to create ESXi VMDK from RHEL7 disk

aknash-cae · Tue May 05, 2020 8:55 pm

Hello, and thank you for this very useful tool! I have used it successfully to create Windows VMs using backup disks.

However, I haven't had any luck creating ESXi VMDK files from RHEL7 system backup disks. I always get this error (last two lines from the attached log file):

Code: Select all

5/4 20:07:35.534 1bc4 Facility ???ERROR: CPPConverting::ConvertImage: Read 3
5/4 20:09:18.737 1bc4 Facility ???ERROR: CPPConverting::Convert: FAILED

I also tried converting to an IMG and a VHD file without success.

Any suggestions as to how I can create this VMDK file?

Thanks

LATER: Well, I tried to attach the log, but the forum software won't accept my upload.

Wed May 06, 2020 7:48 am

Greetings aknash-cae,

Are VMDK files in use, I mean is anything else using them at this point (e.g, backups, powered on VMs?).
You can send StarWind V2V converter log alone (C:\Program Files\StarWind Software\StarWind V2V Image Converter\logs) using Google Drive or Dropbox.

aknash-cae · Thu May 07, 2020 1:04 pm

Thanks for your response. No, the disk wasn't in use when I attempted the conversion. It's a 512GB SSD containing an installation of Red Hat Enterprise Linux v7 that I simply connected to a spare SATA port on my Windows 7 workstation.

Here is the complete log:

Code: Select all

The log file name: 'logs\V2V_Log-20200504-200640.log' (PID 6480)
5/4 20:06:40.094 1808 Facility ???INFO: CV2V_ConverterApp::InitInstance: SetDllDirectory: C:\Program Files\StarWind Software\StarWind V2V Converter\lib
5/4 20:06:40.095 1808 Facility ???INFO: CV2V_ConverterApp::InitInstance: File Version: 9.0.0.202
5/4 20:06:40.100 1808 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_ENGLISH
5/4 20:06:40.100 1808 Facility ???INFO: CV2V_ConverterApp::InitInstance: Load language IDR_XML_RUSSIAN
5/4 20:06:40.100 1808 Facility ???INFO: CV2V_ConverterApp::InitInstance: Set current language English
5/4 20:06:40.102 1808 Facility ???INFO: CPS_V2V_Converter::CPS_V2V_Converter: Version MajorVersion 6, MinorVersion 1, BuildNumber 7601
5/4 20:06:40.106 1808 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - f3ea0000
5/4 20:06:40.107 1808 Facility ???INFO: WrapperHyperV::WrapperHyperV: LoadLibrary C:\Windows\system32\wbem\wmiutils.dll - f3ea0000
5/4 20:06:45.449 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eTypeP2V
5/4 20:06:48.729 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eHDDSelect
5/4 20:06:48.741 1808 Facility ???WARNING: PhysicalInfo::PhysicalDisksInfo::InitDisks: GetDiskFreeSpace \\?\Volume{b05b7464-8d46-11ea-ab37-806e6f6e6963}\ fail - 87. The parameter is incorrect.
5/4 20:06:57.457 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eLocationTo
5/4 20:06:59.992 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eFormat
5/4 20:07:01.576 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOptionsVMware
5/4 20:07:04.281 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOptionsESXI
5/4 20:07:05.801 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eOutputFile
5/4 20:07:31.673 1808 Facility ???INFO: CPPOutputFile::onNext: Out path: G:\CPT\cpt-host.vmdk, Out format 14
5/4 20:07:31.673 1808 Facility ???INFO: ICPPage::OnWizardNext: SetActivePage - eConverting
5/4 20:07:31.676 1bc4 Facility ???INFO: CPPConverting::Convert: InConvertType: 2, OutConvertType: 4
5/4 20:07:31.676 1bc4 Facility ???INFO: CPPConverting::ConvertImage: pathInput: 2, pathOutput: G:\CPT\cpt-host.vmdk
5/4 20:07:31.676 1bc4 Facility ???INFO: P2V::CreateInputImage: path 2
5/4 20:07:31.676 1bc4 Facility ???INFO: P2V::CreateInputImage: Size 2 - 512110190592, BytesPerSector - 512
5/4 20:07:35.019 1bc4 Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 0
5/4 20:07:35.019 1bc4 Facility ???WARNING: LocalDisk::LocalDisk: VirtDisk not supported
5/4 20:07:35.307 1bc4 Facility ???INFO: VMwareFile::NewFile: sFileName - G:\CPT\cpt-host.vmdk
5/4 20:07:35.307 1bc4 Facility ???INFO: VMwareFile::NewFile: SectorType - 1000215216
5/4 20:07:35.307 1bc4 Facility ???INFO: VMwareFile::NewFile: EVMDKCreateType - 3
5/4 20:07:35.307 1bc4 Facility ???INFO: VMwareFile::NewFile: EVMDKAdapterType - 0
5/4 20:07:35.534 1bc4 Facility ???INFO: CPPConverting::ConvertImage: CreateOutputImage: 0
5/4 20:07:35.534 1bc4 Facility ???ERROR: CPPConverting::ConvertImage: Read 3
5/4 20:09:18.737 1bc4 Facility ???ERROR: CPPConverting::Convert: FAILED

Fri May 08, 2020 10:44 am

Greetings,

We did not test StarWind V2V Converter to work with Windows 7.
Learn more about P2V conversion at https://www.starwindsoftware.com/v2v-he ... nario.html
Please make sure to follow this guide https://www.starwindsoftware.com/v2v-he ... oVMDK.html
Please note that 64 bit OS version is needed. Learn more about V2V Converter specification at https://www.starwindsoftware.com/v2v-he ... tions.html

Fri May 08, 2020 11:46 am

Hi,

I had discussion with R&D team recently.
1. What is RHEL7 file system (i.e., XFS or Ext3)?
2. The thing is that Windows cannot work with XFS (even Windows 10) natively. Sure, you can do some customization to make it work.
3. You are working with the disk not with the file system in this particular scenario. Based on the error you get

Code: Select all

???WARNING: PhysicalInfo::PhysicalDisksInfo::InitDisks: GetDiskFreeSpace \\?\Volume{b05b7464-8d46-11ea-ab37-806e6f6e6963}\ fail - 87

V2V cannot get the volume of disk for some reason.

aknash-cae · Tue May 12, 2020 5:42 am

yaroslav (staff) wrote:Greetings,

We did not test StarWind V2V Converter to work with Windows 7.
Learn more about P2V conversion at https://www.starwindsoftware.com/v2v-he ... nario.html
Please make sure to follow this guide https://www.starwindsoftware.com/v2v-he ... oVMDK.html
Please note that 64 bit OS version is needed. Learn more about V2V Converter specification at https://www.starwindsoftware.com/v2v-he ... tions.html

The P2V conversion fails when I run it on Windows 10 also, so I don't think the problem is necessarily the Windows version.

aknash-cae · Tue May 12, 2020 5:43 am

yaroslav (staff) wrote:Hi,

I had discussion with R&D team recently.
1. What is RHEL7 file system (i.e., XFS or Ext3)?
2. The thing is that Windows cannot work with XFS (even Windows 10) natively. Sure, you can do some customization to make it work.
3. You are working with the disk not with the file system in this particular scenario. Based on the error you get
Code: Select all
???WARNING: PhysicalInfo::PhysicalDisksInfo::InitDisks: GetDiskFreeSpace \\?\Volume{b05b7464-8d46-11ea-ab37-806e6f6e6963}\ fail - 87
V2V cannot get the volume of disk for some reason.

The file system is XFS on this disk, so it sounds like your P2V tool won't be able to convert it without customization. Where will I find information about tweaking Windows to handle the XFS file system?
Thanks

Tue May 12, 2020 6:07 am

aknash-cae,

Yes, some customization is needed.
Please, take a look at these resources.
https://medium.com/@matteocontrini/how- ... 2d74f4644f
https://www.reddit.com/r/linuxquestions ... n_windows/.

Tue May 12, 2020 2:29 pm

The P2V conversion fails when I run it on Windows 10 also

So you are trying to convert a physical disk formatted as NTFS into a virtual one and it fails? May I see the logs, please?