Package: initrd-tools Version: 0.1.78 Severity: important
I get the following configuration : 2 SATA drives /dev/sd[ab]1 == /boot (but not a real RAID) /dev/sd[ab]2 == swap (not in RAID) /dev/sda3 == / (temporary install system due to big problems with the debian-installer :)) /dev/sdb3 == /tmp (temporary install) /dev/sd[ab]4 == One big partition for RAID translated into /dev/mdp0 or /dev/md/mdp0 (not using or using devfs) then in this configuration I get, /dev/mdp0p[1234] with /dev/mdp0p1 == future /, 2=/usr, 3=/var, 4=/home Under a chrooted environnement (the future tree is mounted) I try to use mkinitrd to build a RAID enabled initrd image. As you can see I don't use devfs and the name of the drive is not "really" choosen by me. mkinitrd fails to generate the image because it don't know how to handle this root device ... I try to look in mkinitrd script and see that most things are "harcoded" in it. But in the case of mdadm an array could be called /dev/home0 for example with /dev/home0p1 for first partition etc ... (man mdadm IIRC). So can I suggest to add something like MDBASE=/dev/md[p]$minor which could be settled in the mkinitrd.conf ? This will not solve my problem, but at least, should help me a little. I will try to build a patch in a near future. Regards, Benoît -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2 The GNU core utilities ii cpio 2.5-1.2 GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.2-4 The Debian Almquist Shell ii util-linux 2.12-10 Miscellaneous system utilities -- no debconf information
