On Tue, Aug 23, 2005 at 07:03:49PM -0400, Daniel Jacobowitz wrote: > When I installed a kernel using yaird to create the ramdisk, I got an error > that there were no listed devices in the mdadm output. I edited RaidTab.pm > to invoke mdadm with -v (--verbose), and then things seemed to work OK.
Thanks for pointing this out. Some working notes: * between 1.9.0 and 1.12.0 the devices=... got dropped from normal mdadm output. * that's desirable behaviour, since the old format promotes overspecified and fragile mdadm.conf files. * in 1.12.0, -v produces devices=... In 1.9.0, -v produces far more verbose output, that 1.12.0 generates with -v -v. * in the upstream package, I cannot simply ignore devices=..., since it determines which hardware drivers need to be loaded. * in the upstream package, I don't want to require mdadm >= 1.12.0, since other distros have earlier versions. (fedora seems to use 1.6.0) * parsing the mdadm -v -v -v output is a pain; much too verbose. * The cleanest solution seems to be to first try mdadm without -v, and if that doesn't yield devices=... to retry with -v option. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
