windows server 2022 VM black screen after reboot. No login screen but I can ping and access file shares

[Ben Sommer]

it turns out the c:\windows\registration folder was missing. I recovered that folder and it booted but now a new question rises. How come when I shutted down windows normally and then rebooted proxmox hypervisor it ended up loosing that folder? Could it be that something was in the ZFS cache that was not committed to the disks and when I rebooted the hypervisor it was lost? If that is the case does proxmox ensures that all data is committed before it reboots?

Hi
I had the same problem witch my W2019 server. My vm was on a zfs volume too. I recovered the files too from an old backup. Here the way to mount the raw partition in pve, then you can copy the data with scp to the proxmox and extract them at the right place.
In my case it was the partition nr 4, so you had to use /dev/loop22p4

losetup /dev/loop22 disk-drive-ide0.raw
partx -v --add /dev/loop22
mount /dev/loop22p1 /mnt/123

Thx genesispro, you made ma day

Greetings from Berlin

Ben

 

[VinceIT]

it turns out the c:\windows\registration folder was missing. I recovered that folder and it booted but now a new question rises. How come when I shutted down windows normally and then rebooted proxmox hypervisor it ended up loosing that folder? Could it be that something was in the ZFS cache that was not committed to the disks and when I rebooted the hypervisor it was lost? If that is the case does proxmox ensures that all data is committed before it reboots?

Thanks a lot @genesispro you saved me from full backup restoration !

In my case, the problem came after a failed backup to a remote pbs server. The weird thing is that in the backup log, I see percentage from 0% to 100% and the "Backup finished with errors".

Regards,
Vincent

 

[_gabriel]

Original VM data can be corrupted if PBS is too slow (like backup over WAN or too slow Disks).

 

[VinceIT]

Thanks for this information Indeed my pve storage pool was very slow due to zfs compression and deduplication activated for the whole pool (pbs is hosted as a vm on pve).
I recreated the pve pool without these options, and I activated them for the pbs storage disk only. Backups seem to go well now.