{"id":1238,"date":"2022-03-14T18:39:10","date_gmt":"2022-03-14T23:39:10","guid":{"rendered":"https:\/\/lab.rapternet.us\/?p=1238"},"modified":"2022-02-11T21:03:59","modified_gmt":"2022-02-12T03:03:59","slug":"upgrading-proxmox-debian-from-6-4-to-7","status":"publish","type":"post","link":"https:\/\/lab.rapternet.us\/?p=1238","title":{"rendered":"Upgrading Proxmox Debian from 6.4 to 7"},"content":{"rendered":"\n<p>I was running upgrades one day and noticed in Proxmox that there was an error about being on an unsupported version. I hadn&#8217;t upgraded major versions since I setup the system, so now was the time to upgrade.<\/p>\n\n\n\n<!--more-->\n\n\n\n<p>The first stop was of course to the <a href=\"https:\/\/pve.proxmox.com\/wiki\/Upgrade_from_6.x_to_7.0\">Proxmox wiki<\/a> which has a good article on the upgrade path and how to traverse it. This starts with getting the system fully upgraded on the currently installed version.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">root@pve:\/# apt-get update<br>Get:1 http:\/\/security.debian.org buster\/updates InRelease [65.4 kB]<br>Get:2 http:\/\/ftp.us.debian.org\/debian buster InRelease [122 kB]<br>Hit:3 http:\/\/download.proxmox.com\/debian\/corosync-3 stretch InRelease<br>Hit:4 http:\/\/download.proxmox.com\/debian\/pve buster InRelease<br>Reading package lists\u2026 Done<br>E: Repository 'http:\/\/security.debian.org buster\/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<br>N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.<br>N: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Version' value from '10.10' to '10.11'<br>E: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<br>N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.<br>root@pve:\/# apt-get update --fix-missing<br>Get:1 http:\/\/security.debian.org buster\/updates InRelease [65.4 kB]<br>Get:2 http:\/\/ftp.us.debian.org\/debian buster InRelease [122 kB]<br>Hit:3 http:\/\/download.proxmox.com\/debian\/corosync-3 stretch InRelease<br>Hit:4 http:\/\/download.proxmox.com\/debian\/pve buster InRelease<br>Reading package lists\u2026 Done<br>E: Repository 'http:\/\/security.debian.org buster\/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<br>N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.<br>N: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Version' value from '10.10' to '10.11'<br>E: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<br>N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.<br>root@pve:\/# ^C<\/pre>\n\n\n\n<p>This was a surprising start to my upgrade adventure, but luckily has an easy fix.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>apt-get --allow-releaseinfo-change update<\/code><\/pre>\n\n\n\n<p>With that out of the way, we can continue working to updatjng our system to the latest packages before upgrading versions.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">root@pve:\/# apt-get --allow-releaseinfo-change update<br>Get:1 http:\/\/security.debian.org buster\/updates InRelease [65.4 kB]<br>Get:2 http:\/\/ftp.us.debian.org\/debian buster InRelease [122 kB]<br>Get:3 http:\/\/security.debian.org buster\/updates\/main amd64 Packages [308 kB]<br>Get:4 http:\/\/security.debian.org buster\/updates\/main Translation-en [163 kB]<br>Get:5 http:\/\/ftp.us.debian.org\/debian buster\/main amd64 Packages [7906 kB]<br>Hit:6 http:\/\/download.proxmox.com\/debian\/corosync-3 stretch InRelease<br>Hit:7 http:\/\/download.proxmox.com\/debian\/pve buster InRelease<br>Get:8 http:\/\/ftp.us.debian.org\/debian buster\/main Translation-en [5968 kB]<br>Get:9 http:\/\/ftp.us.debian.org\/debian buster\/contrib amd64 Packages [50.1 kB]<br>Fetched 14.5 MB in 6s (2319 kB\/s)<br>Reading package lists\u2026 Done<br>N: Repository 'http:\/\/security.debian.org buster\/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<br>N: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Version' value from '10.10' to '10.11'<br>N: Repository 'http:\/\/ftp.us.debian.org\/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'<\/pre>\n\n\n\n<p>Now I was able to then apt-get dist-upgrade. Onto the bigger upgrade effort.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">root@pve:~# pve6to7 --full<br>= CHECKING VERSION INFORMATION FOR PVE PACKAGES =<br><br>Checking for package updates..<br>WARN: updates for the following packages are available:<br>  pve-kernel-5.4, pve-kernel-5.4.157-1-pve, corosync, libcmap4, libwbclient0, libquorum5, libicu63, samba-libs, libvotequorum8, samba-common, libcfg7, libknet1, libsmbclient, smbclient, pve-kernel-helper, libnss3, libcpg4, libcorosync-common4<br><br>Checking proxmox-ve package version..<br>PASS: proxmox-ve package has version &gt;= 6.4-1<br><br>Checking running kernel version..<br>PASS: expected running kernel '5.4.143-1-pve'.<br><br>= CHECKING CLUSTER HEALTH\/SETTINGS =<br><br>SKIP: standalone node.<br><br>= CHECKING HYPER-CONVERGED CEPH STATUS =<br><br>SKIP: no hyper-converged ceph setup detected!<br><br>= CHECKING CONFIGURED STORAGES =<br><br>PASS: storage 'Backup-Share2' enabled and active.<br>PASS: storage 'local' enabled and active.<br>PASS: storage 'local-lvm' enabled and active.<br>PASS: storage 'local-prime' enabled and active.<br><br>= MISCELLANEOUS CHECKS =<br><br>INFO: Checking common daemon services..<br>PASS: systemd unit 'pveproxy.service' is in state 'active'<br>PASS: systemd unit 'pvedaemon.service' is in state 'active'<br>PASS: systemd unit 'pvestatd.service' is in state 'active'<br>INFO: Checking for running guests..<br>WARN: 14 running guest(s) detected - consider migrating or stopping them.<br>INFO: Checking if the local node's hostname 'pve' is resolvable..<br>INFO: Checking if resolved IP is configured on local node..<br>PASS: Resolved node IP '192.168.1.41' configured and active on single interface.<br>INFO: Checking backup retention settings..<br>WARN: storage 'local' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.<br>WARN: storage 'local-prime' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.<br>INFO: checking CIFS credential location..<br>PASS: no CIFS credentials at outdated location found.<br>INFO: Checking custom roles for pool permissions..<br>INFO: Checking node and guest description\/note legnth..<br>PASS: All node config descriptions fit in the new limit of 64 KiB<br>PASS: All guest config descriptions fit in the new limit of 8 KiB<br>INFO: Checking container configs for deprecated lxc.cgroup entries<br>PASS: No legacy 'lxc.cgroup' keys found.<br>INFO: Checking storage content type configuration..<br>PASS: no problems found<br>INFO: Checking if the suite for the Debian security repository is correct..<br>INFO: Make sure to change the suite of the Debian security repository from 'buster\/updates' to 'bullseye-security' - in \/etc\/apt\/sources.list:4<br>SKIP: No containers on node detected.<br><br>= SUMMARY =<br><br>TOTAL:    22<br>PASSED:   15<br>SKIPPED:  3<br>WARNINGS: 4<br>FAILURES: 0<br><br>ATTENTION: Please check the output for detailed information!<br>root@pve:~#<br><\/pre>\n\n\n\n<p>Following everything from the wiki after that and things went smoothly. I was able to get my upgrade drive and this got me to version 7.1-8.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"conclusion\">Conclusion<\/h2>\n\n\n\n<p>The upgrade went smoother than I expected. My system was fully upgraded and up to date afterwards and everything was running nominally. I may not have a very complex configuration but I was very happy to have it upgrade cleanly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was running upgrades one day and noticed in Proxmox that there was an error about being on an unsupported version. I hadn&#8217;t upgraded major versions since I setup the system, so now was the time to upgrade.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[26],"class_list":["post-1238","post","type-post","status-publish","format-standard","hentry","category-how-to","tag-proxmox"],"_links":{"self":[{"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/posts\/1238","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1238"}],"version-history":[{"count":11,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/posts\/1238\/revisions"}],"predecessor-version":[{"id":1713,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=\/wp\/v2\/posts\/1238\/revisions\/1713"}],"wp:attachment":[{"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1238"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1238"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lab.rapternet.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1238"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}