PVE 8 to 9 In-place Upgrade

Question about the trixie repo's that need to be added prior to the upgrade.

The upgrade document instructs you to update Debian Base Repositories to Trixie using sed for both "/etc/apt/sources.list" and "/etc/apt/sources.list.d/pve-enterprise.list"

It then instructs to add the Proxmox VE9 Package Repository using the new deb822 style which results in a new "pve-enterprise.sources" file.

After doing this and running apt update, warnings are presented because of target packages and translations being configured multiple times. This looks to be because they are configured both in pve-enterprise.list and the new file pve-enterprise.sources.


Code: 
Hit:1 http://security.debian.org trixie-security InRelease
Hit:2 http://ftp.us.debian.org/debian trixie InRelease
Hit:3 http://ftp.us.debian.org/debian trixie-updates InRelease
Hit:4 https://enterprise.proxmox.com/debian/pve trixie InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
582 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Target Packages (pve-enterprise/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Packages (pve-enterprise/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Translations (pve-enterprise/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Translations (pve-enterprise/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Packages (pve-enterprise/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Packages (pve-enterprise/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Translations (pve-enterprise/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1
W: Target Translations (pve-enterprise/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.list:1 and /etc/apt/sources.list.d/pve-enterprise.sources:1

Is this safe to ignore? I get that its just a warning and not an error.
 
Nagorg said:
After doing this and running apt update, warnings are presented because of target packages and translations being configured multiple times. This looks to be because they are configured both in pve-enterprise.list and the new file pve-enterprise.sources.
Click to expand...
Hi!

The upgrade guide then also states "Then you can remove the old /etc/apt/sources.list.d/pve-enterprise.list file", once you confirmed that apt policy shows that the new repositories have been picked up as expected. I think you might have just missed that one step.
 
  • Like
Reactions: matt69 and Nagorg
Hi all

during pve8to9 --full I get this error

Code: 
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.

this is the output of efibootmgr -v and proxmox-boot-tool status


Code: 
root@pve:~# efibootmgr -v
BootCurrent: 0002
Timeout: 3 seconds
BootOrder: 0002,0003,0000
Boot0000* Windows Boot Manager  HD(1,GPT,50a5a2f0-514a-4451-a3a0-1e44a2306871,0x800,0x96000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Boot0002* proxmox       HD(2,GPT,2553c267-2073-44ec-876d-f7e8c4d71000,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0003* UEFI OS       HD(2,GPT,2553c267-2073-44ec-876d-f7e8c4d71000,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
root@pve:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.

Can I securely remove systemd-boot before upgrade and install systemd-boot-efi and systemd-boot-tools after upgrade ?

Thanks
 
  • Like
Reactions: matt69
Any help with this error?

W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook) - your APT repository settings
W: (pve-apt-hook) - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
root@pve:/#
 
aleda said:
You are attempting to remove the meta-package 'proxmox-ve'!
Click to expand...
This is probably caused by a repos not correctly configured.

I don't know your system versioning etc. (You seem to be posting in this thread - so I guess you are in the PVE8to9 upgrade process?).

Could you show output for the following.

Code: 
pveversion -v

grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*
 
gfngfn256 said:
This is probably caused by a repos not correctly configured.

I don't know your system versioning etc. (You seem to be posting in this thread - so I guess you are in the PVE8to9 upgrade process?).

Could you show output for the following.

Code: 
pveversion -v

grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*
Click to expand...
Yes trying to upgrade from 8.4 to 9, here is the results of the command.

root@pve:~# pveversion -v

grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*
proxmox-ve: 8.4.0 (running kernel: 6.8.12-15-pve)
pve-manager: 8.4.13 (running version: 8.4.13/5b08ebc2823dd9cb)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8: 6.8.12-15
proxmox-kernel-6.8.12-15-pve-signed: 6.8.12-15
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20250512.1~deb12u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
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.6.0-2
proxmox-backup-client: 3.4.6-1
proxmox-backup-file-restore: 3.4.6-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.1.2
pve-container: 5.3.2
pve-docs: 8.4.1
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.3
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.8-pve1
/etc/apt/sources.list:deb http://deb.debian.org/debian trixie main contrib non-free-firmware
/etc/apt/sources.list:deb http://deb.debian.org/debian trixie-updates main contrib non-free-firmware
/etc/apt/sources.list:deb http://security.debian.org/debian-security trixie-security main contrib non-free-firmware
grep: /etc/apt/sources.list.d: Is a directory
/etc/apt/sources.list.d/ceph.sources:Types: deb
/etc/apt/sources.list.d/ceph.sources:URIs: http://download.proxmox.com/debian/ceph-squid
/etc/apt/sources.list.d/ceph.sources:Suites: trixie
/etc/apt/sources.list.d/ceph.sources:Components: no-subscription
/etc/apt/sources.list.d/ceph.sources:Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
/etc/apt/sources.list.d/pmg-enterprise.list:# deb https://enterprise.proxmox.com/debian/pmg bookworm pmg-enterprise
/etc/apt/sources.list.d/pmg-install-repo.list:#deb http://download.proxmox.com/debian/pmg bookworm pmg-no-subscription
/etc/apt/sources.list.d/pmgtest-for-beta.list:# deb http://download.proxmox.com/debian/pmg bookworm pmgtest
/etc/apt/sources.list.d/pve-enterprise.list:# deb https://enterprise.proxmox.com/debian/pve trixie pve-enterprise
/etc/apt/sources.list.d/pve-enterprise.list:
/etc/apt/sources.list.d/pve-install-repo.list:#deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
/etc/apt/sources.list.d/pvetest-for-beta.list:# deb http://download.proxmox.com/debian/pve bookworm pvetest
root@pve:~# ^C
root@pve:~#
 
gfngfn256 said:
This is probably caused by a repos not correctly configured.

I don't know your system versioning etc. (You seem to be posting in this thread - so I guess you are in the PVE8to9 upgrade process?).

Could you show output for the following.

Code: 
pveversion -v

grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*
Click to expand...
You were right was a repo issue fixed it and got upgraded thank you!
 
  • Like
Reactions: matt69
begeis said:
I am preparing the upgrade from PVE 8.4.12 to PVE 9.
I run 'pve8to9' in the shell of my proxmox host and got the following error message:
View attachment 90293
I am not sure how to step forward. When I remove 'systemd-boot' as said will a new 'systemd-boot' for PVE 9 be installed during the upgrade?
Disk configuration:
View attachment 90294
Please help!
Click to expand...
I prepared for a possibly needed new installation. Then I deleted 'systemd-boot' with 'apt remove systemd-boot' and started the upgrade after removing all warnings and the failure from pve8to9. The upgrade worked perfect!
 
You must log in or register to reply here.
Top Bottom