Wie meinst du das? Ist das ein Unterschied ob ich es über die Oberfläche von Proxmox mache oder über die Console im Paperless Container. Ich hatte gedacht, dass das technisch am Ende das gleiche ist?!
Hast du eine zu empfehlende Anleitung dazu?
After cleaning all the open sessions and running the last step i got this error.
~# /usr/share/pve-manager/migrations/pve-cephx-rotate-service-keys --apply --confirm-all-clients-refreshed --restrict-ciphers
INFO: Recovery and confirmations may...
Hello,
I am seeing similar behaviour on a Debian Linux VM running Checkmk in my Proxmox cluster.
Current package versions:
- pve-manager: 9.2.21
- qemu-server: 9.2.10
- pve-qemu-kvm: 11.0.3-4
- Kernel: 7.0.14-20-pve
On October 1, I updated the...
it sounds like this issue
https://forum.proxmox.com/threads/evpn-network-segmentation.180785/
is there a roadmap when the issue will solved ? any timeline ?
Dear @HammyHavoc @SInisterPisces ,
I've pushed the ARM64 version onto my unofficial proxmox backup client repository .
I haven't any raspi to try it seriously, but should works as other we only repackage the official static binary (test one...
Hi there!
I had to do the cephx keyring migration by hand since I have a Ceph cluster member which is not part of my PVE cluster. I followed the upstream guide from ceph.com and had a healthy cluster at some point. That is after I rebooted every...
9.2 will not install it keeps giving me an error. I put 8.4 back on. I have 2 1tb drives I want to add to proxmox which has my backups on them. I see the disks listed under disks. How do I import them back in so I can access the data?
Curious as to if I should delete the contents of "/lib/firmware/intel-ucode" and then copy the new microcode files before attempting to update initramfs again. (Trying to avoid boot issues by doing something stupid, so I'm trying to see if this...
I would test installing it, maybe quicker than waiting for a reply. It would also be useful to know if 7.0.14-19 works ok for you, to narrow the problem down
+1 To this issue, i haven't done any tests on kernel 7 other than checking logs after boot and its still being spammed with the same AER errors.
also done test on 7.0.14-4, -5, -8, -12, -14, -16, -17, and -19
Currently pinned to 6.17.13-21-pve...
add more Ram to increase the ARC and/or experiment with "cache=meta-data-only"
add some good NVMe/SSDs as a mentioned "Special Device"; note that only new data will land there - but there is a helping command for this
experiment with a Cache...
We hit the same error today and found the cause on our side: a second systemd-udevd left over from the initramfs. Killing it fixed the problem right away. Maybe worth checking on the affected hosts in this thread:
ps -eo pid,cgroup,args | grep...
Thank you for the information. I ran into an issue when running the listed commands. (No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.) I was able to resolve this by running "proxmox-boot-tool init" after confirming that...
I ran a few more tests. Ubuntu 26.04 with the latest kernel I found at https://kernel.ubuntu.com/mainline (7.3.0-rc3) exhibits the same behavior.
At https://lists.openwall.net/linux-kernel/2026/09/04/1960, there’s a proposed patch for Kernel 7.4...