This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 99%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Hi,
After a test failover the VM (WS 2012 R2 core) has problems booting. It starts chkdsk on boot for C:, then goes into "preparing devices" and it does not always boot successfully at all.
The source VM seems to be OK - no chkdsk problems, no problems rebooting, no eventlog errors etc.
Other VMs have no such problems.
I have tried reprotecting (establishing replication from scratch), to no avail.
Kind regards,
Pawel
@Paweł Mazurkiewicz Sorry for the inconvenience this has caused!
Since we are doing a copy of the original VM, usually the original VM has some issue that is been replicated to the target (A2A).
But if this is physical to Azure, then there are some known issues like AWS or XEN VMs with the drivers that must be removed in Azure.
To investigate this further, I suggest you contact Azure technical support team by raising a support ticket. The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
i can add some potential analysis methods
This VM mostly boots OK, after a delay caused by chkdsk. Anyway, checked netw. config and it looks OK.
No problems with BCD or chkdsk
None of the above helped.
This VM sometimes boots OK after failover, sometimes not.
interesting case have you tried to execute defrag tool and maybe you can try to disable services that can cause this problem