Normal sequence of events at power on

M

mike the newb

Member
Aug 24, 2025
49
9
8
As my name implies, and as a preface, I am new to Linux and Proxmox. I have a new installation of Proxmox on an older SuperMicro server that seems like it will be a good learning environment for me. I'll spare all the interesting things I've experienced so far in order to get to my question(s).

Since this isn't a production server I power it off every day when I'm finished trying to learn. When I power on in the morning, it boots up to shell, which I have to exit from twice to load Proxmox and access the web gui.

I've searched everywhere to find out whether this is normal, or whether I've missed something, without luck.

Is this normal, or have I missed something?

BTW, Hi! and my name is Mike. I'm also a newb that doesn't mind being scolded or laughed at :)
 
That is the UEFI shell, if you have to exit twice, and then it works, that means in your boot sequence in UEFI settings you are likely attempting to boot from a non-boot drive that still has some kind of boot loader. Just enter your UEFI settings for your motherboard and change the boot order to the ‘right’ drive first.
 
  • Like
Reactions: mike the newb
Did I mention I am a COMPLETE newb?
You may be correct, but there is nothing else to boot "into." No other drives, no usb, no network, nothing. Boot priority is "hard disk," with #2 as CDROM (but there is no CD).
Are there UEFI settings to address within PM?
 
Impact said:
You could check efibootmgr.
Click to expand...
I wish I knew what that would tell me. This is what I got:
root@PM:/# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0004,0005,0000,0002
Boot0000* proxmox HD(2,GPT,65a0897f-9fe1-4fd7-b4a0-803d5f6ca5fe,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0004* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0005* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
 
Please use code blocks. It shows that PVE (0000) is in the third place of the boot order. I can't properly research or test this right now (mobile) so no guarantees this won't break anything but efibootmgr -o 0000,0004,0005,0002 should make it the first option.
 
Last edited:
  • Like
Reactions: mike the newb and leesteken
I don't know what code blocks are. As I said, I am as newb as a newb can be. I've spent 30+ years on ms products. Twenty of which I've wanted to go a different route, but, in my industry, ms was always desired by customers for one reason or another.
I'll try this in the morning and report back.
Again, as a newb, I don't know why the boot order is as listed here. I don't even know why there are four "options (0004, 0005, 0000, 0002)."
Lucky for me that it doesn't matter what I may break. I'm just learning, and despite being pathetically undertalented in this regard, at least I'm not under the gun at the moment.

Here's the output, and I'll reboot in the am.

root@PM:/# efibootmgr -o 0000,0004,0005,0002
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0004,0005,0002
Boot0000* proxmox HD(2,GPT,65a0897f-9fe1-4fd7-b4a0-803d5f6ca5fe,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0004* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0005* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
 
But you can google something like forum what are code blocks ;)
These buttons let you do that1756102426757.png
A code block looks like this and is preferred because formatting such as spaces and indentation is preserved and makes things quite a bit easier to read
Bash: 
root@PM:/# efibootmgr -o 0000,0004,0005,0002
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0004,0005,0002
Boot0000* proxmox HD(2,GPT,65a0897f-9fe1-4fd7-b4a0-803d5f6ca5fe,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0004* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0005* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
The output looks good. PVE is now at the start of the boot order and I expect this to work nicely

0002, 0004 and 0005 all point to EFI Shell. You can use this to delete the redundant entries.
I'm not sure why they occur so often here and this is not needed to fix your issue, it just makes for a tidier system.
Bash: 
efibootmgr -b 0002 -B
efibootmgr -b 0004 -B
 
Last edited:
  • Like
Reactions: mike the newb
That worked perfectly, thank you!

I deleted all but the 0000 and rebooted. The 0002 came back, but in the correct order, and it booted all the way into PM.





Bash: 
root@PM:/# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0002
Boot0000* proxmox       HD(2,GPT,65a0897f-9fe1-4fd7-b4a0-803d5f6ca5fe,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0002* UEFI: Built-in EFI Shell      VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
 
  • Like
Reactions: Impact
You must log in or register to reply here.
Top Bottom