please help. stuck on grub>

girtsj

New Member
Sep 21, 2025
2
0
1
Hope someone can help me out. It is the second time it has happened after updating proxmox. I am stuck on grub> and server is not booting. My setup is traightforward - UEFI 7.0.12-1-pve install on EXT4 with 2 VMs running windows 11. Everything on one SSD.
I can boot into GUI using setup USB->advanced->recover boot. I can even start my VMs. But I am using it as a headless machine and need to boot it properly without plugging in usb, keyboard and monitor.
First time it happened after few hours of struggling i pulled the plug and decided to install everything from scratch. But as it has happened again and the system is functioning from rescue mode I am sure there is a way to recover it. Spent few hours already trying various fixes with no luck..

Let me know what info is needed for troubleshooting and I will fetch it.

Any help would be apreciated
 
Are you able to boot an older kernel? You can try to 'pin' a kernel using the `proxmox-boot-tool`.
First to list list all available kernels, if only 7.x kernels are present try installing 'proxmox-kernel-6.17' and pin that using `proxmox-boot-tool kernel pin $the_kernel_you_just_installed --next-boot` (e.g. the --next-boot flag is to only pin it for the next reboot).
 
The strange thing is, there was no kernel update during this update. Just some packages. I think it is something to do with GRUB or UEFI configuration.
Looks like proxmox-boot-tool is not present. see attachment. I have also attached lsblk and kernels installed if that helps.
 

Attachments

  • Screenshot 2026-07-06 090741.png
    Screenshot 2026-07-06 090741.png
    22.8 KB · Views: 8
  • Screenshot 2026-07-06 090741s.png
    Screenshot 2026-07-06 090741s.png
    27.2 KB · Views: 8
  • Screenshot 2026-07-06erw 090741s.png
    Screenshot 2026-07-06erw 090741s.png
    14.7 KB · Views: 8
proxmox-boot-tool exists afaik, I would assume that the command 'proxmox-boot-tool kernel list' would still show output. , i'd still suggest trying to install an older kernel (e.g. proxmox-kernel-6.17) and verifying if that helps.