GRUB not showing Garuda Linux or Advanced Option for Garuda Linux

garuda-inxi 

System:
Kernel: 6.6.30-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/timeshift-btrfs/snapshots/2024-05-07_11-15-39/@/boot/vmlinuz-linux-lts
root=UUID=4bf4066e-96bc-4453-b382-258f40dfaa15 quiet
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3 ibt=off
rootflags=defaults,noatime,space_cache,noautodefrag,compress=zstd,subvol=timeshift-btrfs/snapshots/2024-05-07_11-15-39/@
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: TUF Gaming FX505GE_FX505GE v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: FX505GE v: 1.0 serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: FX505GE.307
date: 05/25/2020
Battery:
ID-1: BAT0 charge: 18.3 Wh (95.8%) condition: 19.1/48.1 Wh (39.7%)
volts: 12.3 min: 11.7 model: Simplo SDI ICR18650 type: Li-ion
serial: <filter> status: charging cycles: 41
CPU:
Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF6
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 1616 high: 2200 min/max: 800/4100 scaling:
driver: intel_pstate governor: performance cores: 1: 2200 2: 2200 3: 2200
4: 800 5: 800 6: 2200 7: 2200 8: 800 9: 2200 10: 800 11: 800 12: 2200
bogomips: 52815
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
ports: active: eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:3e9b
class-ID: 0300
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2024-04; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s ports: active: none empty: HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:1c8c class-ID: 0300
Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:3
chip-ID: 13d3:56a2 class-ID: 0e02 serial: <filter>
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: modesetting,nvidia dri: iris
gpu: i915,nvidia display-ID: 0
Monitor-1: eDP-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: iris device: 3 drv: swrast surfaceless:
drv: nvidia wayland: drv: iris x11: drv: iris inactive: gbm,device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.6-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
GT2) device-ID: 8086:3e9b memory: 7.43 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 8 device: 0 type: integrated-gpu name: Intel
UHD Graphics 630 (CFL GT2) driver: mesa intel v: 24.0.6-arch1.2
device-ID: 8086:3e9b surfaces: xcb,xlib,wayland device: 1
type: discrete-gpu name: NVIDIA GeForce GTX 1050 Ti driver: nvidia
v: 550.78 device-ID: 10de:1c8c surfaces: xcb,xlib,wayland device: 2
type: cpu name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.0.6-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK
driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
API: ALSA v: k6.6.30-1-lts status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.0.5 status: active 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: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: down mac: <filter>
IF-ID-1: br10 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:4
chip-ID: 8087:0aaa class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
Drives:
Local Storage: total: 1.14 TiB used: 221.43 GiB (18.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston
model: RBUSNS8154P3256GJ size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 15.8 Gb/s lanes: 2 tech: SSD serial: <filter>
fw-rev: E8FK11.C temp: 42.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LX015-1U7172
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: SDM1 scheme: GPT
Partition:
ID-1: / raw-size: 238.22 GiB size: 238.22 GiB (100.00%)
used: 221.43 GiB (93.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%)
used: 558 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 238.22 GiB size: 238.22 GiB (100.00%)
used: 221.43 GiB (93.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 238.22 GiB size: 238.22 GiB (100.00%)
used: 221.43 GiB (93.0%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 238.22 GiB size: 238.22 GiB (100.00%)
used: 221.43 GiB (93.0%) fs: btrfs 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: 7.61 GiB used: 287.8 MiB (3.7%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.0 C pch: 59.0 C mobo: N/A
Fan Speeds (rpm): cpu: 0
Info:
Memory: total: 8 GiB available: 7.61 GiB used: 3.05 GiB (40.0%)
Processes: 327 Power: uptime: 7m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 3.02 GiB services: org_kde_powerdevil,
thermald, upowerd Init: systemd v: 255 default: graphical tool: systemctl
Packages: 2557 pm: pacman pkgs: 2521 libs: 511 tools: pamac,paru
pm: flatpak pkgs: 36 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi
default: Zsh v: 5.9 running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2023-08-17
Last full system update: 2024-05-07
Is partially upgraded:   No
Relevant software:       snapper(custom) tlp NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:            postgresql.service [email protected]

When I started my system today the only options I see on the GRUB menu

  • UEFI settings
  • Garuda snapshots
  • Restart
  • Shutdown

I do not see the bootable OS but the snapshots work perfectly fine. When I restore a snapshot the option to boot the Garuda OS still doesn’t show up. How do I proceed from here?

hmm I’d try to boot the live system, and use garuda boot repair. If that doesn’t work, chroot into garuda from the welcome menu and run update-grub there

2 Likes

So I had a question

  1. when I try to use garuda-chroot from the snapshot it says garuda-chroot is not a command. Is there anyway to chroot through the snapshot. Is it only available through live USB?

Use garuda-welcome, chroot app from live ISO or the old way :wink:

or garuda-tools-base-git, with

garuda-chroot -a
3 Likes

I had a similar issue like a month ago after an update froze. These are the steps I did to finally resolve the issue. I have no idea what I am doing, i’m sure there is a better way, but maybe something in this helps.

Booted into live-is (usb)
Garuda-Welcome window (should open default)
Clicked "Chroot" (not sure if needed)
Started Btrfs Assistant 
Clicked snapper top tab
Clicked Browse/Restore
Clicked Last known good snapshot
Clicked Restore (top right)
Gave name (optional)
Told to reboot, rebooted 
Start up took much longer than normal
Cinnamon desktop loaded, ran upd from terminal
System updated without issue
rebooted to confirm issue was resolved

I tried chrooting through live USB. It is showing both my Garuda Linux and Arch Linux as Ubuntu.

sh-5.2# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub
Installing for x86_64-efi platform.
grub-install: error: /boot/efi doesn't look like an EFI partition.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
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/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Found Ubuntu 22.04.2 LTS on /dev/nvme0n1p2
Found Ubuntu 22.04.3 LTS on /dev/nvme0n1p2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2024-01-14 21:09:00 | timeshift-btrfs/snapshots/2024-03-21_00-24-30/@/var/lib/docker/btrfs/subvolumes/2cb5b68d1f00fa0b203736f0cd0901247d041d3c47abdec2fdcc723c92f114aa      | N/A      | N/A                |
Found snapshot: 2023-06-29 22:51:14 | timeshift-btrfs/snapshots/2024-03-21_00-24-30/@                         | ondemand | Before restoring '2024-03-20 22:06:51' |
Found snapshot: 2021-05-26 12:10:37 | timeshift-btrfs/snapshots/2022-08-29_15-56-46/@                         | ondemand | Before restoring '2022-08-28 21:00:02' |
Found 3 snapshot(s)
Unmount /tmp/grub-btrfs.KoIeInLC7f .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.

I removed a working snapshot by mistake and it isn’t showing any working snapshot for me anymore.

The Grub installation didn’t work. Is the EFI partition mounted in the chroot?

1 Like

Apologies I was mounting the wrong partition. I did it correctly now but still the error persists.

╭─garuda@garuda in ~ as 🧙 took 43ms
╰─λ sudo garuda-chroot /mnt/broken/@
sh-5.2# mount /dev/nvme0n1p1 /boot/efi
sh-5.2# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub
Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
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/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Found Ubuntu 22.04.2 LTS on /dev/nvme0n1p2
Found Ubuntu 22.04.3 LTS on /dev/nvme0n1p2
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2024-01-14 21:09:00 | timeshift-btrfs/snapshots/2024-03-21_00-24-30/@/var/lib/docker/btrfs/subvolumes/2cb5b68d1f00fa0b203736f0cd0901247d041d3c47abdec2fdcc723c92f114aa      | N/A      | N/A                |
Found snapshot: 2023-06-29 22:51:14 | timeshift-btrfs/snapshots/2024-03-21_00-24-30/@                         | ondemand | Before restoring '2024-03-20 22:06:51' |
Found snapshot: 2021-05-26 12:10:37 | timeshift-btrfs/snapshots/2022-08-29_15-56-46/@                         | ondemand | Before restoring '2022-08-28 21:00:02' |
Found 3 snapshot(s)
Unmount /tmp/grub-btrfs.mTFqlt3KIb .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

I still do not see garuda linux or advanced options for garuda linux in the grub menu.
Another query I had is why does it report the Garuda linux partition as Ubuntu?

I don’t think that’s what those are. They may be related to the Docker subvolume.

Have you ever used Grub Customizer?

From the live ISO, double-check the boot order with efibootmgr and make sure you are booting to the Grub you just installed.

sh-5.2# efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0000,0002,0003,0001
Boot0000* garuda        HD(1,GPT,12aa9f7b-f07d-b544-be6f-2f3774c89fa7,0x1000,0x80000)/\EFI\garuda\grubx64.efi
Boot0001* UEFI OS       HD(1,GPT,12aa9f7b-f07d-b544-be6f-2f3774c89fa7,0x1000,0x80000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot0002* UEFI: SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/CDROM(1,0x9233d0,0x8000)0000424f
Boot0003* UEFI: SanDisk, Partition 2    PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,MBR,0x0,0x9233d0,0x2000)0000424f

I have never used GRUB customizer

For now the Live USB boots before the others but the usual boot is correct

There is something odd going on here. :thinking:

The output from your Grub installation and efibootmgr looks fine. Let’s try getting back in the chroot, make sure the EFI partition is mounted and everything, and then reinstall the kernel.

pacman -S linux-lts

Paste the output into the thread, then reboot and see if it shows up as a bootable option in Grub.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.