ESP mounted in /efi: some clarifications

virusso80 · 2023-11-27 22:10:15

Hi all,
I installed a fresh arch in a dual boot system with Win10 (one OS per drive).
Since Win10 had been installed in UEFI mode, I had to do the same with arch, to avoid issues with grub.

According to the point 4.2 in the EFI system partition guide, I have chosen to mount the ESP to /efi, it seems to be the most reasonable choice to avoid as much as possible interactions between the two OSs.
I did all the configurations, rebooted, launched os-prober to detect the windows partition etc.
Now i am able to launch without issues, both OSs.

However there is a note saying that when ESP is NOT mounted in /boot I have to care about kernel upgrades and need to mount manually the partition to avoid to be stuck in the old kernel version, as explained here

Can someone explain a bit better what it means exactly?
Moreover, if I would like to "preload the required kernel modules on boot", which are this modules? those form the example?

I would really appreciate any (verbose) clarification

Xyne · 2023-11-27 22:31:14

Packages that deal with booting usually expect boot files to be located under /boot. If you break that assumption, the responsibility of managing the files that would normally go under /boot falls on you. This includes the kernal images that are required to boot your system and processor microcode that can improve the stability and performance of your cpu.

Section 4.2.1 explains how to bind-mount a subdirectory of the EFI partition to your boot directory. This lets you keep the partition mounted under /efi while also ensuring that packages that install and upgrade files under /boot "just work".

Head_on_a_Stick · 2023-11-27 22:31:21

The note only applies if you're using systemd-boot, EFI_STUB booting, or a unified kernel image (ie, anything that requires a kernel image to be present on the ESP itself). If you're using GRUB you don't have to worry about it.

It's bed time for me now so I don't have time for verbosity. Sorry.

virusso80 · 2023-11-27 23:29:45

Head_on_a_Stick wrote:

The note only applies if you're using systemd-boot, EFI_STUB booting, or a unified kernel image (ie, anything that requires a kernel image to be present on the ESP itself). If you're using GRUB you don't have to worry about it.
It's bed time for me now so I don't have time for verbosity. Sorry.

oh really? that is not very clear from the wiki
So you are saying I don't need to do anything else. good to know

Head_on_a_Stick · 2023-11-28 05:45:54

The only situation for which the ESP would have to be mounted is if you wanted to update GRUB's core.img (grubx64.efi), which is on the ESP.

Last edited by Head_on_a_Stick (2023-11-28 05:46:21)

virusso80 · 2023-11-28 07:58:59

Head_on_a_Stick wrote:

The only situation for which the ESP would have to be mounted is if you wanted to update GRUB's core.img (grubx64.efi), which is on the ESP.

ok, thanks a lot, so i am fine as it is now.
I would suggest to put this clearer in the wiki: I think I am not the one to put it in the right context and with the right arguments.

Thanks again

Arch Linux

#1 2023-11-27 22:10:15

ESP mounted in /efi: some clarifications

#2 2023-11-27 22:31:14

Re: ESP mounted in /efi: some clarifications

#3 2023-11-27 22:31:21

Re: ESP mounted in /efi: some clarifications

#4 2023-11-27 23:29:45

Re: ESP mounted in /efi: some clarifications

#5 2023-11-28 05:45:54

Re: ESP mounted in /efi: some clarifications

#6 2023-11-28 07:58:59

Re: ESP mounted in /efi: some clarifications

Board footer