Update stopped accidentally

V

Vittorio

Well-Known Member
Jul 24, 2019
91
5
48
60
Hi all

I accidentally stopped Proxmox update from 8.3.2 to 8.3.3 and this is the latest log I've got from update terminal


Code: 
et:6 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8.12-7-pve-signed amd64 6.8.12-7 [103 MB]
Get:7 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8 all 6.8.12-7 [10.8 kB]
Get:8 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-widget-toolkit all 4.3.4 [220 kB]
Get:9 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-i18n all 3.3.3 [414 kB]
Get:10 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 qemu-server amd64 8.3.6 [291 kB]
Get:11 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-manager all 8.3.3 [548 kB]
Get:12 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 spl all 2.2.7-pve1 [15.5 kB]
Get:13 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 zfs-initramfs all 2.2.7-pve1 [25.8 kB]
Get:14 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 zfsutils-linux amd64 2.2.7-pve1 [549 kB]
Get:15 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 zfs-zed amd64 2.2.7-pve1 [68.7 kB]
Fetched 262 MB in 22s (11.9 MB/s)                                                  
Reading changelogs... Done
(Reading database ... 87010 files and directories currently installed.)
Preparing to unpack .../00-libnvpair3linux_2.2.7-pve1_amd64.deb ...
Unpacking libnvpair3linux (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../01-libuutil3linux_2.2.7-pve1_amd64.deb ...
Unpacking libuutil3linux (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../02-libzfs4linux_2.2.7-pve1_amd64.deb ...
Unpacking libzfs4linux (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../03-libzpool5linux_2.2.7-pve1_amd64.deb ...
Unpacking libzpool5linux (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../04-pve-firmware_3.14-3_all.deb ...
Unpacking pve-firmware (3.14-3) over (3.14-2) ...
Selecting previously unselected package proxmox-kernel-6.8.12-7-pve-signed.
Preparing to unpack .../05-proxmox-kernel-6.8.12-7-pve-signed_6.8.12-7_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-7-pve-signed (6.8.12-7) ...
Preparing to unpack .../06-proxmox-kernel-6.8_6.8.12-7_all.deb ...
Unpacking proxmox-kernel-6.8 (6.8.12-7) over (6.8.12-6) ...
Preparing to unpack .../07-proxmox-widget-toolkit_4.3.4_all.deb ...
Unpacking proxmox-widget-toolkit (4.3.4) over (4.3.3) ...
Preparing to unpack .../08-pve-i18n_3.3.3_all.deb ...
Unpacking pve-i18n (3.3.3) over (3.3.2) ...
Preparing to unpack .../09-qemu-server_8.3.6_amd64.deb ...
Unpacking qemu-server (8.3.6) over (8.3.3) ...
Preparing to unpack .../10-pve-manager_8.3.3_all.deb ...
Unpacking pve-manager (8.3.3) over (8.3.2) ...
Preparing to unpack .../11-spl_2.2.7-pve1_all.deb ...
Unpacking spl (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../12-zfs-initramfs_2.2.7-pve1_all.deb ...
Unpacking zfs-initramfs (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../13-zfsutils-linux_2.2.7-pve1_amd64.deb ...
Unpacking zfsutils-linux (2.2.7-pve1) over (2.2.6-pve1) ...
Preparing to unpack .../14-zfs-zed_2.2.7-pve1_amd64.deb ...
Unpacking zfs-zed (2.2.7-pve1) over (2.2.6-pve1) ...
Setting up libnvpair3linux (2.2.7-pve1) ...
Setting up proxmox-widget-toolkit (4.3.4) ...
Setting up pve-firmware (3.14-3) ...
Setting up qemu-server (8.3.6) ...
Setting up spl (2.2.7-pve1) ...
Setting up pve-i18n (3.3.3) ...
Setting up proxmox-kernel-6.8.12-7-pve-signed (6.8.12-7) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-7-pve /boot/vmlinuz-6.8.12-7-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-7-pve

So I've executed

apt-get update
apt-get -f install

the update didn't suggested anything, but the other command suggested to execute

dpkg --configure -a

Now on the web interface I get 8.3.3 but if I execute uname -r I get 5.15.126-1-pve

It seems to run everything ok, but I don't have the latest kernel

I've already tried rebooting Proxmox with same result

This is what I get with command dpkg --list | grep pve-kernel
Code: 
ii  pve-firmware                         3.14-3                              all          Binary firmware code for the pve-kernel
ii  pve-kernel-5.15.126-1-pve            5.15.126-1                          amd64        Proxmox Kernel Image
rc  pve-kernel-helper                    7.3-8                               all          Function for various kernel maintenance tasks.

What should I do now?

Thanks
 
Last edited:
gfngfn256 said:
What does pveversion -v output?
Click to expand...
I get this

Code: 
Linux new 5.15.126-1-pve #1 SMP PVE 5.15.126-1 (2023-10-03T17:24Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Jan 21 20:05:33 CET 2025 on pts/0
root@new:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 5.15.126-1-pve)
pve-manager: 8.3.3 (running version: 8.3.3/f157a38b211595d6)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-7
proxmox-kernel-6.8.12-7-pve-signed: 6.8.12-7
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
pve-kernel-5.15.126-1-pve: 5.15.126-1
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.4
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.3.3
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1
root@new:~# 
root@new:~# pveversion -v
proxmox-ve: 8.3.0 (running kernel: 5.15.126-1-pve)
pve-manager: 8.3.3 (running version: 8.3.3/f157a38b211595d6)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-7
proxmox-kernel-6.8.12-7-pve-signed: 6.8.12-7
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
pve-kernel-5.15.126-1-pve: 5.15.126-1
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.4
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.3.3
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1
 
Your packages appear up to date, but it seems that something got messed up at the end with the initramfs update.

What is the output from the following:

Code: 
apt-get dist-upgrade

apt policy proxmox-kernel-6.8 | head
 
apt-get dist upgrade result is

Code: 
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.

and the other command gives this

Code: 
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

proxmox-kernel-6.8:
  Installed: 6.8.12-7
  Candidate: 6.8.12-7
  Version table:
 *** 6.8.12-7 500
        500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages
        100 /var/lib/dpkg/status
     6.8.12-6 500
        500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages
     6.8.12-5 500
 
Everything appears correctly installed - except the obvious that you are booted with an older kernel.
I suspect this is because the initramfs needs updating.

So enter update-initramfs -u to update an existing initramfs - as shown here.

I've never done this before, but this is what the end of the upgrade command normally does - and appears got stopped incorrectly.
 
This is the result of update-initramfs -u
Code: 
update-initramfs: Generating /boot/initrd.img-6.8.12-7-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.
and this is the result of proxmox-boot-tool kernel list after the previous command

Code: 
Manually selected kernels:
None.

Automatically selected kernels:
5.15.126-1-pve
6.8.12-6-pve
6.8.12-7-pve

Should I try to reboot now?
 
Vittorio said:
This is the result of update-initramfs -u
Code: 
update-initramfs: Generating /boot/initrd.img-6.8.12-7-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.
Click to expand...
It looks like proxmox-boot-tool does not manage any ESPs. Did you install Proxmox on top of Debian or install PVE 6 or 7 and then upgraded to 8.3? Do you have any ESP (lsblk -o+PARTTYPENAME)?
 
@leesteken nope, my first Proxmox installation, done more than 1 year ago, was directly on hw.
The mess was due to my faulty stop during last update today, I always update when there is something available

Thanks @gfngfn256, I'll try to reboot now
 
Vittorio said:
@leesteken nope, my first Proxmox installation, done more than 1 year ago, was directly on hw.
The mess was due to my faulty stop during last update today, I always update when there is something available
Click to expand...
Okay, but it's really weird that no ESP is setup and managed by proxmox-boot-tool. It looks like you are still booting from the initial ESP with the old kernel version.
Also, PVE 8 never came with Linux kernel 5.15. Therefore, my question of "did you install PVE 6 or 7 and then upgrade to 8.3?" still remains valid.

If you "more than 1 year ago" installed Proxmox 7.x, then you first need to switch to proxmox-boot-tool. I'm sure there is a guide for that in the upgrade guide or Wiki.
 
after reboot, I still get old kernel

Yes, my first installation was on PVE 7.

I really don't know what is ESP, and I'm not an expert...

I found these two threads on forum with ESP as tag https://forum.proxmox.com/tags/esp/
But they are old and I haven't found any help
I have a single machine, not a cluster
 
Last edited:
  • Like
Reactions: Vittorio
@leesteken thanks for your help, I've found those two pages related to upgrade from 7 to 8
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_determine_bootloader_used

running efibootmgr -v I get
Boot0004* proxmox HD(2,GPT,xxxxxxxxxx,0x100000)/File(\EFI\PROXMOX\GRUBX64.EFI) so it's in UEFI mode

What I've found somewhere else is to execute these commands with /boot/efi disk as /dev/sda
proxmox-boot-tool format /dev/sda2
proxmox-boot-tool init /dev/sda2

proxmox-boot-tool refresh
update-initramfs -u -k all
update-grub
reboot


but i'm really worried to do extra mess
 
Last edited:
leesteken said:
Maybe installing a fresh PVE 8.3 and restoring VM/CTs from backups is easiest. I don't remember the details and cannot find the 7->8 upgrade details right now.

EDIT: Maybe this will help: https://pve.proxmox.com/wiki/ZFS:_Switch_Legacy-Boot_to_Proxmox_Boot_Tool
Click to expand...
I don't use ZFS
My /boot/efi partition is this, on vfat


sda2
│ vfat FAT32 7968-5017 1010.3M 1% /boot/efi

So proxmox-boot-tool is still something that I have to check?
I've read, but I'm not sure, that if I don't use ZFS, but vfat, proxmox-boot-tool is replaced by grub, is it correct?

Thanks
 
Now, I have downloaded again new kernel with

apt-get update
apt-get install pve-kernel-6.8.12-7-pve

probably something was missing since it was downloaded again, even if it seems to be already in place

Then I've manually updated grub using

nano /etc/default/grub

and replacing GRUB_DEFAULT with new kernel version

GRUB_DEFAULT="Advanced options for Proxmox VE>Proxmox VE GNU/Linux, with Linux 6.8.12-7-pve"


pveversion -v is

proxmox-ve: 8.3.0 (running kernel: 6.8.12-7-pve)
pve-manager: 8.3.3 (running version: 8.3.3/f157a38b211595d6)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-7
proxmox-kernel-6.8.12-7-pve: 6.8.12-7
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
pve-kernel-5.15.126-1-pve: 5.15.126-1
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.3.2-1
proxmox-backup-file-restore: 3.3.2-2
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.4
pve-cluster: 8.0.10
pve-container: 5.2.3
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-3
pve-ha-manager: 4.0.6
pve-i18n: 3.3.3
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1

it seems I've running now latest kernel, but I don't know I have solved the issue, hoping that with next kernel update everything works fine

My doubt is this line
pve-kernel-5.15.126-1-pve: 5.15.126-1

if I execute uname -r I get the new kernel 6.8.12-7-pve


what is the difference between proxmox-kernel and pve-kernel?


Thanks
 
Last edited:
You must log in or register to reply here.
Top Bottom