Arch Linux

musasabi

Member

From: Chicago, IL

Registered: 2011-06-23

Posts: 63

[SOLVED] bootloader (EFI) woes

I've got a dual boot setup with W10 and Arch. Presently, fdisk shows:

[root@archiso /]# fdisk -l
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1C8F7A0E-FD39-4B58-9A8E-601C1A599E91

Device         Start       End   Sectors   Size Type
/dev/sda1       2048    411647    409600   200M EFI System
/dev/sda2     411648 105269247 104857600    50G Linux filesystem
/dev/sda3  105269248 500118158 394848911 188.3G Microsoft basic data

while the fstab for this install looks like:

[root@archiso /]# cat /etc/fstab 
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda2
UUID=386e400b-5fb2-4813-be67-ac57428f455f	/         	ext4      	rw,relatime,data=ordered	0 1

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

I partitioned the disk with the Arch installer first, then installed W10, then installed Arch.

When I ran bootctl install --path=/dev/sda1, it auto-detected the existing Windows install like it should've, and as one might expect, bootctl outputs the following:

[root@archiso /]# bootctl
Failed to read EFI variable LoaderDevicePartUUID: No such file or directory
System:
     Firmware: UEFI 2.10 (American Megatrends 4.653)
  Secure Boot: disabled
   Setup Mode: setup

Loader:
      Product: systemd-boot 231
    Partition: n/a
         File: └─/EFI/BOOT/loader.efi

Boot Loader Binaries:
          ESP: /dev/disk/by-partuuid/ac85ddef-5ea4-4e82-89c7-d19129090abc
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 231)
         File: └─/EFI/BOOT/bootx64.efi (systemd-boot 231)

Boot Loader Entries in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/ac85ddef-5ea4-4e82-89c7-d19129090abc
         File: └─/EFI/systemd/systemd-bootx64.efi

        Title: Windows Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/ac85ddef-5ea4-4e82-89c7-d19129090abc
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

But, of course, there's that troublesome first bit. When I Googled that, I got a few results, and some source code from the systemd GitHub project page. Haha. That means I messed something up extra special, I assume.

Anyway, when I actually boot, I get the gummiboot/bootctl prompt, but it only has Windows Boot Manager, EFI Default Loader (which boots into the exact same menu options, minus itself), and Reboot Into Firmware Interface.

What's the deal? Why does the installation succeed, then another tool proceeds to tell me that it can't find the UUID? And, of course, how can I fix this nonsense?

Last edited by musasabi (2017-04-30 22:29:30)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,419

Re: [SOLVED] bootloader (EFI) woes

Sounds like you didn't create a config file for Arch