Garuda (Gaming and Mokka) would not install on the latest ISO

Hi friends i tried installing Garuda on my new desktop. However both Garuda gaming, as well as Garuda Mokka i was unable to install with the latest ISO (26-06-2025,) on any of my m2 drives. i had to revert back to the May ISO edition, before i was able to install a fresh copy of Garuda Gaming, not sure if the Mokka ISO of that date also works for i did not try it.

All because the installer could not format my drives and would hang endlessly trying to make the new partitions. i did try to reformat the partitions i wanted to use, but to no avail. i have not tried an empty/fresh m2 drive for i haven’t got any.

System:
  Kernel: 6.15.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=fa32ef0e-5eeb-4831-b916-361f6644d308 rw rootflags=subvol=@
    quiet loglevel=3 ibt=off
  Desktop: KDE Plasma v: 6.4.3 tk: Qt v: N/A info: frameworks v: 6.16.0
    wm: kwin_wayland tools: avail: swayidle vt: 1 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Desktop System: NZXT product: N7 Z790 v: N/A
    serial: <superuser required>
  Mobo: NZXT model: N7 Z790 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: 10.07
    date: 04/25/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M275/M280
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: Intel Core i9-14900KF bits: 64 type: MST AMCP arch: Raptor Lake
    gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x12F
  Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
    st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
    KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 5700 min/max: 800/5700:6000:4400 scaling:
    driver: intel_pstate governor: performance cores: 1: 5700 2: 5700 3: 5700
    4: 5700 5: 5700 6: 5700 7: 5700 8: 5700 9: 5700 10: 5700 11: 5700 12: 5700
    13: 5700 14: 5700 15: 5700 16: 5700 17: 5700 18: 5700 19: 5700 20: 5700
    21: 5700 22: 5700 23: 5700 24: 5700 25: 5700 26: 5700 27: 5700 28: 5700
    29: 5700 30: 5700 31: 5700 32: 5700 bogomips: 203980
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA AD103 [GeForce RTX 4080] vendor: Gigabyte driver: nvidia
    v: 575.64.05 alternate: nouveau,nvidia_drm non-free: 550-570.xx+
    status: current (as of 2025-04) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 16
    ports: active: none off: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0
    chip-ID: 10de:2704 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: MSI G321CU built: 2022 res: mode: 3840x2160
    hz: 120 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: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4080/PCIe/SSE2
    memory: 15.62 GiB display-ID: :1.0
  API: Vulkan v: 1.4.321 layers: 16 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 4080 driver: nvidia v: 575.64.05
    device-ID: 10de:2704 surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.1.6-arch1.1 (LLVM
    20.1.8) device-ID: 10005:0000 surfaces: N/A
  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 Raptor Lake High Definition Audio vendor: ASRock
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22bb
    class-ID: 0403
  API: ALSA v: k6.15.8-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.7 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: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 07:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp7s0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, 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: 1-14:11 chip-ID: 8087:0032
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 17.4 TiB used: 12.73 TiB (73.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:9 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: P9CR40D temp: 40.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Fanxiang model: S880 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: SN17171 temp: 46.9 C
    scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:5 vendor: TeamGroup
    model: T-FORCE TM8FPZ004T size: 3.64 TiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EIFM51.3 temp: 41.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Seagate model: ST12000NM0127
    size: 10.91 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: G006 scheme: GPT
  ID-5: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST3500418AS
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC38 scheme: GPT
  ID-6: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SanDisk 3.2 Gen1
    size: 116.57 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
    fw-rev: DL17 scheme: GPT
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
    used: 61.09 GiB (38.4%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 920 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:1
  ID-3: /home raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
    used: 61.09 GiB (38.4%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:3
  ID-4: /var/log raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
    used: 61.09 GiB (38.4%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:3
  ID-5: /var/tmp raw-size: 159.18 GiB size: 159.18 GiB (100.00%)
    used: 61.09 GiB (38.4%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 46.87 GiB used: 239.3 MiB (0.5%)
    priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 51.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 48 GiB available: 46.87 GiB used: 5.92 GiB (12.6%)
  Processes: 587 Power: uptime: 5h 26m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 18.66 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2137 libs: 581 tools: gnome-software, octopi,
    pacseek, paru, trizen Compilers: clang: 20.1.8 gcc: 15.1.1
    Shell: garuda-inxi default: Bash v: 5.3.3 running-in: lxterminal
    inxi: 3.3.38
Garuda (2.7.3-2):
  System install date:     2025-07-26
  Last full system update: 2025-07-27 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units: 

My knowledge with calamares is:
If you run calamares and it fails and you reformat the drive inside this live-session = :no_entry:
The drive is “blocked” through calamares (my mind) and only with a restart from a live iso or running inside installed os is it then possible for a reformat.
I have tested the latest live-isos in this scenario and a i had the same result..without reboot or even shutdown it was not possible. (i got the same result with all distros that use calamares, of course)

3 Likes

It should/can be sufficient to terminate the Calamares process. Then reformat or repartition with parted/gparted and start Calamares again. In 2-3 cases, this approach has been successful for me.

1 Like

i tried doing that but although gparted did reformat the drive without issues, and in the live session, without reboot, the installer still had issues redoing it.

i tried rebooting as well, but it made no difference, only reverting back to the May edition of this year did i have no more issues installing.

Okay, it’s possible that I did it that way in an earlier version. In any case, that was quite a while ago. I only did it because I was too lazy to reboot and start all over again from Ventoy, the startup settings etc. :innocent: :wink: