[SOLVED] Cannot boot past BIOS after Proxmox 9 upgrade

alex01763

Member
Feb 28, 2023
32
3
13
I'm trying to start my server that I just upgraded from 8 to 9. When I turn it on, it takes some time to show a white rectangle for a milisecond on the top left corner of the screen and shuts down, and restarts to the BIOS. After that, whatever I do, I can't get it to go past that state. I've tried searching the forum and the web, and everyone is suggesting to enter commands, but I can't. I can't go into the OS at all. What should I do? The bios is msi click bios, I have secure boot disabled, and the boot order is correct. I don't know what else I can try without access to the terminal.
 
Did you upgrade from a BIOS boot to a UEFI boot at one point?

If something went wrong during the upgrade, you have two options, reinstall PVE9 from ISO and restore your config from backup (the easiest) or go in with a USB drive, chroot and see where apt or proxmox-boot-tool went haywire.
 
Did you upgrade from a BIOS boot to a UEFI boot at one point?

If something went wrong during the upgrade, you have two options, reinstall PVE9 from ISO and restore your config from backup (the easiest) or go in with a USB drive, chroot and see where apt or proxmox-boot-tool went haywire.
Sorry for the late reply, I had to get some sleep. I managed to get into the system using the recovery boot in the iso, and it seems to work with it. But I don't know what to do from here since most other replies seem to be recovering a completely botched boot drive, but my recovery drive imported everything just fine. I want it to stay this way
 
Last edited:
I found out that I changed the timezone in the bios while upgrading, and the date is a bit messed up. can it be the reason? The BIOS timezone was ahead of my actual timezone, so I turned it back about 11 hours. The webui keeps logging me out telling me I have an invalid ticket so I assume that's part of the reason.


journalctl -b0 -u systemd-boot-system-token returns 0 entries

bootctl command can't be found

I don't think I need to zpool anything, all the pools are there in the recovery boot. But please correct me if I'm wrong.

proxmox-boot-toolcommand doesn't exist

result of efibootmgr -v:
Code:
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0000,0004,0003
Boot0000* proxmox       HD(2,GPT,d7099233-8707-4d7e-a7f2-6b8dd93b2046,0x800,0x100000)/File(\EFI\PROXMOX\GRUBX64.EFI)
      dp: 04 01 2a 00 02 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 33 92 09 d7 07 87 7e 4d a7 f2 6b 8d d9 3b 20 46 02 02 / 04 04 36 00 5c 00 45 00 46 00 49 00 5c 00 50 00 52 00 4f 00 58 00 4d 00 4f 00 58 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0003  UEFI OS       HD(2,GPT,d7099233-8707-4d7e-a7f2-6b8dd93b2046,0x800,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
      dp: 04 01 2a 00 02 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 33 92 09 d7 07 87 7e 4d a7 f2 6b 8d d9 3b 20 46 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f
Boot0004* UEFI: SanDisk, Partition 2    PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0x27c86137,0x3a94000,0x10000)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 00 00 / 04 01 2a 00 02 00 00 00 00 40 a9 03 00 00 00 00 00 00 01 00 00 00 00 00 37 61 c8 27 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
    data: 00 00 42 4f
sandisk has ventoy with proxmox, that I'm running the recovery drive on.

cat /var/log/apt/term.log | grep -C 4 "Removable bootloader found" returns nothing
 
Last edited:
BIOS time should be set to UTC for Proxmox, not local time (unless your time zone is UTC). Don't know about your other issues.
Proxmox seems to have changed BIOS time, if that's even possible. Which is pretty weird, because I definitely changed it myself, but it got reverted after I booted recovery boot a couple of times. But I guess it'll make things easier later on later on, thanks for letting me know !
 
Turns out the solution was pretty simple. I ran pve8to9 again in the recovery boot and it told me that the grub-efi-amd64 was not installed. So I installed it, but during the installation it asked me if I wanted to keep local settings. Which means it got uninstalled during the pve 8 to 9 upgrade process.

Now everything works fine.
 
  • Like
Reactions: SteveITS and UdoB