Search results for query: apt upgrade

  1. M

    <span>nodename</span> showing up in front of everything

    we were already 9.1 out of the gate so I was a bit surprised we had this issue, but mentioned above, a host rebuild fix it. We run FC storage and have a 3 node test cluster, so it didn't take long to get back into working again.
  2. H

    <span>nodename</span> showing up in front of everything

    FWIW - identical proble, but this is going form 8.4 to 8.4.13 upgrade from CLI using these steps: apt-cache policy pve-manager apt install pve-manager=8.4.13 apt dist-upgrade apt-mark hold proxmox-ve pve-manager apt dist-upgrade rebooted and now I have <span> tags everywhere. Single node - no...
  3. Impact

    [SOLVED] GUI Button "Remove" funktioniert nicht

    Welcher Browser wird benutzt? Sind Fehler in dessen Entwicklerkonsole? Wurden helfer Scripte benutzt? Was passiert im incognito Modus des Browsers? Was sagt apt update && apt dist-upgrade?
  4. F

    proxmox dist update kernel from 6.14.11-5-pve to 6.17.13-1-pve

    I'm having an issue with the kernel getting it to update. PVE was 9.0.x and going to 9.1.x, I had an error when it got to the kernel update (through the GUI, but am on 9.1.6 now and 6.14 works but not 6.17) I had to reboot and select the old kernel to get back in 6.14.11-5-pve I believe this...
  5. B

    New PBS installation blocked IO on all cluster VMs indefinitely

    ...to replicate it. I understand that not rebooting the PBS after running an update was an error on my part, but I'm still stunned that an apt upgrade on a single server can effectively crash every VM on the entire cluster. I installed PBS from the 4.1 ISO available from the site and ran an...
  6. O

    <span>nodename</span> showing up in front of everything

    One more time ;-( apt-get dist-upgrade or apt full-upgrade I shouldn't post having high temperature ;-(
  7. M

    <span>nodename</span> showing up in front of everything

    apt update ; apt-dist-upgrade Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://download.proxmox.com/debian/pve trixie InRelease All packages are...
  8. O

    <span>nodename</span> showing up in front of everything

    You mistyped this. apt update ; apt-dist-upgrade Edit: sorry! This time I mistyped! apt dist-upgrade
  9. M

    <span>nodename</span> showing up in front of everything

    pt update; apt dist-upgrade bash: pt: command not found The following packages were automatically installed and are no longer required: libpython3.13 python3-dateutil python3-natsort python3-simplegeneric python3-zc.lockfile libsqlite3-mod-ceph...
  10. Impact

    <span>nodename</span> showing up in front of everything

    Well that expalins it. Disable the enterprise and configure the no-subscription repos, then try apt update && apt dist-upgrade again. There should be absolutely no errors or warnings. Please don't quote every message.
  11. M

    <span>nodename</span> showing up in front of everything

    command 'apt-get update' failed: exit code 100 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...
  12. 9

    [SOLVED] PVE 8.4 zu 9.1.6 - Upgrade schlägt fehl

    Hallo zusammen, ich habe zu Hause meinen Proxmox VE Host von Version 8.4.1 auf 9.1 aktualisiert. Als Grundlage für das Upgrade habe ich den offiziellen Artikel verwendet: Upgrade von 8 auf 9. Mein Setup: Proxmox VE auf einer M.2 NVMe installiert Kein ZFS, kein Software-RAID Die...
  13. 9

    [SOLVED] PVE 8.4 zu 9.1.6 - Upgrade schlägt fehl

    Hallo zusammen, ich habe zu Hause meinen Proxmox VE Host von Version 8.4.1 auf 9.1 aktualisiert. Als Grundlage für das Upgrade habe ich den offiziellen Artikel verwendet: Upgrade von 8 auf 9. Mein Setup: Proxmox VE auf einer M.2 NVMe installiert Kein ZFS, kein Software-RAID Die...
  14. T

    [SOLVED] No /boot after PVE 8 to 9 upgrade

    Same problem for me. Boot loop after a successful upgrade from proxmox 8.4.1 to 9. I have used the @Pinochet method of booting into the upgraded proxmox with supergrub2, and then apt reinstall grub-efi-amd64 grub-install The extra thing in my case was that I booted a copy; I had the original...
  15. T

    [SOLVED] PVE 8.4.17 Recover from Crashed Upgrade

    I meant I tried to upgrade things using apt dist-upgrade but it shows there is nothing to do everything is up to date. BTW other day I was discussing things at the proxmox discord server, and someone shared this link to me...
  16. B

    Netzwerk alle paar Tage weg. Proxmox und VMs nicht mehr erreichbar

    Hallo @Raoul1963, reguläre Paket-Updates (apt update && apt dist-upgrade) könnt ihr bedenkenlos machen — der Kernel-Pin bleibt davon unberührt. Es werden zwar ggf. neuere Kernel-Pakete installiert, aber gebootet wird weiterhin in den gepinnten Kernel. Ihr verliert also keine Sicherheitsupdates...
  17. B

    Netzwerk alle paar Tage weg. Proxmox und VMs nicht mehr erreichbar

    Hallo @Raoul1963, @Karl_OS, Das ist ein bekannter Regression-Bug im Kernel 6.8.12-9-pve, der Intel e1000e NICs betrifft — ihr seid also nicht allein damit. Zum Thema Updates: Reguläre Paket-Updates (apt dist-upgrade) könnt ihr weiterhin machen — die sind sogar empfohlen (Sicherheitsfixes...
  18. T

    [SOLVED] PVE 8.4.17 Recover from Crashed Upgrade

    I tried the apt full-upgrade right now and it gave me the following errors: root@home:/tmp# apt full-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are...
  19. T

    [SOLVED] PVE 8.4.17 Recover from Crashed Upgrade

    To be honest I have tried apt full-upgrade and apt-get dist-upgrade both get stuck in the same issues.
  20. O

    [SOLVED] PVE 8.4.17 Recover from Crashed Upgrade

    I don't know if this is the reason, but in Proxmox one should NOT use apt upgrade (NOR apt-get upgrade ). Only apt full-upgrade (or apt-get dist-upgrade ). Disclaimer: I can't guarantee that in your current state of the system, running the proper command now will make it better or worse...