One of the changes in the updated mdadm package is to ghost /var/run/mdadm and to create it in the mdmonitor init script and also to set the SELinux state on the new dir. So while things booted ok for you, monitoring of arrays is DOA in the version prior to the update. Sent from my iPhone On Apr 10, 2011, at 4:37 PM, Adam Williamson <awilliam@xxxxxxxxxx> wrote: > On Sun, 2011-04-10 at 15:01 -0400, Doug Ledford wrote: >> The bug I'm looking at right now is specifically against the live >> image, so no I can't test that with something in updates testing. It >> needs to make it to the base before it gets on the live media to see >> if it solves the problem there. > > BTW, someone did mention to me that the Beta might need the new mdadm > for the /run change, but there were no critical bugs already filed on > it. I tested it on my laptop, which has an Intel BIOS RAID array; > booting a live image composed with the current mdadm sees the array, and > so does anaconda if you boot a traditional installer image with the > current mdadm. So I wasn't able to find any release-critical issue which > would require the new mdadm. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org > http://www.happyassassin.net > > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
