Arch Linux

davy_crockett

Member

Registered: 2015-10-21

Posts: 75

New linux-hardened kernel not detecting firmware RAID device

Hi,

I'm using a Dell Precision M6700 laptop, with a 1TB MSATA card on which I have arch linux installed. I also have 2 x 2TB internal hard drives that are configured in firmware / BIOS as a RAID 0 device, which I use to store data. I recently reinstalled Arch Linux and I noticed that if I used the 4.14.71-1-lts kernel or the regular linux kernel, I could access my internal hard drives without any issue. However if I use the 4.18.9.a-1-hardened kernel, my raid device is not recognized.

Here is how lsblk, lsblk -f and blkid appear with the hardened kernel

lsblk
NAME                 MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                    8:0    0   1.8T  0 disk  
sdb                    8:16   0   1.8T  0 disk  
sdc                    8:32   0 931.5G  0 disk  
├─sdc1                 8:33   0   512M  0 part  /boot/efi
└─sdc2                 8:34   0   931G  0 part  
  └─archcrypt        254:0    0   931G  0 crypt 
    ├─archvg-system  254:1    0   200G  0 lvm   /
    └─archvg-homevol 254:2    0   731G  0 lvm   /home
sr0                   11:0    1   7.7G  0 rom   

lsblk -f
NAME                 FSTYPE          LABEL                  UUID                                   MOUNTPOINT
sda                  isw_raid_member                                                               
sdb                  isw_raid_member                                                               
sdc                                                                                                
├─sdc1               vfat            SYSTEM                 0A9D-0CCC                              /boot/efi
└─sdc2               crypto_LUKS                            e1e3732a-9538-4479-ad75-bd64f000ed58   
  └─archcrypt        LVM2_member                            iSSVfX-OEKn-s5zJ-Z87S-Tn2d-HtMI-vfIs8q 
    ├─archvg-system  btrfs           Arch Linux             cfcd8f16-699d-463a-8432-1bf090df913d   /
    └─archvg-homevol ext4            Home Volume            5d89be22-b97f-46dc-8ab1-9446e750bfc5   /home
sr0                  udf             DA_VINCIS_DEMONS_S1_D3 44594eb500000000 

blkid
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc1: LABEL="SYSTEM" UUID="0A9D-0CCC" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="fc8ae271-ad98-4cd4-986a-f86b485905ed"
/dev/sdc2: UUID="e1e3732a-9538-4479-ad75-bd64f000ed58" TYPE="crypto_LUKS" PARTLABEL="Linux system partition" PARTUUID="b9649d3e-0e10-4bcd-b5f9-cc7e8da2830a"
/dev/sr0: UUID="44594eb500000000" LABEL="DA_VINCIS_DEMONS_S1_D3" TYPE="udf"
/dev/mapper/archcrypt: UUID="iSSVfX-OEKn-s5zJ-Z87S-Tn2d-HtMI-vfIs8q" TYPE="LVM2_member"
/dev/mapper/archvg-system: LABEL="Arch Linux" UUID="cfcd8f16-699d-463a-8432-1bf090df913d" UUID_SUB="cef28e31-dff0-4ae9-acb2-136da2dc8b8b" TYPE="btrfs"
/dev/mapper/archvg-homevol: LABEL="Home Volume" UUID="5d89be22-b97f-46dc-8ab1-9446e750bfc5" TYPE="ext4"

Here is how lsblk, lsblk -f and blkid appear with the standard linux kernel:

lsblk
NAME                 MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                    8:0    0   1.8T  0 disk  
└─md126                9:126  0   3.7T  0 raid0 
  └─md126p1          259:0    0   3.7T  0 md    
sdb                    8:16   0   1.8T  0 disk  
└─md126                9:126  0   3.7T  0 raid0 
  └─md126p1          259:0    0   3.7T  0 md    
sdc                    8:32   0 931.5G  0 disk  
├─sdc1                 8:33   0   512M  0 part  /boot/efi
└─sdc2                 8:34   0   931G  0 part  
  └─archcrypt        254:0    0   931G  0 crypt 
    ├─archvg-system  254:1    0   200G  0 lvm   /
    └─archvg-homevol 254:2    0   731G  0 lvm   /home
sr0                   11:0    1   7.7G  0 rom   

lsblk -f
NAME                 FSTYPE          LABEL                  UUID                                   MOUNTPOINT
sda                  isw_raid_member                                                               
└─md126                                                                                            
  └─md126p1                                                                                        
sdb                  isw_raid_member                                                               
└─md126                                                                                            
  └─md126p1                                                                                        
sdc                                                                                                
├─sdc1               vfat            SYSTEM                 0A9D-0CCC                              /boot/efi
└─sdc2               crypto_LUKS                            e1e3732a-9538-4479-ad75-bd64f000ed58   
  └─archcrypt        LVM2_member                            iSSVfX-OEKn-s5zJ-Z87S-Tn2d-HtMI-vfIs8q 
    ├─archvg-system  btrfs           Arch Linux             cfcd8f16-699d-463a-8432-1bf090df913d   /
    └─archvg-homevol ext4            Home Volume            5d89be22-b97f-46dc-8ab1-9446e750bfc5   /home
sr0                  udf             DA_VINCIS_DEMONS_S1_D3 44594eb500000000       

blkid
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc1: LABEL="SYSTEM" UUID="0A9D-0CCC" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="fc8ae271-ad98-4cd4-986a-f86b485905ed"
/dev/sdc2: UUID="e1e3732a-9538-4479-ad75-bd64f000ed58" TYPE="crypto_LUKS" PARTLABEL="Linux system partition" PARTUUID="b9649d3e-0e10-4bcd-b5f9-cc7e8da2830a"
/dev/sr0: UUID="44594eb500000000" LABEL="DA_VINCIS_DEMONS_S1_D3" TYPE="udf"
/dev/mapper/archcrypt: UUID="iSSVfX-OEKn-s5zJ-Z87S-Tn2d-HtMI-vfIs8q" TYPE="LVM2_member"
/dev/mapper/archvg-system: LABEL="Arch Linux" UUID="cfcd8f16-699d-463a-8432-1bf090df913d" UUID_SUB="cef28e31-dff0-4ae9-acb2-136da2dc8b8b" TYPE="btrfs"
/dev/mapper/archvg-homevol: LABEL="Home Volume" UUID="5d89be22-b97f-46dc-8ab1-9446e750bfc5" TYPE="ext4"
/dev/md126: PTUUID="cd524702-c0d6-4fa2-9354-5790066b4a5c" PTTYPE="gpt"
/dev/md126p1: PARTLABEL="data" PARTUUID="69d1ce92-98b8-40b4-a278-87b38faf51cc"

Any ideas as for why /dev/md126p1 is showing up with the regular and LTS linux kernels, but not the hardened linux kernel?

loqs

Member

Registered: 2014-03-06

Posts: 19,113

Re: New linux-hardened kernel not detecting firmware RAID device

What is the dmesg and lsmod outputs from both linux and linux-hardened?