-----BEGIN PGP SIGNED MESSAGE-----
Hit a snag booting a rawhide box with some MD devices tonight.
The initramfs is using a command like this to start the md (RAID-1, two
mdadm -As --auto=yes --run /dev/md1
mdadm: /dev/md1 not identified in config file.
And, since that's the device with my root vg, we don't get much further :)
If I replace that with a UUID activation, things look much better:
mdadm -A /dev/md1 --uuid=XXXXXXX:XXXXXXXX:XXXXXXXX:XXXXXXXX
And I get a successful boot. Seems like a bug in mdadm to me - I get the
same thing trying to manually bringup the arrays in rescue (although the
raidstart python script works as it uses UUIDs).
Anyone else seen this before?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----