[SOLVED] UEFI boot doesn't load properly/fsck fails on boot

neonwhite · 2017-01-06 23:37:48

I have a UEFI enabled system and have installed Arch accordingly. It took three tries before I got it, but I now have an installed system. The only issue is that it doesn't boot into the new system, it instead boots into a recovery shell after the disk fails fsck. I have two partitions: /dev/sda1, which contains the EFI boot partition, and /dev/sda2, which contains everything else and is formatted as ext4. Arch is the only OS installed on my machine. fsck tells me that the superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. After running fsck on /dev/sda2, it asks if I want it to 'Free inodes count wrong for group #XXXX (X, counted=X) there are several dozen of these prompts ( I went through a few before I was given the 'press a to enable fix all' option ). I ran fsck twice before attempting to remount the partition. As the guide instructed, when installing Arch I mounted my primary drive at '/mnt'. When attempting to mount to this point again I get an error: 'mount: can't find /dev/sda2 in etc/fstab' My fstab looks like this:

# /etc/fstab: static file system information
#
# <file system>         <dir>    <type>    <options>     <dump>     <pass>
#  /dev/sda2
UUID=7d8d1c12-d11d-494a-bbb4-ef6ec4dc2951   /   ext4   rw,realtime,data=ordered   0 1

# /dev/sda1
UUID=A777-CD96   /boot     /vfat        rw,realtime,fmask=0022,dmask-0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro   0 2

(These next lines are ones I added while following the wiki guides for installing in UEFI mode)
# ESP bind mount
/esp/EFI/arch            /boot     none       defaults,bind   0 0

# mounting efi read only
efivars                       /sys/firmware/efi/efivars   efivars   ro,nosuid,nodev,noexec,noatime   0 0

This is the output of 'fdisk -l'

Device        Start         End               Sectors        Size        Type
/dev/sda1   2048         1050623        1048576      512M      EFI System
/dev/sda2   1050624   976773134    97572211    465.3G   Linux filesystem

I don't think my hard drive is damaged ( although it could be ). I think the issue lies with the fstab, UEFI, and how /esp is binded to the /boot directory. Additionally, while reading the wiki on the EFI System Partition, at the very bottom (where the changes to the fstab are detailed) there is a warning regarding a kernel parameter. I don't think I changed the parameter correctly, but was unable to find any information online or on the wiki. All I did was type in root=system_root while I was chrooted into my system from the install disk.

I have no idea what is wrong with the system and am at a complete loss as to how to fix it. Any assistance would be appreciated. Thank you.

These are the guides I read through on the Arch wiki to install and boot Arch in UEFI mode.
https://wiki.archlinux.org/index.php/EF … _Partition
https://wiki.archlinux.org/index.php/Un … efibootmgr
https://wiki.archlinux.org/index.php/EFISTUB

Last edited by neonwhite (2017-01-08 19:35:38)

jasonwryan · 2017-01-06 23:48:50

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

neonwhite · 2017-01-06 23:51:17

Sorry, but I didn't copy from the files. I used another computer and transposed what I saw on the screen of the problem computer.

ewaller · 2017-01-07 00:16:51

What bootloader are you trying to use? Can you share its configuration?

neonwhite · 2017-01-07 00:52:28

I am using efibootmgr with my /esp/EFI/arch directory binded to the /boot directory. The contents of the /boot directory were copied to /esp/EFI/arch and are the following:

initramfs-linux.img

initramfs-linux-fallback.img

vmlinuz-linux

The following is taken from the wiki (https://wiki.archlinux.org/index.php/EFISTUB)

Using UEFI directly

UEFI is designed to remove the need for an intermediate bootloader such as GRUB. If your motherboard has a good UEFI implementation, it is possible to embed the kernel parameters within a UEFI boot entry and for the motherboard to boot Arch directly. You can use efibootmgr or UEFI Shell v2 to modify your motherboard's boot entries.

This is the command it gives (and the one I used)

# efibootmgr -d /dev/sdX -p Y -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdBZ rw initrd=/initramfs-linux.img"

/dev/sdX was replaced with /dev/sda and Y was replaced with sda2

This is the output of efibootmgr -v

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* EFI USB Device (Generic USB Storage) PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x4294967240,0x16628,0x2990)RC
Boot0001* Arch Linux HD(1,GPT,7fd1135b-efd0-45dd-8327-c67171953f27,0x800,0x100000)/File(\vmlinuz-linux)r.o.o.t.=./.d.e.v./.s.d.a. .r.w. .i.n.i.t.r.d.=./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g.
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC

Last edited by neonwhite (2017-01-07 01:05:54)

neonwhite · 2017-01-07 01:07:28

This is the output of 'dmesg | tail'

[ 1086.764255] ath: EEPROM indicates we should expect a country code
[ 1086.764256] ath: doing EEPROM country->regdmn map search
[ 1086.764257] ath: country maps to regdmn code: 0x3a
[ 1086.764258] ath: Country alpha2 being used: US
[ 1086.764258] ath: Regpair used: 0x3a
[ 1086.764260] ath: regdomain 0x8348 dynamically updated by country IE
[ 1294.199378] EXT4-fs (sda2): VFS: Can't find ext4 filesystem
[ 1411.697997] EXT4-fs (sda2): VFS: Can't find ext4 filesystem
[ 1839.180206] EXT4-fs (sda2): VFS: Can't find ext4 filesystem
[ 1852.585346] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)

ewaller · 2017-01-07 01:23:08

Boot0001* Arch Linux    HD(1,GPT,7fd1135b-efd0-45dd-8327-c67171953f27,0x800,0x100000)/File(\vmlinuz-linux)r.o.o.t.=./.d.e.v./.s.d.a. .r.w. .i.n.i.t.r.d.=./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g.

root should be sda2, not sda

neonwhite · 2017-01-07 04:22:45

Do you think that's the issue? The hard drive isn't damaged or anything? I tried searching to see if anyone had installed arch using efibootmgr and pure UEFI but it doesn't seem to be a popular configuration.

neonwhite · 2017-01-07 04:30:28

That worked. Thank you so much. I can't believe that it was something so simple. You're a lifesaver.

ewaller · 2017-01-07 18:04:40

You are welcome. Be sure to edit your first post and prepend [SOLVED] to the thread title. You might need to change the title slightly to get it all to fit.

Arch Linux

#1 2017-01-06 23:37:48

[SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#2 2017-01-06 23:48:50

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#3 2017-01-06 23:51:17

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#4 2017-01-07 00:16:51

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#5 2017-01-07 00:52:28

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#6 2017-01-07 01:07:28

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#7 2017-01-07 01:23:08

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#8 2017-01-07 04:22:45

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#9 2017-01-07 04:30:28

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

#10 2017-01-07 18:04:40

Re: [SOLVED] UEFI boot doesn't load properly/fsck fails on boot

Board footer