Recent content by Ramalama

Btw, thanks @proxmox Team for fixing this! Really appreciated!

In the meantime there is one more thing you need as Workaround. On my 24.04 LXC Containers i need: apt install containerd.io=1.7.28-1~ubuntu.24.04~noble And additionally now in /etc/docker/daemon.json { "min-api-version": "1.24" } Without the min-api-version, traefik wont work anymore. -->...

https://forum.proxmox.com/threads/opt-in-linux-6-17-kernel-for-proxmox-ve-9-available-on-test-no-subscription.173920/post-808772 Im now at 6.17.2 + 580.105.08 and everything still works without issues. No issues with dkms and nvidia at all. Actually im pretty happy with the 6.17 Kernel, because...

On-Die ECC has no error reporting or edac or anything. On Die ECC is just for the memory module itself due to the high frequency it was simply needed. Im sure they talk about "real" ECC, since normal ECC has error reporting (sometimes not), but EDAC Support anyway.

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 and are no longer required...

That was gemini research lol, i didnt thought that deep research can hallucinate, xD

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 Issues - .... Just for those who are Curious...

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, you have to recover with the iso xD Ist there...

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 its Not a solution for "Not Linux affine" admins in...

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), all following lxc backups will fail in that...

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 that mountpoint inside the container... But for...

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 that mountpoint inside the container... But for...

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 mode: snapshot INFO: ionice priority: 7 INFO...

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 --storage Backup-SAS --remove 0 --mode snapshot...

lol, thank you, so easy :-)