Slackware64-Current fail to assemble non-root raid volume at boot
by tux_dude from LinuxQuestions.org on (#6DGJZ)
A few updates ago on current (can't recall exactly when), slackware no longer assemble a few non-root raid volumes at boot. dmesg shows all the disk required by the volumes are detected. The root volume assembles and the system boots without issue. See system info below:
md0 and md3 (raid1) assemble and boots normally.
md1 and md2 (raid5), both fails to assemble. No error in syslog of dmesg. See configs below:
mdadm.conf
Code:DEVICE /dev/sd[a-x]*
ARRAY /dev/md0 metadata=1.2 name=slack01:root UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md1 metadata=1.1 name=slack01:data01 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md2 metadata=1.1 name=slack01:data02 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md3 metadata=0.90 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxmkinitrd
Code:mkinitrd -c -k 6.1.42 -f ext4 -r luksmd0 -m megaraid_sas:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -C /dev/md0 -RUsing lilo to boot.
md0 and md3 (raid1) assemble and boots normally.
md1 and md2 (raid5), both fails to assemble. No error in syslog of dmesg. See configs below:
mdadm.conf
Code:DEVICE /dev/sd[a-x]*
ARRAY /dev/md0 metadata=1.2 name=slack01:root UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md1 metadata=1.1 name=slack01:data01 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md2 metadata=1.1 name=slack01:data02 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
ARRAY /dev/md3 metadata=0.90 UUID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxmkinitrd
Code:mkinitrd -c -k 6.1.42 -f ext4 -r luksmd0 -m megaraid_sas:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -C /dev/md0 -RUsing lilo to boot.