Search results for query: apt upgrade

OK, so it wasn't the specific of apt update, but in NOT performing an apt dist-upgrade. As per https://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_8.x_to_latest_8.4. That now makes sense, and I appreciate the guidance [note to self, Proxmox on Debian != Debian]...

You shouldn't.

I would run apt update then apt upgrade and reboot the node, then try to install again. AND check the status of the dpkg log files iin /var/log - expect to see each package update appear at least three times, for example 2026-04-23 08:41:23 trigproc man-db:amd64 2.11.2-2 <none> 2026-04-23...

Update I click on (and aborted) an upgrade through the GUI and get the following, should I still be concerned with apt updates and 'wrong' repositories ? Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information...

It didn't for me. Either the OP is using the testing repos, in which case it might be already updated by apt by default (not sure), or OP deliberately installed the new kernel. EDIT: The OP was actually talking about Proxmox Backup Server, but according to the opening post, if I understand...

...on the second node generates the Update prompt also, so I am going to fix dpkg first.oo Ch Tried fixing dpkg, ran apt update, ran apt upgrade, node now completely borked. Will not boot using any existing boot image nor into recovery mode, stalls at about 5 seconds in.. It is version 8.x...

It is not (yet) installed automatically during updates, at least not if you’re using the non-subscription repositories. You have to explicitly install it via apt install proxmox-kernel-7.0. How do I know? I’m using the non-subscription repositories and just ran an apt full-upgrade on PBS and...

Hmm, I didn't know about that repos, and I don't think my setup is better, and especially, I do get the hostname/dhcp after cloudinit is done, as deploy is done on a deploying DHCP setup).. and there are specific bits to it such as IIRC: LVM with swap and root LVs sudo user/password set to...

Thanks, didn't help; Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Your System is up-to-date ... sudo...

I found the solution! The error was misleading according to the zpool stuff. The issue was that for some reason, the upgrade procedure switched grub-efi to the bios version of grub. By following these steps: # Mount root mount /dev/mapper/pbs-root /mnt # Check what's in /boot — is it on the...

Hi, PMG doesn't touch sshd_config by itself. In this case I suspect 2 possible ways it could have happened: Ansible hardening role — Roles like dev-sec.ssh-hardening (or similar CIS/STIG-based hardening playbooks) explicitly set AllowTcpForwarding no as a security best practice. If your...

For anyone still troubled by this issue, upgrading the drive firmware to the latest version can resolve it. My drive has been running normally for two weeks after the upgrade (without any other special configurations). You can download the latest firmware from...

da würde ich nochmal das /var/log/apt/term.log (und history.log) vom system bei dem das upgrade fehlgeschlagen ist durchsehen - da sollte stehen wo es angefangen hat schief zu gehen. sonst auch das journal durchsehen - da steht vl. noch warum die services nicht starten können auf den ersten...

...und bin anschließend der Anleitung gefolgt: https://pmg.proxmox.com/wiki/Upgrade_from_8_to_9 Meldung von pmg8to9 nach apt update && apt upgrade: 20:09/0 pmg ~ # pmg8to9 perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset)...

web ui is black with this error: this issue seems like old thread I followed the path to upgrade 3.4 to 4 but after reboot i assume i did something wrong: running proxmox-backup-manager versions --verbose proxmox-backup 4.0.0 running kernel: 6.17.13-2-pve...

Hi, I managed to upgrade to 9.17, I skipped the 'Update the Ceph Package Repository' section (just the homelab setup, not hyper-converged). Reboots, initial checks, LXC's seem to be running fine. I think I did the step 'Then remove the previous Proxmox VE 8 no-subscription repository from...

Here you go - in case you've not already found it this is courtesy of @uzumo in this thread...

Hey all, please be patient: I'm an absolute noob, I don't know what I'm doing :) Since yesterday, the download speed of my Proxmox VE 8.4.18 node ('cause I still have 900 Mb/s on my other equipments, including on the switch where the node is plugged in) has brutally dropped from 900 Mb/s...

I would like to get comments on my steps which I am planning to do First change the repository echo "deb http://download.proxmox.com/debian/ceph-reef bookworm no-subscription" > /etc/apt/sources.list.d/ceph.list in this way from queny debian to reef debian , we do then apt update apt...

Hi everyone, I'm currently managing a Proxmox Backup Server (PBS) instance that's running out of storage space in the datastore. My current environment is PBS based on Debian Bookworm, which uses ZFS 2.2.6. As many of you know, older ZFS versions do not support adding a single drive to an...