No issues with nvidia dkms drivers on 6.17:
No Issues with 6.17 and 580.82.07
No issues with 6.17 and 580.95.05
(Genoa 9374f + RTX 6000 96gb)
root@pve-bdr:~# apt install proxmox-headers-6.17
The following packages were automatically installed...
kernelnewbies generally has a good list (ie https://kernelnewbies.org/Linux_6.17 https://kernelnewbies.org/Linux_6.16 and https://kernelnewbies.org/Linux_6.15), no need to use an LLM here.
I will test later today the Genoa Servers (9374F + RTX6000) -> Because one above reported dkms issues with 6.17 and Nvidia Drivers.
So Far this Servers Work:
- MS-A2 (AMD 9955HX) -> No Issues
- Genoa 9374F + RTX6000 (580.82.07 & 580.95.05) -> No...
We recently uploaded the 6.17 kernel to our repositories. The current default kernel for the Proxmox VE 9 series is still 6.14, but 6.17 is now an option.
We plan to use the 6.17 kernel as the new default for the Proxmox VE 9.1 release later in...
yes - can relate to that - it bit me while testing as well ... - We do try to add checks for more common problematic configurations to the `pve8to9` script
(using proxmox-boot-tool, while having the ESP mounted on /boot/efi is nothing I've seen...
Its a raid1 (2 disks).
Youre absolutely right, i seen this Message in other Servers and simply unmounted /boot/efi...
The Problem ist Just, on such big Upgrades where you Upgrade 600 packages, you wont See the log and simply reboot
:)
And bam...
Thanks - will try reproducing it with the 8.0 ISO - afaics it's a single disk system?
yeah it's not the most straight-forward to read - but it does contain the most information - and in that case it points us to the issue with your system:
This...
You are only wrong in one Point, that you didnt fixed the key issue, why it falls, instead you simply excluded the Volume.
Otherwise i agreed with everything else. Lxc backups are terrible.
Zfs send/receive ist truly amazing, but no GUI... So...
it's not possible to run multiple backups in parallel on a single node, there's a node-global lock protecting against that. incomplete error handling can always happen and require manual intervention, especially when interacting with storage...
But i found another pretty hefty Bug:
If a backup runs, the snapshot of an LXC container gets created always under /mnt/vzsnap0
So in the case like above, where the snapshot wont get removed, and the directory not deleted (because of the error)...
Found the issue.
rm -rf /Storage-Default/subvol-180-disk-0/opt/kerio/* -> Fixed it.
The root disk (the mountpoint of it, was not empty.
In my Case there were whyever empy folders, dunno why, maybe from beginning before i created a subvolume to...
Found the issue.
rm -rf /Storage-Default/subvol-180-disk-0/opt/kerio/* -> Fixed it.
The root disk (the mountpoint of it, was not empty.
In my Case there were whyever empy folders, dunno why, maybe from beginning before i created a subvolume to...
INFO: Starting Backup of VM 180 (lxc)
INFO: Backup started at 2025-08-12 04:17:21
INFO: status = running
INFO: CT Name: mail
INFO: including mount point rootfs ('/') in backup
INFO: including mount point mp0 ('/opt/kerio') in backup
INFO: backup...
Hi with PBS 4, there is an issue with backup'ing running LXC Containers.
When the Container is Running, i get this:
{{guestname}}
INFO: starting new backup job: vzdump 180 --notes-template '{{guestname}}' --notification-mode notification-system...
Hi,
There is also an official way to do this ;) https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#obsolete
But please make sure you have all repositories correctly configured and updated before running apt list '~o'! This...
Sorry for the late reply,
yes uefi+secure boot.
I Installed the Server on 10.Okt.2023 at 16:09:27, with Kernel 6.2.16-3, Debian 12.2.0-14 (Thats info from the oldest boot log)
So it was the Proxmox 8.0 ISO.
there is maybe broken text in the...