On Mon, Mar 17, 2014 at 4:31 PM, Chris Murphy <li...@colorremedies.com>wrote:
> > > > Chris, > > here is the output for journal -b > > > > https://www.amazon.com/clouddrive/share?s=yuVEpW13SV0n_TIJKaokLs > > Mar 17 14:14:57 peglaptopnew systemd[1]: Mounting /boot/efi... > Mar 17 14:14:57 peglaptopnew mount[460]: mount: unknown filesystem type > 'vfat' > Mar 17 14:14:57 peglaptopnew systemd[1]: boot-efi.mount mount process > exited, code=exited status=32 > Mar 17 14:14:57 peglaptopnew systemd[1]: Failed to mount /boot/efi. > > This is weird. Unknown file system type vfat? That kernel module should be > available by this point in the boot process. > > > I'm going to guess that at the emergency.target shell prompt you can type > exit and it will continue to boot to graphical.target. The boot failure is > just an attempt to get your attention that a locally required volume isn't > mounting. I'm rather opposed to the idea of persistently mounted /boot/efi, > but that's currently what we do and it should work. > > What do you get for: > > mount /boot/efi > lsmod | grep vfat > cat /etc/fstab > blkid > > > 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 > Chris, here's the info you requested. mount /boot/efi mount: unknown filesystem type 'vfat' lsmod | grep vfat returns nothing, no vfat module present. cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Dec 8 17:19:59 2013 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/fedora-root / ext4 defaults 1 1 UUID=1fac12c9-bd58-4f5f-9ae3-7b9bb55cfd85 /boot ext4 defaults 1 2 UUID=A005-B31B /boot/efi vfat umask=0077,shortname=winnt 0 0 /dev/mapper/fedora-home /home ext4 defaults 1 2 /dev/mapper/fedora-swap swap swap defaults 0 0 LABEL=NEWDATA2 /media/NEWDATA2 ext4 defaults,nodev,noexec,nosuid,async,noatime 1 2 blkid /dev/sda1: LABEL="ESP" UUID="A005-B31B" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="a37591b8-de99-44c3-9eb8-e7de6f28d62d" /dev/sda2: LABEL="DIAGS" UUID="9E58-3CE0" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="90f009cd-547f-4829-bd4c-014ef1c2b4f0" /dev/sda3: UUID="1fac12c9-bd58-4f5f-9ae3-7b9bb55cfd85" TYPE="ext4" PARTUUID="9e47e650-33ca-4514-9185-f12a4d9fe3b2" /dev/sda4: LABEL="WINRETOOLS" UUID="4CFE599AFE597D60" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5aafa934-c73a-417d-b9b3-fa51a506c936" /dev/sda5: LABEL="PEGLTOPWIN8" UUID="4A7CD0AC7CD093D3" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="41a07db4-1103-4ffb-969a-67ea87aa477f" /dev/sda6: UUID="E69CF1879CF15293" TYPE="ntfs" PARTUUID="cc82e82f-56da-40c7-b6b4-9d79e0709e99" /dev/sda7: UUID="8066EE7366EE697C" TYPE="ntfs" PARTUUID="3d8e9278-4fb3-4ca8-a57d-15f329642338" /dev/sda8: LABEL="PBR Image" UUID="8E764C71764C5BD9" TYPE="ntfs" PARTLABEL="Microsoft recovery partition" PARTUUID="f5a7ccda-2b8a-45d9-bf2d-a60149646835" /dev/sda9: UUID="UXaRXx-XoYJ-KiZC-4Q3B-A1VR-BxUD-HmgG5q" TYPE="LVM2_member" PARTUUID="f29aa601-9fa5-4f02-98f9-ec85da1df97d" /dev/sr0: UUID="2013-06-27-14-02-10-00" LABEL="Fedora 19 x86_64" TYPE="iso9660" PTTYPE="dos" /dev/mapper/fedora-swap: UUID="f38c5443-bd86-41a5-b32c-3d572bac25de" TYPE="swap" /dev/mapper/fedora-root: UUID="f19bf96d-13b6-44ca-95d6-4491e8c75a16" TYPE="ext4" /dev/mapper/fedora-home: UUID="e2dd9fa7-c6a6-47dc-92d4-da5e8395639e" TYPE="ext4" /dev/sdb1: LABEL="NEWDATA2" UUID="72c38495-62e8-49ce-bc94-7bd4447c39fa" TYPE="ext4" Note that NEWDATA2 is an external USB drive I've been using to copy files between the non working system and another Fedora 19 system where I'm reading my email. It's formatted as ext4 and so gets mounted. I tried a USB stick, but it wont mount since it too is formatted as vfat. No matter what I do the system never boots past emergency mode. It never gets to graphical mode. 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 lsmod shows: Module Size Used by vfat 17411 1 fat 60923 1 vfat usb_storage 56690 1 i915 778082 1 i2c_algo_bit 13257 1 i915 drm_kms_helper 50287 1 i915 drm 283937 2 i915,drm_kms_helper i2c_core 38476 4 drm,i915,drm_kms_helper,i2c_algo_bit video 19206 1 i915 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