I've been unable to use the partitions of LUKS enabled RAID device.
I used the mkinitrd command generator recommended and saw that I had not tried the "-u" option.
Whether using the huge kernel and no initrd or using the generic kernel with initrd I haven't been able to create the /dev/mapper/xxx devices needed for the partitions
. I can create the raid device /dev/md0 and the LUKS opened device /dev/mapper/luksmd0
. I just cannot have the system create (after a reboot) the subsequent devices needed for the partitions. /dev/mapper/luksmd0p1 & p2
I used the following command to create the initrd resulting in the default named device luksmd0
mkinitrd -c -k 18.104.22.168 -m ext4:ehci-hcd:uhci-hdc:usbhid -f ext4 -C /dev/md0 -r /dev/sda1 -u -R
"fdisk -l" shows disk /dev/mapper/luksmd0 with 2 partitions: /dev/mapper/luksmd0p1
. So as far as I can tell, these two devices need to exist in order to mount the partitions just like /dev/sda1 needs to exist to use the partitions of /dev/sda.
Neither entries in /etc/crypttab nor the multiple colon separated arguments I've tried to "-C" in the mkinitrd command have led to success. Since the whole idea is to use a single key to unlock a single LUKS enabled device, I didn't think they would work.
As I mentioned before, the RAID partitions work if dm-crypt is not used.
With the current boot/load process perhaps it's not (easily) possible to use partitions of a LUKS enabled RAID device.
Lack of partitioning LUKS enabled RAID devices isn't a show stopper as I can still use the method of partitioning the disk first to create the RAID devices which are then LUKS enabled and a file system created. It just involves multiple keys. And LVM still works fine with a single key on RAID with LUKS.