Proxmox Update 6.x --> 7.x
-
-
Hab ich nun ein update gemacht oder nicht? pve-Manager müsste doch auch 7.x sein, oder?
proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.4: 6.4-7 pve-kernel-5.13.19-1-pve: 5.13.19-3 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-4.15: 5.4-6 pve-kernel-4.15.18-18-pve: 4.15.18-44 pve-kernel-4.15.17-1-pve: 4.15.17-9 -
Sollte nach Proxmox eigentlich so aussehen:
pve-server:~# pveversion -v proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-4 (running version: 7.1-4/ca457116) -
@meister-mopper in der Tat läuft das Upgrade nicht durch bei mir obwohl er sehr viele Updates findet.
Ist die sources.list korrekt?#deb http://ftp.debian.org/debian bullseye main contrib #deb http://ftp.debian.org/debian bullseye-updates main contrib # PVE pve-no-subscription repository provided by proxmox.com, # NOT recommended for production use deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription deb http://ftp.de.debian.org/debian bullseye main contrib deb http://ftp.de.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org bullseye-security main contrib #deb http://deb.debian.org/debian-security bullseye-security mainapt update:
root@proxmox:/# apt update Hit:1 http://download.proxmox.com/debian/pve bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://download.proxmox.com/debian/pve buster InRelease Hit:4 http://ftp.de.debian.org/debian bullseye InRelease Hit:5 http://ftp.de.debian.org/debian bullseye-updates InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 193 packages can be upgraded. Run 'apt list --upgradable' to see them. root@proxmox:/#apt upgrade:
root@proxmox:/# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: .............. 0 upgraded, 0 newly installed, 0 to remove and 193 not upgraded. -
@lobomau
hast Du das nach der Anleitung gemacht ? -
- du hast noch eine buster-Quelle für Proxmox in apt - besser mal löschen
- mach‘ mal ‚apt dist-upgrade‘ statt nur ‚upgrade‘
-
Edit2: ups... grad neugestartet und es wird 7.x angezeigt:
Achso... der error kommt weil da irgendwie eine enterprise quelle drin. Hmm. Komisch.proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-7 (running version: 7.1-7/df5740ad) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.4: 6.4-7 pve-kernel-5.13.19-1-pve: 5.13.19-3 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-4.15: 5.4-6 pve-kernel-4.15.18-18-pve: 4.15.18-44 pve-kernel-4.15.17-1-pve: 4.15.17-9 ceph-fuse: 14.2.21-1@jleg @dslraser ja, ich war nach Anleitung vorgegangen. Nun habe ich aber mal 'Y' gedrückt anstatt 'N' wie default:
Configuration file '/etc/apt/sources.list.d/pve-enterprise.list' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** pve-enterprise.list (Y/I/N/O/D/Z) [default=N] ?Aber ob es nun geklappt hat?
Configuration file '/etc/vzdump.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** vzdump.conf (Y/I/N/O/D/Z) [default=N] ? Y Installing new version of config file /etc/vzdump.conf ... Created symlink /etc/systemd/system/multi-user.target.wants/pvescheduler.service → /lib/systemd/system/pvescheduler.service. found static machine-id bug from Proxmox VE ISO installer <= 5.4, regenerating machine-id be4611b4b1d2406c9d98ede2cc7503df new machine-id generated, a reboot is recommended Backing up lvm.conf before setting pve-manager specific settings.. '/etc/lvm/lvm.conf' -> '/etc/lvm/lvm.conf.bak' Setting 'global_filter' in /etc/lvm/lvm.conf to prevent zvols from being scanned: global_filter=["a|.*|"] => global_filter=["r|/dev/zd.*|"] Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-2) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1) ... Processing triggers for mailcap (3.69) ... Processing triggers for pve-ha-manager (3.3-1) ... Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.13.19-1-pve Running hook script 'zz-proxmox-boot'.. Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. Processing triggers for libc-bin (2.31-13+deb11u2) ... W: Operation was interrupted before it could finish root@proxmox:~#Sieht nicht so aus. Geht nicht mal mehr apt update:
root@proxmox:~# apt update Hit:1 http://download.proxmox.com/debian/pve bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://download.proxmox.com/debian/pve buster InRelease Hit:4 http://ftp.de.debian.org/debian bullseye InRelease Hit:5 http://ftp.de.debian.org/debian bullseye-updates InRelease Err:6 https://enterprise.proxmox.com/debian/pve bullseye InRelease 401 Unauthorized [IP: 212.224.123.70 443] Reading package lists... Done E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 212.224.123.70 443] E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye 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. root@proxmox:~#Edit.:
sources.list habe ich so wie aus https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_no_subscription_repo übernommen.Das habe ich auch gemacht:
wget https://enterprise.proxmox.com/debian/proxmox-release-bullseye.gpg -O /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpgAus dem Folgenden werde ich nicht schlau. Was für ein cli tool?? "proxmox-release-bullseye.gpg" ist vorhanden. Darin ist wohl dieser Code um checken ob es echt ist oder wie soll man das verstehen?:
*Verify the checksum afterwards with the sha512sum CLI tool:
sha512sum /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg
7fb03ec8a1675723d2853b84aa4fdb49a46a3bb72b9951361488bfd19b29aab0a789a4f8c7406e71a69aabbc727c936d3549731c4659ffa1a08f44db8fdcebfa /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg* -
Du musst die enterprise.list editieren.
sudo nano /etc/apt/sources.list.d/pve-enterprise.listund dort ein hashtag vor die Zeile setzen:
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise -
@meister-mopper ah, danke. Ich dachte mir schon dass es irgendwo noch so eine Liste geben muss
root@proxmox:~# nano /etc/apt/sources.list.d/pve-enterprise.list root@proxmox:~# apt update Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://ftp.debian.org/debian bullseye InRelease Get:3 http://download.proxmox.com/debian/pve bullseye InRelease [3,053 B] Hit:4 http://ftp.debian.org/debian bullseye-updates InRelease Hit:5 http://download.proxmox.com/debian/pve buster InRelease Fetched 3,053 B in 2s (1,629 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. root@proxmox:~# -
Hallo
@crunchip @Meister-MopperIch möchte demnächst von 7.x auf 8.x upgraden.
Allerdings steh ich schon wieder an (und Tante G will mir nichts sagen).
root@proxmox:~# pve7to8 -bash: pve7to8: command not foundwarum findet der das nicht?
Läuft der Befehl erst mit 7.4? -
@negalein sagte in Proxmox Update 6.x --> 7.x:
Läuft der Befehl erst mit 7.4?
ja 7.4 wird benötigt
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
