question

DarrenG-0100 avatar image
0 Votes"
DarrenG-0100 asked TanmayGore-7853 commented

VM won't boot after ARM migration abort

I've been looking into doing the migration from Classic VMs to ARM, and I prepared the migration in order to check out the resulting resources. I aborted so that I could do some final backups, but after aborting the VM will not boot. The portal just says "failed to start Virtual Machine." If I try to re-prepare, it generates an error stating: the Migration of Deployment for the server is in the process of being aborted and cannot be changed until it completes successfully." It's been about 3 hours since I aborted, and the prepared resources appear to be removed from the portal. Any ideas how to get the VM running again?

azure-virtual-machinesazure-virtual-machines-migration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DarrenG-0100 avatar image
1 Vote"
DarrenG-0100 answered TanmayGore-7853 commented

So initially it was discovered by the tech team that a subnet was blocking the abort from proceeding. Manually deleting the subnet in the Portal did not immediately resolve the issue. But some hours later, after initiating another "Prepare" process as part of the testing to generate the error message again, I noticed an Abort button appeared even after the Prepare process failed.

Clicking the Abort button initiated a new Abort process that completed in a few seconds, and after this the VM was able to boot once again. So if anyone is having similar trouble, I would advise manually removing any of the resources that appeared during the Prepare process, and then doing another Abort even if a new Prepare attempt fails.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@DarrenG-0100 Thanks for sharing the resolution here. It would help if you could mark your answer as Accepted answer, so that others who are facing the same issue can easily discover it. Thanks.

0 Votes 0 ·

@DarrenG-0100, I'm glad you able to get back to original state. This subnet issue seems unusual. Let me follow up with the support team to get an understanding.
Prepare, Abort & Commit operations are built to be idempotent, so retrying usually works.

0 Votes 0 ·
learn2skills avatar image
0 Votes"
learn2skills answered

Hi @DarrenG-0100

If you have .vhd disks then you can proceed with building new VM.
https://vikaskumawat.dev/migrate-azure-classic-vm-to-arm-using-azure-portal/


If the Answer is helpful, please click Accept Answer and up-vote, this can be beneficial to other community members.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DarrenG-0100 avatar image
0 Votes"
DarrenG-0100 answered

I can see the vhd disks in the Azure Storage Explorer app, but I can't do the migration to ARM using the instructions in the link you posted because the Prepare step fails now...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TanmayGore-7853 avatar image
0 Votes"
TanmayGore-7853 answered TanmayGore-7853 commented

@DarrenG-0100, can you please retry calling Abort using PS/CLI?
If that didn't fix the issue, contact support to help fix this abort operation being stuck. If you only have a basic support plan use this free support link to create a technical support ticket.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Oh shoot I wish I had that link earlier today. I ended up just upgrading to Standard support in order to make the ticket. The support guys are still working on it; I'll post back with the end result. It appears to be hung up on aborting, and probably isn't something that could be fixed without their intervention.

1 Vote 1 ·

I'm sorry to hear that. We have this link exposed via our documentation.
Abort bring stuck is one of the rarest scenario but we do see it at times.

0 Votes 0 ·