VMs suddenly stopped and I have to start them again.

H

hassoon

Active Member
Jan 27, 2020
72
1
28
65
Im having strange problem after my old server stopped working completely on IBM x3650 M4 and I had to replace the whole server with a working one and insert the old drives into the new server's SAS bay.
everything seemed to work normally on the new server. but after two weeks of smooth operations the vms started to halt by itself.
Ive checked the syslog and I cant find anything strange apart of:

kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Nov 07 08:03:53 awpve kernel: device tap777i0 entered promiscuous mode
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered blocking state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered blocking state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered forwarding state
Nov 07 08:03:54 awpve kernel: device tap777i1 entered promiscuous mode
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered blocking state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered blocking state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered forwarding state
I have changed network driver from virtio to intel, still the same thing. Ive reduced ram and cpu use and still the same outcome.
Im on PVE 8.0.3
and ran apt upadte && apt upgrade
and still the same issue.
can this be IBM FW issue?
VM stops only the server keeps running without showing any error
 
one note I can see before sudden halt is the below


Nov 07 12:30:02 awpve pveproxy[3342]: worker 714147 finished
Nov 07 12:30:02 awpve pveproxy[3342]: starting 1 worker(s)
Nov 07 12:30:02 awpve pveproxy[3342]: worker 811932 started
Nov 07 12:30:08 awpve pvedaemon[607170]: worker exit
Nov 07 12:30:08 awpve pvedaemon[3332]: worker 607170 finished
Nov 07 12:30:08 awpve pvedaemon[3332]: starting 1 worker(s)
Nov 07 12:30:08 awpve pvedaemon[3332]: worker 812175 started
Nov 07 12:30:10 awpve pvedaemon[612950]: <root@pam> successful auth for user 'xxxxxx@pam'
Nov 07 12:30:36 awpve kernel: zd32: p1 p2
Nov 07 12:30:36 awpve kernel: zd0: p1
Nov 07 12:30:36 awpve pvedaemon[812175]: VM 777 qmp command failed - VM 777 qmp command 'guest-ping' failed - got timeout
Nov 07 12:30:36 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 12:30:37 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 12:30:37 awpve qmeventd[2768]: read: Connection reset by peer
Nov 07 12:30:37 awpve pvedaemon[812175]: VM 777 qmp command failed - VM 777 not running
Nov 07 12:30:37 awpve pvestatd[3306]: VM 777 qmp command failed - VM 777 not running
Nov 07 12:30:37 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 07 12:30:37 awpve systemd[1]: 777.scope: Consumed 19min 39.571s CPU time.
Nov 07 12:30:38 awpve qmeventd[817748]: Starting cleanup for 777
Nov 07 12:30:38 awpve qmeventd[817748]: Finished cleanup for 777
 
could it be that the technician put the SAS drives in another order so it would need extra zfs commands?
just did scrub and cant find anything showing error.
do I need to do re silver?
 
Hi,
hassoon said:
Im having strange problem after my old server stopped working completely on IBM x3650 M4 and I had to replace the whole server with a working one and insert the old drives into the new server's SAS bay.
everything seemed to work normally on the new server. but after two weeks of smooth operations the vms started to halt by itself.
Ive checked the syslog and I cant find anything strange apart of:

kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Click to expand...
I'd try turning SMT or EPT off, following the kernel documentation.
hassoon said:
Nov 07 08:03:53 awpve kernel: device tap777i0 entered promiscuous mode
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered blocking state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered blocking state
Nov 07 08:03:53 awpve kernel: vmbr0: port 2(tap777i0) entered forwarding state
Nov 07 08:03:54 awpve kernel: device tap777i1 entered promiscuous mode
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered blocking state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered blocking state
Nov 07 08:03:54 awpve kernel: vmbr1: port 2(tap777i1) entered forwarding state
I have changed network driver from virtio to intel, still the same thing. Ive reduced ram and cpu use and still the same outcome.
Im on PVE 8.0.3
and ran apt upadte && apt upgrade
Click to expand...
Always use full-upgrade or dist-upgrade on Proxmox VE systems (see: https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/)
hassoon said:
and still the same issue.
Click to expand...
What kernel are you running now?
hassoon said:
can this be IBM FW issue?
VM stops only the server keeps running without showing any error
Click to expand...
Make sure you have latest CPU microcode installed: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_firmware_cpu
hassoon said:
one note I can see before sudden halt is the below


Nov 07 12:30:02 awpve pveproxy[3342]: worker 714147 finished
Nov 07 12:30:02 awpve pveproxy[3342]: starting 1 worker(s)
Nov 07 12:30:02 awpve pveproxy[3342]: worker 811932 started
Nov 07 12:30:08 awpve pvedaemon[607170]: worker exit
Nov 07 12:30:08 awpve pvedaemon[3332]: worker 607170 finished
Nov 07 12:30:08 awpve pvedaemon[3332]: starting 1 worker(s)
Nov 07 12:30:08 awpve pvedaemon[3332]: worker 812175 started
Nov 07 12:30:10 awpve pvedaemon[612950]: <root@pam> successful auth for user 'xxxxxx@pam'
Nov 07 12:30:36 awpve kernel: zd32: p1 p2
Nov 07 12:30:36 awpve kernel: zd0: p1
Nov 07 12:30:36 awpve pvedaemon[812175]: VM 777 qmp command failed - VM 777 qmp command 'guest-ping' failed - got timeout
Nov 07 12:30:36 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 12:30:37 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 12:30:37 awpve qmeventd[2768]: read: Connection reset by peer
Nov 07 12:30:37 awpve pvedaemon[812175]: VM 777 qmp command failed - VM 777 not running
Nov 07 12:30:37 awpve pvestatd[3306]: VM 777 qmp command failed - VM 777 not running
Nov 07 12:30:37 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 07 12:30:37 awpve systemd[1]: 777.scope: Consumed 19min 39.571s CPU time.
Nov 07 12:30:38 awpve qmeventd[817748]: Starting cleanup for 777
Nov 07 12:30:38 awpve qmeventd[817748]: Finished cleanup for 777
Click to expand...
that is strange, there is no crash or shutdown shown, but the process seems to be gone (thus the systemd scope is deactivated). Can you install apt install systemd-coredump? That should catch crashes (at least in userspace).
 
fiona said:
Hi,

I'd try turning SMT or EPT off, following the kernel documentation.

Always use full-upgrade or dist-upgrade on Proxmox VE systems (see: https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/)

What kernel are you running now?

Make sure you have latest CPU microcode installed: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_firmware_cpu

that is strange, there is no crash or shutdown shown, but the process seems to be gone (thus the systemd scope is deactivated). Can you install apt install systemd-coredump? That should catch crashes (at least in userspace).
Click to expand...
Thanks

just got another halt

here is what I saw

Nov 07 13:28:30 awpve pvedaemon[3332]: worker 718783 finished
Nov 07 13:28:30 awpve pvedaemon[3332]: starting 1 worker(s)
Nov 07 13:28:30 awpve pvedaemon[3332]: worker 3154004 started
Nov 07 13:30:44 awpve pvedaemon[3071133]: <root@pam> successful auth for user 'root@pam'
Nov 07 13:31:18 awpve pvedaemon[2900375]: VM 777 qmp command failed - VM 777 qmp command 'guest-ping' failed - got timeout
Nov 07 13:31:18 awpve kernel: zd32: p1 p2
Nov 07 13:31:18 awpve kernel: zd0: p1
Nov 07 13:31:19 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 13:31:19 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 13:31:19 awpve qmeventd[2768]: read: Connection reset by peer
Nov 07 13:31:19 awpve pvedaemon[3154004]: VM 777 qmp command failed - VM 777 not running
Nov 07 13:31:19 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 07 13:31:19 awpve systemd[1]: 777.scope: Consumed 37min 15.765s CPU time.
Nov 07 13:31:20 awpve qmeventd[3163562]: Starting cleanup for 777
Nov 07 13:31:20 awpve qmeventd[3163562]: Finished cleanup for 777


kernel is:
Linux awpve 6.2.16-3-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) x86_64 GNU/Linux
 
Last edited:
hassoon said:
Thanks

just got another halt

here is what I saw

Nov 07 13:28:30 awpve pvedaemon[3332]: worker 718783 finished
Nov 07 13:28:30 awpve pvedaemon[3332]: starting 1 worker(s)
Nov 07 13:28:30 awpve pvedaemon[3332]: worker 3154004 started
Nov 07 13:30:44 awpve pvedaemon[3071133]: <root@pam> successful auth for user 'root@pam'
Nov 07 13:31:18 awpve pvedaemon[2900375]: VM 777 qmp command failed - VM 777 qmp command 'guest-ping' failed - got timeout
Nov 07 13:31:18 awpve kernel: zd32: p1 p2
Nov 07 13:31:18 awpve kernel: zd0: p1
Nov 07 13:31:19 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 13:31:19 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 13:31:19 awpve qmeventd[2768]: read: Connection reset by peer
Nov 07 13:31:19 awpve pvedaemon[3154004]: VM 777 qmp command failed - VM 777 not running
Nov 07 13:31:19 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 07 13:31:19 awpve systemd[1]: 777.scope: Consumed 37min 15.765s CPU time.
Nov 07 13:31:20 awpve qmeventd[3163562]: Starting cleanup for 777
Nov 07 13:31:20 awpve qmeventd[3163562]: Finished cleanup for 777
Click to expand...
Did you already install systemd-coredump before this crash? If yes, what does coredumpctl -1 say?

hassoon said:
kernel is:
Linux awpve 6.2.16-3-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) x86_64 GNU/Linux
Click to expand...
I'd try upgrading to the current 6.8 kernel.
 
fiona said:
Did you already install systemd-coredump before this crash? If yes, what does coredumpctl -1 say?


I'd try upgrading to the current 6.8 kernel.
Click to expand...
Thx
Ive just did the below:

root@awpve:~# apt install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
iucode-tool
The following NEW packages will be installed:
intel-microcode iucode-tool
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,052 kB of archives.
After this operation, 14.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.tr.debian.org/debian bookworm/main amd64 iucode-tool amd64 2.3.1-3 [56.1 kB]
Get:2 http://ftp.tr.debian.org/debian bookworm/non-free-firmware amd64 intel-microcode amd64 3.20240813.1~deb12u1 [6,996 kB]
Fetched 7,052 kB in 9s (806 kB/s)
Selecting previously unselected package iucode-tool.
(Reading database ... 45161 files and directories currently installed.)
Preparing to unpack .../iucode-tool_2.3.1-3_amd64.deb ...
Unpacking iucode-tool (2.3.1-3) ...
Selecting previously unselected package intel-microcode.
Preparing to unpack .../intel-microcode_3.20240813.1~deb12u1_amd64.deb ...
Unpacking intel-microcode (3.20240813.1~deb12u1) ...
Setting up iucode-tool (2.3.1-3) ...
Setting up intel-microcode (3.20240813.1~deb12u1) ...
intel-microcode: microcode will be updated at next boot
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..#.........]
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
root@awpve:~#
 
fiona said:
What error do you get?
Click to expand...
here is the latest from the syslog

Nov 07 18:51:16 awpve systemd[4001909]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Nov 07 18:51:16 awpve systemd[4001909]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Nov 07 18:51:16 awpve systemd[4001909]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Nov 07 18:51:16 awpve systemd[4001909]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Nov 07 18:51:16 awpve systemd[4001909]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Nov 07 18:51:16 awpve systemd[4001909]: Removed slice app.slice - User Application Slice.
Nov 07 18:51:16 awpve systemd[4001909]: Reached target shutdown.target - Shutdown.
Nov 07 18:51:16 awpve systemd[4001909]: Finished systemd-exit.service - Exit the Session.
Nov 07 18:51:16 awpve systemd[4001909]: Reached target exit.target - Exit the Session.
Nov 07 18:51:16 awpve systemd[1]: user@0.service: Deactivated successfully.
Nov 07 18:51:16 awpve systemd[1]: Stopped user@0.service - User Manager for UID 0.
Nov 07 18:51:16 awpve systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Nov 07 18:51:16 awpve systemd[1]: run-user-0.mount: Deactivated successfully.
Nov 07 18:51:16 awpve systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Nov 07 18:51:16 awpve systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Nov 07 18:51:16 awpve systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Nov 07 18:51:16 awpve systemd[1]: user-0.slice: Consumed 1.569s CPU time.
Nov 07 19:07:43 awpve kernel: zd32: p1 p2
Nov 07 19:07:43 awpve kernel: zd0: p1
Nov 07 19:07:44 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 19:07:44 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 07 19:07:44 awpve qmeventd[2768]: read: Connection reset by peer
Nov 07 19:07:44 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 07 19:07:44 awpve systemd[1]: 777.scope: Consumed 8min 26.765s CPU time.
Nov 07 19:07:45 awpve qmeventd[4032627]: Starting cleanup for 777
Nov 07 19:07:45 awpve qmeventd[4032627]: Finished cleanup for 777
Nov 07 19:17:01 awpve CRON[4033930]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 07 19:17:01 awpve CRON[4033931]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 07 19:17:01 awpve CRON[4033930]: pam_unix(cron:session): session closed for user root





I noted that once the below is shown

Nov 07 19:07:43 awpve kernel: zd32: p1 p2
Nov 07 19:07:43 awpve kernel: zd0: p1
Nov 07 19:07:44 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 07 19:07:44 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state


I see the vm being halted.
why is tap getting created? is this due to win2016 server's request?
 
fiona said:
What error do you get?
Click to expand...
root@awpve:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


root@awpve:~# uname -a
Linux awpve 6.2.16-3-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) x86_64 GNU/Linux

how do i kernel upgrade?
 
Ive done the steps needed yet still the problem exist.

here is what I see before the halt


Nov 08 09:56:55 awpve pveproxy[3358]: worker 435097 started
Nov 08 10:04:26 awpve pvedaemon[3350]: <root@pam> successful auth for user 'root@pam'
Nov 08 10:05:15 awpve pveproxy[156645]: worker exit
Nov 08 10:05:15 awpve pveproxy[3358]: worker 156645 finished
Nov 08 10:05:15 awpve pveproxy[3358]: starting 1 worker(s)
Nov 08 10:05:15 awpve pveproxy[3358]: worker 452646 started
Nov 08 10:05:23 awpve pveproxy[156646]: worker exit
Nov 08 10:05:23 awpve pveproxy[3358]: worker 156646 finished
Nov 08 10:05:23 awpve pveproxy[3358]: starting 1 worker(s)
Nov 08 10:05:23 awpve pveproxy[3358]: worker 454518 started
Nov 08 10:17:01 awpve CRON[484303]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Nov 08 10:17:01 awpve CRON[484304]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Nov 08 10:17:01 awpve CRON[484303]: pam_unix(cron:session): session closed for user root
Nov 08 10:17:15 awpve pvedaemon[3350]: worker exit
Nov 08 10:17:15 awpve pvedaemon[3349]: worker 3350 finished
Nov 08 10:17:15 awpve pvedaemon[3349]: starting 1 worker(s)
Nov 08 10:17:15 awpve pvedaemon[3349]: worker 484829 started
Nov 08 10:20:09 awpve pvedaemon[3351]: VM 777 qmp command failed - VM 777 qmp command 'guest-ping' failed - got timeout
Nov 08 10:20:12 awpve kernel: zd32: p1 p2
Nov 08 10:20:12 awpve kernel: zd0: p1
Nov 08 10:20:13 awpve kernel: vmbr0: port 2(tap777i0) entered disabled state
Nov 08 10:20:13 awpve kernel: vmbr1: port 2(tap777i1) entered disabled state
Nov 08 10:20:13 awpve qmeventd[2792]: read: Connection reset by peer
Nov 08 10:20:13 awpve pvedaemon[484829]: VM 777 qmp command failed - VM 777 not running
Nov 08 10:20:13 awpve systemd[1]: 777.scope: Deactivated successfully.
Nov 08 10:20:13 awpve systemd[1]: 777.scope: Consumed 14min 57.179s CPU time.
Nov 08 10:20:14 awpve qmeventd[493604]: Starting cleanup for 777
Nov 08 10:20:14 awpve qmeventd[493604]: Finished cleanup for 777
 
hassoon said:
root@awpve:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


root@awpve:~# uname -a
Linux awpve 6.2.16-3-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-3 (2023-06-17T05:58Z) x86_64 GNU/Linux

how do i kernel upgrade?
Click to expand...
See
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
https://pve.proxmox.com/wiki/Package_Repositories

Are the latest BIOS updates installed?

Did you attempt getting a dump with systemd-coredump?
 
Ive gone through the lengthy and terrible IBM firmware updates and Ive done BIOS update as well as Firmware updates, yet the same problem of sudden vm shutdown is still there.
can someone pls help.
 
hassoon said:
root@awpve:~# apt dist-upgrade
Click to expand...
1. First check what repos you have enabled. (You can look in the GUI under Node , Updates ,Repositories).
2. You must have one PVE active repo. If you have a subscription that will be pve-enterprise , if you do not it will be pve-no-subscription .
3. To update; You can either use the GUI, Node , Updates & Press Refresh & then >_ Upgrade, or use the CLI with apt-get update & then apt-get dist-upgrade , (don't use anything else in CLI!)
 
  • Like
Reactions: fiona
gfngfn256 said:
1. First check what repos you have enabled. (You can look in the GUI under Node , Updates ,Repositories).
2. You must have one PVE active repo. If you have a subscription that will be pve-enterprise , if you do not it will be pve-no-subscription .
3. To update; You can either use the GUI, Node , Updates & Press Refresh & then >_ Upgrade, or use the CLI with apt-get update & then apt-get dist-upgrade , (don't use anything else in CLI!)
Click to expand...
deb http://ftp.tr.debian.org/debian bookworm main contrib non-free-firmware

deb http://ftp.tr.debian.org/debian bookworm-updates main contrib non-free-firmware

# security updates
deb http://security.debian.org bookworm-security main contrib non-free-firmware
/etc/apt/sources.list (END)

enterprise is commented out.

root@awpve:~# apt update
Get:1 http://security.debian.org bookworm-security InRelease [48.0 kB]
Hit:2 http://ftp.tr.debian.org/debian bookworm InRelease
Get:3 http://ftp.tr.debian.org/debian bookworm-updates InRelease [55.4 kB]
Fetched 103 kB in 8s (12.3 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
48 packages can be upgraded. Run 'apt list --upgradable' to see them.



root@awpve:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
base-files bsdextrautils bsdutils btrfs-progs curl distro-info-data eject fdisk intel-microcode
iputils-ping libarchive13 libblkid1 libc-bin libc-l10n libc6 libcurl3-gnutls libcurl4 libfdisk1
libglib2.0-0 libmount1 libmpg123-0 libnghttp2-14 libnss-systemd libnss3 libpam-systemd
libpython3.11-minimal libpython3.11-stdlib libsmartcols1 libsqlite3-0 libssl3 libsystemd-shared
libsystemd0 libudev1 libuuid1 locales mount openssl python3.11 python3.11-minimal sqlite3
systemd systemd-boot systemd-boot-efi systemd-coredump systemd-sysv udev util-linux
util-linux-extra
48 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 40.1 MB of archives.
After this operation, 10.2 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.debian.org bookworm-security/main amd64 libarchive13 amd64 3.6.2-1+deb12u2 [343 kB]
Get:2 http://security.debian.org bookworm-security/main amd64 libmpg123-0 amd64 1.31.2-1+deb12u1 [147 kB]
Get:3 http://security.debian.org bookworm-security/main amd64 libnss3 amd64 2:3.87.1-1+deb12u1 [1,331 kB]
Get:4 http://ftp.tr.debian.org/debian bookworm/main amd64 base-files amd64 12.4+deb12u8 [70.9 kB]
Get:5 http://ftp.tr.debian.org/debian bookworm/main amd64 bsdutils amd64 1:2.38.1-5+deb12u2 [94.5 kB]
Get:6 http://ftp.tr.debian.org/debian bookworm/main amd64 libc6 amd64 2.36-9+deb12u9 [2,757 kB]
Get:7 http://ftp.tr.debian.org/debian bookworm/main amd64 libsmartcols1 amd64 2.38.1-5+deb12u2 [107 kB]
Get:8 http://ftp.tr.debian.org/debian bookworm/main amd64 util-linux-extra amd64 2.38.1-5+deb12u2 [111 kB]
Get:9 http://ftp.tr.debian.org/debian bookworm/main amd64 util-linux amd64 2.38.1-5+deb12u2 [1,176 kB]
Get:10 http://ftp.tr.debian.org/debian bookworm/main amd64 libc-bin amd64 2.36-9+deb12u9 [608 kB]
Get:11 http://ftp.tr.debian.org/debian bookworm/main amd64 mount amd64 2.38.1-5+deb12u2 [134 kB]
Get:12 http://ftp.tr.debian.org/debian bookworm/main amd64 libnss-systemd amd64 252.31-1~deb12u1 [163 kB]
Get:13 http://ftp.tr.debian.org/debian bookworm/main amd64 systemd-coredump amd64 252.31-1~deb12u1 [97.5 kB]
Get:14 http://ftp.tr.debian.org/debian bookworm/main amd64 libblkid1 amd64 2.38.1-5+deb12u2 [147 kB]
Get:15 http://ftp.tr.debian.org/debian bookworm/main amd64 libmount1 amd64 2.38.1-5+deb12u2 [165 kB]
Get:16 http://ftp.tr.debian.org/debian bookworm/main amd64 libssl3 amd64 3.0.15-1~deb12u1 [2,025 kB]
Get:17 http://ftp.tr.debian.org/debian bookworm/main amd64 systemd-boot amd64 252.31-1~deb12u1 [100 kB]
Get:18 http://ftp.tr.debian.org/debian bookworm/main amd64 systemd-boot-efi amd64 252.31-1~deb12u1 [112 kB]
Get:19 http://ftp.tr.debian.org/debian bookworm/main amd64 libpam-systemd amd64 252.31-1~deb12u1 [225 kB]
Get:20 http://ftp.tr.debian.org/debian bookworm/main amd64 systemd amd64 252.31-1~deb12u1 [3,036 kB]
Get:21 http://ftp.tr.debian.org/debian bookworm/main amd64 libsystemd-shared amd64 252.31-1~deb12u1 [1,693 kB]
Get:22 http://ftp.tr.debian.org/debian bookworm/main amd64 systemd-sysv amd64 252.31-1~deb12u1 [42.5 kB]
Get:23 http://ftp.tr.debian.org/debian bookworm/main amd64 libuuid1 amd64 2.38.1-5+deb12u2 [28.7 kB]
Get:24 http://ftp.tr.debian.org/debian bookworm/main amd64 libfdisk1 amd64 2.38.1-5+deb12u2 [193 kB]
Get:25 http://ftp.tr.debian.org/debian bookworm/main amd64 libsystemd0 amd64 252.31-1~deb12u1 [332 kB]
Get:26 http://ftp.tr.debian.org/debian bookworm/main amd64 python3.11 amd64 3.11.2-6+deb12u4 [573 kB]
Get:27 http://ftp.tr.debian.org/debian bookworm/main amd64 libpython3.11-stdlib amd64 3.11.2-6+deb12u4 [1,797 kB]
Get:28 http://ftp.tr.debian.org/debian bookworm/main amd64 python3.11-minimal amd64 3.11.2-6+deb12u4 [2,066 kB]
Get:29 http://ftp.tr.debian.org/debian bookworm/main amd64 libpython3.11-minimal amd64 3.11.2-6+deb12u4 [815 kB]
Get:30 http://ftp.tr.debian.org/debian bookworm/main amd64 sqlite3 amd64 3.40.1-2+deb12u1 [353 kB]
Get:31 http://ftp.tr.debian.org/debian bookworm/main amd64 libsqlite3-0 amd64 3.40.1-2+deb12u1 [839 kB]
Get:32 http://ftp.tr.debian.org/debian bookworm/main amd64 udev amd64 252.31-1~deb12u1 [1,688 kB]
Get:33 http://ftp.tr.debian.org/debian bookworm/main amd64 libudev1 amd64 252.31-1~deb12u1 [109 kB]
Get:34 http://ftp.tr.debian.org/debian bookworm/main amd64 fdisk amd64 2.38.1-5+deb12u2 [141 kB]
Get:35 http://ftp.tr.debian.org/debian bookworm/main amd64 iputils-ping amd64 3:20221126-1+deb12u1 [47.2 kB]
Get:36 http://ftp.tr.debian.org/debian bookworm/non-free-firmware amd64 intel-microcode amd64 3.20240910.1~deb12u1 [6,998 kB]
Get:37 http://ftp.tr.debian.org/debian bookworm/main amd64 libc-l10n all 2.36-9+deb12u9 [677 kB]
Get:38 http://ftp.tr.debian.org/debian bookworm/main amd64 locales all 2.36-9+deb12u9 [3,904 kB]
Get:39 http://ftp.tr.debian.org/debian bookworm/main amd64 bsdextrautils amd64 2.38.1-5+deb12u2 [86.8 kB]
Get:40 http://ftp.tr.debian.org/debian bookworm/main amd64 btrfs-progs amd64 6.2-1+deb12u1 [754 kB]
Get:41 http://ftp.tr.debian.org/debian bookworm/main amd64 libnghttp2-14 amd64 1.52.0-1+deb12u2 [73.0 kB]
Get:42 http://ftp.tr.debian.org/debian bookworm/main amd64 curl amd64 7.88.1-10+deb12u8 [315 kB]
Get:43 http://ftp.tr.debian.org/debian bookworm/main amd64 libcurl4 amd64 7.88.1-10+deb12u8 [390 kB]
Get:44 http://ftp.tr.debian.org/debian bookworm/main amd64 distro-info-data all 0.58+deb12u3 [6,272 B]
Get:45 http://ftp.tr.debian.org/debian bookworm/main amd64 eject amd64 2.38.1-5+deb12u2 [48.0 kB]
Get:46 http://ftp.tr.debian.org/debian bookworm/main amd64 libcurl3-gnutls amd64 7.88.1-10+deb12u8 [385 kB]
Get:47 http://ftp.tr.debian.org/debian bookworm/main amd64 libglib2.0-0 amd64 2.74.6-2+deb12u4 [1,400 kB]
Get:48 http://ftp.tr.debian.org/debian bookworm/main amd64 openssl amd64 3.0.15-1~deb12u1 [1,427 kB]
Fetched 40.1 MB in 10s (3,887 kB/s)
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../base-files_12.4+deb12u8_amd64.deb ...
Unpacking base-files (12.4+deb12u8) over (12.4+deb12u7) ...
Setting up base-files (12.4+deb12u8) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../bsdutils_1%3a2.38.1-5+deb12u2_amd64.deb ...
Unpacking bsdutils (1:2.38.1-5+deb12u2) over (1:2.38.1-5+deb12u1) ...
Setting up bsdutils (1:2.38.1-5+deb12u2) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../libc6_2.36-9+deb12u9_amd64.deb ...
Unpacking libc6:amd64 (2.36-9+deb12u9) over (2.36-9+deb12u8) ...
Setting up libc6:amd64 (2.36-9+deb12u9) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../libsmartcols1_2.38.1-5+deb12u2_amd64.deb ...
Unpacking libsmartcols1:amd64 (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Setting up libsmartcols1:amd64 (2.38.1-5+deb12u2) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../util-linux-extra_2.38.1-5+deb12u2_amd64.deb ...
Unpacking util-linux-extra (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Setting up util-linux-extra (2.38.1-5+deb12u2) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../util-linux_2.38.1-5+deb12u2_amd64.deb ...
Unpacking util-linux (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Setting up util-linux (2.38.1-5+deb12u2) ...
fstrim.service is a disabled or a static unit not running, not starting it.
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../libc-bin_2.36-9+deb12u9_amd64.deb ...
Unpacking libc-bin (2.36-9+deb12u9) over (2.36-9+deb12u8) ...
Setting up libc-bin (2.36-9+deb12u9) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../mount_2.38.1-5+deb12u2_amd64.deb ...
Unpacking mount (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Preparing to unpack .../libnss-systemd_252.31-1~deb12u1_amd64.deb ...
Unpacking libnss-systemd:amd64 (252.31-1~deb12u1) over (252.30-1~deb12u2) ...
Preparing to unpack .../systemd-coredump_252.31-1~deb12u1_amd64.deb ...
Unpacking systemd-coredump (252.31-1~deb12u1) over (252.30-1~deb12u2) ...
Preparing to unpack .../libblkid1_2.38.1-5+deb12u2_amd64.deb ...
Unpacking libblkid1:amd64 (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Setting up libblkid1:amd64 (2.38.1-5+deb12u2) ...
(Reading database ... 45303 files and directories currently installed.)
Preparing to unpack .../libmount1_2.38.1-5+deb12u2_amd64.deb ...
.........
Preparing to unpack .../10-distro-info-data_0.58+deb12u3_all.deb ...
Unpacking distro-info-data (0.58+deb12u3) over (0.58+deb12u2) ...
Preparing to unpack .../11-eject_2.38.1-5+deb12u2_amd64.deb ...
Unpacking eject (2.38.1-5+deb12u2) over (2.38.1-5+deb12u1) ...
Preparing to unpack .../12-libarchive13_3.6.2-1+deb12u2_amd64.deb ...
Unpacking libarchive13:amd64 (3.6.2-1+deb12u2) over (3.6.2-1+deb12u1) ...
Preparing to unpack .../13-libcurl3-gnutls_7.88.1-10+deb12u8_amd64.deb ...
Unpacking libcurl3-gnutls:amd64 (7.88.1-10+deb12u8) over (7.88.1-10+deb12u7) ...
Preparing to unpack .../14-libglib2.0-0_2.74.6-2+deb12u4_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.74.6-2+deb12u4) over (2.74.6-2+deb12u3) ...
Preparing to unpack .../15-libmpg123-0_1.31.2-1+deb12u1_amd64.deb ...
Unpacking libmpg123-0:amd64 (1.31.2-1+deb12u1) over (1.31.2-1) ...
Preparing to unpack .../16-libnss3_2%3a3.87.1-1+deb12u1_amd64.deb ...
Unpacking libnss3:amd64 (2:3.87.1-1+deb12u1) over (2:3.87.1-1) ...
Preparing to unpack .../17-openssl_3.0.15-1~deb12u1_amd64.deb ...
Unpacking openssl (3.0.15-1~deb12u1) over (3.0.14-1~deb12u2) ...
Setting up systemd-boot-efi:amd64 (252.31-1~deb12u1) ...
Setting up systemd-sysv (252.31-1~deb12u1) ...
Setting up libc-l10n (2.36-9+deb12u9) ...
Setting up libmpg123-0:amd64 (1.31.2-1+deb12u1) ...
Setting up bsdextrautils (2.38.1-5+deb12u2) ...
Setting up libarchive13:amd64 (3.6.2-1+deb12u2) ...
Setting up systemd-coredump (252.31-1~deb12u1) ...
Setting up libglib2.0-0:amd64 (2.74.6-2+deb12u4) ...
No schema files found: doing nothing.
Setting up distro-info-data (0.58+deb12u3) ...
Setting up intel-microcode (3.20240910.1~deb12u1) ...
intel-microcode: microcode will be updated at next boot
Setting up btrfs-progs (6.2-1+deb12u1) ...
Setting up libsqlite3-0:amd64 (3.40.1-2+deb12u1) ...
Setting up libnghttp2-14:amd64 (1.52.0-1+deb12u2) ...
Setting up libnss-systemd:amd64 (252.31-1~deb12u1) ...
Setting up libcurl3-gnutls:amd64 (7.88.1-10+deb12u8) ...
Setting up libnss3:amd64 (2:3.87.1-1+deb12u1) ...
Setting up locales (2.36-9+deb12u9) ...
Generating locales (this might take a while)...
en_US.UTF-8... done
Generation complete.
Setting up systemd-boot (252.31-1~deb12u1) ...
Setting up eject (2.38.1-5+deb12u2) ...
Setting up udev (252.31-1~deb12u1) ...
Setting up libfdisk1:amd64 (2.38.1-5+deb12u2) ...
Setting up libpam-systemd:amd64 (252.31-1~deb12u1) ...
Setting up libcurl4:amd64 (7.88.1-10+deb12u8) ...
Setting up libpython3.11-minimal:amd64 (3.11.2-6+deb12u4) ...
Setting up curl (7.88.1-10+deb12u8) ...
Setting up openssl (3.0.15-1~deb12u1) ...
Setting up iputils-ping (3:20221126-1+deb12u1) ...
Setting up sqlite3 (3.40.1-2+deb12u1) ...
Setting up python3.11-minimal (3.11.2-6+deb12u4) ...
Setting up libpython3.11-stdlib:amd64 (3.11.2-6+deb12u4) ...
Setting up fdisk (2.38.1-5+deb12u2) ...
Setting up python3.11 (3.11.2-6+deb12u4) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Processing triggers for systemd (252.31-1~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

last time it was showing nothing btw
I wonder if bios update had some effects on this.
now rebooting and seeing if this will work
 
You must log in or register to reply here.
Top Bottom