How to upgrade my pve?

S

Steam

New Member
Mar 22, 2024
4
0
1
I tried upgrading PVE 7.2-3 to 7.4:

Code: 
Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  proxmox-ve pve-container pve-ha-manager pve-kernel-helper pve-manager qemu-server
The following NEW packages will be installed:
  pve-kernel-5.15.158-2-pve
The following packages will be upgraded:
  corosync e2fsprogs ifupdown2 libcfg7 libcmap4 libcom-err2 libcorosync-common4
  libcpg4 libext2fs2 libknet1 libnozzle1 libnss-systemd libnvpair3linux
  libpam-systemd libproxmox-acme-perl libproxmox-acme-plugins
  libproxmox-backup-qemu0 libproxmox-rs-perl libpve-access-control
  libpve-apiclient-perl libpve-cluster-api-perl libpve-cluster-perl
  libpve-common-perl libpve-guest-common-perl libpve-http-server-perl libpve-rs-perl
  libpve-storage-perl libquorum5 librados2-perl libss2 libsystemd0 libtpms0 libudev1
  libuutil3linux libvotequorum8 libzfs4linux libzpool5linux logsave lxc-pve lxcfs
  novnc-pve proxmox-archive-keyring proxmox-backup-client
  proxmox-backup-file-restore proxmox-widget-toolkit pve-cluster pve-docs
  pve-edk2-firmware pve-firewall pve-firmware pve-i18n pve-kernel-5.15
  pve-lxc-syscalld pve-xtermjs spl swtpm swtpm-libs swtpm-tools systemd systemd-sysv
  udev zfs-initramfs zfs-zed zfsutils-linux
64 upgraded, 1 newly installed, 6 to remove and 0 not upgraded.
Need to get 0 B/219 MB of archives.
After this operation, 296 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
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

System not fully up to date (found 75 new packages)

starting shell
root@pve:/#

What is "proximmox-ve"? What do I need to do?
 
Last edited:
Steam said:
What is "proximmox-ve"? What do I need to do?
Click to expand...
proxmox-ve is a meta package that ensures that all relevant parts of the Proxmox VE are installed and will keep being installed.

The error you run in is a protection to avoid removing proxmox-ve due to some misconfiguration, normally in the apt repository sources, or seldom also in the selection of installed packages.

What's the output of apt update and head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/* ?

In the simplest case you just might miss a Proxmox VE repo that you got access too:
https://pve.proxmox.com/wiki/Package_Repositories
 
t.lamprecht said:
proxmox-ve is a meta package that ensures that all relevant parts of the Proxmox VE are installed and will keep being installed.

The error you run in is a protection to avoid removing proxmox-ve due to some misconfiguration, normally in the apt repository sources, or seldom also in the selection of installed packages.

What's the output of apt update and head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/* ?

In the simplest case you just might miss a Proxmox VE repo that you got access too:
https://pve.proxmox.com/wiki/Package_Repositories
Click to expand...

root@pve:~# apt update:
Code: 
root@pve:~# apt update
Hit:1 http://download.proxmox.com/debian/pve bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
71 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@pve:~# head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/*:
Code: 
root@pve:~# head -n-0 /etc/apt/sources.list /etc/apt/sources.list.d/*
==> /etc/apt/sources.list <==
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription


==> /etc/apt/sources.list.d/ceph.list <==
# deb http://download.proxmox.com/debian/ceph-quincy bullseye no-subscription


==> /etc/apt/sources.list.d/pve-enterprise.list <==
#

==> /etc/apt/sources.list.d/pve-install-repo.list <==
# deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription


==> /etc/apt/sources.list.d/pve-no-subscription.list <==
 
You also need the base Debian repos, add the following lines to /etc/apt/sources.list

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

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

Then run apt update again, or refresh the update states through the web UI, and then retry the system upgrade
 
  • Like
Reactions: Steam
t.lamprecht said:
You also need the base Debian repos, add the following lines to /etc/apt/sources.list

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

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

Then run apt update again, or refresh the update states through the web UI, and then retry the system upgrade
Click to expand...

Thank you very much, for I don't know much about computers. It seems to have succeeded!
Code: 
...
Processing triggers for libc-bin (2.31-13+deb11u11) ...
Processing triggers for rsyslog (8.2102.0-2+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...

Your System is up-to-date


Seems you installed a kernel update - Please consider rebooting
this node to activate the new kernel.

starting shell
root@pve:/# reboot
 
You must log in or register to reply here.
Top Bottom