How to install Proxmox with GRUB?

+DS_DV+

Well-Known Member
Feb 9, 2020
36
2
48
Hi,
id like to isntall with grub instead of systemd-boot
according to https://pve.proxmox.com/wiki/Host_Bootloader :
For EFI Systems installed with ZFS as the root filesystem systemd-boot isused, unless Secure Boot is enabled. All other deployments use the standardGRUB bootloader (this usually also applies to systems which are installed ontop of Debian).
i installed it on a uefi system but as BTRFS.
Still it has systemd-boot :(

any advice?
with kind regards
 
the default for zfs with uefi is systemd-boot and with bios grub (:

sadly this does not answer my question how i can force proxmox install to set it up with grub uefi and btrfs :/
 
Install in Legacy BIOS mode and then switch to UEFI, maybe? You would need to do a GRUB rescue/repair (with EFI-vars for UEFI) to fix the boot once after the switch.
EDIT: Maybe test this first using a nested Proxmox VM.
 
  • Like
Reactions: +DS_DV+
thank you for the feedback (:
so far its a fresh setup so i have no problem with wiping the system. Ill try the BIOS <-> UEFI switch first since i noticed a few diffrences when converting debian to proxmox compared to direct proxmox install (:
The GRUB Fix is this correct? https://pve.proxmox.com/wiki/Recover_From_Grub_Failure


A little background:
This should become a test setup where Proxmox is in dualboot with fedora silverblue on the same ssd.
Due to proxmox installer wiping the drive it needs to be installed first. Silverblue respects the proxmoxinstall and just gets ontho the the 5th partition.
But sadly the systemd-boot of proxmox does not recognize the fedora installation :(

It was suggested that grub might do it correctly (:
 
  • Like
Reactions: Kingneutron
I cannot access the Wiki at this moment but I fear that mounting the efivars (for UEFI) is not in there and you might want to search the internet for it.
This should become a test setup where Proxmox is in dualboot with fedora silverblue on the same ssd.
Due to proxmox installer wiping the drive it needs to be installed first. Silverblue respects the proxmoxinstall and just gets ontho the the 5th partition.
But sadly the systemd-boot of proxmox does not recognize the fedora installation :(
Proxmox does not support this, especially the installer that wipes the whole drive.
It was suggested that grub might do it correctly (:
Proxmox disables the OS-prober which will probably make GRUB not detect your Fedora. You can probably enable it but it might get disabled again on an update.
 
  • Like
Reactions: +DS_DV+
Proxmox disables the OS-prober which will probably make GRUB not detect your Fedora. You can probably enable it but it might get disabled again on an update.
oh you are correct.
i had to disable that in a debian to proxmox conversion process.

ok ill go with the conversion route than and just skip this step (:
 
Systemd-boot is installed with UEFI Not Enabled Secure Boot with ZFS/BTRFS.

GRUB bootloader is installed when Secure Boot is enabled in UEFI, even with ZFS or BTRFS.
 
Last edited:
Systemd-boot is installed with UEFI Not Enabled Secure Boot with ZFS/BTRFS.
that might be correct
the wiki is missing the BRTFS part so i dont know about the rest for sure :/
i guess the wiki needs a little overhaul if the devs find some spare time (:
 
Systemd-boot is installed with UEFI Not Enabled Secure Boot with ZFS/BTRFS.

GRUB bootloader is installed when Secure Boot is enabled in UEFI, even with ZFS or BTRFS.

True this.

The Proxmox team may want to consider just using GRUB bootloader exclusively in future versions like how other operating systems do it.

And to avoid the issues from systemd-boot to GRUB migrations.

Can confirm that the GRUB bootloader can still boot with Secure Boot disabled. Have to do this when updating server firmware with an unsigned firmware ISO.
 
I don't have any helpful advice but I'm kinda curious why you want this specific combination.
 
Last edited:
  • Like
Reactions: Kingneutron
> This should become a test setup where Proxmox is in dualboot with fedora silverblue on the same ssd.
> Due to proxmox installer wiping the drive it needs to be installed first. Silverblue respects the proxmoxinstall and just gets onto the the 5th partition.
> But sadly the systemd-boot of proxmox does not recognize the fedora installation

What you are currently building is something of a house of cards, without a strong foundation.

Proxmox is more designed to run 24/7 on dedicated hardware.

I have 2-3 suggestions.

1) Install silverblue in a VM under proxmox. Make proxmox host a "developer workstation" with X and a browser such as firefox, brave or chromium.

2) Install silverblue to external dedicated SSD for dual-boot - so if you ever have to reinstall proxmox, SB won't be affected. You can get a 256GB " SSK External SSD 256GB " on amzn for like $30, and the 128GB is even less.

3) Install ReFind

You could also try installing grub (or Super Grub Disc) to e.g. SDcard or usb stick, and F11 the boot menu (or whatever key for your system) to boot from that.

Don't forget, you still need backups. PBS on separate hardware, and take advantage of dedup. It can run on e.g. an old quad-core laptop with 4-8GB RAM and a 1-2TB SSD.
 
Last edited:
> The Proxmox team may want to consider just using GRUB bootloader exclusively in future versions like how other operating systems do it

I disagree. Grub2 is not the be-all, end-all of bootloaders.

Pop-os uses Systemd-boot, and there is also ZFSBootMenu which definitely comes in handy on a proxmox install.
 
I'm kinda curious why you want this specific combination.
i have an Minifsforum UM773 lite as HTPC which for a while ran PikaOS and then Nobara.
On Pika i just installed the snap for LXD on Nobara i got inucs working.
I did that because i than could move my LXCs which require more performance (mostly the occasional game server) from my 24/7 Proxmox to the HTPC.
Hence this setup is not for 24/7 just for the 2 days once a month i need a game server or sth else my which requires more horsepower ;)

Since i moved everything to Fedora Atomic based Sysytems Incus no longer works :/ So dual booting proxmox seems like the most logical solution.
Even offering more performance / efficiency since not booting up into a full blown DE.

1) Install silverblue in a VM under proxmox. Make proxmox host a "developer workstation" with X and a browser such as firefox, brave or chromium.

2) Install silverblue to external dedicated SSD for dual-boot - so if you ever have to reinstall proxmox, SB won't be affected. You can get a 256GB " SSK External SSD 256GB " on amzn for like $30, and the 128GB is even less.

3) Install ReFind

1) sound like a very interesting project but im not sure im up for it at this point in time XD
2) i did never open the box up but i assumed it only has the nvme slot it came with. (ill take a peak at disassembly videos now that you mentioned it)
3) that is indeed an option i did not know about o.o that might indeed solve my problems since i have spar usb thumb drives which could be used for that.
i never heard of rEFInd before today o.o

i might have to ditch secureboot (which worked ootb with secureblue) but thats ok i dont nessesarly need thant on this box (: