Windows Server 2019 not booting after upgrade

[j3z]

Hi all, good day. After i upgrade to the latest version 7.1-1, the windows server 2019 can't boot up. The VM was created with best practice.
In addition, a huge amount of logs was written to /var/log. I got like 100G in around 5 minutes after the win 2019 boots.

Is there any workaround to have the current win 2019 vm to work like last time.

Here's my pve info

root@pve1:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-5-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-8
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.13.19-5-pve: 5.13.19-10
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.2.0-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

------------------------------------

root@pve1:/var/log# ls -lah /var/log
total 311G
drwxr-xr-x 7 root root 4.0K Mar 2 10:34 .
drwxr-xr-x 11 root root 4.0K Apr 27 2021 ..
-rw-r--r-- 1 root root 1.9K Mar 2 10:34 alternatives.log
drwxr-xr-x 2 root root 4.0K Mar 2 08:21 apt
-rw-r----- 1 root adm 12K Mar 2 10:35 auth.log
-rw-rw---- 1 root utmp 0 Mar 2 08:16 btmp
-rw-r----- 1 root adm 580K Mar 2 11:12 daemon.log
-rw-r----- 1 root adm 27K Mar 2 10:34 debug
-rw-r--r-- 1 root root 902 Mar 2 08:21 dpkg.log
-rw-r----- 1 root adm 104G Mar 2 11:12 kern.log
-rw-rw-r-- 1 root utmp 292 Mar 2 10:35 lastlog
drwxr-xr-x 2 root root 4.0K Mar 2 08:16 lxc
-rw-r----- 1 root adm 4.1K Mar 2 10:34 mail.info
-rw-r----- 1 root adm 4.1K Mar 2 10:34 mail.log
-rw-r----- 1 root adm 1.9K Mar 2 10:34 mail.warn
-rw-r----- 1 root adm 104G Mar 2 11:12 messages
drwx------ 2 root root 4.0K Mar 2 08:16 private
drwxr-xr-x 3 root root 4.0K Mar 2 08:15 pve
-rw-r--r-- 1 root root 1.2K Mar 2 10:34 pve-firewall.log
drwxr-xr-x 2 root root 4.0K Mar 2 08:34 pveproxy
-rw-r----- 1 root adm 104G Mar 2 11:12 syslog
-rw-r----- 1 root adm 4.2K Mar 2 11:12 user.log
-rw-rw-r-- 1 root utmp 21K Mar 2 10:35 wtmp

 

[dcsapak]

can you show us part of the log from where the vm started ?

also what does

he windows server 2019 can't boot up.

mean exactly? does it hang somewhere? do you get an error on vm start?

 

[j3z]

can you show us part of the log from where the vm started ?

also what does
mean exactly? does it hang somewhere? do you get an error on vm start?

it hangs on the Windows logo

pardon me, not really an expert on pve.
where can i locate the logs for the vm?

 

[dcsapak]

where can i locate the logs for the vm?

no i meant from the syslog file (the big one)

you can show the current log with 'journalctl' . with '-f' you can 'follow' the log while trying to start for example, and when appending '> /tmp/filename' you can output it into a file, then with ctrl+c abort it

so you can start

journalctl -f > /tmp/journal.log

try to start the vm, and then press ctrl+c to abort the journalctl command, then upload the /tmp/journal.log file

 

[j3z]

no i meant from the syslog file (the big one)

you can show the current log with 'journalctl' . with '-f' you can 'follow' the log while trying to start for example, and when appending '> /tmp/filename' you can output it into a file, then with ctrl+c abort it

so you can start

journalctl -f > /tmp/journal.log

try to start the vm, and then press ctrl+c to abort the journalctl command, then upload the /tmp/journal.log file

thanks for the information.
I have uploaded the log to my google drive. you can download it from:
https://drive.google.com/file/d/1XYZbUOuJj9U85lIpSqao5gRTRfFG-0kW/view?usp=sharing

 

[j3z]

issue resolved after i upgraded to a newer version. Here's the info after upgrade/

proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-13
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: not correctly installed
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-6
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1