StarWind Software

Thank you for your patience.
The issue has been confirmed by my colleagues.
The workaround can be:
1. Using an older version (let me know if you want to have the link to it).
2. Do the following
Log into the VM
1. $ vi /etc/default/grub
1.1. Change the line
GRUB_DEFAULT=1
Save and exit.

2. $ grub2-mkconfig -o /boot/grub2/grub.cfg
3. $ shutdown -h now

Convert the VM.

yaroslav (staff) wrote: ↑

Tue Mar 19, 2024 4:58 pm

Thank you for your patience.
The issue has been confirmed by my colleagues.
The workaround can be:
1. Using an older version (let me know if you want to have the link to it).
2. Do the following
Log into the VM
1. $ vi /etc/default/grub
1.1. Change the line
GRUB_DEFAULT=1
Save and exit.

2. $ grub2-mkconfig -o /boot/grub2/grub.cfg
3. $ shutdown -h now

Convert the VM.

Thank you Yaroslav. I have the old installer for StarWind V2V version 9.0.1.268. Is there a newer version that does not have the problem? If so I would appreciate a download link for it. Thanks in advance for your help!

The issue should be fixed in the next build.
So, for now, stick with the older build. Thanks for your patience!!

yaroslav (staff) wrote: ↑

Wed Mar 20, 2024 6:24 pm

The issue should be fixed in the next build.
So, for now, stick with the older build. Thanks for your patience!!

Sounds good. Thanks for your help!

You are always welcome

Hi Yaroslav, please could you provide a link to the older working version? I have the same issue too.
Thanks in advanced!

yaroslav (staff) wrote: ↑

Tue Mar 19, 2024 4:58 pm

Thank you for your patience.
The issue has been confirmed by my colleagues.
The workaround can be:
1. Using an older version (let me know if you want to have the link to it).
2. Do the following
Log into the VM
1. $ vi /etc/default/grub
1.1. Change the line
GRUB_DEFAULT=1
Save and exit.

2. $ grub2-mkconfig -o /boot/grub2/grub.cfg
3. $ shutdown -h now

Convert the VM.

Welcome to StarWind Forum.
Let us try fixing it by removing the Integration tools as they might be causing some problems when running the VM at the destination.

Cheers,

Hi Yaroslav,
I have been through all the testing, it is when the destination format is vhdx preallocated (due to source being thick provisioned), which is the issue you confirmed should be resolved in a new build / isn't an issue in previous versions.

Please could you provide the link to download the older version (9.0.1.268) without the bug?
Thanks
Dan

yaroslav (staff) wrote: ↑

Tue Mar 26, 2024 1:15 pm

Welcome to StarWind Forum.
Let us try fixing it by removing the Integration tools as they might be causing some problems when running the VM at the destination.

Cheers,

Please contact us at support@starwind.com so I can send you the link and help you if needed.

dear all
I was testing the product starwind latest version

I was migrating a vmware esxi 6 version – vm with windows 2012r2 to a new windows hypervisor server with win2022 server – the process of migration completes without any warnings
But when I am starting up the conerted win2012r2 machine (under hypervisor) I get the error

“New Virtual Machine' Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error 'The file or directory is corrupted and unreadable. ' (0x80070570). (Virtual machine ID C38B17FC-14F0-4015-B016-969B44E69925)”

Have you any idea?

Hi,

Did you try the older version already?
Please also try different provisioning settings.

Hi,

I have the same issue as described above.

- When migrating from a ESXi 6.7 (V to V connected to vCenter 6.7) to Hyper V Windows server 2019 Hyper-V host.
- When I migrate a VM with Thick provisioning Lazy zeroed disks the disk are corrupt after migrating.
- When migrating the disk(s) to a local file (on the Hyper-V host) as a VHDX Pre-Allocated disk it is corrupt after migrating.
- When migrating the disk(s) to a local file (on the Hyper-V host) as a VHDX Growable disk everything is fine.
- When migrating a vm with thin provisioning disks everything is also fine.

I also can open the corrupt vdisks from the Disk Managment (Attache VHD) only when I select read only. Otherwise it also says that the disk is corrupt.

Thanks for looking in to it!

Lionel Der Boven

Please download the old v2v converter here https://drive.google.com/file/d/1hDP4gl ... sp=sharing

Hi,

Thanks. I wil try the older version on my next VM. I keep you posted.

Keep me posted.