Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: EFI System Partition: Using it as /boot versus /boot/efi

  1. #1
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    920

    Default EFI System Partition: Using it as /boot versus /boot/efi

    This is a more generic Linux question. As I have an EFI motherboard with Secure Boot I need an ESP partition: I have one mounted as /boot/efi and it works fine on this installation. But I was wondering; Is there any disadvantage to making the entirety of /boot my ESP? That way I can make better use of the 4GB I assign to it, having it store grub and the kernel images too... they're all loaded temporarily as part of the boot process so it makes sense to use this one little partition for everything! As long as it's fat32 there shouldn't be anything breaking the configuration right? Especially on a machine where I don't plan to dual-boot, only one OS installed on the main drive so there would be no kernel image conflicts.

    Just in case though I wanted to ask for opinions: Does anyone else place the entirety of /boot on the EFI partition instead of just /boot/efi? Does it work well for you, do you find it more optimal this way? As a bonus question; Is exfat (fat64) a newer and better partition format to use, or is it still a good idea to stick to fat32 exclusively for the ESP else the BIOS might complain?

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,825
    Blog Entries
    15

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Hi
    Never tried it... no plans to, I have a separate boot, ideally it doesn't need to be more than 260MB (FAT only), some manufacturers install efi utilities, BIOS updates, efi-shell (non-secure boot only), test utilities, never seen a need for any bigger...

    Best to have a read here: https://uefi.org/specifications
    Last edited by malcolmlewis; 05-Apr-2021 at 16:22.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,463
    Blog Entries
    3

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Quote Originally Posted by MirceaKitsune View Post
    But I was wondering; Is there any disadvantage to making the entirety of /boot my ESP? That way I can make better use of the 4GB I assign to it, having it store grub and the kernel images too... they're all loaded temporarily as part of the boot process so it makes sense to use this one little partition for everything!
    I normally use 500M for the EFI partition. I'm inclined to think that 4G is too big.

    The KaOS distro does this. I am not a big fan of that decision, but it has not caused any problems when I try KaOS.

    Especially on a machine where I don't plan to dual-boot, only one OS installed on the main drive so there would be no kernel image conflicts.
    Yes, dual booting can be a potential problem with that scheme. But as long as you don't dual boot, I am not aware of any particular problems.

    I'm not sure whether "exfat" is compatible with the EFI specification. I think it isn't.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  4. #4
    Join Date
    Jan 2009
    Location
    Romania, Bucharest
    Posts
    920

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Thanks for clarifying. The only notable issue someone brought up is that the FAT filesystem doesn’t allow symlinks; On openSUSE this may be a problem as the latest kernel is symlinked. Arch / Manjaro doesn’t appear to do this by comparison: I didn’t find any symbolic links within /boot so it should be good on at least some distros.

  5. #5
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,987

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Quote Originally Posted by MirceaKitsune View Post
    This is a more generic Linux question. As I have an EFI motherboard with Secure Boot I need an ESP partition: I have one mounted as /boot/efi and it works fine on this installation. But I was wondering; Is there any disadvantage to making the entirety of /boot my ESP?
    I there an advantage? Turn off secure boot. I never considered moving linux files to FAT. I never used a large EFI system Partition. 100 MB suffice for 10 distributions:

    Code:
    3400G:~ # df -h /boot/efi 
    Filesystem      Size  Used Avail Use% Mounted on 
    /dev/sda1       100M   34M   67M  34% /boot/efi 
    3400G:~ #
    Tumbleweed occupies 0.3 MB here:

    Code:
    3400G:~ # ll -h /boot/efi/EFI/tw-btrfs/grubx64.efi 
    -rwxr-xr-x 1 root root 312K Mar 31 08:57 /boot/efi/EFI/tw-btrfs/grubx64.efi
    3400G:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,211

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    IMHO you should keep the EFI partition as clean and lean as possible (see most advises above). It is not part of your openSUSE system. Better look at it as an extension of the BIOS, and you do not see the BIOS as part of openSUSE either I guess.
    It is only mounted at /boot/efi to give access to it using your openSUSE system. Not to use it for anything else. Like you should only use any other non-Linux file system only for the direct exchange of data between a Linux system and a non-Linux system and never as an integrated part of your Linux system.
    Henk van Velden

  7. #7
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    3,179
    Blog Entries
    1

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    I've seen reports that mounting the ESP to /boot/ seems to be supported in Slackware. I tried doing it with a 15.3 test installation some weeks ago and failed to make it boot without moving the kernels & initrds back to a Linux native filesystem for /boot/ and mounting the ESP on /boot/efi/. It's disappointing that a relatively modern specification like UEFI requires a crude and ancient filesystem.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, TW, 15.3 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.2 on i965P w/ Radeon
    Tertiary: Mageia, Fedora, Debian, more on Kaby Lake & older Intel, AMD, NVidia &&&&&

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,211

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Of course when you mount something to /boot, it will make all that is there already unavailable.

    Thus either you have organized all in /boot being in the root partition / and then mounting whatever file system (in your case the EFI FAT file system) over /boot will make the Grub configuration, the kernel and all what is in /boot unvisible to the ready system, or you have organized a separate file system for /boot, in which case it depends on what is mounted first on /boot, the boot file system or the EFI file system, the second mount will prevail in what is visible.
    Henk van Velden

  9. #9

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Quote Originally Posted by mrmazda View Post
    It's disappointing that a relatively modern specification like UEFI requires a crude and ancient filesystem.
    E in UEFI means Extensible. You may extend it via loading modules.

  10. #10
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    3,179
    Blog Entries
    1

    Default Re: EFI System Partition: Using it as /boot versus /boot/efi

    Quote Originally Posted by Svyatko View Post
    E in UEFI means Extensible. You may extend it via loading modules.
    Loading modules via UEFI firmware (genericially speaking, BIOS), before Grub? The spec requires control switched from "firmware/BIOS" to code from some storage medium filesystem formatted only as some form of FAT, so FAT is the only place I can think of where additional modules might be available, at which point, boot process has been pushed over the cliff, too late for loading additional modules.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, TW, 15.3 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.2 on i965P w/ Radeon
    Tertiary: Mageia, Fedora, Debian, more on Kaby Lake & older Intel, AMD, NVidia &&&&&

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •