[SOLVED] Asus RAID controller not detected in newer linux version

olsoncr

New Member
Credits
126
Hey guys,
First poster here.

I haven Asus SABERTHOOT motherboard that has an internal raid controller where I have my RAID1 volume with my personal stuff. For some reason the old linux versions (Centos6.x Ubuntu 19.X, etc) detect the raid controller without problem, the issue is with the newer linux versions (any).

My question is, is there any way that I can check the driver/kernel modules used in those older versions so I can install then my self in a new linux version (in particular Fedora 33)?

I have no idea where to start. I've been using linux for a long time so I am very proficient with the linux shell and linux in overall.

Any light will be appreciated.
 


wizardfromoz

Administrator
Staff member
Gold Supporter
Credits
17,776
G'day @olsoncr and welcome to linux.org :) :)

Do the legwork for me, have a look at the Forums tab at top and scout around for the most appropriate subforum to place this Thread and I can move it there.

If you sit around in Getting Started or General Linux you may just trail off into the next pages and be missed.

Let me know and good luck

Chris Turner
wizardfromoz
 

olsoncr

New Member
Credits
126
Thanks @wizardfromoz
I found 'Linux Hardware' forum, maybe there?

I do appreciate the help
 

f33dm3bits

Gold Member
Gold Supporter
Credits
24,162
First things first, it will be useful to get the output of the device and what kernel modules and driver it is using when it is working.
Code:
lspci -nn
lspci -v
Then search for the device and share the output.
 

olsoncr

New Member
Credits
126
Just installed fedora 33. the raid controller is not detected but I can see each individual disk (sda and adb):

[[email protected] ~]# lspci -v

00:11.0 RAID bus controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [RAID5 mode] (rev 40)
Subsystem: ASUSTeK Computer Inc. Device 84df
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19, NUMA node 0
I/O ports at f090
I/O ports at f080
I/O ports at f070
I/O ports at f060
I/O ports at f050
Memory at feb0b000 (32-bit, non-prefetchable) [size=1K]

Capabilities: [70] SATA HBA v1.0
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: ahci


[[email protected] ~]# lspci -nn | grep -i raid
00:11.0 RAID bus controller [0104]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [RAID5 mode] [1002:4393] (rev 40)
[[email protected] ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 931.3G 0 part
└─pdc_bedfjagjb 253:1 0 931.3G 0 dmraid
└─pdc_bedfjagjb1 253:2 0 931.3G 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 931.3G 0 part
└─pdc_bedfjagjb 253:1 0 931.3G 0 dmraid
└─pdc_bedfjagjb1 253:2 0 931.3G 0 part
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 600M 0 part /boot/efi
├─sdc2 8:34 0 1G 0 part /boot
└─sdc3 8:35 0 231.3G 0 part
└─luks-559415d8-0628-4172-b8b0-c50fe491e274 253:0 0 231.3G 0 crypt /home
zram0 252:0 0 4G 0 disk [SWAP]
[[email protected] ~]# pvs
File descriptor 29 (/home/olson/.cache/appstream-cache-B6SC00.mdb (deleted)) leaked on pvs invocation. Parent PID 6310: -bash
WARNING: Not using device /dev/sdb1 for PV Qu9uzf-bnwx-O0Ar-2ScG-2MBz-6rxc-DNS0ez.
WARNING: Not using device /dev/sda1 for PV Qu9uzf-bnwx-O0Ar-2ScG-2MBz-6rxc-DNS0ez.
WARNING: PV Qu9uzf-bnwx-O0Ar-2ScG-2MBz-6rxc-DNS0ez prefers device /dev/mapper/pdc_bedfjagjb1 because device name matches previous.
WARNING: PV Qu9uzf-bnwx-O0Ar-2ScG-2MBz-6rxc-DNS0ez prefers device /dev/mapper/pdc_bedfjagjb1 because device name matches previous.
PV VG Fmt Attr PSize PFree
/dev/mapper/pdc_bedfjagjb1 home lvm2 a-- 931.32g 231.32g

[[email protected] ~]#
 

Attachments

olsoncr

New Member
Credits
126
Just found the problem. Seems like when installing newer versions of linux, anaconda was not able to load dmraid module so it was not able to recognize my disks as raid. After installing a fresh Fedora 33, I ended up adding dmraid kernel module to /etc/modules-load.d/dm_mod.conf. Then applied a LVM filter to /dev/sd[a|b] so LVM stop detecting the same metadata in 2 disks and boom! I recovered my RAID volume.

Hope this helps someone in the future.
 

wizardfromoz

Administrator
Staff member
Gold Supporter
Credits
17,776
I love it when they solve their own problems, sort of makes us redundant but allows us time to work in other areas.

Well done, @olsoncr :)

So software solution, Anaconda and Fedora.

I will move this to Fedora and mark it as solved.

@f33dm3bits take note.

Avagudweegend

Wiz
 

f33dm3bits

Gold Member
Gold Supporter
Credits
24,162
That was kind of my whole point to compare what modules were loaded on a working system and then try to get them to load in the not working system. Glad you figured out the rest yourself @olsoncr!
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!


Top