[SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

kokice12 · 2013-12-26 19:44:32

Hello to you all,

I installed arch linux on my new Lenovo E130 following Beginner's guide. After install, when I rebooted the system I'm dropped into emergency shell. Whole log:

:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda1'
fsck: fsck.vfat: not found
fsck: error 2 while executing fsck.vfat for /dev/sda1
ERROR: fsck failed on '/dev/sda1'
:: mounting '/dev/sda1' on real root
mount: unknown filesystem type 'vfat'
You are now being dropped into an emergency shell.

/dev/sda1 is my UEFI partition in fat32 filesystem, mounted to /boot in fstab. Also it's wierd that fsck is trying to run on this partition as it's entery in fstab is

/dev/sda1        /boot        vfat        defaults        0         0

so no fsck is expected? Also I tried linux-lts kernel and installing dostools and than mkinitcpio to renew all the hooks, the error is still the same.

Thanks for all your help.

Last edited by kokice12 (2013-12-27 00:54:35)

ewaller · 2013-12-26 22:10:49

Could you share your partitioning scheme? From that, it appears you are trying to use a vfat partition as your linux root. If I may, I would call that a really bad(TM) idea. I hope that your root is really somewhere else, and is a file system that supports ownership, groups, and executable flags.

Oh, buy the way, Welcome to Arch Linux

kokice12 · 2013-12-26 23:06:58

My root is on ext4 partition, let me just show you my fstab

/dev/sda1        /boot        vfat        defaults        0         0
/dev/sda2        none         swap        defaults        0         0
/dev/sda3        /            ext4        rw,relatime,data=ordered        0        1

I really don't know why is it forcing fsck on partition with pass=0 in fstab?

And thank you

WonderWoofy · 2013-12-26 23:41:15

I would venture to guess that somehow your kernel being booted is not matching the kernel modules in /usr/lib/modules. Not sure how that would happen if you are really on a fresh install, but you can probably check if the booted kernel and installed linux package match when you get dropped into the emergency.target.

kokice12 · 2013-12-27 00:27:24

Not the problem:

# uname -r
3.12.6-1-ARCH

and in pacman (chrooted)

# pacman -Qs linux
...
local/linux 3.12.6-1 (base)

Scimmia · 2013-12-27 00:42:20

You set your bootloader up wrong. The root= parameter needs to point to your root partition, not the boot partition.

kokice12 · 2013-12-27 00:54:03

Scimmia wrote:

You set your bootloader up wrong. The root= parameter needs to point to your root partition, not the boot partition.

Thank you very much!

mongrelion · 2017-02-17 19:23:32

Scimmia wrote:

You set your bootloader up wrong. The root= parameter needs to point to your root partition, not the boot partition.

Thank you so much! I was having the same problem.

ewaller · 2017-02-17 19:46:39

Glad that solved it.

I shall use this opportunity to close this old thread

Arch Linux

#1 2013-12-26 19:44:32

[SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#2 2013-12-26 22:10:49

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#3 2013-12-26 23:06:58

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#4 2013-12-26 23:41:15

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#5 2013-12-27 00:27:24

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#6 2013-12-27 00:42:20

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#7 2013-12-27 00:54:03

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#8 2017-02-17 19:23:32

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

#9 2017-02-17 19:46:39

Re: [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

Board footer