You are not logged in.

#1 2020-01-22 19:47:02

doctor-venom
Member
Registered: 2020-01-22
Posts: 9

[SOLVED] cant boot to newly installed arch linux systemd boot loader

After installing arch linux as a secondary OS with UEFI and luks encryption, i rebooted and on boot there is only option:
Reboot Into Firmware Interface

although i created the arch.conf file in /boot/loader/entries and set the default option in /boot/loader/loader.conf to arch.

how to make it show arch linux entry on boot?

lsblk output:

NAME           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0            7:0    0 541.5M  1 loop  /run/archiso/sfs/airootfs
sda              8:0    0 447.1G  0 disk
├─sda1           8:1    0   128M  0 part
├─sda2           8:2    0 300.4G  0 part
├─sda3           8:3    0   516M  0 part
├─sda4           8:4    0   100M  0 part
├─sda5           8:5    0   512M  0 part  /mnt/boot
└─sda6           8:6    0 145.5G  0 part
  └─luks       254:0    0 145.5G  0 crypt
    ├─vg0-swap 254:1    0     8G  0 lvm   [SWAP]
    └─vg0-root 254:2    0 137.5G  0 lvm   /mnt
sdb              8:16   1   3.7G  0 disk
└─sdb1           8:17   1   3.7G  0 part  /run/archiso/bootmnt
sr0             11:0    1  1024M  0 rom

blkid output:

/dev/sda2: UUID="3228802C287FED6B" TYPE="ntfs" PARTLABEL="Microsoft Basic Data" PARTUUID="b7adfbee-bb0d-4fb6-b399-825f3dd36df4"
/dev/sda3: UUID="A49020BB90209638" TYPE="ntfs" PARTUUID="48416643-22ca-4d82-82db-f6e5a2face59"
/dev/sda4: UUID="92F9-A54E" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="1c58e0a1-6103-470b-b29a-962372d5bea2"
/dev/sda5: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="E661-CE25" TYPE="vfat" PARTLABEL="Arch Linux EFI system partiton" PARTUUID="bead8e7f-4e3b-4e30-8017-5786f0ae3686"
/dev/sda6: UUID="a0619b20-d947-4825-9f0c-035489416dbf" TYPE="crypto_LUKS" PARTUUID="d6272142-fd28-4d57-8ee0-d2527c3a38a4"
/dev/sdb1: LABEL="ARCH_202001" UUID="F2C3-6646" TYPE="vfat" PARTLABEL="Main Data Partition" PARTUUID="439c017b-e35d-4008-84da-220d6a5d39bb"
/dev/loop0: TYPE="squashfs"
/dev/mapper/luks: UUID="5AegdN-M6P3-prrf-EIIf-vnZn-R3un-p53r7e" TYPE="LVM2_member"
/dev/mapper/vg0-swap: UUID="838e6137-9de3-4d86-96ea-74c72afa0c4c" TYPE="swap"
/dev/mapper/vg0-root: LABEL="root" UUID="db6d891b-7e7b-45e4-8741-2ba6b3c9f561" TYPE="ext4"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="0cc4916a-f205-420a-a4f8-e8f3d2952651"

contents or /boot/loader/loader.conf

timeout 5
#console-mode keep
default arch-*
default b408dbd96add48d6ac7f58b245099d2e-*

contents of /boot/loader/entries/arch.conf

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=UUID=a0619b20-d947-4825-9f0c-035489416dbf:vg0 root=/dev/mapper/vg0-root resume=/dev/mapper/vg0-swap rw intel_pstate=no_hwp

the output of efibootmgr -v:

BootCurrent: 0007
Timeout: 2 seconds
BootOrder: 0002,0000,0006,0007,0001,0004
Boot0000* Windows Boot Manager  HD(4,GPT,1c58e0a1-6103-470b-b29a-962372d5bea2,0x37e11646,0x3200d)/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.}....................
Boot0001* SlimtypeDVD A  DA8AESH        BBS(CDROM,,0x0)..GO..NO........o.S.l.i.m.t.y.p.e.D.V.D. .A. . .D.A.8.A.E.S.H....................A...........................>..Gd-.;.A..MQ..L.5.3.8.0.1.A. .7.A.4.6.6.7.4.1.5.2.6.7.4........BO
Boot0002* Linux Boot Manager    HD(5,GPT,bead8e7f-4e3b-4e30-8017-5786f0ae3686,0x25a11000,0x100000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0004  TOSHIBA MQ01ABD100    BBS(HD,,0x0)..GO..NO........o.K.I.N.G.S.T.O.N. .S.A.4.0.0.S.3.7.4.8.0.G....................A...........................>..Gd-.;.A..MQ..L.0.5.2.0.B.6.3.7.0.8.D.5.5.F.8.8. . . . ........BO..NO........k.S.a.n.D.i.s.k. .C.r.u.z.e.r. .B.l.a.d.e. .1...2.6....................A.......................>..Gd-.;.A..MQ..L.4.C.5.3.2.0.0.0.0.2.0.3.1.0.1.2.3.0.3.5........BO
Boot0006* UEFI OS       HD(5,GPT,bead8e7f-4e3b-4e30-8017-5786f0ae3686,0x25a11000,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0007* UEFI: SanDisk Cruzer Blade 1.26, Partition 1  PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,GPT,439c017b-e35d-4008-84da-220d6a5d39bb,0x800,0x774fdf)..BO

output of parted --list:

Model: ATA KINGSTON SA400S3 (scsi)
Disk /dev/sda: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name                            Flags
 1      1049kB  135MB  134MB               Microsoft reserved partition    msftres
 2      135MB   323GB  323GB  ntfs         Microsoft Basic Data            msftdata
 3      323GB   323GB  541MB  ntfs                                         hidden, diag
 5      323GB   324GB  537MB  fat32        Arch Linux EFI system partiton  boot, esp
 6      324GB   480GB  156GB
 4      480GB   480GB  105MB  fat32        EFI system partition            boot, esp


Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 4005MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name                 Flags
 1      1049kB  4004MB  4003MB  fat32        Main Data Partition  msftdata

Last edited by doctor-venom (2020-01-22 21:27:42)

Offline

#2 2020-01-22 20:02:41

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

Don't post screenshots of text, paste the actual text (from the chroot): https://wiki.archlinux.org/index.php/Co … s_and_code


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2020-01-22 20:03:44

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

Don't post screenshots of text, paste the actual text (from the chroot): https://wiki.archlinux.org/index.php/Co … s_and_code


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2020-01-22 20:38:02

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

Can we please see the (textual) output of

efibootmgr -v
parted --list

And can you confirm that the bootctl install command copied systemd-bootx64.efi to /EFI/BOOT/bootx64.efi on the EFI system partition?

Last edited by Head_on_a_Stick (2020-01-22 20:38:43)


Jin, Jîyan, Azadî

Offline

#5 2020-01-22 20:53:32

doctor-venom
Member
Registered: 2020-01-22
Posts: 9

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

i have updated my question with textual outputs and the commands you requested.

i ran the bootctl path=/boot install command, but there is only BOOTX64. EFI in /boot/EFI/BOOT folder.
the systemd-boot.efi file is in /boot/EFI/systemd folder.

Last edited by doctor-venom (2020-01-22 20:56:35)

Offline

#6 2020-01-22 21:13:38

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 9,003
Website

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

doctor-venom wrote:

there is only BOOTX64. EFI in /boot/EFI/BOOT folder

Yes, that's fine. All is as it should be.

Is Secure Boot disabled?


Jin, Jîyan, Azadî

Offline

#7 2020-01-22 21:26:22

doctor-venom
Member
Registered: 2020-01-22
Posts: 9

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

i figured out the problem, i was following a tutorial but instead of a standard linux kernel i used linux-hardened kernel hence in my /boot directory i had:

vmlinuz-linux-hardened and initramfs-linux-hardened.img

but in the /boot/loader/entries/arch.conf i wrote

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=UUID=a0619b20-d947-4825-9f0c-035489416dbf:vg0 root=/dev/

so changing /boot/loader/enteries/arch.conf to

title Arch Linux
linux /vmlinuz-linux-hardened
initrd /intel-ucode.img
initrd /initramfs-linux-hardened.img
options cryptdevice=UUID=a0619b20-d947-4825-9f0c-035489416dbf:vg0 root=/dev/

solved the problem for me and now it can choose Arch linux in boot menu and boot without any problems.

thanks Head_on_a_stick.
hope this will help someone in the future.

Offline

#8 2020-01-22 21:27:47

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

doctor-venom wrote:

i figured out the problem, i was following a tutorial...

That is the extent of the problem. Third party tutorials are unsupported here. If you want help, use the wiki.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#9 2020-01-22 21:42:51

doctor-venom
Member
Registered: 2020-01-22
Posts: 9

Re: [SOLVED] cant boot to newly installed arch linux systemd boot loader

yeah nothing can be better than archwiki and i always refer to it. and when i didnt, got problems immediately xD

Offline

Board footer

Powered by FluxBB