Bootloader does not show Arch (Dualboot)

Issues & Assistance
21

I did update-grub now with the same output as above, yet grub still shows no bootable os (only the UEFI settings).
What confuses me even further is that in the uefi boot settings I can now select grub or "NVMe0 ..." (which gets me to the garuda bootloader).

https://i.imgur.com/1oZTycZ.png

update-grub:

╭─stk@stk in ~ as 🧙 took 7s
╰─λ sudo update-grub | nc termbin.com 9999
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Arch Linux (rolling) on /dev/nvme0n1p2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2023-09-07 11:15:37 | @/.snapshots/18/snapshot | post | grub                                          |
Found snapshot: 2023-09-07 11:15:30 | @/.snapshots/17/snapshot | pre  | pacman -Su grub                               |
Found snapshot: 2023-09-07 10:44:48 | @/.snapshots/16/snapshot | post | libb2 libtorrent-rasterbar qbittorrent qt6-base qt6-svg qt6-translations |
Found snapshot: 2023-09-07 10:44:43 | @/.snapshots/15/snapshot | pre  | pacman -S --needed qbittorrent                |
Found snapshot: 2023-09-07 09:52:47 | @/.snapshots/14/snapshot | post | grub                                          |
Found snapshot: 2023-09-07 09:41:36 | @/.snapshots/13/snapshot | pre  | pacman -Su grub                               |
Found snapshot: 2023-09-07 09:40:29 | @/.snapshots/12/snapshot | post | luajit                                        |
Found snapshot: 2023-09-07 09:40:28 | @/.snapshots/11/snapshot | pre  | pacman -Su                                    |
Found snapshot: 2023-09-07 06:54:37 | @/.snapshots/10/snapshot | post | apache                                        |
Found snapshot: 2023-09-07 06:54:36 | @/.snapshots/9/snapshot  | pre  | /usr/bin/pacman -S --noconfirm extra/apache   |
Found 10 snapshot(s)
Unmount /tmp/grub-btrfs.kh1GrWx42P .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
22

It looks like it’s detected now. Have you checked the Garuda Grub menu yet to see if it has been added?

2 Likes
23

So you installed Arch. How did you install Arch?
You are also booting Windows, too?
And now installed Garuda.

So you have (at least) 3 systems installed and something is messed up and you don't know why but you expect us to help fix it?

Does that about summarize it correctly?

1 Like
24

@Bro did you wake up on the wrong side of the bed today? :laughing:

3 Likes
25

Yes.

1 Like
26

the arch install medium may not have the needed SCSI interface driver to recognize it as a root partition during install. it may also have something to do with multiple OS's sharing an EFI parition.
Windows will mess with and change it's own EFI partition if it sees any changes.

these new nvme setups use a PCI interface to utilize the SSD and not the standard ATA/SATA and therefore need to have a specific hardware driver available during the installation process, which may just be why the WIndoze and Garuda installs are seen to and work to boot up but not the Arch one.

i recommend having each OS on it's own SSD for this reason and so that each OS has it's own EFI partition, which from that point you can instruct your BIOS/UEFI to manually select which EFI to load as the primary bootloader when you start up your machine.

if you cannot use multiple SSD's then i suggest manually partitioning the SSD's you have to provide each OS with it's own EFI parition, assuming that it's possible to have more than one EFI on any one single drive.

this will require the total wiping of all your hard drives so backup ALL of your user data accordingly.

edit:

"EFI System Partition or ESP is a special partition on a disk that contains executables and associated files required to boot up a machine. The executables in this partition are '.efi' files that set up an environment for the rest of the OS to boot. This can be filesystem drivers, USB plugins, ACPI assistance etc. There will be an "EFI" directory within in the ESP that contains the efi executables."
" It might seem like the ESP is unique to a disk and there can be only one ESP for a disk based on the way the OS treats the ESP. Unlike MBR, on GPT, the ESP doesn't have to be at the beginning of the disk and there can be many ESPs for a disks. This will allow you have multiple boot environments with different configurations for a single disk. You can have Debian EFI and Windows EFI on the same disk, isolated from each other, without having to chainload boot executables. You can even have another ESP with some other boot environment like Ventoy on the same disk, allowing you too boot linux live environments without an external storage ( I will write another article on this)."

1 Like
27

No, I don’t have Windows installed as you can see in multiple posts of mine, there are only 3 partitions installed: Arch, Garuda and an esp.
Windows came preinstalled but I overwrote it, no clue why it’s bootloader is still an option in my UEFI Boot settings, I havn’t tried launching it.

Also I don’t necessarily want you to fix it, I want to have Garuda and Arch installed alongside eachother and I want to be able to boot both from the same bootloader. If you tell me there is smth wrong with my system and I can “fix” it by completely reinstalling everything, while paying attention to this and that I am fine doing so. You don’t need to help me repair my system (in case it’s corrupt) but just saying how can I make it work even with a completely new install would be perfectly fine by me.
Just for that I would have to know that there is an actual problem right now, and how to not let it accur again in an fresh install.

See I have no idea what’s wrong and what to do about it, and just hope there might be someone that can help me with that.

28

Yes, it is not added, sadly :frowning:

29

What is in /boot/efi/EFI?

exa --tree -L2 /boot/efi/EFI
1 Like
30

Try custom.cfg

1 Like
31

Thank’s, I’ll probably try this if I can’t bring anything else to work.

1 Like
32

Having more than one EFI partition on a disk will not work. It is no problem to have multiple installations share an EFI partition, I'm not sure why that is being suggested.

2 Likes
33 
╭─stk@stk in ~
╰─λ exa --tree -L2 /boot/efi/EFI
/boot/efi/EFI
├── BOOT
│  └── BOOTX64.EFI
├── Garuda
│  └── grubx64.efi
└── GRUB
└── grubx64.efi

Oh ok.

34

I’ll look this up. Thanks.

35

Is that bottom grubx64.efi in /boot/efi/EFI or is it in /boot/efi/EFI/GRUB?

I am not sure the Grub installation succeeded (on Arch, from the chroot). If you would be willing to try again, I’d be interested to look at the terminal output.

If you boot to the Garuda live environment to set up the chroot, it will be make it much easier to paste the input/output into the thread because you can just crack open a browser and log in to the forum from the live environment.

1 Like
36

chainloading from one EFI is problematic at best with a Windows install which, ever since win10, will overwrite your EFI whenever it updates itself.

each OS is best off with it's own segregated EFI that you can manually choose in GRUB when you set a GRUB to to boot from the BIOS options.

once it's setup properly you'll never need to mess with it again as each OS will update it's own EFI when you update the OS and remove the possibility of EFI overwrites and other bootloader issues.

37

There is a grubx64.efi in /boot/efi/EFI/GRUB and one in /boot/efi/EFI/Garuda, none in /boot/efi/EFI
https://termbin.com/nvm9

I will try this again.

38

First I chrooted into my garuda install using:

╭─garuda@garuda in ~ as 🧙 took 21ms
╰─λ sudo mount /dev/nvme0n1p3 /mnt

╭─garuda@garuda in ~ as 🧙 took 53ms
╰─λ sudo garuda-chroot /mnt/@
sh-5.1#

Then I mounted the efi partition:

sh-5.1# mount /dev/nvme0n1p1 /boot/efi

Then I installed GRUB again:

sh-5.1# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
Installing for x86_64-efi platform.
Installation finished. No error reported.

lsblk -f shows me:

sh-5.1# lsblk -f
NAME        FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
loop1
loop2
loop3
sda
|-sda1
`-sda2
sdb
sr0
zram0                                              [SWAP]
nvme0n1
|-nvme0n1p1                          434.2M    15% /boot/efi
|-nvme0n1p2
`-nvme0n1p3                          412.4G     3% /

And finally I regenerated the GRUB config file:

sh-5.1# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda-dr460nized/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Found Arch Linux (rolling) on /dev/nvme0n1p2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2023-09-07 19:36:58 | @/.snapshots/20/snapshot | post | libtiff srt tree|
Found snapshot: 2023-09-07 19:36:57 | @/.snapshots/19/snapshot | pre  | pacman -Syu tree|
Found snapshot: 2023-09-07 11:15:37 | @/.snapshots/18/snapshot | post | grub            |
Found snapshot: 2023-09-07 11:15:30 | @/.snapshots/17/snapshot | pre  | pacman -Su grub |
Found snapshot: 2023-09-07 10:44:48 | @/.snapshots/16/snapshot | post | libb2 libtorrent-rasterbar qbittorrent qt6-base qt6-svg qt6-translations |
Found snapshot: 2023-09-07 10:44:43 | @/.snapshots/15/snapshot | pre  | pacman -S --needed qbittorrent                                           |
Found snapshot: 2023-09-07 09:52:47 | @/.snapshots/14/snapshot | post | grub            |
Found snapshot: 2023-09-07 09:41:36 | @/.snapshots/13/snapshot | pre  | pacman -Su grub |
Found snapshot: 2023-09-07 09:40:29 | @/.snapshots/12/snapshot | post | luajit          |
Found snapshot: 2023-09-07 09:40:28 | @/.snapshots/11/snapshot | pre  | pacman -Su      |
Found snapshot: 2023-09-07 06:54:37 | @/.snapshots/10/snapshot | post | apache          |
Found snapshot: 2023-09-07 06:54:36 | @/.snapshots/9/snapshot  | pre  | /usr/bin/pacman -S --noconfirm extra/apache                              |
Found 12 snapshot(s)
Unmount /tmp/grub-btrfs.gMLzoto8kP .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

That should be it, right?

39

All those steps are correct, but you want to chroot into your Arch installation on p2--not the Garuda installation on p3.

You can exit out of the chroot, then unmount p3, mount p2 and go through all those same steps the exact same way and you should be good.

2 Likes
40

F …