No boot disk found after reboot

Aurora
1

I’m installing Aurora for the fist time on a Aspire E 15. I’m using the AMD/Intel image.
I decided to install on /dev/sdb (after installing on /dev/sda gave the same problem), giving the whole disk to the install process.
Everything goes fine, but at reboot, it appears the disk was not make bootable.

Here’s the partition of the disk:

❯ fdisk /dev/sdb -l
Disk /dev/sdb: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: KINGSTON RBUSNS8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 413BFFB9-4738-417C-AF2D-CE749643A758

Device       Start       End   Sectors   Size Type
/dev/sdb1     2048   1230847   1228800   600M EFI System
/dev/sdb2  1230848   5425151   4194304     2G Linux extended boot
/dev/sdb3  5425152 250068991 244643840 116.7G Linux filesystem

I’m running the live Aurora from USB, and am not sure what I can do now. I’ve tried unsuccessfully to run the grub2-install command (I can’t seem to find the /usr/lib/grub/x86_64-efi/modinfo.sh file).

Any suggestion on how to proceed from this situation?

2

Which “live ISO” did you use?

So what are the specs on that machine? Also is that on SSD?

Also make sure your BIOS is set to UEFI mode.

3

I used the ISO aurora-stable-webui-x86_64.iso and did the install to hard drive.

It has a hdd on sda and SSD on sdb. I tried installation on each of them with the same result.
I have disabled secureboot and use uefi mode.
I have tried to boot the installation on disk with https://www.system-rescue.org/ , but it complains it doesn’t find /sbin/init on the disk (though looking at the sysroot just after install there is one, so there’s some setup that needs to be done to boot the system so /sbin/init can be found).

I encrypt the data partition (in my case it is the third partition on disk, the first one being the efi partition and the second the boot partition).

After another fresh install, I tried installing grub manually before the reboot, after a chroot /var/mnt/sysroot (grub2-install /dev/sda), but it complains it doesn’t find modinfo.sh for x86-64 at /usr/lib/grub/x86_64-efi/modinfo.sh. There is only /usr/lib/grub/i386-pc.

The next step will probably be to try to install a fesora distribution to see if it passes….
Waiting a bit to see if a solution gets suggested here before I try that :crossed_fingers:

4

I had never used btrfs before, and discovered its subvolumes.
Following this info: How to chroot a system that uses btrfs subvolumes? - #2 by chrismurphy - Fedora Discussion
I booted on Fedora netinst, and mounted all subvolume I have found.
However, I cannot chroot to the aurora sysimage because /bin/bash is not present. And on the fedora system I booted in rescue mode, I don’t have the needed modinfo.
According to this: ubuntu - grub2-install Error: modinfo.sh Missing - Common solutions attempted - Unix & Linux Stack Exchange
I might have to install a package, but dnf has no repo enabled…. I’m discovering the system step by step, so now I have to find how to add a repo to dnf….
If there’s a better way, suggestions welcome :wink:

5

No idea what is happening honestly. Firstly make sure your BIOS is set to UEFI only, that is kind of hard requirement. If it doesn’t support UEFI, then I am not sure if these ISOs will even work.

You can try installing Kinoite and if that is successfull, then rebase to Aurora.

6

EDIT: this post was updated several times to fix and improve instructions.

So, this seems to be a usual behaviour of Acer laptops. I didn’t find a solution online but a LLM gave me the solution (so it has to be out there somewhere, I probably didn’t search at the right place), and I’ll quote parts of the answer I got.

First, I encountered this with multiple distros, so it is not linked to Aurora. From the llm:

This is a very common issue with Acer Aspire laptops, particularly the E15 series.
 The problem is rarely the Linux installation itself, but rather Acer’s aggressive UEFI
 implementation which refuses to boot a new EFI entry unless it is explicitly “trusted”
 in the BIOS, or placed in a specific “fallback” location.

When still running the live system, before the reboot at the end of the install, chroot to the installed system (in /mnt/sysroot).

  • In the chroot, issue these commands:
    mount /dev/sda1 /boot/efi
cp /usr/lib/bootupd/updates/EFI/fedora/grubx64.efi /boot/efi/EFI/BOOT/grubx64.efi
  • reboot

This can be sufficient.

If at the reboot your system is not available (eg in the F12 boot disks list), you need to take additional steps.

After you reboot, if it **still** says “No Bootable Device”, you must add the file to the BIOS “Trust” list. Acer firmware is very picky.

1. **Reboot** and press **F2** to enter BIOS.

2. Go to **Security** → Set a **Supervisor Password** (required to change these settings).

3. **Enable Secure Boot** (temporarily, just to access the menu).

4. Select **“Select an UEFI file as trusted for executing”**.

5. Navigate to `HDD0` → `EFI` → `fedora` → `shimx64.efi` (or `grubx64.efi` if shim isn’t there).

   * *Note:* You can also try trusting `EFI` → `BOOT` → `BOOTX64.EFI` if the fedora one doesn’t appear.

6. Name it “Aurora”.

7. Go to **Boot** tab and move “Aurora” to the top.

8. (Optional) Disable Secure Boot and remove the Supervisor Password.

9. **F10** to Save and Exit

I think in an earlier attempt I made a mistake in the first step, and so I validated these steps work too.
Doing this I could choose to boot Aurora by pressing F12 at boot.

The procedure on a debian system was easier: debian’s grub-install has the additional flag –force-extra-removable, which apparently does all that’s needed. Here’s the command in the chroot of the installed system, before rebooting:


grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=debian --force-extra-removable

I hope this can help other in the future.

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.