Garuda gets stuck at Loading initial ramdisk even in recovery mode

When I install Garuda, the live distro works fine with both free and proprietary drivers. I do have NVIDIA GTX-1660ti and Intel UHD graphics. However, after the first mandatory update, I cannot even boot. I get stuck at 'Loading initial ramdisk'. The problem is that I cannot even get into the recovery mode, I see the same problem if I try to get into the recovery mode. I have seen others complaining the same, but they all could get into recovery mode to be able to do something.

garuda-inxi from the live-distro with the proprietary driver enabled.
╭─garuda@garuda in ~ as 🧙 took 1m5s
 ╰─λ sudo garuda-inxi
  Kernel: 6.2.13-zen-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=garuda root=miso:LABEL=GARUDA_GNOME_RAPTOR quiet
    systemd.show_status=1 ibt=off driver=nonfree nouveau.modeset=0
    i915.modeset=1 radeon.modeset=1
  Desktop: GNOME v: 43.5 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM v: 44.0
    Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: Dell product: G5 5500 v: N/A serial: <filter> Chassis:
    type: 10 serial: <filter>
  Mobo: Dell model: 0DV11C v: A02 serial: <filter> UEFI: Dell v: 1.24.0
    date: 03/14/2023
  ID-1: BAT0 charge: 54.7 Wh (100.0%) condition: 54.7/68.0 Wh (80.5%)
    volts: 15.9 min: 15.2 model: LGC-LGC4.474 DELL JJRRD0C type: Li-poly
    serial: <filter> status: full
  Info: model: Intel Core i7-10750H bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
    model-id: 0xA5 (165) stepping: 2 microcode: 0xF4
  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: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 2494 high: 2932 min/max: 800/5000 base/boost: 2673/2600
    scaling: driver: intel_pstate governor: powersave volts: 0.8 V
    ext-clock: 100 MHz cores: 1: 800 2: 2600 3: 2600 4: 2600 5: 2600 6: 2600
    7: 2600 8: 2600 9: 2600 10: 2932 11: 2600 12: 2797 bogomips: 62399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: DP-1 off: eDP-1 empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 0000:00:02.0
    chip-ID: 8086:9bc4 class-ID: 0300
  Device-2: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: Dell
    driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+
    status: current (as of 2023-03) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-22 bus-ID: 0000:01:00.0
    chip-ID: 10de:2191 class-ID: 0300
  Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-5:5 chip-ID: 0c45:671f class-ID: 0e02
  Display: server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1
    compositor: gnome-shell driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: DP-1 pos: primary model: LG (GoldStar) IPS QHD serial: <filter>
    built: 2023 res: 2560x1440 hz: 60 dpi: 123 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  Monitor-2: eDP-1 note: disabled model: LG Display 0x05e4 built: 2018
    res: 2560x1440 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
  Device-1: Intel Comet Lake PCH cAVS vendor: Dell
    driver: sof-audio-pci-intel-cnl alternate: snd_hda_intel, snd_soc_skl,
    snd_sof_pci_intel_cnl bus-ID: 0000:00:1f.3 chip-ID: 8086:06c8
    class-ID: 0401
  Device-2: NVIDIA TU116 High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 0000:01:00.1 chip-ID: 10de:1aeb
    class-ID: 0403
  API: ALSA v: k6.2.13-zen-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.70 status: n/a (root, process) 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
  Device-1: Intel Comet Lake PCH CNVi WiFi vendor: Rivet Networks
    driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:06f0
    class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek vendor: Dell driver: r8169 v: kernel port: 3000
    bus-ID: 0000:3a:00.0 chip-ID: 10ec:2502 class-ID: 0200
  IF: enp58s0 state: down mac: <filter>
  Device-3: Lite-On Dell Wireless Device type: USB
    driver: hid-generic,usbhid bus-ID: 1-2:2 chip-ID: 04ca:00bd class-ID: 0301
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-14:8 chip-ID: 8087:0026 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
  Hardware-1: Intel Comet Lake PCH-H RAID driver: intel_nvme_remap v: N/A
    port: 5060 bus-ID: 0000:00:17.0 chip-ID: 8086:06d7 rev: class-ID: 0104
  Local Storage: total: 1011.64 GiB used: 0 KiB (0.0%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: PC SN730
    NVMe WDC 1024GB size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B type: SSD serial: <filter> rev: 11170012 temp: 40.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 38d 5h cycles: 282
    read-units: 46,645,764 [23.8 TB] written-units: 43,435,207 [22.2 TB]
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: HP model: v236w
    size: 57.77 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No partition data found.
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.39 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  System Temperatures: cpu: 54.0 C mobo: N/A
  Fan Speeds (RPM): N/A
  Processes: 297 Uptime: 27m wakeups: 3 Memory: 15.39 GiB
  used: 5.07 GiB (33.0%) Init: systemd v: 253 default: graphical
  tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1211
  libs: 350 tools: pamac,paru Shell: garuda-inxi (sudo) default: Bash
  v: 5.1.16 running-in: gnome-terminal inxi: 3.3.26
Garuda (2.6.16-1):
  System install date:     2023-04-10
  Last full system update: 2023-04-10 ↻
  Is partially upgraded:   Yes
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Yes
  Failed units:            snapper-cleanup.service 

Maybe you could try switching to the LTS kernel.
Boot to your live USB and use the chroot function in the Garuda Welcome, then:

pacman -S linux-lts linux-lts-headers

Then exit from the chroot, reboot and select the LTS kernel under the GRUB Advanced options sub-menu.


The only thing that works about that is the recovery mode in lts kernel, regular and failsafe boot still gets stuck at the same point. However, booting in the recovery mode does not give a shell, it waits for a long time and then shows an emergency shell with some errors regarding dracut.

The following is the logs it -

The last few lines were as follows - /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[  194.405351] archlinux dracut-initqueue[486]:     [ -e "/dev/disk/by-uuid/d68ddd16-da61-4ae2-b6a9-96ddbf2b51c3" ]
[  194.405351] archlinux dracut-initqueue[486]: fi"
[  194.410503] archlinux dracut-initqueue[486]: Warning: dracut-initqueue: starting timeout scripts
[  194.922994] archlinux dracut-initqueue[486]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[  194.925864] archlinux dracut-initqueue[486]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\ "if ! grep -q /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[  194.925864] archlinux dracut-initqueue[486]:     [ -e "/dev/disk/by-uuid/d68ddd16-da61-4ae2-b6a9-96ddbf2b51c3" ]
[  194.925864] archlinux dracut-initqueue[486]: fi"
[  194.930568] archlinux dracut-initqueue[486]: Warning: dracut-initqueue: starting timeout scripts
[  194.930568] archlinux dracut-initqueue[486]: Warning: Could not boot.
[  194.957201] archlinux systemd[1]: Starting Dracut Emergency Shell...

The partition it is complaining about is the root file system of Garuda. Somehow it is not able to access the root filesystem for some reason.

Booting from the stock kernel (installed using pacman -S linux linux-header) and configuring grub actually shows the problem. I can now see that it is forever stuck at loading the root device.

When I get into the dracut emergency shell, I can see the USB device /dev/sda, but I cannot see the nvme device. So, somehow the initramfs is not loading the nvme devices.

Using AHCI instead of RAID in the BIOS boots the system just fine. However that stops Windows from working. Trying to add vmd module using dracut-rebuild fails with the error that vmd module cannot be found or installed.

Maybe you could try these kernel command line options (set according to chapter 3.3)?

1 Like

That’s right, this is the required setting. From the download page:

Make sure that your device’s SATA controller is set to AHCI mode in your device’s setup utility. Otherwise, the Linux kernel may not be able to detect your drive.

This sounds like an issue with your Windows configuration. I’m not sure why Windows would require your BIOS to be configured for RAID if you are not actually using a RAID setup, however troubleshooting Windows issues is somewhat beyond the scope of this forum.


Even though it is mentioned in the download page, the system did work just fine before the update. So I am still trying to make it work with RAID. Otherwise, I would have to go change the settings in BIOS every time I have to boot into Windows, which is workable. I am pretty sure it would be a lot harder to change Windows settings because of the lack of help. Thanks for the help, I will try the above suggestion. It is just taking me some time.

Apparently, just booting Windows once in safe mode was enough to make it install the AHCI drivers. Problem solved.

1 Like

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