Hi!
I'm trying to upgrade Proxmox (5.4-2 to 6.x) now that I finally have physical access to my server again. I'm following the upgrade procedure (in place upgrade) from the wiki but I'm running into dependencies issues I don't know how to resolve.
I've backed up my VMs and the /etc/ folder just in case. The pve5to6 command only warns of VMs that are still running, other checks pass. This is a standalone node, not in a cluster.
I don't have a subscription, and the only repositories configured are in my /etc/apt/sources.list file.
Stretch - all packages are up to date:
After changing repositories to buster:
Output of pveversion -v:
I've tried manually installing cryptsetup-run and pve-cluster in the hopes of getting some more info to no avail. apt --fix-broken install and dpkg --configure -a did not do anything. It seems to me manually installing these packages or different versions of the dependencies might help, but I don't want to make the situation any worse.
Any help would be greatly appreciated.
EDIT: I also checked that no packages were being held, both with apt-mark showhold and dpkg --get-selections | grep hold
I'm trying to upgrade Proxmox (5.4-2 to 6.x) now that I finally have physical access to my server again. I'm following the upgrade procedure (in place upgrade) from the wiki but I'm running into dependencies issues I don't know how to resolve.
I've backed up my VMs and the /etc/ folder just in case. The pve5to6 command only warns of VMs that are still running, other checks pass. This is a standalone node, not in a cluster.
I don't have a subscription, and the only repositories configured are in my /etc/apt/sources.list file.
Stretch - all packages are up to date:
Code:
root@vroem:~# cat /etc/apt/sources.list
deb http://ftp.se.debian.org/debian stretch main contrib
deb http://ftp.se.debian.org/debian stretch-updates main contrib
deb http://download.proxmox.com/debian stretch pve-no-subscription
# security updates
deb http://security.debian.org stretch/updates main contrib
root@vroem:~# apt update
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://download.proxmox.com/debian stretch InRelease
Ign:3 http://ftp.se.debian.org/debian stretch InRelease
Hit:4 http://ftp.se.debian.org/debian stretch-updates InRelease
Hit:5 http://ftp.se.debian.org/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@vroem:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
After changing repositories to buster:
Code:
root@vroem:~# apt update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://ftp.se.debian.org/debian buster InRelease [121 kB]
Get:3 http://ftp.se.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://security.debian.org buster/updates/main amd64 Packages [257 kB]
Get:5 http://security.debian.org buster/updates/main Translation-en [141 kB]
Get:6 http://ftp.se.debian.org/debian buster/main amd64 Packages [7,907 kB]
Get:7 http://download.proxmox.com/debian buster InRelease [3,051 B]
Get:8 http://download.proxmox.com/debian buster/pve-no-subscription amd64 Packages [321 kB]
Get:9 http://ftp.se.debian.org/debian buster/main Translation-en [5,971 kB]
Get:10 http://ftp.se.debian.org/debian buster/contrib amd64 Packages [50.2 kB]
Get:11 http://ftp.se.debian.org/debian buster/contrib Translation-en [44.2 kB]
Get:12 http://ftp.se.debian.org/debian buster-updates/main amd64 Packages [7,860 B]
Get:13 http://ftp.se.debian.org/debian buster-updates/main Translation-en [5,672 B]
Fetched 14.9 MB in 3s (4,455 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
643 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@vroem:~#
root@vroem:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
cryptsetup-run : Breaks: cryptsetup (< 2:2.0.3-1) but 2:1.7.3-4 is to be installed
pve-cluster : Breaks: pve-ha-manager (<= 3.0-3) but 2.0-9 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Output of pveversion -v:
Code:
root@vroem:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-30-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 7.1-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
I've tried manually installing cryptsetup-run and pve-cluster in the hopes of getting some more info to no avail. apt --fix-broken install and dpkg --configure -a did not do anything. It seems to me manually installing these packages or different versions of the dependencies might help, but I don't want to make the situation any worse.
Any help would be greatly appreciated.
EDIT: I also checked that no packages were being held, both with apt-mark showhold and dpkg --get-selections | grep hold
Last edited: