Windows Server Boot Loop after scheduled snapshot after upgrade 6.x to 7.3-4

WLP

Member
Oct 28, 2021
4
0
6
49
I have a 3-node cluster recently upgraded from 6.4 to 7.3-4

After the upgrade, scheduled weekly backups continue to go off without a hitch except for our 2 Domain Controllers running on Windows Server 2019 standard. Both of these machines go into boot loop.

DC1 requires a manual reboot to restore service. This requires 4 steps:
1. # qm unlock 100
2. # ha-manager set vm:100 --state disabled
3. manually reboot the VM with GUI
4. #ha-manager set vm:100 --state enabled

DC2: After snapshot is created is stuck in bootloop with additional error: 'boot failed: not a bootable disk'
DC2 Requires 4 steps to restore service
1. # qm unlock 200
2. # ha-manager set vm:200 --state disabled
3. restore from the most recent snap shot made
4. #ha-manager set vm:200 --state enabled

This has happened to the two Windows servers after every weekly-snapshot since upgrading to ProxMox ver 7.3-4 not sure how to fix this. I have read similar problems were solved by installing intel-microcode but thought I'd reach out before trying anything experimental.


Here is a copy of my weekly backup config
1nVjUlCAhtF7LVLPRCyANRUjmk3yvLMK3Gz43-QsPXGhlSdD-DrcF_jL_RraxyRABvA3InF8Ds0_qqO0vcjuXguScmaei9-yo_dEVEU-KBOLWlqpqeR8BzBZFKrWJztcLbE1pAJ0aukOIqsmI_rSw4w
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!