Hi all. When I booted my Proxmox host today all I saw was the "Welcome to Grub" screen and got stuck there. After troubleshooting for hours by following this thread I got nowhere
I then found this thread with someone mentioning secure boot.
Also this one
I then reset the keys but that didnt help. Only until I switched to Windows UEFI secure boot option it worked.
I installed Proxmox with "Other OS" option on my ASUS X570-E which is said to disable Secure Boot.
Since I never actively changed anything in Proxmox I don't understand why it suddenly didn't boot anymore without Secure Boot enabled.
I had the issue yesterday as well but after a few restarts and changing around the boot order I somehow got into Proxmox. Today it didn't work at all.
Can it be that Proxmox only boots with the same devices attached and plugged into the system as the day before? Because I had a SD-card reader plugged into my USB-C the other day and didn't have it installed today and two hard disks where also not attched. Can this somehow affect the boot process? And how can I avoid having this problem again?
I did an update today:
Start-Date: 2025-02-28 07:25:33
Commandline: apt-get dist-upgrade
Upgrade: librados2:amd64 (17.2.7-pve3, 17.2.8-pve1), ceph-fuse:amd64 (17.2.7-pve3, 17.2.8-pve1), proxmox-widget-toolkit:amd64 (4.3.4, 4.3.6), libpve-rs-perl:amd64 (0.9.1, 0.9.2), libproxmox-acme-perl:amd64 (1.5.1, 1.6.0), python3-ceph-common:amd64 (17.2.7-pve3, 17.2.8-pve1), librbd1:amd64 (17.2.7-pve3, 17.2.8-pve1), grub-pc-bin:amd64 (2.06-13+pmx2, 2.06-13+pmx5), librgw2:amd64 (17.2.7-pve3, 17.2.8-pve1), ceph-common:amd64 (17.2.7-pve3, 17.2.8-pve1), libproxmox-rs-perl:amd64 (0.3.4...
- pigpen
- bios grub uefi
- Replies: 92
- Forum: Proxmox VE: Installation and configuration
I then found this thread with someone mentioning secure boot.
When running "proxmox-boot-tool init" on a new system drive, I get an error message and it doesn't finish. "Failed to create EFI Boot variable entry: Invalid argument"
Anybody know what it's about? Is this an efi/bios setting around secure-boot that needs to be changed?
It affects both nvme0n1 and nvme1n1.
According to "proxmox-boot-tool status" he system is booted with systemd/uefi:
root@proxmox:/# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
60EC-4347 is configured with: uefi (versions...
Anybody know what it's about? Is this an efi/bios setting around secure-boot that needs to be changed?
It affects both nvme0n1 and nvme1n1.
According to "proxmox-boot-tool status" he system is booted with systemd/uefi:
root@proxmox:/# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
60EC-4347 is configured with: uefi (versions...
- gabrioth
- Replies: 3
- Forum: Proxmox VE: Installation and configuration
I set up a new node today for my cluster. Dell 7050m, ran diags, passed, set all BIOS settings as desired (including Secure Boot) -> Installed Proxmox from flash drive -> updated -> joined cluster -> realized I gave it the wrong IP.
So, in the cluster I kicked the node out, and then, according to instructions I believe I'm supposed to go full Office Space on the BAD computer, but I opted just to wipe it and reinstall from scratch. I used the built in BIOS drive wipe feature which took about 5 seconds, then plugged in the flash drive to reinstall, and when attempting to boot off of it I...
So, in the cluster I kicked the node out, and then, according to instructions I believe I'm supposed to go full Office Space on the BAD computer, but I opted just to wipe it and reinstall from scratch. I used the built in BIOS drive wipe feature which took about 5 seconds, then plugged in the flash drive to reinstall, and when attempting to boot off of it I...
- yurdle
- Replies: 2
- Forum: Proxmox VE: Installation and configuration
I then reset the keys but that didnt help. Only until I switched to Windows UEFI secure boot option it worked.
I installed Proxmox with "Other OS" option on my ASUS X570-E which is said to disable Secure Boot.
Since I never actively changed anything in Proxmox I don't understand why it suddenly didn't boot anymore without Secure Boot enabled.
I had the issue yesterday as well but after a few restarts and changing around the boot order I somehow got into Proxmox. Today it didn't work at all.
Can it be that Proxmox only boots with the same devices attached and plugged into the system as the day before? Because I had a SD-card reader plugged into my USB-C the other day and didn't have it installed today and two hard disks where also not attched. Can this somehow affect the boot process? And how can I avoid having this problem again?