Encrypted root on software RAID with 2.6.33

Question

Hi,
I ran an update earlier today on my HTPC, hoping for mantis included in the 2.6.33 kernel to work with my TV-Tuner card, when I recognized that the configuration for software-raids changed.
So I followed the instructions on: Installing with Software RAID or LVM and added the dm_mod module to the MODULES list and replaced raid with mdadm in the HOOKS list resulting in
HOOKS="base udev autodetect sata mdadm usbinput ecrypt filesystems"
After that I successfully rebuilt the kernel and decided it was time for a reboot, but after running the hooks udev, mdadm and encrypt, the screen shows:
Waiting 10 seconds for device /dev/mapper/root ...
root device '/dev/mapper/root' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/mapper/roo'.
You are being dropped to a recovery shell.
cat /proc/mdstat shows no configured raid arrays, while assembling them with mdassemble works.
I've tried to boot with and without specifying the raid arrays in grub's kernel line, always with the same result.
Even after booting from a live CD an chrooting in the system to rebuild the kernel - same error message.
Any ideas what I've done wrong?
Best regards

Answer 1

I just checked my mdadm.conf again and compared it with the commands listed here and on the wiki-page.
# cat /etc/mdadm.conf
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 level=raid1 num-devices=2 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
# mdadm -D --scan
ARRAY /dev/md0 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
# mdadm --detail --scan
ARRAY /dev/md0 metadata=0.90 UUID=13db5ec4:4d02ad99:5be3d20e:87599807
ARRAY /dev/md1 metadata=0.90 UUID=dda2a7de:a998f117:3f649c17:a7325bd1
ARRAY /dev/md2 metadata=0.90 UUID=26a15bc5:2345a817:f8c460fb:3d47969b
ARRAY /dev/md3 metadata=0.90 UUID=be48517f:ebc6eabb:f8463e19:ac167733
I'm going to change this and rebuild the kernel image.
Don't know where the difference comes from :/
Okay - the difference comes from running the command in the arch livecd system and in the chrooted environment
But both somehow don't seem to work for me.
When running "mkinitcpio -p kernel26", this is the output:
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.33-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
find: "/sys/devices/": Datei oder Verzeichnis nicht gefunden
:: Parsing hook [sata]
:: Parsing hook [mdadm]
Custom /etc/mdadm.conf file will be used in initramfs for assembling arrays.
:: Parsing hook [usbinput]
:: Parsing hook [encrypt]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
So /etc/mdadm.conf should be used?
lilsirecho wrote:When using mdadm for a raid0 in my machine, the assembly of the raid md0 is made during initrd.  A statement for md0 and its 2 drives appears during boot-up.
I can't see any statement about creating any of my mdX devices.
It's just
Running Hook [udev]
Triggering udev uevents ... done
Running hook [mdadm]
Running hook [enrypt]
Waiting 10 seconds for device /dev/md2 ...
Waiting 10 seconds for device /dev/mapper/root ...
Root device '/dev/mapper/root' doesn't exist. Attempting to create it.
ERROR: Unable to determine majo/minor number of root device '/dev/mapper/root'.
You are being dropped to a recovery shell
Last edited by flo (2010-04-21 19:25:03)