7.4-16 to 8 migration fails

kdude

New Member
Aug 10, 2023
3
0
1
Hello to all awesome proxmox devs and users!

I followed the upgrade guide, and during the upgrade (from GUI Updates >_ Upgrade button)
the console window exits with the following error: i have not attempted to reboot this node, i fear it will fail to boot in this state.

Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-6-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.
Processing triggers for pve-ha-manager (4.0.2) ...
Can't locate AptPkg/Config.pm in @INC (you may need to install the AptPkg::Config module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/lib/x86_64-linux-gnu/perl5/5.32/AptPkg/hash.pm line 20, <DATA> line 960.
BEGIN failed--compilation aborted, <DATA> line 960.
Connection to 192.168.254.183 closed.
 
my current state (not rebooted after this failed message)

root@prox1:~# pveversion -v
proxmox-ve: 8.0.2 (running kernel: 5.15.108-1-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-4
pve-kernel-5.4: 6.4-5
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
proxmox-kernel-6.2: 6.2.16-7
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.128-1-pve: 5.4.128-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 17.2.6-pve1+3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: 0.8.41
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1
root@prox1:~#
 
Hi,
I followed the upgrade guide, and during the upgrade (from GUI Updates >_ Upgrade button)
the upgrade guide clearly mentions that you shouldn't use the UI for the major upgrade, because the connection will be lost: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Actions_step-by-step

the console window exits with the following error: i have not attempted to reboot this node, i fear it will fail to boot in this state.
Please share the full output of the following commands
Code:
apt update
apt dist-upgrade
 
here's what that gives now

root@prox1:~# [B]apt update[/B] Hit:1 http://ftp.us.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://ftp.us.debian.org/debian bookworm-updates InRelease Hit:4 http://download.proxmox.com/debian/pve bookworm InRelease Hit:5 http://download.proxmox.com/debian/ceph-quincy bookworm InRelease Reading package lists... Done root@prox1:~# [B]apt dist-upgrade[/B] Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-libc-dev 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,811 kB of archives. After this operation, 0 B 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 linux-libc-dev amd64 6.1.38-4 [1,811 kB] Fetched 1,811 kB in 0s (4,655 kB/s) Reading changelogs... Done (Reading database ... 84893 files and directories currently installed.) Preparing to unpack .../linux-libc-dev_6.1.38-4_amd64.deb ... Unpacking linux-libc-dev:amd64 (6.1.38-4) over (6.1.38-3) ... Setting up linux-libc-dev:amd64 (6.1.38-4) ... root@prox1:~#
 
Sounds like everything is in place then. Please also check the output of the pve7to8 helper script and if you really want to make sure, re-install the kernel package, but apt doesn't complain about it not being configured, so it should be fine.