NEWS
Update auf Proxmox 8 Problem
-
Hallo Zusammen
Bin ein Linux Anfänger und wagte mich ans update...gemäss Doku
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8lief auch soweit gut. bis ca 97%
Dann kamen diese Fragen mit:/etc/issue -> Proxmox VE will auto-generate this file on boot, and it has only cosmetic effects on the login console. Using the default "No" (keep your currently-installed version) is safe here. /etc/lvm/lvm.conf -> Changes relevant for Proxmox VE will be updated, and a newer config version might be useful. If you did not make extra changes yourself and are unsure it's suggested to choose "Yes" (install the package maintainer's version) here.
Da habe ich aus Neugier/Dummheit mal d (show difference) gedrückt.
Anstatt yes oder no wie in der Doku
Wie komme ich von da wieder zurück um die Installation weiterzufahren?Grüsse
Nachtrag:
Via Putty geht noch was und das kommt mit: pve7to8root@pve:~# pve7to8 = CHECKING VERSION INFORMATION FOR PVE PACKAGES = Checking for package updates.. PASS: all packages up-to-date Checking proxmox-ve package version.. PASS: already upgraded to Proxmox VE 8 Checking running kernel version.. WARN: unexpected running and installed kernel '5.15.158-2-pve'. = CHECKING CLUSTER HEALTH/SETTINGS = SKIP: standalone node. = CHECKING HYPER-CONVERGED CEPH STATUS = SKIP: no hyper-converged ceph setup detected! = CHECKING CONFIGURED STORAGES = PASS: storage 'local' enabled and active. PASS: storage 'local-lvm' enabled and active. INFO: Checking storage content type configuration.. PASS: no storage content problems found PASS: no storage re-uses a directory for multiple content types. = MISCELLANEOUS CHECKS = INFO: Checking common daemon services.. PASS: systemd unit 'pveproxy.service' is in state 'active' PASS: systemd unit 'pvedaemon.service' is in state 'active' PASS: systemd unit 'pvescheduler.service' is in state 'active' PASS: systemd unit 'pvestatd.service' is in state 'active' INFO: Checking for supported & active NTP service.. PASS: Detected active time synchronisation unit 'chrony.service' INFO: Checking for running guests.. PASS: no running guest detected. INFO: Checking if the local node's hostname 'pve' is resolvable.. INFO: Checking if resolved IP is configured on local node.. PASS: Resolved node IP '192.168.1.201' configured and active on single interface. INFO: Check node certificate's RSA key size PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048) PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048) INFO: Checking backup retention settings.. PASS: no backup retention problems found. INFO: checking CIFS credential location.. PASS: no CIFS credentials at outdated location found. INFO: Checking permission system changes.. INFO: Checking custom role IDs for clashes with new 'PVE' namespace.. PASS: no custom roles defined, so no clash with 'PVE' role ID namespace enforced in Proxmox VE 8 INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded.. WARN: systems seems to be upgraded but LXCFS is still running with FUSE 2 library, not yet rebooted? INFO: Checking node and guest description/note length.. PASS: All node config descriptions fit in the new limit of 64 KiB PASS: All guest config descriptions fit in the new limit of 8 KiB INFO: Checking container configs for deprecated lxc.cgroup entries PASS: No legacy 'lxc.cgroup' keys found. INFO: Checking if the suite for the Debian security repository is correct.. PASS: found no suite mismatch INFO: Checking for existence of NVIDIA vGPU Manager.. PASS: No NVIDIA vGPU Service found. INFO: Checking bootloader configuration... PASS: bootloader packages installed correctly INFO: Check for dkms modules... SKIP: could not get dkms status SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter = SUMMARY = TOTAL: 30 PASSED: 24 SKIPPED: 4 WARNINGS: 2 FAILURES: 0 ATTENTION: Please check the output for detailed information!
-
@mickemup sagte in Update auf Proxmox 8 Problem:
Wie komme ich von da wieder zurück um die Installation weiterzufahren?
Mit
q
in der Regel. -
@thomas-braun
Danke habs nun hingekriegt
Und scheint alles wieder zu laufen.