Problems after upgrading from 6.x to 7.4-3

sysoevik

New Member
Mar 30, 2023
8
1
3
Hello, it is my first post.
After upgrading my proxmox installation from 6.x to 7.4-3, i've encountered several errors:


Code:
Errors were encountered while processing:
 pve-kernel-5.15.102-1-pve
 pve-kernel-5.15
 proxmox-ve
 initramfs-tools



dpgk -a,apt --fix-broken install... and so on are not able to fix the problem


apt --fix-broken install output :

Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.140) ...
update-initramfs: deferring update (trigger activated)
Setting up pve-kernel-5.15.102-1-pve (5.15.102-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.15.102-1-pve /boot/vmlinuz-5.15.102-1-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.15.102-1-pve /boot/vmlinuz-5.15.102-1-pve
update-initramfs: Generating /boot/initrd.img-5.15.102-1-pve
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/DD94-5E62
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD94-DA49
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
E: 'zz-pve-efiboot' is not a valid hook script name.
run-parts: /etc/initramfs/post-update.d//pve-efiboot-sync exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/pve-kernel-5.15.102-1-pve.postinst line 19.
dpkg: error processing package pve-kernel-5.15.102-1-pve (--configure):
 installed pve-kernel-5.15.102-1-pve package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of pve-kernel-5.15:
 pve-kernel-5.15 depends on pve-kernel-5.15.102-1-pve; however:
  Package pve-kernel-5.15.102-1-pve is not configured yet.


dpkg: error processing package pve-kernel-5.15 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on pve-kernel-5.15; however:
  Package pve-kernel-5.15 is not configured yet.


dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.15.102-1-pve
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/DD94-5E62
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD94-DA49
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
E: 'zz-pve-efiboot' is not a valid hook script name.
run-parts: /etc/initramfs/post-update.d//pve-efiboot-sync exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 pve-kernel-5.15.102-1-pve
 pve-kernel-5.15
 proxmox-ve
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

pveversion -v output :
Code:
proxmox-ve: not correctly installed (running kernel: 5.15.102-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.4: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.1-1
proxmox-backup-file-restore: 2.4.1-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.6.5
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-1
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

And older kernel is obviously is still here:
Code:
dpkg --list | grep pve-kernel
ii  pve-firmware                         3.6-4                            all          Binary firmware code for the pve-kernel
iU  pve-kernel-5.15                      7.3-3                            all          Latest Proxmox VE Kernel Image
iF  pve-kernel-5.15.102-1-pve            5.15.102-1                       amd64        Proxmox Kernel Image
ii  pve-kernel-5.4                       6.3-1                            all          Latest Proxmox VE Kernel Image
ii  pve-kernel-5.4.73-1-pve              5.4.73-1                         amd64        The Proxmox PVE Kernel Image
rc  pve-kernel-helper                    6.3-1                            all          Function for various kernel maintenance tasks.
 
Last edited:
How you did the upgrade?

Can you please try to re-install the pve-manager by issue the following command:
Bash:
apt install proxmox-ve --reinstall
 
what is the content of your

/etc/apt/sources.list
/etc/apt/sources.list.d/*

?
/etc/apt/sources.list

Code:
deb http://ftp.ru.debian.org/debian bullseye main contrib


deb http://ftp.ru.debian.org/debian bullseye-updates main contrib


# PVE pve-no-subscription repository provided by proxmox.com




deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription




# security updates
deb http://security.debian.org bullseye-security main contrib

/etc/apt/sources.list.d/*

Code:
# deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise
 
How you did the upgrade?

Can you please try to re-install the pve-manager by issue the following command:
Bash:
apt install proxmox-ve --reinstall

output of apt
Code:
apt install proxmox-ve --reinstall
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for proxmox-ve:amd64


I changed out sources for newer ones added comuinty repo and dist-upgraded, probably messed something up but second server upgraded fine
 
Code:
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise

should be commented too if you don't have the subscription.
(Could be possible that it's blocking apt-update)


or if you have a subscription, remove
Code:
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

but don't use both at the same time.
 
Code:
deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise

should be commented too if you don't have the subscription.
(Could be possible that it's blocking apt-update)


or if you have a subscription, remove
Code:
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription

but don't use both at the same time.
commented out, same behaviour :(
 
you should have this

Code:
/etc/kernel/postinst.d# ls
apt-auto-removal  initramfs-tools  proxmox-auto-removal  zz-proxmox-boot  zz-update-grub

remove zz-pve-efiboot if it's exist in this directory
Backed it up, removed it, behaviour is still the same

Code:
dpkg --configure initramfs-tools
Setting up initramfs-tools (0.140) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.15.102-1-pve
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/DD94-5E62
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
Copying and configuring kernels on /dev/disk/by-uuid/DD94-DA49
        Copying kernel and creating boot-entry for 5.15.102-1-pve
        Copying kernel and creating boot-entry for 5.4.73-1-pve
E: 'zz-pve-efiboot' is not a valid hook script name.
run-parts: /etc/initramfs/post-update.d//pve-efiboot-sync exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
 
Did you have upgraded to last 6.X no subscription version before upgrading to 7.X ?

because zz-pve-efiboot has been removed 3years ago from packages.

Seem than a remaining files from old packges is still installed
 
Did you have upgraded to last 6.X no subscription version before upgrading to 7.X ?

because zz-pve-efiboot has been removed 3years ago from packages.

Seem than a remaining files from old packges is still installed
Yep it seems it is the case, reading from terminal history it seems, that i've added sources in the wrong order, so now i need to figure out wich files to delete and how to get newer ones, if you have have any idea whre to start help will be apreciated, but in anycase thanks a lot now i know what i've done wrong :)
 
Hi!

The Official upgrade guide is wrong, when you do major version upgrade the following process is working:
- Make backup from the /etc/ directory,
- Upgrade the base debian linux first (every other repo must be disabled)
- Upgrade the other packages/repos (every other repo can be enabled: proxmox)

Otherwise you end up conflicting/half installed packages. (Example: pve-firewall package always conflicts, it stops the upgrade process. I have done this many PVE version upgrades, always failed the "official" process)
Code:
$> cd /root
$> tar -cf etc.tar.gz /etc

$> apt-mark hold proxmox-ve
$> apt-mark hold pve-manager

Check the contents of the following, ENABLE only the base debian repos, disable the others ( "#" comment out )
Code:
/etc/apt/mirror.list
/etc/apt/mirror.list.d/

$> apt-get clean all
$> apt-get autoclean
$> apt-get update
$> apt-get full-upgrade

Code:
REBOOT

Now, you can add/enable the other packages/repos that match your debian version/release ( remove "#" comment sign )
Code:
/etc/apt/mirror.list
/etc/apt/mirror.list.d/

$> apt-get clean all
$> apt-get autoclean
$> apt-get update

$> apt-mark unhold proxmox-ve
$> apt-mark unhold pve-manager

$> apt-get upgrade

Code:
DONE.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!