Change default EFI boot size

Feedback Requests
1

Hello, been using garuda for a bit and I still loving it.

However I just have one suggestion for the install process and that is to change the default boot partition to 260MB. The reason for this is because I use an Advanced Format drive and 300MB doesn't format to fat32 correctly (You won't know this happened until its finished and doesn't even boot)

This issue seems very common across all distros for some reason.
The alternative is to issue mkfs.vfat -F32 -S2 /dev/sdx which would enable the format to go ahead by adjusting the sector size so it is compatible with 4k format

Currently I have to use the terminal to create the partiton and format it before I begin the installation process as the manual partitioning keeps adjusting the boot partition side to 264MB.

Cheers

1 Like
2

Yes its possible to reduce it to 260 mb by default

2 Likes
3

That would be fab, it just saves a step for me to do when I need to reinstall garuda for whatever reason.

Thanks for the quick responses again, you guys are awesome.

2 Likes
4

Done

5 Likes
5

Btw my efi partition is only 100MB , dual boot with windows

2 Likes
6

Hello,

I have mentioned this before under feature request to reduce the size from 300 to 260M as it would otherwise require manual intervention to be able to boot into the garuda linux.

I haven't reinstalled in a while but decided to change towards a wayland native env like sway or wayfire. That's when I noticed the 300M size has returned in the installer so if possible as I can't find it in current location anymore on gitlab, to decrease the size back to 260M

Cheers

Edit:
Ah so it still falls under feature, didn't want to nerco bump it in case.
Been digging around and found the calamares repo

So once again it would be a simple line change from 300 to 260 but now benefiting other distros using it too

1 Like
7

If it's something that's really bugging you...

  • Hand-install Garuda with any size /boot/ or /boot/efi 1 you desire. It is obvious you know how to do so.
  • Don't repeatedly install Garuda, if that is what you are doing. You're operating inside a rolling-release environment.

You can always make a custom Calamares install of Garuda or Arch or any Arch-based (or other) distribution. Configure it how you want, and make it your own. Heck, start your own website and publish your ISOs under any name you want.

Calamares is incredibly easy to work with and the -git resources available for it's use are growing rapidly. I suggest you investigate them. There are many online tutorials.

regards

1 Arch uses /boot and Manjaro or Garuda (and probably others) use /boot/efi but it can be whichever you like.

1 Like
8

?

image
image1109×325 38.1 KB

Maybe you post on wrong place?

Since this topic was solved, but not closed by forum software, I do it now.

1 Like
11

I just found this now because I run into a different Issue.

I just installed garuda. and have 2 kernel flavors installed.
linux and linux-zen.

but due to my laptop having nvidia graphics i now can not update anymore because each .efi file is over 100mb.

so I would be for increasing it to 1 GB.

especially because Garuda makes it very easy to install additional kernels.

maybe if that is possible at least if an nvidia card is detected.
or at least show something like a warning on the installer.

unless the 100MB .efi files is not a bug itself. but short investigation resulted in it being possible with nvidia.

from arch wiki:

It is recommended to make the partition 1 GiB in size to ensure it has adequate space for multiple kernels or unified kernel images, a boot loader, firmware updates files and any other operating system or OEM files. If still in doubt, 4 GiB ought to be enough for anybody.

https://wiki.archlinux.org/title/EFI_system_partition

12

IIRC Garuda start with 256 MB, but now it use 300MB for the efi part.
I have on this Notebook 5 OS

lsblk -f
NAME        FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0                                                                                    [SWAP]
nvme0n1                                                                                  
├─nvme0n1p1 vfat   FAT32 SYSTEM_DRV  94BA-ECE1                             223,9M    13% /boot/efi
├─nvme0n1p2                                                                              
├─nvme0n1p3 ntfs         Windows-SSD A2A8BB95A8BB6707                                    
├─nvme0n1p4 ntfs         WINRE_DRV   B8F6BC25F6BBE234                                    
├─nvme0n1p5 btrfs        KDE         fc62cc44-07ab-497b-ac89-15704c290993   66,4G    81% /var/tmp
│                                                                                        /var/log
│                                                                                        /var/cache
│                                                                                        /srv
│                                                                                        /root
│                                                                                        /home
│                                                                                        /
├─nvme0n1p6 btrfs        Sway        164f2dfe-ce11-4d5f-aa4c-ce24aa6cdd6a                
├─nvme0n1p7 btrfs        i3wm        21e02e96-0ed6-4629-9a39-85ffee7a4359                
└─nvme0n1p8 btrfs        Hyprland    b147dd48-f302-484d-80b0-661e7ff40a76

They need 13% of the efi space.

Your needs maybe differ, but 200 MB in 300 MB seems to fit. :slight_smile:

I am too tired checking the other OS’s but on KDE I have 3 kernel.

mhwd-kernel -li
Currently running: 6.9.10-zen1-1-zen (linux-zen)
The following kernels are installed in your system:
local/linux-amd-znver3 6.10.v.0-1
local/linux-lts 6.6.40-1
local/linux-zen 6.9.10.zen1-1
1 Like
13

But do you have nvidia kernel modules installed.

that is the problem i seem to have.

my main desktop has 5 kernel flavors with no problem.

but on my current laptop with fresh garuda installation and now only one kernel flavor:

[root@legionellio EFI]# du -h /boot/efi/EFI/
288K    /boot/efi/EFI/Garuda
288K    /boot/efi/EFI/boot
33M     /boot/efi/EFI/Lenovo/BIOS
33M     /boot/efi/EFI/Lenovo
232M    /boot/efi/EFI/Linux
265M    /boot/efi/EFI/

ls -lah /boot/efi/EFI/Linux/
total 232M
drwx------ 2 root root 4,0K 21. čec 12.32 .
drwx------ 6 root root 4,0K  4. čec 15.53 ..
-rwx------ 1 root root 116M 21. čec 12.31 linux-6.9.10-zen1-1-zen-c128c8dcd5a446f994f1f52c16941d11-rolling.efi
-rwx------ 1 root root 116M 21. čec 12.32 linux-6.9.9-zen1-1-zen-c128c8dcd5a446f994f1f52c16941d11-rolling.efi
14 
System:
Kernel: 6.9.9-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: hpet avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=2dbb32d8-d11b-4764-8af2-371170b8ac64 rw rootflags=subvol=@
quiet resume=UUID=a0a79332-b6c9-49e4-81d0-a97478d3515d loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 82Y5 v: Legion Slim 5 14APH8
serial: <filter> Chassis: type: 10 v: Legion Slim 5 14APH8 serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN serial: <filter>
part-nu: LENOVO_MT_82Y5_BU_idea_FM_Legion Slim 5 14APH8
uuid: 220abf30-60ef-42ad-9afd-fc5cee6129a7 UEFI: LENOVO v: MACN23WW
date: 08/18/2023
Battery:
ID-1: BAT0 charge: 36.1 Wh (48.1%) condition: 75.1/73.6 Wh (102.1%)
power: 15.3 W volts: 15.4 min: 15.5 model: SMP L22M4PA2 type: Li-poly
serial: <filter> status: discharging cycles: 7
CPU:
Info: model: AMD Ryzen 7 7840HS with Radeon 780M Graphics socket: FP8
bits: 64 type: MT MCP arch: Zen 4 gen: 5 level: v4 note: check built: 2022+
process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x74 (116) stepping: 1
microcode: 0xA704103
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 851 high: 4391 min/max: 400/5137 base/boost: 3800/5125
scaling: driver: amd-pstate-epp governor: performance volts: 1.2 V
ext-clock: 100 MHz cores: 1: 400 2: 400 3: 4391 4: 400 5: 400 6: 400
7: 400 8: 400 9: 400 10: 400 11: 3640 12: 400 13: 400 14: 400 15: 400
16: 400 bogomips: 121362
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] vendor: Lenovo
driver: nvidia v: 555.58.02 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
ports: active: none empty: DP-1,HDMI-A-1,eDP-1 bus-ID: 01:00.0
chip-ID: 10de:28a0 class-ID: 0300
Device-2: AMD Phoenix1 vendor: Lenovo driver: amdgpu v: kernel
arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm) built: 2023+ pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: eDP-2 empty: DP-2, DP-3, DP-4,
DP-5, DP-6, Writeback-1 bus-ID: 05:00.0 chip-ID: 1002:15bf class-ID: 0300
temp: 33.0 C
Device-3: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:2 chip-ID: 04f2:b7b6
class-ID: fe01 serial: <filter>
Display: unspecified server: X.Org v: 24.1.1 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 1646x1029 s-dpi: 96 s-size: 436x272mm (17.17x10.71")
s-diag: 514mm (20.23")
Monitor-1: eDP-2 model: Samsung 0x4188 built: 2021 res: 1646x1029 hz: 120
dpi: 134 gamma: 1.2 size: 312x195mm (12.28x7.68") diag: 368mm (14.5")
ratio: 16:10 modes: max: 2880x1800 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: radeonsi inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 24.1.4-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon 780M (radeonsi
gfx1103_r1 LLVM 18.1.8 DRM 3.57 6.9.9-zen1-1-zen) device-ID: 1002:15bf
memory: 500 MiB unified: no
API: Vulkan v: 1.3.279 layers: 11 device: 0 type: integrated-gpu name: AMD
Radeon 780M (RADV GFX1103_R1) driver: mesa radv v: 24.1.4-arch1.2
device-ID: 1002:15bf surfaces: xcb,xlib device: 1 type: discrete-gpu
name: NVIDIA GeForce RTX 4060 Laptop GPU driver: nvidia v: 555.58.02
device-ID: 10de:28a0 surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.1.4-arch1.2 (LLVM
18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
driver: snd_pci_ps v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x,
snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x,
snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.5
chip-ID: 1022:15e2 class-ID: 0480
Device-4: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 05:00.6
chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.9.9-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.1 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
vendor: Lenovo driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 03:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Foxconn / Hon Hai Bluetooth 5.2 Adapter [MediaTek MT7922]
driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0
bus-ID: 1-5:4 chip-ID: 0489:e0d8 class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
Local Storage: total: 982.52 GiB used: 147.8 GiB (15.0%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFS001TEJ9X115N
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 51020A12 temp: 39.9 C
scheme: GPT
SMART: yes health: PASSED on: 30 hrs cycles: 54
read-units: 1,130,926 [579 GB] written-units: 1,267,983 [649 GB]
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: USB 3.2Gen1
size: 28.65 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 919.97 GiB size: 919.97 GiB (100.00%)
used: 147.54 GiB (16.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 264.3 MiB (88.3%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 919.97 GiB size: 919.97 GiB (100.00%)
used: 147.54 GiB (16.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-4: /var/log raw-size: 919.97 GiB size: 919.97 GiB (100.00%)
used: 147.54 GiB (16.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 919.97 GiB size: 919.97 GiB (100.00%)
used: 147.54 GiB (16.0%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.54 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
ID-2: swap-2 type: partition size: 33.6 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: amdgpu temp: 33.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.54 GiB used: 6.64 GiB (21.8%)
Processes: 385 Power: uptime: 59m states: freeze,mem,disk suspend: s2idle
wakeups: 1 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 12.17 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 256 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 2256 libs: 606 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.1.1 alt: 13 Shell: garuda-inxi (sudo) default: Bash
v: 5.2.26 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-07-04
Last full system update: 2024-07-21 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
15

Regardless of the problem described, you should update your system and restart it.

1 Like
16

I was just about to

I just wanted to post my findings immediately

as I wrote above

During update the efi files for the new kernel could not be written because the efi partition is full.

now i deleted one kernel flavor and manually all the efi files, rebuilt the one kernel and will now reboot.

I am just thinking of maybe less experienced users.
especially as resizing the efi partition afterwards is a PITA, because it is usually one of the first in the partition layout

1 Like
17

Seems I do something wrong :slight_smile:
I have two PC with Nvidia GPU but also the Notebooks do not have this big Files neither I have this path like you.

sudo ls -lah /boot/efi/EFI/
insgesamt 2,0K
drwx------ 4 root root 512 17. Jul 2021  .
drwx------ 3 root root 512  1. Jan 1970  ..
drwx------ 2 root root 512 17. Jul 2021  boot
drwx------ 2 root root 512 17. Jul 2021  Garuda

 ╭─sgs@i3 in ~ took 16ms
🕙 14:44:42
 ╰─λ sudo ls -lah /boot/efi/EFI/Garuda
insgesamt 285K
drwx------ 2 root root  512 17. Jul 2021  .
drwx------ 4 root root  512 17. Jul 2021  ..
-rwx------ 1 root root 284K  1. Apr 04:05 grubx64.efi

 ╭─sgs@i3 in ~ took 16ms
🕙 14:44:56
 ╰─λ sudo ls -lah /boot/efi/EFI/boot
insgesamt 289K
drwx------ 2 root root  512 17. Jul 2021  .
drwx------ 4 root root  512 17. Jul 2021  ..
-rwx------ 1 root root 288K  9. Mär 15:27 bootx64.efi

 ╭─sgs@i3 in ~ took 16ms
🕙 14:45:04
 ╰─λ sudo du -h /boot/efi/EFI/Garuda
285K	/boot/efi/EFI/Garuda

 ╭─sgs@i3 in ~ took 8ms
🕙 4:~~~48:06
 ╰─λ sudo du -h /boot/efi/EFI/boot
289K	/boot/efi/EFI/boot

Notebook

sudo du -h /boot/efi/EFI/
172K	/boot/efi/EFI/Microsoft/Boot/bg-BG
212K	/boot/efi/EFI/Microsoft/Boot/cs-CZ
212K	/boot/efi/EFI/Microsoft/Boot/da-DK
220K	/boot/efi/EFI/Microsoft/Boot/de-DE
220K	/boot/efi/EFI/Microsoft/Boot/el-GR
164K	/boot/efi/EFI/Microsoft/Boot/en-GB
212K	/boot/efi/EFI/Microsoft/Boot/en-US
220K	/boot/efi/EFI/Microsoft/Boot/es-ES
172K	/boot/efi/EFI/Microsoft/Boot/es-MX
164K	/boot/efi/EFI/Microsoft/Boot/et-EE
212K	/boot/efi/EFI/Microsoft/Boot/fi-FI
172K	/boot/efi/EFI/Microsoft/Boot/fr-CA
220K	/boot/efi/EFI/Microsoft/Boot/fr-FR
164K	/boot/efi/EFI/Microsoft/Boot/hr-HR
220K	/boot/efi/EFI/Microsoft/Boot/hu-HU
212K	/boot/efi/EFI/Microsoft/Boot/it-IT
192K	/boot/efi/EFI/Microsoft/Boot/ja-JP
192K	/boot/efi/EFI/Microsoft/Boot/ko-KR
164K	/boot/efi/EFI/Microsoft/Boot/lt-LT
164K	/boot/efi/EFI/Microsoft/Boot/lv-LV
212K	/boot/efi/EFI/Microsoft/Boot/nb-NO
220K	/boot/efi/EFI/Microsoft/Boot/nl-NL
220K	/boot/efi/EFI/Microsoft/Boot/pl-PL
212K	/boot/efi/EFI/Microsoft/Boot/pt-BR
212K	/boot/efi/EFI/Microsoft/Boot/pt-PT
60K	/boot/efi/EFI/Microsoft/Boot/qps-ploc
164K	/boot/efi/EFI/Microsoft/Boot/ro-RO
212K	/boot/efi/EFI/Microsoft/Boot/ru-RU
164K	/boot/efi/EFI/Microsoft/Boot/sk-SK
164K	/boot/efi/EFI/Microsoft/Boot/sl-SI
164K	/boot/efi/EFI/Microsoft/Boot/sr-Latn-RS
212K	/boot/efi/EFI/Microsoft/Boot/sv-SE
212K	/boot/efi/EFI/Microsoft/Boot/tr-TR
164K	/boot/efi/EFI/Microsoft/Boot/uk-UA
184K	/boot/efi/EFI/Microsoft/Boot/zh-CN
184K	/boot/efi/EFI/Microsoft/Boot/zh-TW
14M	/boot/efi/EFI/Microsoft/Boot/Fonts
20K	/boot/efi/EFI/Microsoft/Boot/Resources/en-US
20K	/boot/efi/EFI/Microsoft/Boot/Resources/de-DE
212K	/boot/efi/EFI/Microsoft/Boot/Resources
60K	/boot/efi/EFI/Microsoft/Boot/CIPolicies/Active
64K	/boot/efi/EFI/Microsoft/Boot/CIPolicies
27M	/boot/efi/EFI/Microsoft/Boot
56K	/boot/efi/EFI/Microsoft/Recovery
27M	/boot/efi/EFI/Microsoft
288K	/boot/efi/EFI/Boot
4,0K	/boot/efi/EFI/GRUB
288K	/boot/efi/EFI/Garuda
104K	/boot/efi/EFI/systemd
4,0K	/boot/efi/EFI/tools
288K	/boot/efi/EFI/i3wm/i3
576K	/boot/efi/EFI/i3wm
288K	/boot/efi/EFI/KDE/kde-1
576K	/boot/efi/EFI/KDE
284K	/boot/efi/EFI/Hyprland
4,0K	/boot/efi/EFI/Linux
30M	/boot/efi/EFI/
18

The kernel modules are not stored on the EFI partition with a typical Grub install. In general, a large EFI partition is not needed if you are not storing the kernel and images there. The files Grub stores on there are usually less than a single MB.

For example, here is an Nvidia laptop with a typical Grub installation:

❯ inxi -G
Graphics:
  Device-1: Intel HD Graphics 630 driver: i915 v: kernel
  Device-2: NVIDIA GM107GLM [Quadro M1200 Mobile] driver: nvidia
    v: 555.58.02
  Device-3: Chicony HP HD Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915,nvidia,nvidia-nvswitch
    resolution: 1: 1920x1080~50Hz 2: N/A
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.1.3-arch1.1
    renderer: Mesa Intel HD Graphics 630 (KBL GT2)

❯ sudo eza -lT --total-size /boot/efi/
drwxr-x--- 582k root 31 Dec  1969 /boot/efi
drwxr-x--- 582k root 26 Jun 12:24 └── EFI
drwxr-x--- 291k root 26 Jun 12:24    ├── boot
.rw-r----- 291k root 26 Jun 12:24    │  └── bootx64.efi
drwxr-x--- 291k root 26 Jun 12:24    └── endeavouros
.rw-r----- 291k root 26 Jun 12:24       └── grubx64.efi

All of the files on the EFI partition combined are only 582 KB–about half of a single megabyte.

It looks like you have generated a couple unified kernel images with dracut. This is not necessary if you are using Grub. My guess is you did this unintentionally, is that right?

If you are trying to rebuild your initramfs images, you can do that with this command:

sudo dracut-rebuild

See also this article:

2 Likes