There's probably a third bug in here: mdmonitor should've mailed me when an array came up degraded at boot (I suspect that because mdmonitor gets started so early in the boot process, not all the moving pieces are there for mail delivery to happen). Eventually, you'll boot again with both drives in the array somehow, except they'll be out of sync, resulting in massive corruption. If you're lucky, you'll boot just with the other drive, and discover that your filesystem's contents are weeks/months out of date, and maybe you'll be lucky enough to figure out what happen, and switch back to the other drive and resync. But, not everyone's so lucky.
This first started happening in F16. It took me a while to figure out the cause for an occasionally raid assembly failure at boot. Fixed it, and forgot about it. Well, looks like the F17 anaconda brought back the broken /etc/default/grub, which found its way into my grub.cfg, and I just lost a full day, cleaning up this mess.
So, if you use raid 1 and upgraded to F17, you may need to fix this before it's too late: put back the missing uuid into /etc/default/grub, and into every entry in grub.cfg
Pissed.
Attachment:
pgpgG2OAiSM1l.pgp
Description: PGP signature
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
