After BIOS Update I can't boot into Garuda

Issues & Assistance
1

Hello! Few times asking help in forum I was advised to update my BIOS. The MSI manufacturer specify thou to not update the BIOS if everything goes fine and no bios issue it’s seen. But being new in Linux and 2-3 users told me few times to do it, I was thinking maybe they are right, so I did updated my BIOS. Right away on the first reboot after update I can’t anymore boot into Garuda. For enter into my system I have to use the USB Live stick and lose various minutes to go through all installation options for finally achieve to start Garuda.
I installed Garuda on a separated SSD, having Windows 10 also on other ssd. Few days ago I tried to update Windows and all was broken. I tried many options after read lot of tutorials but was not possible recover Wndows 10 neither to update it, neither to use anymore that SSD. The ssd appears on my disks manager but I can’t use in any way. So, I used only Garuda since that day and installed Windows on QEMU Virtual Machine for being able to use some software in Windows needed for my work. Abd everything was just fine…until I updated the BIOS!
Because after updating the BIOS, now I have another big problem added to the loose of Windows and its SSD. Now I have beside an unusable 500GB SSD, an “un-bootable” Garuda system. Which worked perfect before the BIOS update!
Here the inxi file if someone can help me solve some of these issues. Thanks in advance!

  Kernel: 6.14.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=2f678765-81ac-4c6e-a969-e67fac01d040 rw rootflags=subvol=@ loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.12.0 wm: kwin_wayland tools:
    avail: i3lock vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG Z690 EDGE WIFI DDR4 (MS-7D31) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American Megatrends LLC. v: 1.K0
    date: 10/14/2024
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP arch: Alder Lake gen: core 12
    level: v3 note: check built: 2021+ process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151)
    stepping: 2 microcode: 0x38
  Topology: cpus: 1x dies: 1 clusters: 10 cores: 16 threads: 24 mt: 8 tpc: 2 st: 8 smt: enabled
    cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB L2: 14 MiB
    desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB desc: 1x30 MiB
  Speed (MHz): avg: 807 min/max: 800/5200:5100:3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 807 2: 807 3: 807 4: 807 5: 807 6: 807 7: 807 8: 807 9: 807 10: 807
    11: 807 12: 807 13: 807 14: 807 15: 807 16: 807 17: 807 18: 807 19: 807 20: 807 21: 807 22: 807
    23: 807 24: 807 bogomips: 152985
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel AlderLake-S GT1 vendor: Micro-Star MSI driver: i915 v: kernel alternate: xe
    arch: Xe process: Intel 10nm built: 2020-21 ports: active: none empty: DP-4, DP-5, HDMI-A-3,
    HDMI-A-4, HDMI-A-5, HDMI-A-6 bus-ID: 00:02.0 chip-ID: 8086:4680 class-ID: 0380
  Device-2: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: ASUSTeK driver: nvidia v: 570.133.07
    alternate: nouveau,nvidia_drm non-free: 550/565.xx+ status: current (as of 2025-01;
    EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: none off: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2
    bus-ID: 01:00.0 chip-ID: 10de:2208 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6 compositor: kwin_wayland
    driver: X: loaded: modesetting,nvidia unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DP-2 model: LG (GoldStar) ULTRAGEAR+ serial: <filter> built: 2024 res:
    mode: 3840x2160 hz: 60 scale: 100% (1) dpi: 140 gamma: 1.2 size: 697x392mm (27.44x15.43")
    diag: 800mm (31.5") ratio: 16:9 modes: max: 3840x2160 min: 640x480
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia nouveau drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 2 drv: nouveau device: 3 drv: swrast gbm: drv: iris
    surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 memory: 11.72 GiB
    display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 14 device: 0 type: discrete-gpu name: NVIDIA GeForce RTX 3080 Ti
    driver: N/A device-ID: 10de:2208 surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu
    name: Intel UHD Graphics 770 (ADL-S GT1) driver: N/A device-ID: 8086:4680
    surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM 19.1.7 256 bits)
    driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: corectrl, nvidia-settings, nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA102 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
  Device-3: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-11:4 chip-ID: 0db0:1feb class-ID: 0300
  Device-4: Corsair HS80 MAX WIRELESS Gaming Receiver driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 1b1c:0a97
    class-ID: 0300 serial: <filter>
  API: ALSA v: k6.14.2-zen1-1-zen status: kernel-api with: aoss type: oss-emulator tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.4.2 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 Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:7af0 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: Micro-Star MSI driver: igc v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: enp5s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
  IF-ID-1: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
  IF-ID-2: virbr0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 1-14:8 chip-ID: 8087:0026 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: no address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no
    pairing: no
Drives:
  Local Storage: total: 4.11 TiB used: 1.43 TiB (34.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Crucial model: CT500P3PSSD8 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: P9CR413 temp: 45.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS100T1X0E-00AFY0
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 614900WD temp: 45.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 043 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 2B6Q scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 vendor: Kingston model: DataTraveler 3.0 size: 14.44 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1
    mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 201.81 GiB (21.7%) fs: btrfs
    dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 297.9 MiB (99.5%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:1
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 201.81 GiB (21.7%) fs: btrfs
    dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 201.81 GiB (21.7%)
    fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 201.81 GiB (21.7%)
    fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.12 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 24 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.12 GiB used: 5.41 GiB (17.4%)
  Processes: 477 Power: uptime: 27m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.38 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1891 pm: pacman pkgs: 1876 libs: 557 tools: octopi,paru pm: flatpak pkgs: 15
    Compilers: clang: 19.1.7 gcc: 14.2.1 Client: Unknown Client: garuda-rani inxi: 3.3.37
Garuda (2.7.2-1):
  System install date:     2025-03-22
  Last full system update: 2025-04-19
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:
2

Check new BIOS, disable fast and secure boot, change boot order to garuda.

6 Likes
3

I did checked after update, and I disabled Fast Boot + Secure Boot, BUT… I have not anymore (I can’t see it) Garuda in BIOS boot order options! It’s disappeared! And I only can enter Garuda from Live stick.

4

I have a MSI motherboard. When updating the bios, it always goes back to the default settings. Specifically, Secure Boot: On → Switch to “Disable” (it defaults to on). I also need to match the speed of my DDR5’s to the correct settings (default was non-optimal). The last thing is to check your boot device order, it may be waiting for a drive that isn’t there.

5

I can’t count how often I update the BIOS on different PC’s and Notebooks, but never the BIOS removed my OS, Linux or M$. Never.
Boot live ISO, mount all devices and post

lsblk -f
4 Likes
6

I don’t know what DDR5 speed is. Has anything to do with my booting issue? My motherboard is DDR4!

7

I’m now inside Garuda. I booted on Live ISO and I’m inside the installed System.
And I have the Terminal output from “lsblk -f” but I don’t know how to copy/paste it from terminal to here only screen shoot (sorry the first was wrong one!)

Screenshot_20250419_212730
Screenshot_20250419_2127301140×847 146 KB

8

Please, start learning the basics.
Mark the text and copy with
Ctrl + Shift + C
Paste in terminal is
Ctrl + Shift + V

I see your Garuda partition. But I can’t copy the text from a picture.

5 Likes
9 
NAME      FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1    ntfs         Crucial 2T  522E9DAF2E9D8D1B                      948,9G    49% /run/media/elkamynante/Crucial 2T
sdb
└─sdb1    ntfs         Samsung 1TB 30E8E795E8E7579C                      582,4G    37% /run/media/elkamynante/Samsung 1TB
sdc
├─sdc1    exfat  1.0   Ventoy      4E21-0000
└─sdc2    vfat   FAT16 VTOYEFI     626B-4255
zram0     swap   1     zram0       3de1fe41-b351-4d5d-870e-d5a5ed82cfb8                [SWAP]
nvme1n1
├─nvme1n1p1
│         vfat   FAT32             5199-EC6C                               1,5M    99% /boot/efi
└─nvme1n1p2
btrfs                    2f678765-81ac-4c6e-a969-e67fac01d040  728,5G    22% /var/log
/var/tmp
/var/cache
/home
/root
/srv
/
nvme0n1
├─nvme0n1p1
│
└─nvme0n1p2
ntfs                     7428FF8428FF43A0                      465,2G     0% /run/media/elkamynante/7428FF8428FF43A0

Thank you for this!

10

You could try reinstalling the GRUB from your live USB.
I hope this is not going to be a problem:

Your EFI system partition seems to be full.

3 Likes
11

Is there some way to “empty” it?
As for reinstalling the grub I have no idea how to do it!

12

Depends on what’s in there :wink:

There must be a button to do this in the live USB (I’m off without a laptop for a few days).
Or check this tutorial to do it manually:

4 Likes
13

You know how to manage the uefi boot order inside bios ?

sda sata 2tb not possible to boot ..check (no efi boot partition → no uefi bios entry)

sdb sata 1tb not possible to boot ..check ( = sda)

sdc ventoy usb live.iso …can boot ..check (sdc2 efi partition → uefi bios entry)

nvme 1 500GB installed linux (…should boot if you have the correct bios boot order ) check
nvme1n1p2 your root partition to boot over efi partition

your efi partition ..something is not right.. default we should see like this

sdb
├─sdb1 vfat FAT32 efi-dragon 3E54-F5B0 298,8M 0% /boot/efi
└─sdb2 btrfs dragon fd644241-2723-4347-b0fc-747c588e12fa 245,5G 47%

Perhaps you must delete all useless files inside the efi partition
Default you have one or two folder there. /boot/efi/Efi/Garuda + /boot/efi/EFI/boot

  • 1 file on each folder (grubx64.efi / bootx64.efi). If you have more folder/files there → pls delete.
    To see if and to fix : boot live-iso → Garuda chroot → Konsole → command mc
    navigate to /boot/efi/Efi/ and delete the useless stuff. (F8 = delete) → if ready press F10 then command exit…check
    After this step run Garuda Boot Repair → use first option (reinstall) choice esp + correct partition efi + root (nvme1n1p1 + nvme1n1p2 → apply → rdy …check

nvme 0 500GB 2 partitions

    • nvme0n1p1 → not formatted (default is this the efi partition formatted with vfat (fat32) to boot M$ ( inside data M$ bootmanager)
    • nvme0n1p2 ntfs …possible there is M$ installed but can´t boot reason no bootmanager
      to boot
  3. missing also some partition there..but who knows why… me not
    This nvme is useless unless you fix it with an M$ iso. (sorry no help for this)
  4. Boot order now for your uefi bios boot settings …nvme1
    (you read only perhaps UEFI OS (Nv… not Garuda inside bios)
  5. Take a look inside bios settings… ahci mode for your harddrive (not raid) ..bios mode must be set to uefi.. secure boot off …fastboot off
    → save settings → reboot–> result ?

@ Garuda Team one time more…sorry for my very long post and i know..not a garuda issue
@ djbashtan Linux..special arch os is a learning by doing and reading to become more knowledge about what i do 20 inch in front from my monitor. :innocent:

14

Hey, thank you a lot for these instructions. But of course, me being a total ignorant in Linux I’ve messed-up some things here so being tired of this :poop:, I took the short and easy way and I reinstalled Garuda. Now my PC starts normal and all looks ok, only having 1 OS, Garuda. And now I have to start again to (re)configure the system and apps, hopping I will can keep it for much longer time running ok (very improbable thou). I come to the conclusion, Linux OS is made specifically to get people mad :innocent:
Greetings and best wishes!

15

I clean re-install is always an option if you have backups. :slight_smile:

Just wanted to throw in: Dual-booting Garuda and Windows generally works fine with just small caveats. However, Windows must be installed first, then Garuda, and ideally on different drives. If Windows is installed second, Redmond eliminates the competition.

16

And the more you learn, the more you can fix (for yourself).

4 Likes
17

There are a lot more ‘bells & whistles’ in BIOS these days, setting memory speed is one of them. The default memory settings (a configurable parameter in my bios) won’t change anything with booting.
The key item is that upgrading BIOS on the MSI motherboard, I have, always resets all settings back to some ‘default’ settings. So after I update bios, the first reboot for me is into bios to change the ‘default’ settings to appropriate ones. I’ve written these down to remind me (MSI has been averaging ~1 upgrade/month for the MPG X870E CARBON WIFI).

18

Yeah, I was supposing MSI would do exactly that (returning to default) and that why immediately after updating it I configured back “my settings” disabling Fast Boot and Secure Boot and trying to fix the Boot order. Tht was when I’ve seen first time my problem was very different because, my Garuda OS was simply “dissipated”, “gone”, “not-existent”, from BIOS and from that point I’ve only been able to start my system using the Live stick. Anyway, now I was so smart and I solved a very difficult Linux mystery that nobody knew how to do it: I reinstalled Garuda from scratch! :rofl: (and of course, as expected, now I have others different “mysteries” to solve :rofl:
Bro, I’m asking myself, how is possible in Garuda Linux, every “install” is different that the one before! Inexplicable for me so far!. I’ve reinstalled Garuda 3 times by now, and each one was totally different, new issues every time and me, amazingly and bravely and crazily, spending more time to read and find how to fix issues, than to use the system :rofl:)

19

:rofl: I’m sure if I go like now, in 1 year I will be frikin expert in “Garuda fixing issues”. Problem is I’m afraid I start to notice a vague feeling of “enough is enough”, and go back to Windows :rofl:. Well, we’ll see how that goes! For now I’m heroically ressisting the temptation! :innocent:

20

I didn’t had Windows installed at that point in “history”. Was only Garuda on a ssd and nothing else on 3 others ssds. After Bios Update, nevertheless, my Garuda OS doesn’t existed anymore on bios. It existed of course on my ssd, but would only start using the Live stick! Using the grub menu from Ventoy was the only way to find my Garuda efi partition and start the system.