Boot Stuck on Loading Initial Ramdisk

Guys, I really hope you’d be so kind as to help me. I’m a noob, and I’m struggling to resolve the issue. I have tried a meaningful number of solutions from the forum, and at some point I realized that I am risking messing something up severely.

The crux of the problem is that several months ago my system stopped loading, freezing at "loading initial ramdisk". Thinking that it may be some temporary package problem I reverted back to a snapshot that worked and stayed on it since. But the problem isn't resolving.

I am dual-booting with Windows (I know Garuda isn't supposed to be, but it had been working fine).

garuda-inxi

System:
Kernel: 5.17.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=51f78b03-ce2c-4d81-8364-4f8c1b537f00 rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma v: 5.24.4 tk: Qt v: 5.15.3 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 3604
date: 04/14/2021
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3
family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA201009
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3214 high: 4581 min/max: 2200/4950 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3603 2: 3511
3: 3141 4: 3048 5: 2573 6: 3021 7: 2873 8: 3711 9: 4581 10: 3524 11: 2887
12: 3590 13: 3966 14: 2885 15: 2312 16: 2870 17: 3271 18: 2871 19: 3488
20: 2875 21: 3213 22: 2870 23: 2873 24: 3592 bogomips: 177261
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: ASRock
driver: amdgpu v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: DP-2 empty: DP-1,DP-3,HDMI-A-1 bus-ID: 0d:00.0 chip-ID: 1002:73bf
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-2 mapped: DisplayPort-1 model: ROG XG27UQ serial: <filter>
built: 2020 res: 3840x2160 dpi: 164 gamma: 1.2
size: 596x335mm (23.46x13.19") diag: 684mm (26.9") ratio: 16:9 modes:
max: 3840x2160 min: 720x400
OpenGL: renderer: AMD Radeon RX 6800 XT (sienna_cichlid LLVM 13.0.1 DRM
3.44 5.17.1-zen1-1-zen)
v: 4.6 Mesa 22.0.0 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0f:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound Server-1: ALSA v: k5.17.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: N/A modules: iwlwifi pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: down mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 07:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-6:4 chip-ID: 8087:0029 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 1.93 TiB used: 323.58 GiB (16.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QGXA7
temp: 51.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Samsung model: SSD 980 PRO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 2B2QGXA7
temp: 56.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Kingston
model: DataTraveler 3.0 size: 115.33 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 1100 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: 323.58 GiB (34.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:6
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 323.58 GiB (34.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 323.58 GiB (34.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 323.58 GiB (34.7%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.31 GiB used: 883 MiB (2.8%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.0 C mobo: 48.0 C gpu: amdgpu temp: 57.0 C
mem: 58.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
Processes: 494 Uptime: 3d 8h 4m wakeups: 1 Memory: 31.31 GiB
used: 13.37 GiB (42.7%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1847 lib: 478 Shell: Zsh
v: 5.8.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.14
Garuda (2.5.6-2):
System install date:     2021-12-05
Last full system update: 2022-03-29
Is partially upgraded:   Yes
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

What didn't work for me:

When I was messing with the solutions offered in the last post I acquired a duplicated entry in grub and then some time later my Windows entry disappeared from there. I've been able to restore it in grub through some advice on this forum, but I am now afraid to mess around unsupervised.

Maybe try installing the linux-lts kernel

sudo pacman -Syu linux-lts linux-lts-headers

and see how it goes.

4 Likes

Thanks for the suggestion, but this didn't help either :frowning:

Firstly, looks like there has been a few system performance and stability improvements to your bios since your version:

If you are still having issues after the BIOS update (and no other help threads about this issue seem to help), maybe try doing a few passes of memtest just to be sure all of the RAM is okay so you can cross that off the list too.

4 Likes

Thank you for the suggestion. I updated bios and then, after pacman update complained about some packages not being compatible, ran garuda-update that, I think, finished without major errors. The problem, however, did not go away.

I guess with the updated bios I should try what I tried before - reinstalling the linux kernel from chroot and if that doesn't work will investigate MemTest86.

sorry, stupid follow up: was I supposed to do it from chroot or was regular login ok?

If you are still on the old restored system, from regular. If you tried updating and are stuck again, from chroot.
Either way, remember that booting to lts is not automatic, and you'll have to select it in GRUB under advanced options.

1 Like

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