Search results for query: apt upgrade

Either you missed a step in the upgrade guide or something else is wrong with your repository configuration. There are existing threads about You are attempting to remove the meta-package 'proxmox-ve'! which might help in troubleshooting this. Double check that you only have the trixie...

What started me down this path I got to the apt dist-upgrade the process failed with message !! WARNING !! You are attempting to remove the meta-package 'proxmox-ve'! A bit further down on the screen message If you are unsure why 'proxmox-ve' would be removed, please verify -your apt repository...

I tried updating my PBS from 6.8.12-18 to 6.8.12-20 and received an error. Here's the console output (errors have been put in bold: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were...

...browser with Ctrl + F5 after running this. the only problem is that this solution will work untell you run an apt updare < or apt upgrade because the pve-manage may reinstall again with the official pvemanagerlib.js that will bring you back to square one the...

A few questions and observations that might help narrow this down: How was the reinstall done? PVE ships `pveceph purge` specifically for this scenario — it stops all Ceph services, wipes `/var/lib/ceph/{mon,mgr,mds,osd,...}/` (including the monitor's RocksDB), and removes the keyrings and...

I tried to investigate further, but I didn't come closer to a solution: apt dist-upgrade installs the new kernel and it is reported as available by proxmox-boot-tool kernel list But - and this is the weird part - it is not selected for (re-)booting. I also tried to pin the kernel, but this did...

I retried the upgrade with the exact same outcome: booted into PVE9 with old kernel. This time, I made sure to execute the steps mentioned above. During the source list update, I was warned that /etc/apt/sources.list.d/pve-install-repo.list also needed the trixie sources - which I updated...

As far as I can remember, I followed the exact commands from https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 apt update apt dist-upgrade ======= sed -i 's/bookworm/trixie/g' /etc/apt/sources.list sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/pve-enterprise.list ======= apt update...

I planned to upgrade from PVE 8 to 9 this weekend. In preparation, I ran pve8to9 --full and received the bootloader info message: INFO: Checking bootloader configuration... FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove...

Hello, yesterday I replace a harddrive in my zfs raid. After this I execute the following command. zpool replace rpool 18419091268690890705 /dev/disk/by-id/ata-WDC_WD4005FFBX-68CAUN0_WD-AS05X86R Tonight the process was successfully and the ZFS Raid is online again. Now I installed the last...

I assume after reading the link provided you didn't want me to run the apt upgrade -y ....so i didn't. thank you kindly good sir

That looks like a failed/partial upgrade. Please share the output of this apt update apt dist-upgrade pveversion -v I'd stop reading here. This guide cannot be trusted.

This issue appears after upgrading from latest 3.4 to version 4.

Is this shutdown manually triggered, e.g. by stopping the systemd service? What is the current status of the services? systemctl status proxmox-backup.service proxmox-backup-proxy.service Edit: Also, since which upgrade does this happen? Can you identify the previously working version, e.g. by...

hi, i changed mtu of all the Vm manually through GUI, it take a bit long time , but done, thanks a lot IIRC apt, is showing a messsage to use apt autoremove to remove these packages, but i am still a little bit scared, if some reason it failed, if boot failed, using rescue mode in proxmox iso...

apt dist-upgrade

Hi all, Have a 4 node cluster, ran the latest debian upgrade on a node running Linux 6.17.13-2-pve (2026-03-13T08:06Z). ssh and openssh-server failed to install, tried again got following output. Unable to open syslog: Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }...

Thank you for sharing, @Hank42. In your post #25, it stood out to me that you mentioned holding some packages while upgrading others. In general, this is not a good idea. The various components of the system are interconnected, and partial upgrades can easily lead to inconsistencies. Unless...

hi, thanks for your reply, and sorry for my late reply the reason i manually edited the VM config file is there is more than 50 vm running in the cluster, and manually changing there mtu value going to each vm is time consuming and repeatitave, this reason i am planninmg the floowing script:-...

No helper scripts - fresh install of 8.4 - > upgrade to 8.4.13 (adding to an existing cluster is the goal). Hoping this helps someone else as I found the root cause and fixed my issue . To resolve the issue, I did a force (re)install of proxmox-widget-toolkit to my specific version...