Page MenuHomeSolus

Unable to boot after updating to current 5.0.5-113 (Acer Notebook; UEFI)
Open, Needs More InfoPublic

Description

Hello,

I have/had an issue where I'm able to install Solus 4 Fortitude onto my notebook, but can't boot (via UEFI) afterwards with the following error message:

"Error loading \EFI\com.solus-project\kernel-com.solus-project.current.4.20.16-112: Not Found"
"Failed to execute Solus 4.0 Fortitude \EFI\com.solus-project\kernel-com.solus-project.current.4.20.16-112: Not Found"

Someone on my Flarum post regarding this issue suggested just installing Solus 3.9999 and upgrading to 4.0. This worked until I ran another full upgrade of the system a few days later. Now I'm not able to boot into my Solus installation except when I switch the Kernel pre boot.

com.solus-project.current.5.1.7-119 [DOES NOT WORK]
com.solus-project.current.5.0.5-113 [DOES NOT WORK]
com.solus-project.current.4.20.16-112 [WORKS]

It seems that no Kernel above 4.20 works.

After fiddling and looking into several other posts this seems to affect different types of Motherboards from Acer. (another Flarum Post). Here is another user with a similar problem (I don't know if he has Acer too): third flarum post

I can't change the "standard" boot kernel via clr-boot-manager update. I get an Error "Bus Error" (please see comment for Log with CBM_DEBUG). So the only workaround for me atm is to change the kernel during boot (switched the default kernel to the 4.20 one.

Sadly I'm not able to troubleshoot this issue any further without advice. Please tell me what more info you need to investigate this issue.

Event Timeline

cigh033 created this task.Apr 23 2019, 9:39 AM
chax added a subscriber: chax.Apr 24 2019, 10:06 AM

try running clear-boot-manager command like this

sudo CBM_DEBUG=1 clr-boot-manager update

maybe it will tell you more about why clear-boot-manager is failing.

thank you for your recommendation. Sadly I can't seem to find any oddity in the output:

[INFO] cbm (../src/bootman/bootman.c:L482): Current running kernel: 4.20.16-112.current
[INFO] cbm (../src/bootman/sysconfig.c:L98): Discovered UEFI ESP: /dev/disk/by-partuuid/64b48b2e-fbc5-4f36-8c92-eb13e60cd281
[INFO] cbm (../src/bootman/sysconfig.c:L123): Fully resolved boot device: /dev/nvme0n1p1
[DEBUG] cbm (../src/lib/probe.c:L261): Root device exists on device-mapper configuration
[DEBUG] cbm (../src/bootman/bootman.c:L130): UEFI boot now selected (systemd)
[INFO] cbm (../src/bootman/bootman.c:L502): path ///usr/lib/initrd.d does not exist
[INFO] cbm (../src/bootman/update.c:L116): Checking for mounted boot dir
[INFO] cbm (../src/bootman/update.c:L119): boot_dir is already mounted: /boot
[DEBUG] cbm (../src/bootman/update.c:L291): Now beginning update_native
[DEBUG] cbm (../src/bootman/update.c:L300): update_native: 2 available kernels
[DEBUG] cbm (../src/bootman/update.c:L320): update_native: Running kernel is (current) ///usr/lib/kernel/com.solus-project.current.4.20.16-112
[SUCCESS] cbm (../src/bootman/update.c:L335): update_native: Bootloader updated
[SUCCESS] cbm (../src/bootman/update.c:L349): update_native: Repaired running kernel ///usr/lib/kernel/com.solus-project.current.4.20.16-112
[DEBUG] cbm (../src/bootman/update.c:L358): update_native: Checking kernels for type current
[INFO] cbm (../src/bootman/update.c:L373): update_native: Default kernel for type current is ///usr/lib/kernel/com.solus-project.current.5.0.5-113
Bus error
DataDrake triaged this task as Needs More Info priority.Apr 30 2019, 1:22 PM
DataDrake edited projects, added Hardware; removed Lacks Project.
DataDrake added a subscriber: DataDrake.

Can you check for me that your boot partition is not out of space?

cigh033 added a comment.EditedMay 2 2019, 5:45 PM

Hi, Bryan thank you for looking into this.
├── [ 4096] EFI
│   ├── [ 4096] Boot
│   │   └── [ 87642] BOOTX64.EFI
│   ├── [ 4096] com.solus-project
│   │   ├── [ 27453855] initrd-com.solus-project.current.4.20.16-112
│   │   ├── [ 27455992] initrd-com.solus-project.current.5.0.5-113
│   │   ├── [ 25279846] initrd-com.solus-project.lts.4.9.166-128
│   │   ├── [ 10355872] kernel-com.solus-project.current.4.20.16-112
│   │   ├── [ 10433696] kernel-com.solus-project.current.5.0.5-113
│   │   └── [ 7914592] kernel-com.solus-project.lts.4.9.166-128
│   └── [ 4096] systemd
│   └── [ 87642] systemd-bootx64.efi
└── [ 4096] loader
├── [ 4096] entries
│   ├── [ 464] Solus-current-4.20.16-112.conf
│   ├── [ 460] Solus-current-5.0.5-113.conf
│   └── [ 374] Solus-lts-4.9.166-128.conf
└── [ 32] loader.conf

6 directories, 12 files

df -h shows:

/dev/nvme0n1p1 488M 105M 384M 22% /mnt

I have done nothing with my laptop after the opening of the task. Now LTS is the only kernel that boots.

If you need any more info, feel free to ask

thanks

cigh033 raised the priority of this task from Needs More Info to Normal.May 2 2019, 6:34 PM
JoshStrobl lowered the priority of this task from Normal to Needs More Info.May 2 2019, 6:40 PM
ZVNexus added a subscriber: ZVNexus.May 3 2019, 5:07 PM

Have you tried just recreating your EFI partition with a live session?

https://getsol.us/articles/troubleshooting/boot-rescue/en/

Hi @ZVNexus, I did as advised in the tutorial (+ decrypting my drive before mounting of course).

sudo clr-boot-manager update

gives me another bus error.

with CBM_DEBUG=1 it shows this:

root@solus / # sudo CBM_DEBUG=1 clr-boot-manager update
[INFO] cbm (../src/bootman/bootman.c:L482): Current running kernel: 4.20.16-112.current
[DEBUG] cbm (../src/lib/probe.c:L261): Root device exists on device-mapper configuration
[DEBUG] cbm (../src/bootman/bootman.c:L130): UEFI boot now selected (systemd)
[INFO] cbm (../src/bootman/bootman.c:L502): path /usr/lib/initrd.d does not exist
[INFO] cbm (../src/bootman/update.c:L116): Checking for mounted boot dir
[INFO] cbm (../src/bootman/update.c:L119): boot_dir is already mounted: /boot
[DEBUG] cbm (../src/bootman/update.c:L291): Now beginning update_native
[DEBUG] cbm (../src/bootman/update.c:L300): update_native: 2 available kernels
[DEBUG] cbm (../src/bootman/update.c:L320): update_native: Running kernel is (current)
/usr/lib/kernel/com.solus-project.current.4.20.16-112
[SUCCESS] cbm (../src/bootman/update.c:L335): update_native: Bootloader updated
[SUCCESS] cbm (../src/bootman/update.c:L349): update_native: Repaired running kernel /usr/lib/kernel/com.solus-project.current.4.20.16-112
[DEBUG] cbm (../src/bootman/update.c:L358): update_native: Checking kernels for type current
[INFO] cbm (../src/bootman/update.c:L373): update_native: Default kernel for type current is
/usr/lib/kernel/com.solus-project.current.5.0.5-113
Bus error

It's just your root partition that is encrypted, correct? Not the entire drive itself? I generally don't do anything in regards to encryption so I don't know.

Did you format the EFI partition before following that guide? I found that trying to save the currently existing EFI partition generally is always trouble, unless you have any other non Solus related entries in there (it doesn't appear so) it's probably safe to format the EFI partition to whatever filesystem it's currently using (should be FAT16), then follow that guide to create a new EFI partition for Solus.

I'm kinda lost with your Suggestion, i mean, if the Boot Manager wont Update after formatting, i lost my Installation iirc. Only the root should be crypted as i followed the normal solus install Routine.

Gnome Disks --> Format the EFI partition.

Then follow this.
https://getsol.us/articles/troubleshooting/boot-rescue/en/

Instead of updating the boot manager, it will create it for said disk to the available EFI partition.

Correct me if I'm wrong, but if

sudo clr-boot-manager update

gives me another bus error after formatting my EFI partition, i won't be able to boot, or am I missing something?

ZVNexus added a comment.EditedMay 6 2019, 11:42 AM

That's strange. In Linux generally a bus error is a fault raised by the hardware. It's trying to access memory that the CPU cannot address. Weird. Honestly, best bet is instead of wasting time trying to fix your install is just backing up all data and reinstalling Solus. You are most likely going to spend way more time trying to fix your install than just reinstalling.

Also, unless you carry around your computer and travel with it I wouldn't bother encrypting.

I'm sorry if it was not clear until now: This happens to me after every new installation. I tried it twice now. Once with 4.0 Fortitude and another time with 3.9999 (first time boot: OK; after sudo eopkg up: not working)

Not encrypting is not an option to me, as I travel a lot with it.

And any other distro works fine?

never checked. My guess is that the problem is somewhere in CLR-Boot-Manager in connection with the Acer EFI Firmware. AFAIK clr-boot-manager is not used in any other distro.
If someone from the core team needs me to test it with another distro, I will, but right now I don't think that it would be helping. But still I appreciate your efforts Alex.

Also, generally never buy from Acer again (if you have a choice). ASUS, Dell, and Lenovo all make much better laptops :D

Could we look into this soon(ish)? Unfortunatly I am not able to upgrade my kernel right now.

cigh033 updated the task description. (Show Details)Jun 25 2019, 11:16 AM