can't boot F19 system

[Chris Murphy]

On Mar 17, 2014, at 6:12 PM, "pgaltieri ." <pgaltieri at gmail.com> wrote:
> 
> If I look at /usr/lib/modules on the non working system I get:
> 
> 3.12.11-201.fc19.x86_64/
> 3.12.9-201.fc19.x86_64/
> 3.13.5-101.fc19.x86_64/
> 3.13.5-103.fc19.x86_64/
> 
> uname -a shows
> 
> Linux peglaptopnew 3.13.5-103.fc19.x86_64 #1 SMP Mon Mar 3 18:46:36 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> 
> and both vfat.ko and fat.ko are present in
> 
> 3.13.5-103.fc19.x86_64/kernel/fs/fat
> 
> If I run
> 
> insmod /usr/lib/modules/3.13.5-103.fc19.x86_64/kernel/fs/fat/fat.ko
> insmod /usr/lib/modules/3.13.5-103.fc19.x86_64/kernel/fs/fat/vfat.ko
> 
> Then do
> 
> lsmod | grep vfat
> 
> it now shows both fat and vfat modules loaded
> 
> I then did an exit from emergency mode, but it again dropped into emergency mode

So after insmod, see if mount /boot/efi works. And if it does then exit.

And then, figure out why vfat.ko isn't loading. That I don't understand. I don't think it needs to be in the initramfs. But maybe once /boot/efi is mounted, it's worth doing dracut -f to rebuild the initramfs, and then reboot.

If that doesn't fix it, I'm curious whether the grub menu kernel options work. I'd try them in reverse order.

I have had this problem once before, it was the identical error but in my case was only with the rescue kernel option which is actually a rescue initramfs. The problem was that vfat.ko isn't built into the non-host initramfs and the rescue kernel /lib/modules directory had since been deleted so there wasn't a vfat.ko available. Sorta makes the rescue option not much of a rescue but whatever - your situation is the opposite, you have vfat.ko it's just not loading for some reason. What about

cat /etc/modprobe.d/blacklist.conf



Chris Murphy