You are not logged in.
Pages: 1
On my EFI machine, I'm using Arch Linux in a single boot configuration with systemd-boot and never had problems.
However, for some reason I cannot get my head around using EFI and multi boot.
My configuration:
As you see, I have a separate boot partition where the EFI stuff, the kernel and initramfs is located. Also, the config for systemd-boot is in /boot/loader
This works fine for my primary Arch on /dev/nvme0n1p3.
Then, I installed a second Arch Linux on /dev/nvme0n1p4.
In this second Arch, I also mounted /dev/nvme0n1p1 to /boot.
But this leads to an issue: because both Arch (or Arches?) are using the same boot partition, they are overwriting kernels and initramfs of the other Arch.
So, what is the correct way to set up multi boot? I can think of 3 solutions:
- create separate boot partition for each Arch
- don't use boot partitions at all, store kernel directly on system partition
- create sub-folders in /boot (don't know if this is possible)
Last edited by lugge (2025-09-10 06:49:28)
Offline
If you use GRUB instead you wouldn't have to mount the ESP under /boot/.
For systemd-boot consider an XBOOTLDR partition for the second Arch system's /boot/ partition.
And please replace your image of text with plain text enclosed in code tags. Posting an image of text is just stupid.
Jin, Jîyan, Azadî
Offline
- create sub-folders in /boot (don't know if this is possible)
It's possible: see https://wiki.archlinux.org/title/EFI_sy … bind_mount.
You need to mount the EFI system partition to /efi, create a directory like /efi/EFI/arch1 and bind-mount it to /boot. On the other install, you do the same, except pick a different directory name (e.g. "arch2").
Online
lugge wrote:- create sub-folders in /boot (don't know if this is possible)
It's possible: see https://wiki.archlinux.org/title/EFI_sy … bind_mount.
You need to mount the EFI system partition to /efi, create a directory like /efi/EFI/arch1 and bind-mount it to /boot. On the other install, you do the same, except pick a different directory name (e.g. "arch2").
Thanks!
And do you suggest this method or should I stick to the XBOOTLDR approach?
Offline
It's up to you. Both methods should work.
With the XBOOTLDR approach, you need to create an XBOOTLDR partition, which means repartitioning. With the bind-mount approach, you only need the EFI system partition.
Online
It's up to you. Both methods should work.
With the XBOOTLDR approach, you need to create an XBOOTLDR partition, which means repartitioning. [...]
And I need this partition for every additional OS, as far as I understand. Thus, things could get messy in the future.
Also, according to the wiki there may be issues with XBOOTLDR and fastboot.
Then I will try out the bind-mount approach.
Offline
Update: the bind-mount approach works like a charm.
I will stick to it, thank you all.
Offline
Pages: 1