On Mon, Mar 17, 2014 at 7:28 PM, Chris Murphy <li...@colorremedies.com>wrote:
> > On Mar 17, 2014, at 8:24 PM, Chris Murphy <li...@colorremedies.com> wrote: > > > > > On Mar 17, 2014, at 8:15 PM, Chris Murphy <li...@colorremedies.com> > wrote: > > > >> > >> On Mar 17, 2014, at 7:57 PM, Chris Murphy <li...@colorremedies.com> > wrote: > >>> But maybe once /boot/efi is mounted, it's worth doing dracut -f to > rebuild the initramfs, and then reboot. > >> > >> It's not worth it. I just used lsinitrd on my working system and > neither fat.ko or vfat.ko are in the initramfs. So somehow on your system > either vfat.ko or fat.ko (or both) are being blacklisted. > >>> > >>> If that doesn't fix it, I'm curious whether the grub menu kernel > options work. I'd try them in reverse order. > >> > >> Still interested with which kernel this does work. > >> > >>> What about > >>> > >>> cat /etc/modprobe.d/blacklist.conf > >> > >> Better is > >> > >> grep -i fat /usr/lib/modprobe.d/* > > > > And while you're at it also fpaste the grub.cfg. > > And while you're at it, reboot with the busted kernel option, and at the > emergency shell: > > modprobe vfat > ## note any messages for that command and then also > dmesg > ## note the last entries that seem relevant > > > Chris Murphy > > -- > users mailing list > users@lists.fedoraproject.org > 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 > modprobe vfat returns with no messages at all. The vfat module is not loaded. There is no file /etc/modprobe.d/blacklist.conf Here's a link to dmesg output https://www.amazon.com/clouddrive/share?s=xbSlzWw9RXoqK8H9HAVgIw Here's a link to grub.cfg https://www.amazon.com/clouddrive/share?s=M-h6hV1bQcEinfQSrTkMsc The kernel that is causing my issues is the same kernel I've been running for a while, 3.13.5-103.fc19.x86_64. Here's the steps that lead to my current problem: 1) log out and run shutdown from button on top right of login screen (I'm running mate desktop) 2) System indicates it's powering off, however, system does not turn off it restarts and boots back to login screen 3) Try shutdown again - same result 4) Get frustrated :-) 5) Hit power button to turn off system. 6) Power system on, goes to emergency mode. And no matter what I do it never gets passed emergency mode. What I find interesting is that both the root and home filesystems are mounted. So I was able to back up stuff. I am running LVM, I don't know if this is part of the problem. I tried booting off an older kernel 3.12.11-201.fc19.x86_64 and it also put me in emergency mode, but when I did an lsmod the vfat module was loaded and there where a total of 69 modules loaded. If I exit from the emegency mode prompt the process starts all over, the circle fills up, turns into the Fedora "f", pauses for a while and then puts me back info emergency mode. Paolo
-- users mailing list users@lists.fedoraproject.org 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
