Raid assembling fails

Ask Fedora
, ,
1

i have a raid0 created during fedora setup, which i’m trying to access while booting from live USB.

But assembling fails as no superblock found on both drives.

Am i missing something?

liveuser@localhost-live:~$ lsblk -o +FSTYPE,UUID
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS         FSTYPE      UUID
loop0         7:0    0   1.6G  1 loop /run/rootfsbase     squashfs    
sda           8:0    1  14.4G  0 disk                                 
└─sda1        8:1    1  14.4G  0 part /run/initramfs/live vfat        8274-9E95
zram0       252:0    0     8G  0 disk [SWAP]                          
nvme0n1     259:0    0 238.5G  0 disk                                 
├─nvme0n1p1 259:1    0   100M  0 part                     vfat        0673-EE01
├─nvme0n1p2 259:2    0    16M  0 part                                 
├─nvme0n1p3 259:3    0 231.9G  0 part                     ntfs        7654765254761559
├─nvme0n1p4 259:4    0   840M  0 part                     ntfs        C8BC7532BC751BDE
├─nvme0n1p5 259:5    0     1G  0 part                     vfat        0150-63B8
└─nvme0n1p6 259:6    0     4G  0 part                     ext4        7d687dbc-9497-42c2-8484-ee1159a8d839
nvme1n1     259:7    0 931.5G  0 disk                                 
├─nvme1n1p1 259:8    0 822.1G  0 part                     crypto_LUKS b652af38-4d3f-488d-92b3-073f3217cc03
└─nvme1n1p2 259:9    0 109.5G  0 part                     crypto_LUKS 0fafb902-db94-4a8e-ad50-6477df93786a
nvme2n1     259:10   0 931.5G  0 disk                                 
├─nvme2n1p1 259:11   0 822.1G  0 part                     crypto_LUKS 1e339a60-5cac-43d4-b7c8-4ab770aacefa
└─nvme2n1p2 259:12   0 109.5G  0 part                     crypto_LUKS 5529c265-28d3-46f0-b389-4f6403d26169

liveuser@localhost-live:~$ sudo mdadm --assemble --verbose /dev/md0 /dev/nvme1n1 /dev/nvme2n1
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/nvme1n1
mdadm: /dev/nvme1n1 has no superblock - assembly aborted

liveuser@localhost-live:~$ sudo mdadm --examine /dev/nvme1n1
/dev/nvme1n1:
   MBR Magic : aa55
Partition[0] :   1953525167 sectors at            1 (type ee)

liveuser@localhost-live:~$ sudo mdadm --examine /dev/nvme2n1
/dev/nvme2n1:
   MBR Magic : aa55
Partition[0] :   1953525167 sectors at            1 (type ee)
2

Are you able to boot into the system and example the raid?
What is in /etc/mdadm.conf?

From the lsblk output I wonder if you have to first luks open the 4 partitions and then build the RAID out of them?

3

I’m not able to boot, let me try to first unlock partitions and then assemble the raid

4

@barryascott unlocked, seems like those partitions aren’t managed through mdadm as i thought.

how do i build a raid using btrfs?

liveuser@localhost-live:~$ lsblk -o +FSTYPE,UUID
NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS         FSTYPE      UUID
loop0           7:0    0   1.6G  1 loop  /run/rootfsbase     squashfs    
sda             8:0    1  14.4G  0 disk                                  
└─sda1          8:1    1  14.4G  0 part  /run/initramfs/live vfat        8274-9E95
zram0         252:0    0     8G  0 disk  [SWAP]                          
nvme0n1       259:0    0 238.5G  0 disk                                  
├─nvme0n1p1   259:1    0   100M  0 part                      vfat        0673-EE01
├─nvme0n1p2   259:2    0    16M  0 part                                  
├─nvme0n1p3   259:3    0 231.9G  0 part                      ntfs        7654765254761559
├─nvme0n1p4   259:4    0   840M  0 part                      ntfs        C8BC7532BC751BDE
├─nvme0n1p5   259:5    0     1G  0 part                      vfat        0150-63B8
└─nvme0n1p6   259:6    0     4G  0 part                      ext4        7d687dbc-9497-42c2-8484-ee1159a8d839
nvme1n1       259:7    0 931.5G  0 disk                                  
├─nvme1n1p1   259:8    0 822.1G  0 part                      crypto_LUKS b652af38-4d3f-488d-92b3-073f3217cc03
│ └─my_home_1 253:0    0   822G  0 crypt                     btrfs       55f27c48-0369-481e-9d89-97354e0ff882
└─nvme1n1p2   259:9    0 109.5G  0 part                      crypto_LUKS 0fafb902-db94-4a8e-ad50-6477df93786a
nvme2n1       259:10   0 931.5G  0 disk                                  
├─nvme2n1p1   259:11   0 822.1G  0 part                      crypto_LUKS 1e339a60-5cac-43d4-b7c8-4ab770aacefa
│ └─my_home_2 253:1    0   822G  0 crypt                     btrfs       55f27c48-0369-481e-9d89-97354e0ff882
└─nvme2n1p2   259:12   0 109.5G  0 part                      crypto_LUKS 5529c265-28d3-46f0-b389-4f6403d26169
5

It seems you just mount one part of the raid and btrfs will do the rest.
I did some web searches to figure that out.

Does sudo btrfs filesystem show report?
Are the parts of the raid shown?

6

It does!

liveuser@localhost-live:~$ sudo btrfs filesystem show
Label: 'home_volume'  uuid: 55f27c48-0369-481e-9d89-97354e0ff882
	Total devices 2 FS bytes used 390.92GiB
	devid    1 size 822.04GiB used 234.01GiB path /dev/mapper/my_home_1
	devid    2 size 822.04GiB used 234.01GiB path /dev/mapper/my_home_2

So basically all i have to do is unlock the LUKS and then mount the /dev/mapper/X to some directory?

7

Yes, which is what you did I assume.

8

Yes, thanks a lot for your help!