Updating proxmox 6.1.3 to 8.x

[Degrec]

Hello,

I am currently trying to update Proxmox from version 6.1.3 to 8.x.

After some research, I ran apt update and realized that I'm using the enterprise repository. This Proxmox installation hasn't been updating since 2021.

root@proxmox02:~# apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.es.debian.org/debian buster InRelease                         
Hit:3 http://ftp.es.debian.org/debian buster-updates InRelease                 
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
  401  Unauthorized [IP: 170.130.165.90 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease  401  Unauthorized [IP: 170.130.165.90 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Here is the content of my pve-enterprise.list file:

root@proxmox02:/etc/apt/sources.list.d# cat pve-enterprise.list
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

And my /etc/apt/sources.list file:

root@proxmox02:/etc/apt/sources.list.d# cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian buster main contrib

deb http://ftp.es.debian.org/debian buster-updates main contrib

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

Would it be safe to assume that updating the content of the pve-enterprise.list file from https://enterprise.proxmox.com/debian/pve buster pve-enterprise to deb http://download.proxmox.com/debian/pve buster pve-no-subscription and then running apt update again will resolve the issue?

Thanks in advance.

 

[leesteken]

Would it be safe to assume that updating the content of the pve-enterprise.list file from https://enterprise.proxmox.com/debian/pve buster pve-enterprise to deb http://download.proxmox.com/debian/pve buster pve-no-subscription and then running apt update again will resolve the issue?

Probably (but 6.4 has been out for support for so long that I would not call it "safe"), but you'll need to update to the latest PVE 6.4 and then to the latest PVE 7 and then 8. There are guides for that (but I could fund 6 to 7, only 7 to 8), but maybe a fresh install of PVE 8 (preferably on another system) and restore CT/VMs from backup is much easier and quicker.

 

[Degrec]

Probably (but 6.4 has been out for support for so long that I would not call it "safe"), but you'll need to update to the latest PVE 6.4 and then to the latest PVE 7 and then 8. There are guides for that (but I could fund 6 to 7, only 7 to 8), but maybe a fresh install of PVE 8 (preferably on another system) and restore CT/VMs from backup is much easier and quicker.

Best regards,

I previously migrated the VMs that we currently have in production to another Proxmox server. I will proceed with update with the assumptions that I made.

If the update fails, I will opt for a fresh installation.

Thank you.

 

[Degrec]

After realizing the kernel was not updated following the execution of the pve6to7 script, I rebooted the system. However, I encountered the following errors on the updated Proxmox server:

Failed deactivating /dve/pve/swap
A stop job is running for /dev/disk/by-uuid/d7e55187-9d02-4bef-936c-4272761e05ed
A stop job is running for /dev/disk/by-id/dm-name-pve-swap
A stop job is running for /dev/mapper/pve-swap
A stop job is running for /dev/dm-0

Additionally, I observed the error usb 5-2: device descriptor read/64, error -71 when attempting physical machine access with an usb keyboard

Is it safe to assume these issues are related to VMs running concurrently on another Proxmox server that shares the same storage? I currently cannot turn them down because it is a production machine.

 

[leesteken]

After realizing the kernel was not updated following the execution of the pve6to7 script,

That script does not do an update. It only does some automatic checks and warns about possible issues. Use the manual guide (that tells you to run this command to find possible issues) for manually upgrading from 6 to 7 (but I don't have a link for you, sorry).
The normal update procedure of apt update && apt dist-ugprade only upgrades to the latest minor version (61 to 6.4).

However, I encountered the following errors on the updated Proxmox server:

A stop job is running for /dev/disk/by-uuid/d7e55187-9d02-4bef-936c-4272761e05ed
A stop job is running for /dev/disk/by-id/dm-name-pve-swap
A stop job is running for /dev/mapper/pve-swap
A stop job is running for /dev/dm-0

Additionally, I observed the error usb 5-2: device descriptor read/64, error -71 when attempting physical machine access with an usb keyboard

Is it safe to assume these issues are related to VMs running concurrently on another Proxmox server that shares the same storage? I currently cannot turn them down because it is a production machine.

I have no idea, sorry. Is there no clue in the system log?

 

[Degrec]

That script does not do an update. It only does some automatic checks and warns about possible issues. Use the manual guide (that tells you to run this command to find possible issues) for manually upgrading from 6 to 7 (but I don't have a link for you, sorry).
The normal update procedure of apt update && apt dist-ugprade only upgrades to the latest minor version (61 to 6.4).

I have no idea, sorry. Is there no clue in the system log?

After successfully upgrading to Proxmox VE 6.4, I ran the pve6to7 script to prepare for further updates. Upon realizing that the kernel version remained outdated, I proceeded to reboot the system, where i got these errors.

The web GUI of your Proxmox server is inaccessible and i'm encountering indefinite stop job errors during reboot, so I'm unsure how to check the logs.

EDIT: I hard rebooted the machine and it seems that I can now login to the machine physically and via web gui, I'm going to continue the update process.

 

[Degrec]

I modified the sources.list and accidentally ran apt upgrade instead of pveupgrade / apt dist-upgrade as recommended and now im getting the following errors:

Checking for package updates..
WARN: updates for the following packages are available:
  perl-base, python-six, libcrypt-ssleay-perl, libhttp-message-perl, libencode-perl, libradosstriper1, ceph-common, python3-cephfs, python3-rados, python3-rbd, libboost-coroutine1.74.0, libboost-program-options1.74.0, libboost-thread1.74.0, libleveldb1d, liboath0, librabbitmq4, postfix, libicu67, librrds-perl, iptables, libip4tc2, libip6tc2, libterm-readline-gnu-perl, libnet-ssleay-perl, libcurl4, libbrotli1, libc6-dev, libcrypt-dev, libnsl-dev, libwbclient0, libicu67, libsystemd0, libpython2-stdlib, libpixman-1-0, libasound2-data, python2.7-minimal, libcrypt-openssl-random-perl, libsqlite3-0, libcephfs2, librbd1, libpython2.7, libfilesys-df-perl, python2.7, libc6, libuuid-perl, liblocale-gettext-perl, python2, python3, python3.9, udev, locales, python3-six, libopus0, libanyevent-perl, libudev1, rsyslog, libjson-xs-perl, libapt-pkg-perl, python3-pycurl, samba-libs, libldb2, libpython3.9, python3-ldb, python3-talloc, sqlite3, libiptc0, libip4tc2, gdisk, libtcmalloc-minimal4, groff-base, python3-minimal, libclone-perl, libc-bin, libpulse0, nmap, liblinear4, lua-lpeg, xfsprogs, libicu67, libinih1, python2-minimal, libvorbisenc2, libnet-dbus-perl, libpython3-stdlib, libpython3.9-stdlib, libgfortran5, samba-common, mawk, librrd8, ceph-fuse, libpam-systemd, libgstreamer-plugins-base1.0-0, libsndfile1, libgoogle-perftools4, libyaml-libyaml-perl, libcrypt-openssl-rsa-perl, systemd, libip4tc2, libsdl1.2debian, libcrypt-openssl-bignum-perl, libtemplate-perl, liblua5.3-0, libauthen-pam-perl, libcommon-sense-perl, iproute2, libbpf0, libxml-libxml-perl, libsmbclient, smbclient, libjemalloc2, libnss-systemd, libasound2, libxtables12, libc-dev-bin, libxml2, libicu67, libflac8, libpython2.7-minimal, libfreetype6, libbrotli1, perl, perl-modules-5.32, libperl5.32, libxml-parser-perl, liblinux-inotify2-perl, libvorbis0a, libcairo2, libpython2.7-stdlib, libtext-iconv-perl, curl, nmap-common, libhtml-parser-perl, python3-chardet, libgstreamer1.0-0, librados2, libboost-iostreams1.74.0, libboost-thread1.74.0, procmail, libnspr4, libcurl3-gnutls, libbrotli1, python3-apt, distro-info-data, libxslt1.1, libtext-charwidth-perl, libslang2, libpng16-16

After running pveupgrade

root@proxmox02:/etc/apt# pveupgrade
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 were automatically installed and are no longer required:
  bsdmainutils libfuse3-3 libqrencode4 proxmox-archive-keyring proxmox-backup-client proxmox-backup-file-restore proxmox-backup-restore-image pve-kernel-5.4
  pve-lxc-syscalld qrencode zstd
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  criu libldb1 libpve-access-control libpve-cluster-api-perl libpve-guest-common-perl libpve-storage-perl libpve-u2f-server-perl libpython-stdlib librados2-perl
  lxc-pve proxmox-ve pve-cluster pve-container pve-firewall pve-ha-manager pve-manager python python-argcomplete python-cephfs python-certifi python-chardet
  python-configparser python-future python-idna python-ipaddr python-minimal python-prettytable python-protobuf python-rados python-rbd python-requests
  python-talloc python-urllib3 python3.7 qemu-server
The following NEW packages will be installed:
  alsa-topology-conf alsa-ucm-conf distro-info-data libboost-context1.74.0 libboost-coroutine1.74.0 libboost-iostreams1.74.0 libboost-program-options1.74.0
  libboost-thread1.74.0 libbpf0 libbrotli1 libc-devtools libcrypt-dev libdeflate0 libgd3 libicu67 libinih1 libip4tc2 libip6tc2 libjbig0 libldb2 libleveldb1d
  liblinear4 libmpdec3 libnsl-dev libnss-nis libnss-nisplus liboath0 libperl5.32 libpython3.9 libpython3.9-minimal libpython3.9-stdlib librabbitmq4 libtiff5
  libtirpc-dev libwebp6 libxpm4 lua-lpeg perl-modules-5.32 python3-ceph-argparse python3-cephfs python3-ldb python3-rados python3-rbd python3-talloc python3.9
  python3.9-minimal systemd-timesyncd
The following packages will be upgraded:
  ceph-common ceph-fuse curl gdisk groff-base iproute2 iptables libanyevent-perl libapt-pkg-perl libasound2 libasound2-data libauthen-pam-perl libc-bin
  libc-dev-bin libc6 libc6-dev libcairo2 libcephfs2 libclone-perl libcommon-sense-perl libcrypt-openssl-bignum-perl libcrypt-openssl-random-perl
  libcrypt-openssl-rsa-perl libcrypt-ssleay-perl libcurl3-gnutls libcurl4 libfilesys-df-perl libflac8 libfreetype6 libgfortran5 libgoogle-perftools4
  libgstreamer-plugins-base1.0-0 libgstreamer1.0-0 libhtml-parser-perl libhttp-message-perl libiptc0 libjemalloc2 libjson-xs-perl liblinux-inotify2-perl
  liblocale-gettext-perl liblua5.3-0 libnet-dbus-perl libnet-ssleay-perl libnspr4 libnss-systemd libopus0 libpam-systemd libpixman-1-0 libpng16-16 libpulse0
  libpython2-stdlib libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3-stdlib librados2 libradosstriper1 librbd1 librrd8 librrds-perl
  libsdl1.2debian libslang2 libsmbclient libsndfile1 libsqlite3-0 libsystemd0 libtcmalloc-minimal4 libtemplate-perl libterm-readline-gnu-perl
  libtext-charwidth-perl libtext-iconv-perl libudev1 libuuid-perl libvorbis0a libvorbisenc2 libwbclient0 libxml-libxml-perl libxml-parser-perl libxml2
  libxslt1.1 libxtables12 libyaml-libyaml-perl locales mawk nmap nmap-common perl perl-base postfix procmail python-six python2 python2-minimal python2.7
  python2.7-minimal python3 python3-apt python3-chardet python3-minimal python3-pycurl python3-six rsyslog samba-common samba-libs smbclient sqlite3 systemd
  udev xfsprogs
109 upgraded, 47 newly installed, 35 to remove and 0 not upgraded.
Need to get 0 B/109 MB of archives.
After this operation, 122 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 147 new packages)

Have I completely messed it up, or is there something I can do to fix it?

EDIT: I'm thinking about just booting an iso with proxmox 8, I think it will be easier than trying to fix this. Is there any other files I should backup besides the ones mentioned in the wiki(/etc/passwd, /etc/network/interfaces, /etc/resolv.conf)?

 

[Kingneutron]

https://github.com/kneutron/ansitest/tree/master/proxmox

Look into the bkpcrit script, it does no harm to backup all of /etc and some other critical dirs