Garuda boot option missing from GRUB

Dasfiter · 23 June 2024 18:49

I just finished doing the song and dance regarding using a live USB iso to do garuda-chroot and the option does appear in the bios to boot. However, it does nothing. Mind you that I am booting from an nvme drive not sure if that changes anything.

When trying to boot from grub garuda is no longer present after the last update. I am currently running dual boot win10 and Garuda. Though at this point I’m almost ready to nuke windows entirely to hopefully avoid issues like this. (Unclear if it was related since I haven’t booted into windows in the last year)

I’ve tried disabling uefi, enabling it, any combination thereof, the system has been running fine for the last year and a half until last night’s garuda-update. I’m not sure what to do now. I’m at the limit of my knowledge. I could use some help.

filo · 23 June 2024 19:14

What exactly have you done inside chroot? Song and dance doesn’t help …

Dasfiter · 23 June 2024 19:43

I followed the instructions to reinstall grub since I figured it might’ve had to do with that. I mounted the proper partition and then installed grub and dis grub update. It seems that that might not have been the issue. I checked in /mnt/boot/efi and all the proper efi files are there, but when I try to boot to the garuda one using ventoy it seems goes to a black screen and then returns me to the bios.

filo · 23 June 2024 20:00

It might help to see the details of those steps, to check if e.g. the update-grub was ok.
In addition you could provide

cat /etc/fstab
lsblk -prfo +PARTUUID
efibootmgr

How did this all started?
If after a garuda-update, maybe something went wrong there and you could launch it again from inside chroot.

Dasfiter · 23 June 2024 20:22

Excellent idea. Allow me to boot up the live iso again and try that.

Dasfiter · 23 June 2024 20:50

This all started this morning. The only significant change I did last night was garuda update. I was also trying to see why ollama would only run with the CPU, but that, I imagine, would not impact the system since I was only modifying the ollama service and the rocm files.

This is from the live iso, doing grub-update after doing chroot went without a hitch. My current Garuda system lives in /dev/nvme0n1p5, but even after a successful grub installation the system still does not show up on grub.

cat /etc/fstab
File: /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
/dev/mapper/root-image /             auto      defaults           0      0

lsblk -prfo +PARTUUID
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
/dev/loop0 squashfs 4.0   0 100% /run/miso/sfs/livefs
/dev/loop1 squashfs 4.0   0 100% /run/miso/sfs/mhwdfs
/dev/loop2 squashfs 4.0   0 100% /run/miso/sfs/desktopfs
/dev/loop3 squashfs 4.0   0 100% /run/miso/sfs/rootfs
/dev/sda
/dev/sda1 btrfs  sl_small 6e2831a2-2ad0-4ee7-80bf-db3eebe050be    05d640ff-344c-4815-9989-f43918ef74ac
/dev/sdb
/dev/sdb1 btrfs  Big\x20Boi 7367d22e-37c8-4b80-b417-5632d634da96    c3336ce5-f3c4-418c-a52e-5c8c3276b8f6
/dev/sdc
/dev/sdc1 ntfs  Big\x20Chungus 01D78186EE901620    6652fddd-915d-c899-d977-1ddcf9456916
/dev/sdd
/dev/sdd1 ntfs  Hybrid\x202 DA18EF3E18EF17F1    db8cdcc1-01
/dev/sde
/dev/sde1 exfat 1.0 Ventoy BE04-BEED    a9983fc6-2c78-8712-b574-17bd1c575dd3
/dev/mapper/ventoy iso9660 Joliet\x20Extension GARUDA_DR460NIZEDGAMING_BIRDOFPR 2024-04-28-13-20-22-00 0 100% /run/miso/bootmnt
/dev/sde2
/dev/sdf
/dev/zram0       [SWAP]
/dev/nvme1n1
/dev/nvme1n1p1 btrfs  Nvme1 dfd83670-b8b9-4447-99ab-63ec236c8259    fbc4444b-60c8-43cb-8ee4-9edff7590457
/dev/nvme0n1
/dev/nvme0n1p1 vfat FAT32  181A-EEC8    64475a12-cb08-4f9a-acd5-c3d442052430
/dev/nvme0n1p2        586c1c41-0ffb-42fc-99de-01995c179209
/dev/nvme0n1p3 ntfs   181624B316249432    422da5c2-181d-4417-ab2a-e24a68892213
/dev/nvme0n1p4 ntfs   506457F16457D7F4    8e03e2d0-1e6f-4658-a22a-f25252480938
/dev/nvme0n1p5 btrfs   35d598b9-8535-4b02-af0c-3bb4cfbf2a39    622374e7-2aee-0d49-aebd-123639b61caf

efibootmgr
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0003,0000,0004,0005,0006,0007
Boot0000* Windows Boot Manager HD(1,GPT,64475a12-cb08-4f9a-acd5-c3d442052430,0x800,0x32000)/
\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004
a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030
002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000
010000000040000007fff0400
Boot0003* garuda HD(1,GPT,64475a12-cb08-4f9a-acd5-c3d442052430,0x800,0x32000)/\EFI\GAR
UDA\GRUBX64.EFI
Boot0004* Hard Drive BBS(HD,,0x0)0000474f00004e4fad00000001000000730049004e00540045004c002
000530053004400500045004b004e0057003000320030005400380000000501090002000000007fff040002010c00
d041030a00000000010106000101010106000000031710000100000000000000000000007fff040001043600ef476
42dc93ba041ac194d51d01b4ce6500048004e0048003900320030003600300032005a005500320050003000430000
007fff04000000424f00004e4fcf0000000100000087006100640064006c0069006e006b0020004d002e003200200
050004300490045002000470033007800340020004e0056004d00650000000501090002000000007fff040002010c
00d041030a0000000001010600020101010600000001010600000101010600000003171000010000006479a746503
01a427fff040001043e00ef47642dc93ba041ac194d51d01b4ce63200390036004400300037003100310031004500
310045003000300031003300390036003200380000007fff04000000424f00004e4fc900000001000000810053006
1006d00730075006e006700200053005300440020003800340030002000500052004f002000530065007200690065
00730000000501090002000000007fff040002010c00d041030a00000000010106000201010106000000010106000
00a01010600000003120a000000ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63100530054
00410053004e004400410030004200350031003400310020004100200020002000200000007fff04000000424f000
04e4fb300000001000000810043005400320030003000300042005800350030003000530053004400310000000501
090002000000007fff040002010c00d041030a0000000001010600020101010600000001010600000a01010600000
003120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce6330032003100340038004500
4400370033004400350045002000200020002000200020002000200000007fff04000000424f00004e4fb90000000
1000000810053005400340030003000300044004d003000300034002d003200430056003100300034000000050109
0002000000007fff040002010c00d041030a0000000001010600020101010600000001010600000a0101060000000
3120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020
002000200020002000200046005a0034004e003900350032004c0000007fff04000000424f00004e4fb9000000010
000008100530054003200300030003000440058003000300032002d00320044005600310036003400000005010900
02000000007fff040002010c00d041030a0000000001010600020101010600000001010600000a010106000000031
20a000500ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce62000200020002000200020002000
2000200020002000200034005a0042005a00310032005700370000007fff04000000424f
Boot0005* UEFI: Generic-USB3.0 CRW -SD1.00, Partition 1 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3
)/USB(1,0)/HD(1,GPT,a9983fc6-2c78-8712-b574-17bd1c575dd3,0x800,0x7730b7d8)0000424f
Boot0006* UEFI: Generic-USB3.0 CRW -SD1.00, Partition 2 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3
)/USB(1,0)/HD(2,GPT,07b18dec-7eb1-97a7-e91f-5d94b5848e56,0x7730bfd8,0x10000)0000424f
Boot0007* USB BBS(HD,,0x0)0000474f00004e4fa9000000010000006100470065006e0065007200690063002
d0055005300420033002e003000200043005200570020002d005300440031002e0030003000000005010900020000
00007fff040002010c00d041030a000000000101060001080101060003000305060001007fff040001042e00ef476
42dc93ba041ac194d51d01b4ce632003000310035003000360033003000310030003100330000007fff0400000042
4f

sudo mount /dev/nvme0n1p5 /mnt
sudo garuda-chroot /mnt/@filo 

sh-5.2# ls /etc/mkinitcpio.d
linux-zen.preset.pacsave
sh-5.2# ls /boot
amd-ucode.img  efi  grub  memtest86+
sh-5.2# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=181A-EEC8                            /boot/efi      vfat    umask=0077 0 2
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /              btrfs   subvol=/@,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /home          btrfs   subvol=/@home,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /root          btrfs   subvol=/@root,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /srv           btrfs   subvol=/@srv,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /var/cache     btrfs   subvol=/@cache,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /var/log       btrfs   subvol=/@log,defaults,noatime,compress=zstd,discard=async,ssd 0 0
UUID=35d598b9-8535-4b02-af0c-3bb4cfbf2a39 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,compress=zstd,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 00

Dasfiter · 23 June 2024 22:46

The Garuda Linux system failed to boot into the OS, displaying only the UEFI firmware and Windows boot options. This happened due to the GRUB bootloader being unable to find the necessary kernel and initramfs files.

Root Cause

The primary issue was that the kernel image and initramfs were missing from the /boot directory. This likely happened due to an update or system change that removed or corrupted these files.

Solution Steps

1. Boot from a Live USB

Create a bootable USB with a Linux distribution (Garuda or any other live environment).
Boot from the USB.

2. Mount the Partitions

Identify the partitions:
```
lsblk
```

Mount the root and EFI partitions:

sudo mount /dev/<your_partitions>/mnt
sudo mount /dev/<your_partitions> /mnt/boot/efi

3. Enter the Chroot Environment

Enter chroot:

sudo garuda-chroot /mnt/@

4. Ensure Kernel and Initramfs Files are Present

Reinstall the linux-zen kernel:

pacman -S linux-zen --noconfirm
Rebuild the initramfs:

mkinitcpio -P

5. Update GRUB Configuration

Generate the GRUB configuration file:
```
grub-mkconfig -o /boot/grub/grub.cfg
```

6. Clean Up and Reboot

Exit chroot:
Reboot the system: