[SOLVED] - Stuck on "Welcome to GRUB" after update

Hi,

First of all I'm a newbie to Linux and Proxmox so please keep it simple

I've runned Proxmox for a while now and updated previously without issues.
But today I installed the pending updates and it mentioned a new kernel so I rebooted.
I then got stuck on a screen saying "Welcome to GRUB" and nothing more.

I've managed to bypass this using the Proxmox ISO and Rescue boot so I can atleast use Proxmox.
But everytime I reboot I need to use the Proxmox ISO to boot it.

I don't know what happened with GRUB or how to solve it. Anyone who can help me?

Can you post output for the following:

Code:

cat /var/log/apt/term.log | grep -C 4 "Removable bootloader found"

Code:

Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

Removable bootloader found at '/boot/efi/EFI/BOOT/BOOTX64.efi', but GRUB packages not set up to update it!
Run the following command:

echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u

I suspected so. If you have not already run the suggested command when it appeared while upgrading, (I guessed you may have missed it), do so now.

So enter in the Proxmox host:

Code:

echo 'grub-efi-amd64 grub2/force_efi_extra_removable boolean true' | debconf-set-selections -v -u

I ran the command and rebooted. But still get stuck on same screen.
So I reinserted my Ventoy USB with Proxmox ISO and got it running again.

Any other suggestions?

What does efibootmgr -v show?

Code:

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0001,0000
Boot0000* proxmox       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
Boot0001* UEFI OS       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0002* UEFI: VerbatimViasat PMAP, Partition 2        PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/USB(8,0)/HD(2,MBR,0x7c1301ac,0x39a4000,0x10000)..BO

Try the following:

Reboot without the Ventoy disk, & enter the BIOS
Then select/set the "proxmox" entry as the boot device.

In BIOS it mentions a HDD with UEFI OS, nothing regarding proxmox, but it's the same drive, so I selected that one, and that's how it was from the beginning.
I still get the same screen and stuck again.

Code:

NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                            8:0    0 465.8G  0 disk
├─sda1                         8:1    0  1007K  0 part
├─sda2                         8:2    0     1G  0 part /boot/efi
└─sda3                         8:3    0 464.8G  0 part
  ├─pve-swap                 252:0    0     8G  0 lvm  [SWAP]
  ├─pve-root                 252:1    0    96G  0 lvm  /
  ├─pve-data_tmeta           252:2    0   3.4G  0 lvm 
  │ └─pve-data-tpool         252:4    0 337.9G  0 lvm 
  │   ├─pve-data             252:5    0 337.9G  1 lvm 
  │   ├─pve-vm--101--disk--0 252:6    0    64G  0 lvm 
  │   ├─pve-vm--106--disk--0 252:7    0     8G  0 lvm 
  │   ├─pve-vm--107--disk--0 252:8    0    64G  0 lvm 
  │   ├─pve-vm--103--disk--0 252:9    0     8G  0 lvm 
  │   ├─pve-vm--104--disk--0 252:10   0     2G  0 lvm 
  │   ├─pve-vm--110--disk--0 252:11   0     8G  0 lvm 
  │   ├─pve-vm--109--disk--0 252:12   0     8G  0 lvm 
  │   ├─pve-vm--200--disk--0 252:13   0    64G  0 lvm 
  │   ├─pve-vm--200--disk--1 252:14   0     4M  0 lvm 
  │   ├─pve-vm--201--disk--0 252:15   0     4M  0 lvm 
  │   ├─pve-vm--201--disk--1 252:16   0    32G  0 lvm 
  │   ├─pve-vm--105--disk--0 252:17   0     3G  0 lvm 
  │   ├─pve-vm--108--disk--0 252:18   0     8G  0 lvm 
  │   ├─pve-vm--102--disk--1 252:19   0     8G  0 lvm 
  │   └─pve-vm--100--disk--0 252:20   0     8G  0 lvm 
  └─pve-data_tdata           252:3    0 337.9G  0 lvm 
    └─pve-data-tpool         252:4    0 337.9G  0 lvm 
      ├─pve-data             252:5    0 337.9G  1 lvm 
      ├─pve-vm--101--disk--0 252:6    0    64G  0 lvm 
      ├─pve-vm--106--disk--0 252:7    0     8G  0 lvm 
      ├─pve-vm--107--disk--0 252:8    0    64G  0 lvm 
      ├─pve-vm--103--disk--0 252:9    0     8G  0 lvm 
      ├─pve-vm--104--disk--0 252:10   0     2G  0 lvm 
      ├─pve-vm--110--disk--0 252:11   0     8G  0 lvm 
      ├─pve-vm--109--disk--0 252:12   0     8G  0 lvm 
      ├─pve-vm--200--disk--0 252:13   0    64G  0 lvm 
      ├─pve-vm--200--disk--1 252:14   0     4M  0 lvm 
      ├─pve-vm--201--disk--0 252:15   0     4M  0 lvm 
      ├─pve-vm--201--disk--1 252:16   0    32G  0 lvm 
      ├─pve-vm--105--disk--0 252:17   0     3G  0 lvm 
      ├─pve-vm--108--disk--0 252:18   0     8G  0 lvm 
      ├─pve-vm--102--disk--1 252:19   0     8G  0 lvm 
      └─pve-vm--100--disk--0 252:20   0     8G  0 lvm 
sdb                            8:16   0 931.5G  0 disk
└─sdb1                         8:17   0 931.5G  0 part /mnt/lxc_shares/backup
sdc                            8:32   0   3.6T  0 disk
└─sdc1                         8:33   0   3.6T  0 part /mnt/lxc_shares/data
sdd                            8:48   1  28.9G  0 disk
├─sdd1                         8:49   1  28.8G  0 part
└─sdd2                         8:50   1    32M  0 part
sr0                           11:0    1  1024M  0 rom

You have not replied & I am about to finish my day. So basically in the lsblk output you should find one of the partitions mounted on /boot/efi
Let's call that partition <p2> (I don't know what it is, so replace it with whatever name it actually has).

So lets try correcting that ESP sync. for that partition, with the following:

Code:

umount /boot/efi

proxmox-boot-tool init /dev/<p2>   #replace <p2> with whatever you have eg: /dev/sda2 or maybe /dev/nvme0n1p2 etc.

Reboot.

My reply was marked for approval for some reason.

I followed your steps and it worked perfectly!
Thank you so very much for your time and expertise!

Good. Maybe check the EFI status currently, with:
efibootmgr -v

Currently it says

Code:

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000
Boot0000* proxmox       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
Boot0001* UEFI OS       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

Ok. So AFAIK the UEFI OS (your currently booted 0001) is actually the fallback bootloader. The regular bootloader should actually be the proxmox one (your 0000). This is probably caused by historic situation.

Change the order with: efibootmgr -o 0000,0001
Then check again with efibootmgr -v
Then reboot & check again with efibootmgr -v

Boot order was set to 0000,0001
But after reboot it was reversed to 0001,0000

Boot order is still 0001,0000

As in the third stage of the above, but not in the second.

If so what I would try:

Change the order with: efibootmgr -o 0000,0001
Then check again with efibootmgr -v
Then reboot & enter BIOS & select the proxmox boot option & save, continue with boot.
Check again with efibootmgr -v

In BIOS my HDD was marked as UEFI OS as I mentioned before but after some looking around I found some setting called UEFI Hard Disk Drive BBS Priorities where I could set proxmox as primary

So after reboot the output of efibootmgr -v is now

Code:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* proxmox       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
Boot0001* UEFI OS       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

Excellent. Happy you got it working, maybe mark this thread as Solved. At the top of the thread, choose the Edit thread button, then from the (no prefix) dropdown choose Solved.

推荐订阅源

Proxmox Support Forum