Search results

I am now very happy I never upgrade before the first point release is available ;) I hope for native support in Truenas Scale so we can skip the plugin entirely and avoid the patching of Proxmox.

What specific plugin do you refer to?

Maybe your package cache is filling your disk so try to clean it to increase free space: sudo apt-get clean

I can confirm that. Thanks to PVE;)

Hi Fiona, Already available. That was quick :)

That did not solve it in my case. A combination of the update and HaProxy.

Also reported on the German language forum as well: https://forum.proxmox.com/threads/proxmox-pve-proxy-h%C3%A4ngt-sich-immer-auf.164744/post-762074. Seems patches are already made ;-)

Downgrading to 5.2.0 and everything works as expected again? apt install libpve-http-server-perl=5.2.0

Error log flooded with: detected empty handle Can't use an undefined value as a symbol reference at /usr/share/perl5/PVE/APIServer/AnyEvent.pm line 150 After this starts pvemanager is not accessible anymore. I have tried this: apt reinstall libanyevent-perl libpve-http-server-perl but the same...

Solve: A network cable was disconnected ;-)

One node in a cluster of two nodes. One node shows proper statistic but the other does not for any VM's. Clicking on the node itself gives this error message: api error (status = 400 Bad Request): api error (status = 595 <unknown status code>): See attached screendump.

Try read the entire thread before making assumptions. The reason is explained here: https://forum.proxmox.com/threads/pve-8-0-and-8-1-hangs-on-boot.137033/post-609320 which also explains why this has nothing todo with the kernel but was related to living out a module from the initramfs which was...

Try read the entire thread before making assumptions. The reason is explained here: https://forum.proxmox.com/threads/pve-8-0-and-8-1-hangs-on-boot.137033/post-609320 which also makes it obviously way you see no problems on proxmox 7.4

Yep, that did the trick :) The fix enables booting on these kernels: - 5.15.126-1-pve - 6.2.16-19-pve - 6.5.11-4-pve Thank's Thomas :cool: To recap in case other comes to this thread: echo "simplefb" >> /etc/initramfs-tools/modules update-initramfs -u -k 6.5.11-4-pve (or update-initramfs -u...

Seems it is the initrd build system on 8.0 and 8.1 which is making unbootable initrd files because if I build a initrd file for pve-kernel-5.15.126-1-pve: 5.15.126-1 on 8.1 the system cannot boot using the pve-kernel-5.15.126-1-pve: 5.15.126-1 an showing exactly the same as for kernel > 6.1...

proxmox-kernel-6.2.16-19-pve same problem

nomodeset was enabled. This is wat I see after adding earlyprintk=vga which is exactly the same as I saw before, no output what so ever To me it looks like a kernel segfault . networking is enabled (management interface: $ ping -c1 esx2 PING esx2.datanom.net (172.16.3.9) 56(84) bytes of data...

Forgot: $ sudo pveversion -v [sudo] password for mir: proxmox-ve: 8.1.0 (running kernel: 5.15.126-1-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.0.9 pve-kernel-5.15: 7.4-7 proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4 proxmox-kernel-6.5: 6.5.11-4...

Hi all, Serious problem with proxmox-kernel-6.2 (proxmox-kernel-6.2.16-19-pve) and proxmox-kernel-6.5 (proxmox-kernel-6.5.11-4-pve-signed) previous kernels proxmox-kernel-6.1 and the one I currently boots on pve-kernel-5.15.126-1-pve works as expected. The symptom is that when boot sequence...

After upgrading to this kernel sensor readings through i2c is broken. The console is spammed with these messages: [24271.599465] i2c i2c-0: Failed! (01) Booting on kernel pve-kernel-5.15.83-1-pve and sensor reading is restored and no i2c errors in the log. Hardware: System Information...