[SOLVED] Error getting loaded image path

vinnom · 2022-11-17 22:55:27

Hi guys!

After a fresh install, I'm getting the title as error when booting.

I didn't do anything differently from a fresh install (really, I used archinstall script and everything went smoothly)

I chose minimal install from it and additionally just installed vim and amd-ucode. I left the bootloader as default, so it's systemd-boot.

Not sure how to get this through. As image isn't loaded, it seems that I can't get neither dmesg or journalctl from this failed boots. Journalctl entries are only from those which I chrooted from install media.

Here are some info:

blkid:

/dev/sda1: UUID="82EC-F41A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="35b62242-3935-4224-a82d-7e5e2925a3b6"

/dev/sda2: UUID="d3b5b920-cbc6-4ff5-9c3b-dd57446c55a2" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="a03a730c-3b2d-4b42-9c60-f546ade5fd94"

/dev/sdb1: UUID="f71b7692-dba2-4dbe-9614-98a04fcbe39e" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="b36188cf-cff4-4e03-8ebe-cf481bd88405"

/etc/fstab

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=d3b5b920-cbc6-4ff5-9c3b-dd57446c55a2	/         	ext4      	rw,relatime	0 1

# /dev/sda1
UUID=82EC-F41A      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/sdb1
UUID=f71b7692-dba2-4dbe-9614-98a04fcbe39e	/home     	ext4      	rw,relatime	0 2

/boot/loader/loader.conf

timeout 3
#console-mode keep

/boot/loader/entries/default-entry.conf

# Created by: archinstall
# Created on: 2022-11-17_02-11-56
title Arch Linux (linux)
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=a03a730c-3b2d-4b42-9c60-f546ade5fd94 rw rootfstype=ext4

I already tried to switch PARTUUID to UUID on default-entry.conf, the result is the same on booting:

Boot image

Any ideas on how I could proceed?

edit: couldn't get image tag to work, so here it is https://imgur.com/a/wZiYb0b

EDIT

defragmenteur wrote:

See this post on systemd github.

the issue linked by this quote contains a discussion in which a PR for fixing this report is merged.

Last edited by vinnom (2022-11-22 22:06:31)

skunktrader · 2022-11-17 23:21:15

I'm just guessing here but it does seem strange to me that all the partitions have the same label

vinnom · 2022-11-18 00:38:26

oh, thanks, I didn't notice!

I changed their names to rootp, esp and homep on the same order from fstab. The error is the same however

HalosGhost · 2022-11-18 00:44:08

Moving to Guided Installer section.

All the best,

-HG

cfr · 2022-11-18 00:46:34

I'd recommend asking for this to be moved to the Guided Installer forum, where archinstall's developer/maintainer looks.

If you boot the live ISO, mount your partitions and then check whether things are installed as expected (cf. https://wiki.archlinux.org/title/Systemd-boot). For example, do you have

/mnt/boot/EFI/systemd/systemd-bootx64.efi
/mnt/boot/EFI/BOOT/BOOTX64.EFI

What is in /mnt/boot otherwise?
and does efibootmgr show an appropriate entry?

Is secure boot disabled?

vinnom · 2022-11-18 01:07:29

If you boot the live ISO, mount your partitions and then check whether things are installed as expected (cf. https://wiki.archlinux.org/title/Systemd-boot). For example, do you have

here the tree:

boot/
├── EFI
│   ├── BOOT
│   │   └── BOOTX64.EFI
│   ├── Linux
│   └── systemd
│       └── systemd-bootx64.efi
├── amd-ucode.img
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│   ├── entries
│   │   └── 2022-11-17_02-11-56_linux.conf
│   ├── entries.srel
│   ├── loader.conf
│   └── random-seed
└── vmlinuz-linux

and bootctl status

System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (unsupported)
  TPM2 Support: no
  Boot into FW: not supported

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─n/a

Random Seed:
 Passed to OS: no
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/35b62242-3935-4224-a82d-7e5e2925a3b6)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 252.1-1-arch)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 252.1-1-arch)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/35b62242-3935-4224-a82d-7e5e2925a3b6
         File: └─/EFI/systemd/systemd-bootx64.efi

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/35b62242-3935-4224-a82d-7e5e2925a3b6)

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Arch Linux (linux)
           id: 2022-11-17_02-11-56_linux.conf
       source: /boot/loader/entries/2022-11-17_02-11-56_linux.conf
        linux: /vmlinuz-linux
       initrd: /amd-ucode.img
               /initramfs-linux.img
      options: root=UUID=d3b5b920-cbc6-4ff5-9c3b-dd57446c55a2 rw

efibootmgr displays the same boot entry which bootctl displays

cfr · 2022-11-18 01:36:45

vinnom wrote:

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/35b62242-3935-4224-a82d-7e5e2925a3b6)
efibootmgr displays the same boot entry which bootctl displays

Does it really show the same? Because that seems very odd. I don't use systemd-boot, but EFI boot entries never look like that. They don't use Linux syntax at all.

I'm guessing efibootmgr shows something different, because bootctl also shows boot entries which look weird on my system. In fact, I'm not sure the entry it shows me is an nvram entry at all.

Last edited by cfr (2022-11-18 01:41:02)

vinnom · 2022-11-18 01:41:40

yeah, the same. Not the same syntax, but the same entry

BootCurrent: 0005
Timeout: 3 seconds
BootOrder: 0002,0004,0005
Boot0002* Linux Boot Manager	HD(1,GPT,35b62242-3935-4224-a82d-7e5e2925a3b6,0x800,0xff800)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0004* Hard Drive	BBS(HD,,0x0)50303a2053534432534331323047334c43373236423130342d333730502000
Boot0005* UEFI: SanDisk Cruzer Blade 1.26	PciRoot(0x0)/Pci(0x9,0x0)/Pci(0x0,0x0)/USB(4,0)/HD(1,MBR,0x8802a288,0x17f800,0x7800)

cfr · 2022-11-18 01:58:13

The output for the boot loader looks wrong. See https://www.freedesktop.org/software/sy … otctl.html for an example of the expected output.

You have

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─n/a

which is what I have. In my case, I'm not surprised to find systemd denying I have any boot loader at all or that it refuses to recognise any competitor has any features worth mentioning.

But you're supposed to be using systemd-boot itself, so you should have something more like

https://www.freedesktop.org/software/systemd/man/bootctl.html wrote:

Current Boot Loader:                         ← details about sd-boot or another boot loader
      Product: systemd-boot version            implementing the Boot Loader Interface
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Load drop-in drivers
               ✓ Boot loader sets ESP information
          ESP: /dev/disk/by-partuuid/01234567-89ab-cdef-dead-beef00000000
         File: └─/EFI/systemd/systemd-bootx64.efi

However, I have no idea whether such output is indicative or aspirational.

vinnom · 2022-11-18 02:22:04

hmmm

yeah, it sure looks weird. It's like the boot loader is available, but it isn't set as the current one. Yet, efibootmgr list it as a valid boot.

Tomorrow I'll try to dig deeper into the documentation and wiki

AlmaMater · 2022-11-19 00:06:47

Today I also had issue installing Arch. Tried like 3 times.

At the end I used an older .ISO and everything went Ok.(from Oct )

Hope it helps

Last edited by AlmaMater (2022-11-19 00:07:10)

vinnom · 2022-11-19 17:03:49

I gave up from systemd-boot, maybe there are some incompatibility of it with my board EFI implementation.

Accordingly with the below post from this topic, systemd-boot should be filling variables and bootctl status should output the "Current boot loader" correctly.

V1del wrote:

Firmware can only show something if your EFI has certain EFI variables filled, which isn't guaranteed the "current boot loader" info will only show information if certain EFI variables are filled, which systemd-boot will fill, others may not

However, I suggest moving this from Arch Linux Guided Installer forum, as I got the same error after trying manually installing systemd-boot:

// First remove all boot entries
efiboomgr -b xxxx -B // for all entries, except the flash media UEFI boot

// Remove everything from /boot
rm -rf /boot/*

// Reinstall kernel and ucode files
pacman -S linux amd-ucode

// Reinstall systemd-boot
bootctl install

// Configured most basic configuration for on /boot/loader/entries/default-entry.conf
title   Arch Linux
linux   /vmlinuz-linux
initrd  /amd-ucode.img
initrd  /initramfs-linux.img
options root="UUID=d3b5b920-cbc6-4ff5-9c3b-dd57446c55a2" rw

Yet, the error was the same. Then I repeated all steps before the "bootctl install" one and followed rEFInd wiki install steps. System booted correctly now.

Not sure if I should update this topic title as solved, as systemd-boot issue isn't quite solved.

Just for completion, my board is a "ASUSTeK COMPUTER INC. SABERTOOTH 990FX".

cfr · 2022-11-20 04:12:40

If you want the topic moved, use the 'report' button at the bottom right of any post and ask a moderator to move it wherever.

I'm glad you got refind working, but it is odd that systemd-boot doesn't work. I've seen some people report problems on Macs recently, but that doesn't seem likely related?

vinnom · 2022-11-20 14:52:20

cfr wrote:

If you want the topic moved, use the 'report' button at the bottom right of any post and ask a moderator to move it wherever.

thanks!

cfr wrote:

I'm glad you got refind working, but it is odd that systemd-boot doesn't work. I've seen some people report problems on Macs recently, but that doesn't seem likely related?

hmm, not sure. I need to read those reports and try to find any similarity.

On my past installations, Grub was my main boot manager and never had any problem with it, just tried systemd-boot this time, so still learning about it.

ewaller · 2022-11-20 14:52:49

Moved by request.

defragmenteur · 2022-11-21 00:06:30

See this post on systemd github.

vinnom · 2022-11-22 22:03:37

Thanks for the suggestion @defragmenteur
The discussion really seems the same issue I have and it makes sense that @AlmaMater post, in which an older version worked for him.

I tried to build a newer version of systemd-boot with PR already merged, but I got a build issue which I couldn't figure out how to solve.

It really seems that a newer sd-boot have this issue fixed. Probably next month I'll have to fresh install again because I'm gonna build a new desktop and I assume that 12/2022 arch installation will have the new sd-boot version on it.

I'll mark this as solved and update the title, thanks!

gabx · 2022-12-05 09:45:52

I have been booting under UEFI for a while with no issue at all. After an upgrade, my box does not boot anymore and I have same message as OP: Error getting loaded image path?.
I upgraded systemd as I thought a bug in systemd-boot was the culprit, but nothing changed.

This thread is marked as SOLVED, but I can't see how the issue with systemd-boot has been solved. I don't want to change for GRUB.

Thank you for any hint.

cfr · 2022-12-05 18:42:28

gabx wrote:

This thread is marked as SOLVED, but I can't see how the issue with systemd-boot has been solved. I don't want to change for GRUB.
Thank you for any hint.

It is as solved as it can be here. If you want help building a fixed version (until the fix makes it into Arch) or using a different boot loader (which need not be grub!), I recommend starting a new thread and linking this one and the upstream discussion. Otherwise, there's nothing to do but wait.

Whether an issue is solved or not is a matter for the OP. The OP's problem has been solved, in the OP's view, and that's that.

Last edited by cfr (2022-12-05 18:43:47)

Arch Linux

#1 2022-11-17 22:55:27

[SOLVED] Error getting loaded image path

#2 2022-11-17 23:21:15

Re: [SOLVED] Error getting loaded image path

#3 2022-11-18 00:38:26

Re: [SOLVED] Error getting loaded image path

#4 2022-11-18 00:44:08

Re: [SOLVED] Error getting loaded image path

#5 2022-11-18 00:46:34

Re: [SOLVED] Error getting loaded image path

#6 2022-11-18 01:07:29

Re: [SOLVED] Error getting loaded image path

#7 2022-11-18 01:36:45

Re: [SOLVED] Error getting loaded image path

#8 2022-11-18 01:41:40

Re: [SOLVED] Error getting loaded image path

#9 2022-11-18 01:58:13

Re: [SOLVED] Error getting loaded image path

#10 2022-11-18 02:22:04

Re: [SOLVED] Error getting loaded image path

#11 2022-11-19 00:06:47

Re: [SOLVED] Error getting loaded image path

#12 2022-11-19 17:03:49

Re: [SOLVED] Error getting loaded image path

#13 2022-11-20 04:12:40

Re: [SOLVED] Error getting loaded image path

#14 2022-11-20 14:52:20

Re: [SOLVED] Error getting loaded image path

#15 2022-11-20 14:52:49

Re: [SOLVED] Error getting loaded image path

#16 2022-11-21 00:06:30

Re: [SOLVED] Error getting loaded image path

#17 2022-11-22 22:03:37

Re: [SOLVED] Error getting loaded image path

#18 2022-12-05 09:45:52

Re: [SOLVED] Error getting loaded image path

#19 2022-12-05 18:42:28

Re: [SOLVED] Error getting loaded image path

Board footer