you now need "nofail" as an option so the automatic systemd crap will not stop on a missing fs. And I have also noticed that once systemd parses the fstab file changing it won't work, you have to reboot it to get it to figure out you removed it. There is probably a way to cancel what systemd is doing, but rebooting after updating fstab is simpler. Using nofail and/or updating fstab (removing entries) has allowed me to reboot the machine and get it up--but you have to fix the issue or make changes and reboot to get systemd to not keep trying. On Wed, Mar 25, 2015 at 3:05 PM, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > On Wed, 25 Mar 2015 12:33:24 -0600 > Ronal B Morse wrote: > >> You might have to update dracut, too. >> >> I'm not sure what the relationship between dracut and RAID configuration >> is. Are RAIDs entered into the initramfs? > > I don't know if any raid config info is in there, but it > definitely needs additional drivers in the initramfs (that's > how I eventually got the system to boot). > > I'm suspecting it knows enough to recognize the some of the > raid metadata then gets upset because there is no raid > driver loaded. I just wonder if the response to that could > be more useful than hanging forever :-). > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
