Hello the community,
I really need your help today. I know this topic has already been discussed multiple time, but for now any of the answer works for me.
After migrate my pve from 7.4 to 8.4, the booting sequence is stuck without any bug visible ( I tried to run in debug=all, but I saw nothing )
Parameters:
- uefi only
- secure boot enabled ( I switched to a signed kernel 6.8.12 -13 -pve)
I tried to:
- reinstall the kernel using chroot mode, and proxmox-boot-tool reformat / reinit / refresh )
At this moment, I can just see that /etc/kernel/cmdline is missing.
- apt update - upgrade - autoremove to clean up the packages installed
- start in recovery mode -> stuck at the same moment
- try to boot with a previous kernel 5.19
- using proxmox 8.4 ISO with "boot repair"
I'm adding attached the picture of the end of the boot sequence and the grub parameters for a normal boot.
I have the feeling that proxmox does not know what to do after loading the initramfs. Maybe it happens when it loads the drivers ...... I'm running out of idea here.
Can you help me please to figure out what is the issue ?
Thanks
I really need your help today. I know this topic has already been discussed multiple time, but for now any of the answer works for me.
After migrate my pve from 7.4 to 8.4, the booting sequence is stuck without any bug visible ( I tried to run in debug=all, but I saw nothing )
Parameters:
- uefi only
- secure boot enabled ( I switched to a signed kernel 6.8.12 -13 -pve)
I tried to:
- reinstall the kernel using chroot mode, and proxmox-boot-tool reformat / reinit / refresh )
At this moment, I can just see that /etc/kernel/cmdline is missing.
- apt update - upgrade - autoremove to clean up the packages installed
- start in recovery mode -> stuck at the same moment
- try to boot with a previous kernel 5.19
- using proxmox 8.4 ISO with "boot repair"
I'm adding attached the picture of the end of the boot sequence and the grub parameters for a normal boot.
I have the feeling that proxmox does not know what to do after loading the initramfs. Maybe it happens when it loads the drivers ...... I'm running out of idea here.
Can you help me please to figure out what is the issue ?
Thanks
