mdadm fails to assemble RAID5 from 4 LUKS devices on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My setup is the following: 4 LUKS encrypted drives with mdadm RAID5 on top. The reason I encrypted first and then added them into the array was based on performance: 4 threads doing encryption/
Yes, I ran this after mdadm.conf update:
sudo mdadm --udev-rules
sudo update-initramfs -u -k 3.2.0-32-generic
cat /etc/mdadm/
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
DEVICE partitions
# DEVICE /dev/mapper/
ARRAY /dev/md0 uuid=cbb6468c:
# ARRAY /dev/md0 level=raid5 num-devices=4 spares=0 devices=
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This file was auto-generated on Sat, 13 Oct 2012 22:37:39 -0400
# by mkconf $Id$
# POLICY domain=
affects: | update-manager (Ubuntu) → initramfs-tools (Ubuntu) |
tags: | added: mdadm |
tags: | added: initramfs luks raid5 |
tags: | added: crypttab |
Status changed to 'Confirmed' because the bug affects multiple users.