No worries, I would have liked to figure out why this one particular volume/drive won't convert, but if y'all don't care I suppose it doesn't matter since I have a work around.

and afa the progress bar.. it goes from 0-100% then goes back to 0 again.

ran disk2vhd on the drive and was able to mount it successfully in Hyper-V

check disk run from within windows returns a lot fast than I would have expected but returns no errors on the drive/volume. Drive contains a couple or oracle control files and redo logs and oracle archive log files that max out at 500 MB (718 of those). Will try to run disk2vhd. had some earlier dow...

So in summary I have 5.5 ESXi virtual machine with 4 drives. 3 (including drive with system volume) convert all different ways and attach to Hyper-V machine without issue. The forth drive gets the same error when converting: 1. Using P2V from the ESXi virtual machine 2. Using V2V on Hyper-V host cap...

Running P2V (physical disk to Hyper-V machine) from inside the source VM fails with the same error as well... There is nothing abnormal about this disk... hmmm... other 3 converted drives look great included booting system drive The log file name: 'logs\V2V_Log-20241120-205657.log' (PID 7040) 11/20 ...

no snapshots on any of the disks.
I can try P2V on the probably disk from inside the source guest on the ESXi server tonight probably.

I have 3 out 4 of the local disks of the ESXi Vm I am testing conversion to Hyper-V with. The fourth fails with the log belove. Please note, that even my successfull conversions have the line: 11/20 11:28:33.462 ed0 Facility ???ERROR: VMwareFile::InternalParseFile: Invalid format. Descriptor not fou...

Think i found the issue, just posting for reference. Each of my data drives had two VMDK files one named "filename.vmdk" and one named "filename_flat.vmdk". First go round I selected the one without the "_flat" (against my better judgement), best I can tell that is just...

will do, was trying to just have a little more control over the process. eliminate potential network issues etc.

where the logs from a sucessfull convert vs a failed convert starts here:

11/15 11:48:42.054 1878 Facility ???ERROR: CVHDXFile::ParseFile: Log header signature is fail - 1635017060.

I am moving large (300 GB is large for me) disk files (vmdk) from an ESXi host to a new Hyper-V 2019 core server using WinSCP. Once I have them downloaded I am using V2V to convert the virtual disk files to vdhx (onto a different physical hard drive from the source vmdk that was copied from the ESXi...

That worked. You are my Hero!

Thanks!

First time using V2V. Conversion status said success, same with the log. Converted Windows 10 VM from ESXI 5.5 to hyper-v Core 2019 but it fails to start immediately with error: An error occurred while attempting to start the virtual machine(s). <machine name> failed to change state. See below for e...

I see the progress bar it just took a very long time to actually make any progress past 4%, eventually I saw the converted virtual disk start increasing in size, which I suppose is good enough along with the status bar.

Thanks.