UEFI Loader Not Installed

[jennydaman]

Describe the bug

Destructive installation on /dev/sda, then reboot. Bootloader did not start.

To Reproduce

1. create bootable USB
2. boot USB in UEFI mode
3. clr-installer
4. choose "Destructive Installation"
5. shut down
6. unplug USB
7. power on

Expected behavior

bootloader (systemd-boot) starts then loads the Linux kernel, TTY login

I fixed this problem by rebooting into the live USB and running

efibootmgr --create --disk /dev/sda --part 1 --loader /EFI/BOOT/BOOTX64.EFI --label "Clear Linux"

Screenshots

none :(

Environment (please complete the following information):

• Clear Linux OS Version: 33540
• Installer Version 2.7.0
• Platform: ASRock motherboard
• UEFI version: FM2A75 Pro4-M P2.00
• Processor: AMD A10-5800K
• I physically unplugged every other hard drive, /dev/sda was the only disk.

Additional context

none

[mdhorn]

@jennydaman Can you please provide the /root/clr-installer.log which might help give us an idea if something went wrong. Note: You may wish to review the file for personal data you do not wish to share such as a username or device identifiers, but no secure information such as passwords will ever be present.

[jennydaman]

Here are my last install logs.

clr-installer.yaml clr-installer.log

I will be doing a full (destructive) reinstall later this evening, we'll see if it happens again.

[mdhorn]

Here are my last install logs.

clr-installer.yaml clr-installer.log

I will be doing a full (destructive) reinstall later this evening, we'll see if it happens again.

Installing the boot loader appears to work without error when calling clr-boot-manager, including removing quiet from the kernel command line:

020/07/31 22:35:32 [INF] Installing boot loader
2020/07/31 22:35:32 [DBG] /tmp/install-312099603/usr/bin/clr-boot-manager update --image --path=/tmp/install-312099603
2020/07/31 22:35:32 [DBG] Using default shellProxy.DefaultGetProxyValue
2020/07/31 22:35:32 [DBG] [Previous line repeated 4 times]
2020/07/31 22:35:32 [DBG] cmd.Env: []
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/cli/cli.c:L142): No such file: /tmp/install-312099603//etc/kernel/update_efi_vars
2020/07/31 22:35:32 [DBG] [INFO] cbm (../src/bootman/bootman.c:L744): Current running kernel: 5.7.10-972.native
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/bootman.c:L140): shim-systemd caps: 0x26, wanted: 0x00
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/bootman.c:L157): Legacy boot now selected (shim-systemd)
2020/07/31 22:35:32 [DBG] [INFO] cbm (../src/bootman/bootman.c:L764): path /tmp/install-312099603//etc/kernel/initrd.d does not exist
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/bootman.c:L784): Non regular file: /tmp/install-312099603//usr/lib/initrd.d/.., skipping.
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/bootman.c:L784): Non regular file: /tmp/install-312099603//usr/lib/initrd.d/., skipping.
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/update.c:L40): Skipping to image-update
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/update.c:L76): Now beginning update_image
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/lib/cmdline.c:L361): Removing cmdline using file: /tmp/install-312099603//etc/kernel/cmdline-removal.d/clr-installer.conf
2020/07/31 22:35:32 [DBG] [DEBUG] cbm (../src/bootman/update.c:L85): update_image: 1 available kernels
2020/07/31 22:35:32 [DBG] [INFO] cbm (../src/bootman/update.c:L111): update_image: Attempting bootloader update
2020/07/31 22:35:32 [DBG] [SUCCESS] cbm (../src/bootman/update.c:L114): update_image: Bootloader update successful
2020/07/31 22:35:33 [DBG] [DEBUG] cbm (../src/bootman/update.c:L125): update_image: Attempting install of /tmp/install-312099603//usr/lib/kernel/org.clearlinux.lts2019.5.4.53-53
2020/07/31 22:35:33 [DBG] [SUCCESS] cbm (../src/bootman/update.c:L130): update_image: Successfully installed /tmp/install-312099603//usr/lib/kernel/org.clearlinux.lts2019.5.4.53-53
2020/07/31 22:35:33 [DBG] [DEBUG] cbm (../src/bootman/update.c:L135): update_image: Setting default_kernel to /tmp/install-312099603//usr/lib/kernel/org.clearlinux.lts2019.5.4.53-53
2020/07/31 22:35:33 [DBG] [DEBUG] cbm (../src/lib/cmdline.c:L361): Removing cmdline using file: /tmp/install-312099603//etc/kernel/cmdline-removal.d/clr-installer.conf
2020/07/31 22:35:33 [DBG] [INFO] cbm (../src/bootman/bootman.c:L459): Checking for mounted boot dir
2020/07/31 22:35:33 [DBG] [INFO] cbm (../src/bootman/bootman.c:L467): boot_dir is already mounted: /tmp/install-312099603/boot
2020/07/31 22:35:34 [DBG] [SUCCESS] cbm (../src/bootman/update.c:L140): update_image: Default kernel is now /tmp/install-312099603//usr/lib/kernel/org.clearlinux.lts2019.5.4.53-53

It will be interesting to see if the problem you encountered is repeatable.

[jennydaman]

The bootloader was installed correctly, however it did not appear as a boot option in the UEFI menu (fixed manually using efibootmgr).

[mdhorn]

The bootloader was installed correctly, however it did not appear as a boot option in the UEFI menu (fixed manually using efibootmgr).

That is was/should be done with the call to the clr-boot-manager as well, but no error was reported that it was not completed.

[jennydaman]

So I tried the reinstall, same result.

Though I noticed that the boot entry was instantiated after a sudo swupd update

[mdhorn]

So I tried the reinstall, same result.

Though I noticed that the boot entry was instantiated after a sudo swupd update

In this case, swupd is making a call to clr-boot-manager at the end of the update.