-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Wolff III wrote: > I have been having some intermittant problems booting where a raid device > isn't usable and the boot halts. I have only gone through this twice, > but both times the first time it happened it referred to one of the > two mirrors, after rebooting it referred to the other such array and > then the third reboot worked. I have some other arrays with just one > device in the mirror and those weren't a problem either time I had to > go through that process. > In both cases the error message referred to a problem with the superblock, > but I expect the real problem was that the array wasn't set up properly. > I am not sure what component to file this under? (As of yesterday, a search > for rawhide bugs mentioning raid in the summary turned up zilch.) I've had a problem with the initrd based array activation as well: https://bugzilla.redhat.com/show_bug.cgi?id=431720 [ just edited the summary to include "RAID" as well as "MD" ] Although, from your description these might be completely unrelated - I've only seen the "mdadm: /dev/mdX not identified in config file." message in my case. Regards, Bryn. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHq1Vl6YSQoMYUY94RAughAKCVOrI8mCFaLqFy0XJSKOyrx2xa8gCgqa+F fBHIeAOJJFCVJ2pxOKIeoQc= =jecE -----END PGP SIGNATURE----- -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
