ASUS motherboard RAID - drives not detected

Hi there,

I just installed Garuda on my machine and i have an issue with storage drives.

I am using my motherboard (Asus Strix B550-A Gaming) RAID module to use two old and small SATA SSDs in RAID 0, mainly for convenience (one 500 GB volume instead of 2x250GB).

So, my SATA controller is set to 'RAID' mode in UEFI (and not standard AHCI mode).

The problem is that, in this configuration, only my NVMe drives are detected in Garuda. All my SATA drives just don't show up, neither in KDE drives manager nor with terminal commands.

For instance below is the output of lsblk command.

Any help would be appreciated, thanks in advance.

LSBLK output:

sda           8:0    1     0B  0 disk
sdb           8:16   1     0B  0 disk
zram0       254:0    0  31,2G  0 disk [SWAP]
nvme0n1     259:0    0 238,5G  0 disk
├─nvme0n1p1 259:1    0   100M  0 part
├─nvme0n1p2 259:2    0    16M  0 part
├─nvme0n1p3 259:3    0 237,9G  0 part /mnt/windows
└─nvme0n1p4 259:4    0   512M  0 part
nvme1n1     259:5    0 465,8G  0 disk
├─nvme1n1p1 259:6    0   300M  0 part /boot/efi
├─nvme1n1p2 259:7    0   7,8G  0 part [SWAP]
└─nvme1n1p3 259:8    0 457,7G  0 part /var/tmp

GARUD-INXI output :

Kernel: 6.2.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9524c41d-7c0a-4cf5-8fb0-d3ae1cafffe9 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=b2ca9daf-41fe-4f98-b519-e2dd36230aa8 loglevel=3
Desktop: KDE Plasma v: 5.27.3 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-A GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 2803
date: 04/27/2022
Info: model: AMD Ryzen 5 5600 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: 0xA20120A
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3578 high: 3779 min/max: 2200/4467 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3705 2: 3500
3: 3500 4: 3589 5: 3779 6: 3586 7: 3500 8: 3600 9: 3500 10: 3592 11: 3500
12: 3595 bogomips: 83999
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
built: 2020-22 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:73df
class-ID: 0300
Device-2: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 2-2.1:4 chip-ID: 046d:0825 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu 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-2 mapped: DisplayPort-1 model: AOC Q3279WG5B
serial: <filter> built: 2017 res: 2560x1440 hz: 60 dpi: 90 gamma: 1.2
size: 725x428mm (28.54x16.85") diag: 842mm (33.1") ratio: 15:9 modes:
max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22
LLVM 15.0.7 DRM 3.49 6.2.6-zen1-1-zen) direct-render: Yes
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
bus-ID: 2-2.1:4 gen: 4 chip-ID: 046d:0825 speed: 16 GT/s class-ID: 0102
lanes: 16 serial: <filter> 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
Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 4-1:2 chip-ID: 0b05:180d
class-ID: 0300
Sound API: ALSA v: k6.2.6-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.67 running: yes
Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: AzureWave driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 07:00.0 chip-ID: 168c:0042 class-ID: 0280
IF: wlp7s0 state: down mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0a:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-7.2:4
chip-ID: 13d3:3501 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Hardware-1: Advanced Micro Devices [AMD] Device driver: N/A v: N/A port: N/A
bus-ID: 02:00.1 chip-ID: 1022:43bd rev: class-ID: 0104
Local Storage: total: 704.24 GiB used: 247.71 GiB (35.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 950 PRO 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B0QBXX7 temp: 32.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Kingston model: SNV2S500G
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 type: SSD serial: <filter> rev: ELFK0S.6 temp: 31.9 C scheme: GPT
ID-1: / raw-size: 457.65 GiB size: 457.65 GiB (100.00%)
used: 87.72 GiB (19.2%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:8
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:6
ID-3: /home raw-size: 457.65 GiB size: 457.65 GiB (100.00%)
used: 87.72 GiB (19.2%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:8
ID-4: /var/log raw-size: 457.65 GiB size: 457.65 GiB (100.00%)
used: 87.72 GiB (19.2%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:8
ID-5: /var/tmp raw-size: 457.65 GiB size: 457.65 GiB (100.00%)
used: 87.72 GiB (19.2%) fs: btrfs dev: /dev/nvme1n1p3 maj-min: 259:8
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.23 GiB used: 51.8 MiB (0.2%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 7.81 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p2 maj-min: 259:7
System Temperatures: cpu: 46.0 C mobo: N/A gpu: amdgpu temp: 44.0 C
mem: 42.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Processes: 335 Uptime: 34m wakeups: 0 Memory: 31.23 GiB
used: 7.4 GiB (23.7%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1333
libs: 410 tools: octopi,pamac,paru Shell: fish v: 3.6.0 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.25
Garuda (2.6.15-1):
System install date:     2023-03-15
Last full system update: 2023-03-15
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

What are sda and sdb? Something else?

Just a quick sanity check: the drives are detected in AHCI mode, is that right?

Try booting to the fallback image from the advanced boot options in the Grub menu and see if you get a different result.


Didn't try in AHCI mode as i fear i'm gonna lose the data i currently have on my RAID. But all disks are accessible on my windows install.

sda and sdb are the empty slots of my card reader.

I'll try the fallback image and report back

EDIT: Same result with the fallback image. I'll add that the drives weren't detected either in USB live mode when i installed Garuda.

Too bad, that would have indicated an easy fix.

There are plenty of kernel parameters related to RAID (see this thread for some examples that seemed to work for people: centos - md raid not mounted by dracut - Unix & Linux Stack Exchange), but I'm not sure if the kernel parameters are relevant for a hardware RAID setup.

This thread is kind of old, but it was a person that wasn't able to get their hardware RAID working on Linux. Obviously that isn't the outcome you want, but they documented their efforts reasonably well and it might be useful to read through while you hunt for clues: ubuntu - Hardware RAID not recognized by OS - Super User

1 Like

After some more digging, it looks like i would need to install RCRAID drivers to make this work :

However, the AUR package seems to not be compatible with kernel 6.2 yet :

Bummer. Try using the LTS kernel, which is on 6.1 and see if you can get it working with that.

1 Like

The author also states that AMD support on these drivers for linux is nonexistent, and advises not to use them.

Guess i'll just fall back to AHCI and handle my 2 drives separately (or maybe a software raid).

If you end up doing a software RAID, it turns out RAID0 is really simple to set up on Btrfs. It came up in another thread here in the forum not too long ago:


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