martin f krafft a écrit :
also sprach Fabrice Lorrain <[EMAIL PROTECTED]> [2006.11.11.1844 +0100]:
Generating mdadm.conf... done.
update-initramfs: Generating /boot/initrd.img-2.6.16-2-k7
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
update-initramfs: Generating /boot/initrd.img-2.6.14.3-arkham
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
Assembling MD arrays...failed (no arrays found in config file or
automatically).
[...]
I don't see at all the usfullness of putting mdadm in all my initrds :
- I don't need it,
So tell mdadm not to do anything with debconf
At "aptitude install" time ? How (didn't find any mention of debconf or
priority in aptitude(8) ?
or /etc/default/mdadm; your two parameters are INITRDSTART and AUTOSTART
Yes but it's post-installation configuration (same goes for
dpkg-reconfigure --priority=low mdadm).
- It is a slow process
The mdadm hook takes less than a second to run.
[...]
Nov 11 19:21:13 Calling hook mdadm
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/md-mod.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/linear.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/multipath.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/raid0.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/raid1.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/xor.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/raid456.ko
Nov 11 19:21:13 Adding module
/lib/modules/2.6.18-2-amd64/kernel/drivers/md/raid10.ko
Nov 11 19:21:13 I: mdadm: using configuration file: /etc/mdadm/mdadm.conf
Nov 11 19:21:13 I: mdadm: will start MD array /dev/md1 from the initial ramdisk.
Nov 11 19:21:13 I: mdadm: will start MD array /dev/md7 from the initial ramdisk.
Nov 11 19:21:13 I: mdadm: use `dpkg-reconfigure --priority=low mdadm` to change
this.
Nov 11 19:21:13 Calling hook thermal
[...]
Where did you get those logs ? Took longer on my box. And it depends on
the number of kernel
installed.
- it barf a bunch of warning
- and the "Assembling MD arrays" pass failed because uneeded.
better safe than sorry, don't you think?
Mostly Agreeded.
"failed (no arrays found in config file or automatically)." show up in
red in my xterm... which usually means something should be fixed.
Maybe asking the user if he wants to build/start any array might help.
If you retitle this bug something like "please add a means to disable the
initramfs hook", reopen it, and change the severity to wishlist, I will
consider it for after etch.
Thanks, for the hint. Done.
@+,
Fab
