On Thu, May 19, 2005 at 05:50:06AM -0700, rds wrote: > > > Quick question: why not add an auto=md clause to /etc/mdadm/mdadm.conf? > > That way you have the option of *not* assembling some md drives if > > necessary. > > I can't try this right now but I doubt this would help. The reason is that > when > the system boots initrd would not know how to assemble /dev/md1 because > .../initrimg/script does not contain "mdadm -A" record for /dev/md1. This is > the root of the problem.
Oops, there's indeed one other point you'll need to check: you'll also need to make sure AUTOSTART is set correctly in /etc/default/mdadm. As Maks pointed out, the idea is that initrd only activates the md devices needed to boot. /etc/rcS.d/S04mdadm-raid can then activate the rest of the devices, (and optionally mknod(2) them as well) in time for S10checkroot and S30checkfs. Note that md does not create udev events, only md devices that exist at the time initrd ends are passed to udev by udevstart and get a rule applied, for the rest you'll need auto=md, although you can sometimes get away with omitting that due to a rather odd interaction between LVM, devfs on the initrd and udev. I made some notes on this issue, see http://www.xs4all.nl/~ekonijn/yaird/yaird.html#raid. Not for sarge, but I think the optimal approach would be: 1. make auto=md the default when installing a debian system with mdadm. 2. let udev ignore md devices. This would achieve: - user can decide which devices are activated automatically and which are not. - devices can get a symbolic name (/dev/md-root) based on UUID, rather than a name /dev/mdX that depends on detection order. - end to the inconsistency between devices accessed by initrd and the rest. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
