Unable to boot Windows server 2019 VM

[roller]

Hello,

I have a Windows 2010 host machine on which I run a Windows server 2019 VM using VirtualBox. The host machine and the VM got switched off suddenly due to a power cut at my place.

The host machine came back up alright when the power was restored. However, I'm unable to boot my VM again. I've only tried once fearing further corruption but it has not booted for the last 45 mins. It just shows a black screen with a windows sign and a loading circle. I've attached VBox log file but let me know if you need anything else.

Could you please advise if it is somehow possible to try another reboot or somehow restore this VM. I really have an important project stored on this VM and any corruption would be a huge loss for at least 2 months of effort.

Any pointers would be appreciated.

VBox.log

VBox.log

(79.65 KiB) Downloaded 11 times

Regards, Gaurav

[mpack]

00:00:03.698257 VirtualBox VM 6.0.18 r136238 win.amd64 (Feb 20 2020 17:48:03) release log
...
00:00:04.010416 Guest OS type: 'WindowsNT_64'

No way this ever worked for a Windows 2019 guest.

You also seem to have assigned 7 CPU cores out of the 6 available. This could certainly be interfering with the smooth running of the VM: the host can't run on fumes, and that is exactly where VirtualBox itself runs (the CPU allocation is for guest apps). Assigning more cores than a VM needs makes it slow down, not speed up. How many it "needs" depends on what you're running in there. None of my VMs get more than 2 cores.

00:03:42.503483 TM: Giving up catch-up attempt at a 60 000 353 749 ns lag; new total: 60 000 353 749 ns
00:06:43.080157 TM: Giving up catch-up attempt at a 60 000 020 595 ns lag; new total: 120 000 374 344 ns
00:09:27.676629 TM: Giving up catch-up attempt at a 60 000 294 302 ns lag; new total: 180 000 668 646 ns
00:12:29.092713 TM: Giving up catch-up attempt at a 60 000 066 491 ns lag; new total: 240 000 735 137 ns
... etc

Also 22.3 GB for RAM but only 40MB for graphics RAM?

I hope this isn't one of those where you only thought to back up the VDI, i.e. the disk image, and ignored the other important (though smaller) files that make a working VM.