You are not logged in.
Pages: 1
Hi all,
I am installing arch on an Acer VN7-592G, dual booting with windows 10 on two different physical drives. I followed the installation guide without any problems, and went with systemd-boot as my bootloader. However I can't seem to boot into my installation. Both bootctl and efibootmgr can see the systemd-boot as Linux Boot Manager, but without a boot-order attached to it. If I manually add it through efibootmgr (or if i run bootctl update), efibootmgr will reflect the change. But when I reboot, I can only see my Windows bootloader as an option in the UEFI boot menu. Furthermore, if I boot back into the arch usb and run efibootmgr again, the boot order shows that the previous changes were reset.
I'm at a loss. Both secure boot and fast boot have been disabled, and there aren't many other things I can change in my UEFI menu. What am I doing wrong?
Thank you for any response
Last edited by bzisjo (2017-02-20 08:35:12)
Offline
Can we see the output of:
# efibootmgr -v
# parted --list
You can use a pastebin client to generate a URL that can be posted here.
Please also post the commands that you used to mount your partitions and chroot into the system.
You could try setting the systemd-boot.efi loader as the default from Windows but I think this will only work if you have shared the EFI system partition:
bcdedit /set "{bootmgr}" path "\EFI\systemd\systemd-boot.efi"
That command must be run with Administrator privileges.
Offline
Thanks for the reply! Here are the outputs:
efibootmgr -v (0003 is not in the boot order)
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0001* Windows Boot Manager HD(2,GPT,dca8cec8-2d39-4089-897d-ec24291d202f,0xe1800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...t................
Boot0002* USB HDD: SanDisk Extreme PciRoot(0x0)/Pci(0x14,0x0)/USB(21,0)/HD(1,MBR,0x4294967193,0xac,0x20000)RC
Boot0003* Linux Boot Manager HD(2,GPT,dca8cec8-2d39-4089-897d-ec24291d202f,0xe1800,0x32000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
parted --list
Model: ATA SAMSUNG MZNLN256 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 473MB 472MB ntfs Basic data partition hidden, diag
2 473MB 578MB 105MB fat32 EFI system partition boot, esp
3 578MB 595MB 16.8MB Microsoft reserved partition msftres
4 595MB 256GB 255GB ntfs Basic data partition msftdata
Model: ATA SanDisk SD8SB8U1 (scsi)
Disk /dev/sdb: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 912GB 912GB ntfs Basic data partition msftdata
2 912GB 1013GB 101GB ext4
3 1013GB 1024GB 11.0GB linux-swap(v1)
Model: SanDisk Extreme (scsi)
Disk /dev/sdc: 62.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 88.1kB 67.2MB 67.1MB primary fat16 esp
Model: SD ND4GB (sd/mmc)
Disk /dev/mmcblk0: 4009MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4194kB 4009MB 4005MB primary fat32 lba
And after booting into the live USB, I mount by:
# mount /dev/sdb2 /mnt
# mount /dev/sda2 /mnt/boot
# arch-chroot /mnt
so the EFI partition should be shared between windows and arch. I will give the Windows default workaround a try later.
Some additional info that may or may not be helpful:
fstab
# /dev/sdb2
UUID=4e5a6c72-1df3-4341-bda3-03a01bdb1947 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2
UUID=4678-4777 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sdb3
UUID=462e9d6c-5179-425b-b5bd-517c7359c3aa none swap defaults 0 0
loader.conf
default arch
timeout 4
editor 0
arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=ed368542-783c-462f-aab2-11a0475b2714 rw
PARTUUIDs
total 0
lrwxrwxrwx 1 root root 10 Feb 19 06:20 2f667710-d3d9-4376-b1d7-5d8e4118f2d8 -> ../../sda3
lrwxrwxrwx 1 root root 10 Feb 19 06:20 77a7d47f-594a-4940-944b-e1e295e3e4ce -> ../../sda4
lrwxrwxrwx 1 root root 10 Feb 19 06:20 79ef3b99-01 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Feb 19 06:20 79ef3b99-02 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Feb 19 06:20 a8939e01-149f-4eb6-9df9-85eb0e9151f4 -> ../../sdb3
lrwxrwxrwx 1 root root 15 Feb 19 06:18 d6657679-01 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 10 Feb 19 06:20 dbac9c33-a4e5-4b33-8529-908fd63ee4cf -> ../../sdb1
lrwxrwxrwx 1 root root 10 Feb 19 06:20 dca8cec8-2d39-4089-897d-ec24291d202f -> ../../sda2
lrwxrwxrwx 1 root root 10 Feb 19 06:20 e0d1c098-8c4d-4dea-abdf-98e9d157906c -> ../../sda1
lrwxrwxrwx 1 root root 10 Feb 19 06:20 ed368542-783c-462f-aab2-11a0475b2714 -> ../../sdb2
Offline
In my opinion, the UEFI firmware on your motherboard is defective and is booting $ESP/EFI/Microsoft/Boot/bootmgfw.efi rather than the specified $ESP/EFI/BOOT/BOOTX64.EFI
Rod Smith's excellent site has a section on this unfortunately common problem:
http://www.rodsbooks.com/efi-bootloader … ive-naming
The usual solution is to instruct Windows to load systemd-boot.efi, as I have already indicated.
Offline
Yea your solution does fix the problem. Thanks!
Offline
Good stuff, please mark the thread [SOLVED] to help others who may have this problem.
Offline
Pages: 1