Booting/installation failure 20250308 images

Issues & Assistance
1

Hi!

I’m trying to get garuda up and running but I do run from ‘error to error’.

At first there was just a black screen - used the fix with ventoy to boot the image.

But the image is showing an error - tested mokka and hyperland. As I’m a new user I cannot upload images…

It is showing something like:

dracut-init2queue{7331}: Warning: dracut-initqueue: starting timeput scripts
…
Warning: /dev/disk/by-label/GARUDA_HYPERLAND_BROADWING does not exist

Entering emergency mode…

That’s it - nothing more.

Any hints?

Kind regards,

1 Like
2

Did you remove the USB-Stick?
Did you install on USB-Stick?

Use live ISO to check lsblk -f and /ets/fstab
Search for /boot/ and the initramfs- images

3

Blockquote
Did you remove the USB-Stick?

No I didn’t

Blockquote
Did you install on USB-Stick?

No I didn’t

Blockquote
Use live ISO to check lsblk -f and /ets/fstab
Search for /boot/ and the initramfs- images

I do not reach the system. The last output is ‘Reached Target Basic System’ and after that the error-messages are shown…

4

This is standard for new members to prevent spam and other nonsense. You can use an external pic hoster and post the link here.

In Grub2 mode?

Checksum correct after download? Checksum of the iso on the ventoy-stick correct after copying?

BIOS settings correct? Secure Boot off, Fastboot off, AHCI on?
Manufacturer and model of the Mobo/PC/Laptop?

1 Like
5

Blockquote
In Grub2 mode?

yes

Blockquote
Checksum correct after download? Checksum of the iso on the ventoy-stick correct after copying?

yes

Blockquote
BIOS settings correct? Secure Boot off, Fastboot off, AHCI on?
Manufacturer and model of the Mobo/PC/Laptop?

yes
MSI MEG x570 unify

This is the error:

6

hi tom_246

i have both isos mokka and hyperland. i have a usb drive with those versions and more from garuda and it worked fine Ventoy and grub 2 at all. Did you have a older Ventoy USB Drive please update them or reinstall Ventoy again to your USB Drive.

Do you use the official isos from the Website or the devs isos?

7

Hi Duke187!

The ventoy I creaded three days ago - should be up to date.

I tested this stick with endeavour and manjaro and both do boot up to reach the desktop. Right now it’s something with the garuda-image, which is the original one - no dev-iso.

8

okay that is wired because i had those issues sometimes with the dev isos but actually installed via Ventoy Hyperland and its working on my pc. (garuda-hyprland-linux-zen-250308.iso downloaded and created on 17 march 25 and 2.6GiB)

9

Used an old garuda-iso (garuda-dr460nized-linux-zen-240428.iso) and this iso is just booting fine… Just did the upload to ventoy-stick…

I don’t know what changed between 240428 and 250308… but my PC doesn’t like it… :sweat_smile:

11

I tested some other USB-Sticks and an ssd connected by usb… always the same result…
Without ventoy garuda-iso will not boot, using ventoy I’m stuck at ‘reached targed basic system’…

So no chance for me to use Garuda? Will I have to wait for the next iso-release in 2026 to test it again? :wink: :innocent:

12

On which system you are creating the usb stick?

Do you want install to a ssd external or from it?

Did you try disconnect other ssd or other usb port?

Do you have a nvidia gpu card?

13

No problems on my PCs, with and without Nvidia GPU. The notebooks, AMD and Intel CPU, internal GPU, only work with the detour Grub2.

You are now the first one where nothing works.

Maybe it would be helpful for our developers if you would post garuda-inxi from an old Gauruda ISO.
Or from other OS, inxi -Faz.

BTW
How old is you Hardware?

1 Like
14

I’m creating the usb stick on the PC I will use to install/run Garuda (dual boot with Win).

For installation I will use free space on the internal nvme-drive.

I used several usb-ports - even installed a new pcie-card with usb-ports.

No, no nvidia gpu.

1 Like
15

Will do so - but it will be on the weekend - work…

I’m using an MSI x570 Motherboard with ryzen 9 5950x cpu.

16

Maybe it’s the other way around and “Broadwing” doesn’t like your PC. :grin:

I only know the error message from installed systems (and a simple dracut rebuild is usually enough), but I have never seen it on a live.iso.

Try disconnecting all internal drives and check whether the live.iso can then be booted without issues.

If none of this works, then simply install your working “Bird of Prey” garuda-dr460nized-linux-zen-240428.iso. After the system update it will be up to date, what you still need for “Broadwing” is kwin-effect-rounded-corners-git and (IIRC) the panel colorizer. You can install that afterwards if you want:

If you want Garuda Mokka, then also install the “Bird of Prey” dr460nized.iso and then migrate to Mokka:

If you want to install Garuda Hyprland, then take the “Bird of Prey” hyprland.iso:

2 Likes
17

This is the output of garuda-inxi.

sudo garuda-inxi
System:
Kernel: 6.8.7-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=1234 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7C35 v: 2.0 serial: N/A
Mobo: Micro-Star model: MEG X570 UNIFY (MS-7C35) v: 2.0 serial: <filter>
uuid: 1234 UEFI: American Megatrends LLC.
v: A.L1 date: 09/03/2024
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 5950X socket: AM4 bits: 64 type: MT MCP
arch: Zen 3+ gen: 4 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 2312 high: 3400 min/max: 2200/5083 boost: enabled
base/boost: 3400/5050 scaling: driver: acpi-cpufreq governor: schedutil
volts: 1.1 V ext-clock: 100 MHz cores: 1: 2200 2: 3400 3: 2200 4: 2200
5: 2200 6: 2200 7: 2200 8: 2200 9: 3400 10: 2200 11: 2200 12: 2200
13: 2200 14: 2200 15: 2200 16: 2200 17: 2200 18: 2200 19: 2200 20: 2200
21: 2200 22: 2200 23: 2200 24: 2200 25: 2200 26: 2200 27: 2200 28: 2200
29: 2200 30: 2200 31: 2200 32: 3400 bogomips: 217601
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel arch: RDNA-1 code: Navi-1x process: TSMC n7 (7nm)
built: 2019-20 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1
empty: DP-2,DP-3,HDMI-A-1 bus-ID: 2f:00.0 chip-ID: 1002:731f
class-ID: 0300
Display: server: X.Org v: 23.2.6 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :1 screens: 1
Screen-1: 0 s-res: 3440x1440 s-dpi: 96 s-size: 910x381mm (35.83x15.00")
s-diag: 987mm (38.84")
Monitor-1: DP-1 model: Mi Monitor serial: <filter> built: 2020
res: 3440x1440 hz: 50 dpi: 109 gamma: 1.2 size: 800x330mm (31.5x12.99")
diag: 864mm (34") modes: max: 3440x1440 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5700 (radeonsi navi10
LLVM 17.0.6 DRM 3.57 6.8.7-zen1-2-zen) device-ID: 1002:731f
memory: 7.81 GiB unified: no
API: Vulkan v: 1.3.279 layers: 3 device: 0 type: discrete-gpu name: AMD
Radeon RX 5700 (RADV NAVI10) driver: mesa radv v: 24.0.5-arch1.1
device-ID: 1002:731f surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.5-arch1.1 (LLVM
17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2f:00.1 chip-ID: 1002:ab38
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 31:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.8.7-zen1-2-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.5 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
Network:
Device-1: Mellanox MT27710 Family [ConnectX-4 Lx] driver: mlx5_core
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 8 port: N/A
bus-ID: 24:00.0 chip-ID: 15b3:1015 class-ID: 0200
IF: enp36s0f0np0 state: up speed: 10000 Mbps duplex: full mac: <filter>
Device-2: Mellanox MT27710 Family [ConnectX-4 Lx] driver: mlx5_core
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 8 port: N/A
bus-ID: 24:00.1 chip-ID: 15b3:1015 class-ID: 0200
IF: enp36s0f1np1 state: up speed: 25000 Mbps duplex: full mac: <filter>
Device-3: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 27:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp39s0 state: down mac: <filter>
Device-4: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 28:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlo1 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:2 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 1.85 TiB used: 4.29 GiB (0.2%)
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Crucial model: CT1000T500SSD8
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: P8CR004 temp: 34.9 C
scheme: GPT
SMART: yes health: PASSED on: 53 hrs cycles: 60
read-units: 455,843 [233 GB] written-units: 1,008,977 [516 GB]
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: 613200WD temp: 46.9 C scheme: GPT
SMART: yes health: PASSED on: 268d 4h cycles: 2,837
read-units: 41,917,600 [21.4 TB] written-units: 52,797,561 [27.0 TB]
ID-3: /dev/sda maj-min: 8:0 vendor: Intenso model: Alu Line
size: 29.53 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 2.0 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A serial: <filter>
fw-rev: 8.07 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 525.84 GiB size: 525.84 GiB (100.00%)
used: 4.25 GiB (0.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:8
ID-2: /boot/efi raw-size: 750 MiB size: 748.5 MiB (99.80%)
used: 584 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p5
maj-min: 259:7
ID-3: /home raw-size: 525.84 GiB size: 525.84 GiB (100.00%)
used: 4.25 GiB (0.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:8
ID-4: /var/log raw-size: 525.84 GiB size: 525.84 GiB (100.00%)
used: 4.25 GiB (0.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:8
ID-5: /var/tmp raw-size: 525.84 GiB size: 525.84 GiB (100.00%)
used: 4.25 GiB (0.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6
maj-min: 259:8
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 43.2 C mobo: N/A gpu: amdgpu temp: 32.0 C
mem: 36.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 65535
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 3.28 GiB (10.5%)
Processes: 569 Power: uptime: 10m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1247 libs: 370 tools: octopi,paru Compilers:
gcc: 13.2.1 Shell: garuda-inxi (sudo) default: Bash v: 5.2.26
running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2025-03-29
Last full system update: 2025-03-29
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:

What happened during installation is that the Windows Explorer is showing a btrfs-filesystem with some snapshots (‘@’, cache, home, log, root, srv, tmp) now. Disk management isn’t showing anything with this ‘drive letter’!?

What is this? Where is it coming from?

18

I think calamares choose only the volume and settings the user selects. @dalto :slight_smile: ?

19

It isn’t a network-share.

I mounted the network-share with another drive-letter and it is fine.

After reboot this new drive isn’t listed with the ip anymore - now it is a ‘local disk’.

Disk part is showing the two nvme-drives only but the disk management isn’t showing any drive with this letter… According to Windows Explorer it is some 11GB - there is no partition with this size…

20

I just included a fat32-partition with mount-point /boot/efi and the free space as /… Nothing more…

21

As I do know now how to get Garuda installed I deleted the two partitions I created for the Garuda installation and this ghost-partition is gone…

Funny thing…