/dev/nvme0n1p2 /boot/efi vfat defaults 0 1
I'll answer myself: yes, you can.So couldn't I just use # proxmox-boot-tool init /dev/nvme0n1p2 to setup my existing unmounted ESP?
I see. What would be an advantage over a system which is able to boot with no issues again?sure, you can also use proxmox-boot-tool to manage the ESP, but for your setup there is no advantage..
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p2 1022M 289M 734M 29% /boot/efi
root@pve:/# mount /dev/nvme0n1p2 /boot/efi
root@pve:/#
root@pve:/#
root@pve:/# ls -la /boot/efi/
total 12
drwxr-xr-x 3 root root 4096 Jan 1 1970 .
drwxr-xr-x 5 root root 4096 Sep 14 13:34 ..
drwxr-xr-x 4 root root 4096 Mar 8 2023 EFI
root@pve:/# grub-install --target x86_64-efi --no-floppy --bootloader-id proxmox /dev/nvme0n1
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@pve:/#
root@pve:/# grub-install --target x86_64-efi --no-floppy --bootloader-id proxmox --removable /dev/nvme0n1
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@pve:/#
root@pve:/# update-initramfs -u -k all
Thanks man, did the same and it worked!Hey everyone, just wanted to chip in since I had the exact same Problem. Upgrade from 8 to 9 according to the official docs went smooth but then after a reboot I got stuck in a bootloop. It would just show "Welcome to grub" and then reboot.
Here is how I solved it:
I downloaded and booted from the official proxmox 9 iso and chose the rescue mode under advanced options.
After the System booted I could login through ssh. After reading the docs I tried to mount the efi partition first to check if the partition itself was ok:
Code:root@pve:/# mount /dev/nvme0n1p2 /boot/efi root@pve:/# root@pve:/# root@pve:/# ls -la /boot/efi/ total 12 drwxr-xr-x 3 root root 4096 Jan 1 1970 . drwxr-xr-x 5 root root 4096 Sep 14 13:34 .. drwxr-xr-x 4 root root 4096 Mar 8 2023 EFI
Then I just ran the grub commands:
Code:root@pve:/# grub-install --target x86_64-efi --no-floppy --bootloader-id proxmox /dev/nvme0n1 Installing for x86_64-efi platform. Installation finished. No error reported. root@pve:/# root@pve:/# grub-install --target x86_64-efi --no-floppy --bootloader-id proxmox --removable /dev/nvme0n1 Installing for x86_64-efi platform. Installation finished. No error reported. root@pve:/# root@pve:/# update-initramfs -u -k all
The initramfs command would actually give me a few warnings about the removable bootloader and that grub would not update it.
But after a reboot everything was just working fine again.
Thanks for all your help![]()
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages.
could you post the output of pve8to9 as well as "proxmox-boot-tool status" and "efibootmgr -v" for the third node, *before doing the upgrade*? thanks!Second node upgrade shit the bed as well.
This node had a fail warning before the upgrade:
So I made certain that I fixed that and re-ran the upgrade check before doing the upgrade.
After the upgrade it got stuck in the same old welcome to grub reboot loop. I thought no worries, I had the PVE 9.1 USB stick good to go. But things got even more fucking weird, as the PVE installer menu would appear and the USB keyboard would stop responding, so I couldn't select the rescue option.
Thought it was the keyboard, so tried a different one (I should note the keyboards were working fine to select BIOS options, and bring up the BIOS boot menu). Again same result with different keyboard and different USB ports, keyboard would wouldn't let me select the options in the PVE installer menu.
Thought maybe the installer was buggered, so tried another USB stick and re-imaged it. Same result.
Desperate times, so I went into the storage under my house to dig out a PS/2 to USB keyboard adapter... (thinking surely this won't work)... well it worked, was able to use it to finally go through to the PVE installer menus. No idea if the PVE installer does something funky with the USB ports while it is running up?
I might sell tickets to the upgrade of my third node.
I'm wondering if these issues are impacting users who have upgraded from PVE 7 to 8 to 9 over the years. I am guessing that upgrade path doesn't work at all. Only users who go from a clean PVE 8 to 9.
We use essential cookies to make this site work, and optional cookies to enhance your experience.