Manjaro Architect bug when handling RAID volumes

Hi.

There is a bug in Manjaro Architect 0.9.33, while trying to mount RAID volumes.

I have created RAID volumes both manually and from Manjaro Architect. The result is the same. Manjaro Architect use the device name (mdxxx) correctly, but prefix it with /dev/md/ where it should be /dev only. I guess this is somehow hardcoded. It is therefore unable to mount the volume as the path is wrong.

NAME            MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0             7:0    0  73.9M  1 loop  /run/miso/sfs/livefs
loop1             7:1    0 564.3M  1 loop  /run/miso/sfs/mhwdfs
loop2             7:2    0   1.4G  1 loop  /run/miso/sfs/desktopfs
loop3             7:3    0 596.5M  1 loop  /run/miso/sfs/rootfs
sda               8:0    0   1.8T  0 disk  
├─sda1            8:1    0   1.8T  0 part  
└─sda9            8:9    0     8M  0 part  
sdb               8:16   0   1.8T  0 disk  
├─sdb1            8:17   0   1.8T  0 part  
└─sdb9            8:25   0     8M  0 part  
sdc               8:32   0   1.8T  0 disk  
├─sdc1            8:33   0   1.8T  0 part  
└─sdc9            8:41   0     8M  0 part  
sdd               8:48   0   1.8T  0 disk  
├─sdd1            8:49   0   1.8T  0 part  
└─sdd9            8:57   0     8M  0 part  
sde               8:64   1  29.7G  0 disk  
├─sde1            8:65   1   2.7G  0 part  /run/miso/bootmnt
└─sde2            8:66   1     4M  0 part  
nvme1n1         259:0    0 465.8G  0 disk  
├─nvme1n1p1     259:2    0   301M  0 part  
│ └─md126         9:126  0   300M  0 raid1 
└─nvme1n1p2     259:3    0 465.5G  0 part  
  └─md127         9:127  0 930.7G  0 raid0 
    └─cryptroot 254:0    0 930.7G  0 crypt /mnt/var/lib/machines
nvme0n1         259:1    0 465.8G  0 disk  
├─nvme0n1p1     259:4    0   301M  0 part  
│ └─md126         9:126  0   300M  0 raid1 
└─nvme0n1p2     259:5    0 465.5G  0 part  
  └─md127         9:127  0 930.7G  0 raid0 
    └─cryptroot 254:0    0 930.7G  0 crypt /mnt/var/lib/machines

can you return

cat /proc/mdstat
mdadm --detail --scan

Thanks for reporting. As a workaround until it is fixed, you can remount your volumes manually and proceed with installs3

Won't help much Stéphane but to satisfy your curiosity :wink:

Personalities : [raid0] [raid1] 
md126 : active raid1 nvme1n1p1[0] nvme0n1p1[1]
      307200 blocks super 1.2 [2/2] [UU]
      
md127 : active raid0 nvme1n1p2[1] nvme0n1p2[0]
      975890432 blocks super 1.2 512k chunks

and

sh-5.0# mdadm --detail --scan
ARRAY /dev/md/root metadata=1.2 name=manjaro:root UUID=8a683593:00e9ad3d:02878bf2:1e66d049
ARRAY /dev/md/ESP metadata=1.2 name=manjaro:ESP UUID=932a4de0:7806d68e:694eb030:dcddd007

Thank you Chrysostomus. As a workaround, I created symbolic links in /dev/md/

The issue starts here. I'll look into it when I get a new computer. If someone wants to fix it before September, pull requests are welcome.

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

Forum kindly sponsored by