You are not logged in.
After installing BL-Deuterium on a new machine, there is this message "No bootable devices found" at reboot.
I have 2 disks on my machine (SSD and HDD). OS was installed using 'guided partitioning' using entire SSD drive (booting UEFI partition was created automatically).
UEFI is 'on' and Secure boot 'off'
Am I doing something wrong?
NOTE: I was not asked to install a GRUB loader.
Thanks in advance.
Last edited by cyrf0006 (2018-04-04 18:32:56)
Offline
I was not asked to install a GRUB loader.
Well that's not a good sign
You can use this guide to attempt to restore GRUB from our "live" environment:
https://wiki.debian.org/GrubEFIReinstall
^ This presumes that you have installed a UEFI system, please post back if this is not the case.
Errors of this sort are usually unetbootin's fault due to an incorrect transfer of the ISO image to the installation medium — how did you do that?
Offline
I did not use unetbootin, but rather followed this. I tried with two different USB sticks.
I may try to install the grub from the live environment, but I'd rather solve the problem by reinstalling from scratch. Note that I was not explicitly prompted to install GRUB, but during the installation process it looks like it was installed.
I wonder if the problem is not related to the previous filesystem (as if "Guided Partioning - Use entire disk" was leaving stuff behind). I say that because when I switch to the booting menu, it still offers me the possibility of booting Ubuntu (previous OS when I bought the computer), although I cannot actually boot it.
Offline
Note that I was not explicitly prompted to install GRUB, but during the installation process it looks like it was installed.
That's right, I remember now — a UEFI system installs GRUB without prompting because multi-booting should be a trivial affair compared to non-UEFI systems.
Unfortunately, the average quality of most UEFI firmware implementations is very poor and you may have a bad one (join the club), try this hack:
https://wiki.debian.org/GrubEFIReinstal … bootloader
If your firmware is particularly badly behaved we may have to spoof BunsenLabs' UEFI bootloader and disguise it as a Windows bootloader
EDIT: you can clear those old Ubuntu NVRAM entries with the `efibootmgr` command, if you want (or use the UEFI firmware menu, that may be more reliable).
Last edited by Head_on_a_Stick (2018-04-04 18:00:25)
Offline
I confirm that the hack suggested works, wow!
I am not sure I fully understand what it does. Should I be worry that the problem rise again in the future (for example after an upgrade)?
Thanks for this quick feedback!
Offline
I confirm that the hack suggested works
Nice, thanks for the feedback
I am not sure I fully understand what it does. Should I be worry that the problem rise again in the future (for example after an upgrade)?
Your motherboard is defective and so will only boot the so-called "removable" .efi loader (as used by "live" USB sticks and suchlike) so the hack just copies GRUB's .efi loader to $ESP/EFI/BOOT/BOOTX64.EFI
This should survive upgrades, I've been using the method in my UEFI laptop for several years now :cry:
Offline