Recent content by Moayad

Hi, Could you please post the output of `pveversion -v`? To get more info on what exactly happens, it would check the Syslog looking for any interesting error/warning message related to `pveproxy` or `pvedaemon` or `pvestatd`. UPDATE: are all the storage active i.e., up and running?

Hi, Could you please share the syslog from the node?

Hi, Do you have any HTTP proxy? Did you check the firewall? Does the issue happen on different browsers as well?

Hi, May you try to renew the certificate on your cluster using the following command? pvecm updatecerts --force If that didn't help, could you please check the syslog looking for any error message?

Hi, Have you tried to update the firmware/BIOS UEFI any other PCI driver? Could you please check the syslog from last failed boot? Do you have GPU added to your server? Could you post the output of `pveversion -v` command when you boot from an older Proxmox kernel?

Hi, I will reply to your original thread since you have the same issue https://forum.proxmox.com/threads/no-boot-after-6-8-1.145008/

Hello, We offer support only in English or German! Could you please post the output of the following: pveversion -v cat /etc/pve/storage.cfg

Hi, Could you update the certificates using the following command? pvecm updatecerts --force

Hi, Can you use request DNS using CLI?

Hi, May you post the task log of the backup job? That will help us to see why the error failed. Yes, you can clone the LXC and test to upgrade the LXC to Debian 12. To answer on the remaining questions, we to know the following: - LXC configuration - Where you are trying to backup the LXC...

Hello, When you boot from an older Proxmox-kernel you don't see any issues with your servers? If yes, you can pin the older Proxmox-kernel 6.5 [0]. [0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_kernel_pin

Hi, I would pin the older pve-kernel as mentioned below link [0] see section (Known Issues & Breaking Changes). [0] https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.2

Hi, Do you have subscription in your Proxmox VE server? I guess you have to download the deb instead of adding it in your /etc/apt/source

Hi, You can move the VM config from the offline node `mv /etc/pve/nodes/<OFFLINE NODE NAME>/qemu-server/<VMID>.conf /path/to/backup/config/file/<VMID>.conf` Or you can only edit the VM config to not boot when the offline node back online.

Hi, Do you have anyother CT on the same `SATORI` storage? I would mount the CT using this command `pct mount <CTID>` This may give you direct access to inspect its storage. You can also check the syslog to see if there is any interesting error message.