Recent content by RolandK

i cannot answer your specific question, but at https://ubuntu.com/certified/202302-31272 there is information that this server is certified with ubuntu. and proxmox is using ubuntu kernel

yes, there is a long thread for this already at https://forum.proxmox.com/threads/slow-memory-leak-in-6-8-12-13-pve.168961/

you can also try this method https://forum.proxmox.com/threads/proxmox-server-via-wifi-list-of-wifi-bridge-adapters-which-work-with-proxmox.161124/

you may try this way: https://forum.proxmox.com/threads/proxmox-server-via-wifi-list-of-wifi-bridge-adapters-which-work-with-proxmox.161124/

eine weitere möglichkeit besteht darin einen router zu verwenden, der den client/bridge mode beherrscht. d.h. du machst das wifi nicht auf dem pve host sondern verbindest den host via lan mit dem router im client/bridge mode. es werden noch erfahrungswerte/berichte gesucht von leuten die das...

yes, i think this is a better aproach instead of struggling with local wifi adapters & issues. have a look at https://forum.proxmox.com/threads/proxmox-server-via-wifi-list-of-wifi-bridge-adapters-which-work-with-proxmox.161124/ and report your own findings/experience with different wifi...

deine beschreibung klingt etwas wirr beschreib dein setup bitte als erstes mal etwas genauer wo ist das proxmox installiert und wie genau? partitionstabelle und zpool infos wären hilfreich

>Warum setzt man ein System in der Firma auf, was man nur mit KI eingerichtet bekommen hat weil mit KI jetzt jeder alles kann

da die website im wartungsmodus ist - was kostet denn der spass?

> Given the setup and the fact that it directly impacts the Intel E810 NIC, I also suspect it’s tied to the ice driver changes introduced in those newer kernels yes, seems so: https://securityvulnerability.io/vulnerability/CVE-2025-21981...

does your system do efi boot or grub boot ? efi boot can very picky , i have a LOT more problems with efi boot then with traditional bios/grub boot

there is another caveat: https://forum.proxmox.com/threads/help-with-trim-on-virtio-scsi-single.123819/#post-542552 i.e. it appears, that subsequent fstrim runs need a reboot in between, to be effective with ext4

there are no errors/warnings visible in any of the pbs logs on the pve host where the backup had this error i find in journalctl Sep 16 12:40:33 pve2-bnkw pvedaemon[3818711]: <root@pam> starting task UPIDve2-bnkw:003C2BCF:7C760E9F:68C93EA1:vzdump:101:root@pam: Sep 16 12:40:33 pve2-bnkw...

i manually started some backup while there was some load on the pbs disks and got "corrupted double-linked list" error once on backup. the second backup run afterwards ran fine and validating the backup did not show any error should i worry ? what does this error mean ? ... NFO: 27% (452.0...

yes, i can confirm these are both upstream issues for the groff one there is an upstream bugreport at https://bugs-devel.debian.org/cgi-bin/bugreport.cgi?bug=1101827 for the apparmor one, i don't find appropriate