You are not logged in.
I'm a linux user since the late 90's but a newcomer to Arch so please tell me if this should be moved to the Newbie section instead.
Trying to install Arch to dualboot with Windows 10 on a UEFI Lenovo T440P.
The installation seems to have completed good with a base system in place which I can access using arch-chroot. I followed the install instructions from the Wiki.
Also Grub is installed and loading on boot.
The problem is that Grub is not showing my Arch installation as an option.
The boot menu shows:
Windows Boot Manager
EFI default loader
Boot Into Firmware Interface
If I select EFI default loader I'm moved to a menu with:
Windows Boot Manager
Boot Into Firmware Interface
Those to optiona either take me to Win10 or the firmware settings.
Can someone suggest to me how to start troubleshoot this?
Last edited by Gulnar (2016-05-15 12:22:30)
Offline
Please post the full output of:
# efibootmgr -v
# parted -l
These commands can be run from any GNU/Linux live ISO image.
Please also provide a list of the *exact* commands which were used to install the GRUB bootloader to the hard drive and create the configuration file.
Jin, Jîyan, Azadî
Offline
The boot manager was installed using:
# bootctl install
As In understood it was not necessary to supply any additional path information if the Arch wiki install instructions was followed.
The output from parted is as follows:
# parted -l
Model: ATA ST500LM021-1KJ15 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1050MB 1049MB ntfs hidden, diag
2 1050MB 1322MB 273MB fat32 EFI system partition boot, esp
3 1322MB 1456MB 134MB Microsoft reserved partition msftres
4 1456MB 291GB 289GB ntfs Basic data partition msftdata
5 291GB 479GB 189GB ext4
6 479GB 500GB 20.7GB ntfs hidden, diag
Model: Kingston DataTraveler G3 (scsi)
Disk /dev/sdb: 3870MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 88.1kB 42.0MB 41.9MB primary fat16 esp
And from efibootmgr:
#efibootmgr -l
BootCurrent: 000D
Timeout: 0 seconds
BootOrder: 0016,0015,0007,0008,0000,0001,0002,0003,0009,000A,000B,000C,000D,000E,0013,0017,0014
Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0001 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0002 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0003 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0004 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0005 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0006 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0007* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0008* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0009* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot000A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot000B* ATA HDD1: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f605)
Boot000C* ATA HDD2: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot000D* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot000E* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot000F* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot0010* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot0011* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0012* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0013 Other HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot0014 Other CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot0015* Linux Boot Manager HD(2,GPT,efe4052c-d395-4fd0-852e-f0dbbcbe1f9d,0x1f4800,0x82000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0016* Arch Linux HD(1,GPT,6bdd7682-5d8f-410b-9e11-5913686f66a1,0x800,0x1f4000)/File(\vmlinuz-linux)r.o.o.t.=./.d.e.v./.s.d.a.5. .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.
Boot0017* Windows Boot Manager HD(2,GPT,efe4052c-d395-4fd0-852e-f0dbbcbe1f9d,0x1f4800,0x82000)/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.}...................
Offline
You didn't installed grub. But there's a conflict on the booting order. You might enter the BIOS boot order, to modify your booting order or you should read the efibootmgr man page, then modify the booting order.
do it good first, it will be faster than do it twice the saint
Offline
As @TheSaint says, you are using systemd-boot rather than GRUB and you need to configure it correctly.
Jin, Jîyan, Azadî
Offline
You are right. Setting it up according to your link fixed the bootloader issue in a quick way.
esp/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=<YOUR UUID> rw
Offline
By the way. How do I set this thread to Answered?
Offline
As the owner of the thread, you can edit your first post in the thread. That will allow you to edit the thread title.
Just prepend [SOLVED]. You may need to re-wicker the title is it is too long.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline