P2V - Source system crashes at 14%

[kylemcisaac]

Good day,

I am completing a P2V migration, select the necessary drives and configurations, but when I get to 14%, the system blue screens and reboots. The migration is going to a new Hyper-V server over the network.

The system blue screen from Event Viewer shows: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc80aac400028, 0x00000000fe200000, 0x000000000001111a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4032c654-0919-48f6-a0fb-e6eef950322c.

I thought it was a hard disk issue, completed check disks with no errors reported; ensured SMART looked OK which it did. I also decided to complete a cloud backup using our backup provider (NinjaRMM), and it was able to get to 46% already without errors.

Any ideas?

Thanks,
Kyle

[yaroslav (staff)]

I think something on the VSS side is causing that crash rather than V2V. Can you please tell me more about the conversion scenario? What is the source, and what does the dump complain about?
Try Disk2vhd software to see if it has any success.

[kylemcisaac]

I think something on the VSS side is causing that crash rather than V2V. Can you please tell me more about the conversion scenario? What is the source, and what does the dump complain about?
Try Disk2vhd software to see if it has any success.

The existing server is essentially a desktop PC running Server 2016. They had a Windows-based RAID configured, which has since been broken to be just a single drive, and an additional drive containing backups. I tried running with the additional drive with no success, so I set the backup drive and additional drive from the RAID (which is empty) offline, tried again and hit14% and failed.

Their system is running Trend Micro endpoint, so not sure if that's causing any issues or not. The main hard disk has three volumes, a 500MB System Reserved partition, their OS partition (214.35GB, boot, page, and crash dump), and their Data partition (716.,67GB). The drive is a SATA SSD, no errors in SMART. The backup drive does show errors on SMART, but isn't being targeted in V2V.

I have attempted Disk2VHD as well, using the options "Prepare for use in Virtual PC" and "Use Vhdx", sending the file to the new Hyper-V server's share. It copied over fine with no errors. Going to attempt with Volume Shadow Copy as well now.

[yaroslav (staff)]

Could you please share the minidump, if any?

[kylemcisaac]

Could you please share the minidump, if any?

Unfortunately, couldn't find a Minidump. When I was running Disk2VHD this time, while using Volume Shadow Copy, once it hit the second partition, it locked up the server completely without a bluescreen.

Is there a way for me to run P2V without Volume Shadow Copy?

[yaroslav (staff)]

P2V is shadow-copy-based. I think you need to stick with Disk2VHD.

[kylemcisaac]

P2V is shadow-copy-based. I think you need to stick with Disk2VHD.

I've had mixed results with Disk2VHD, unfortunately. Could it be potentially storage space available causing the shadow-copy to fail?

[yaroslav (staff)]

I am not sure (this is out of scope).
BSOD is happening because of driver conflicts (i.e., kernel is not happy).
Do you have any filter drivers like backup software, BitLocker, or AV?