Garuda wont boot while my secondary ssd is installed

Issues & Assistance Unsupported hardware | Dual boot
1

in my last post I was unable to boot into garuda because my system journal failed to work. this was eventually solved by taking out my secondary ssd and trying again. this worked well for a bit but I now have just wiped both my drives completely to set my small 240gb drive as my dual boot drive and set my large nvme drive (1tb) to a application/game drive. since I did not fully understand what the problem was I just assumed it was windows interfering rather than the actual drive. I ended up being wrong and now I am here to hopefully get a better fix than to just remove the drive

so if there is any way I can allow my 1tb drive to play nicely with linux I would gladly appreciate any assistance

my specs:
cpu: e5 2697v3
gpu: rx 5700xt
ram:24gb ddr4
crucial ct240bx200ssd (240gb sata)
cusu gen4 (1tb nvme) controller is sm2269xt very common controller used with many name brand ssds

2

hi friend.

A common issue is no permission for Garuda to boot as first in your bios. e.g your new drive takes priority over Garuda.

The best way to do this is to enter your bios at boot by pressing DEL, F2 or the F3 key and selecting the drive Garuda is on as number 1 to boot your computer.

See how you go.

2 Likes
3

My apologies, but that info is insufficient for diagnostic purposes. If you are unable to boot, you can still post the garuda-inxi output that our forum requires on technical assistance requests from the live environment. The garuda-inxi output is a fundamental part of receiving assistance on our forum.

Thank you.

5 Likes
4

I have already tried this as well as many of the other common fixes and I am getting to the boot menu for it I just can’t get past a journal service error

The other thing is I don’t have anything set to boot off of the second drive

1 Like
5 
System:
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=c25be73a-8c17-4972-b783-c74746698e4f rw rootflags=subvol=@
quiet 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 vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: INTEL product: N/A v: N/A serial: <superuser required>
Mobo: INTEL model: E5-A99 v: V1.2 serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends v: 5.11
date: 07/24/2024
CPU:
Info: model: Intel Xeon E5-2697 v3 bits: 64 type: MT MCP arch: Haswell
level: v3 note: check built: 2013-15 process: Intel 22nm family: 6
model-id: 0x3F (63) stepping: 2 microcode: 0x49
Topology: cpus: 1x dies: 1 clusters: 14 cores: 14 threads: 28 tpc: 2
smt: enabled cache: L1: 896 KiB desc: d-14x32 KiB; i-14x32 KiB L2: 3.5 MiB
desc: 14x256 KiB L3: 35 MiB desc: 1x35 MiB
Speed (MHz): avg: 2979 min/max: 1200/3600 scaling: driver: intel_cpufreq
governor: performance cores: 1: 2979 2: 2979 3: 2979 4: 2979 5: 2979 6: 2979
7: 2979 8: 2979 9: 2979 10: 2979 11: 2979 12: 2979 13: 2979 14: 2979
15: 2979 16: 2979 17: 2979 18: 2979 19: 2979 20: 2979 21: 2979 22: 2979
23: 2979 24: 2979 25: 2979 26: 2979 27: 2979 28: 2979 bogomips: 145263
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
XT / 5700/5700 XT] vendor: Dataland 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-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 05:00.0 chip-ID: 1002:731f 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: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: 0
Monitor-1: DP-2 model: Pixio PX248PS serial: <filter> built: 2023 res:
mode: 1920x1080 hz: 165 scale: 100% (1) dpi: 92 gamma: 1.2
size: 600x330mm (23.62x12.99") diag: 609mm (24") ratio: 16:9, 15:9 modes:
max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5700 XT (radeonsi
navi10 LLVM 19.1.7 DRM 3.61 6.14.2-zen1-1-zen) device-ID: 1002:731f
memory: 7.81 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.309 layers: 5 device: 0 type: discrete-gpu name: AMD
Radeon RX 5700 XT (RADV NAVI10) driver: N/A device-ID: 1002:731f
surfaces: xcb,xlib,wayland device: 1 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 wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 05:00.1 chip-ID: 1002:ab38 class-ID: 0403
API: ALSA v: k6.14.2-zen1-1-zen status: kernel-api tools: N/A
Server-1: 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000
bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 238.14 GiB used: 9.2 GiB (3.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT240BX200SSD1
size: 223.57 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: .6 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 model: Mass Storage Device size: 14.57 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: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 49.67 GiB size: 49.67 GiB (100.00%) used: 9.17 GiB (18.5%)
fs: btrfs dev: /dev/sda7 maj-min: 8:7
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.6 MiB (26.7%) fs: vfat dev: /dev/sda3 maj-min: 8:3
ID-3: /home raw-size: 49.67 GiB size: 49.67 GiB (100.00%)
used: 9.17 GiB (18.5%) fs: btrfs dev: /dev/sda7 maj-min: 8:7
ID-4: /var/log raw-size: 49.67 GiB size: 49.67 GiB (100.00%)
used: 9.17 GiB (18.5%) fs: btrfs dev: /dev/sda7 maj-min: 8:7
ID-5: /var/tmp raw-size: 49.67 GiB size: 49.67 GiB (100.00%)
used: 9.17 GiB (18.5%) fs: btrfs dev: /dev/sda7 maj-min: 8:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 23.37 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 28
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 26.0 C mobo: N/A gpu: amdgpu temp: 35.0 C
mem: 40.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 24 GiB available: 23.37 GiB used: 3.14 GiB (13.4%)
Processes: 510 Power: uptime: 1m states: freeze,mem,disk suspend: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
image: 9.34 GiB services: org_kde_powerdevil, power-profiles-daemon,
upowerd Init: systemd v: 257 default: graphical tool: systemctl
Packages: pm: pacman pkgs: 1258 libs: 360 tools: octopi,paru Compilers:
gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.1 running-in: konsole
inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-04-15
Last full system update: 2025-04-17 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:
6

My apologies again, but I asked very politely and you still did not post your garuda-inxi output. As I already explained, our forum requires a garuda-inxi output be posted to receive assistance. Your post has been moved to our forum’s purgatory, until such time as you make good on providing the information our forum requires.

Please edit your Opening Post (OP) to provide your full system specs, (garuda-inxi).

You did take ownership of your drives after formatting them, right.

Please see:

man chown
1 Like
7

I have returned your post to the open forum, as you edited your post to add your inxi.

As I mentioned:

8

Have you tried taking out the second drive, and first installing, running and updating Garuda’s first run on just one drive, and then reintroduce the second drive, making sure the Garuda partition remains your first bootable one in your bios?

Also you may have to update your bios, it is from last year. For, i’m sorry to say, your explanations do not really make much sense to me. A successful install should leave you with at least one partition that is boot-able.

1 Like
9

What file system did you install on your secondary drive, ext4, btrfs, ntfs, other?

If the secondary drive will not mount you should run an error check on the drive to make sure it is not faulty.

By what method are you connecting your secondary drive, internal sata, esata, usb?

If connecting via USB, what version does your USB enclosure use?

I’ve had many controllers on USB enclosures become faulty or fail. Have you thought of removing the drive from the enclosure (if you are using a USB drive) and mount it internally?

Check your dmesg logs from when you attempt to boot with the secondary drive connected.

Please post:

sudo dmesg
10

I am trying to figure out how to take ownership of the drive through windows because it is the only os I can boot with my second ssd installed.

I am not completely sure what that looks like but I did decide to set every option to full control if that might help

11

Ya, that’s not going to work.

Please answer my prior questions.

Can you boot the live environment with both drives connected?

12

20250417_223329
20250417_2233291920×2560 307 KB

This is what I recieve where trying to boot to the live environment

13

Well that really handicaps troubleshooting with no logs to view.

Crappy, but again please answer my prior questions:

1 Like
14

I believe my drive is formated to ntfs
my ssd is connected via on board nvme
and according to a quick error scan on windows it said it has no problems

15

Is your controller is set to AHCI mode in your BIOS, (not RAID , Optane, or RST).

1 Like
16

my sata controller is set to ahci but I dont know if that affects nvme settings although the internet seems to think it does so I am pretty sure it is set.properly

17

In your BIOS make sure that the drive containing your Garuda installation is set as the first boot priority, and that the NTFS drive is prioritized after Garuda.

Sometimes resetting your bios to the factory default can cure weird hardware issues.

AGAIN, what method are you using to connect your secondary drive?

Consider formatting the secondary drive to exfat instead of ntfs.

18

sorry, my mistake. my secondary ssd is a m.2 nvme drive and is connected directly to my motherboard.

I am now currently formating to exfat and I will get back to you with results

also did try restoring bios to default and nothing really changed

19

changing to exfat did not make much difference sadly

20

Just a sanity check you have installed the m2 nvme in the m2 nvme slot not the m2 sata slot

1 Like