Fedora not detectable on boot options, but bootable through bootnext xxxx from live media

Ask Fedora
, , ,
1

The only boot option that I can choose normally is windows, I tried several installs and found myself on efibootmgr trying to fix and suprisingly I was able to boot into fedora which I think works as installed, I updated and restarted but ended up again with windows as the only option to choose.

General specs of my laptop:
2016 Acer aspire
500gb HDD (windows is installed)
256 gb SSD (trying to configure and install Fedora in this drive)
64bit

what instructions can I follow or some specifics to be able to fix boot?

2

Added boot, dual-boot, grub, windows

3

Please post the output of these commands once you have logged into Fedora.

efibootmgr
lsblk -f

I’m wondering if the fedora boot files are missing from the EFI partition on the
500GB drive.

2 Likes
5

This is the output that it showed

Screenshot_20241113_0041111
Screenshot_20241113_00411111355Ă—549 103 KB

7

changing the boot order gave no effect, I have done it twice with no luck, still the same result

9

Please post terminal output as preformatted text (using the </> button form the top line of the text entry panel). Many lines in the output from efibootmgr have <space>RC at the end, but the <space> is missing from the Boot0000* line. I’ve never seen the <space>RC on my systems, but it is a known thing efibootmgr issues #34 has examples and some explanation in comments:

if the firmware doesn’t find any boot entry that works, it runs \EFI\BOOT\BOOTX64.EFI. In this setup, shim checks if fallback.efi is in the same directory as it, and if so it runs that. fallback.efi subsequently iterates \EFI*\ (filtering out the directories “BOOT”, “.”, and “…”) searching for BOOT.CSV, and recreates a boot entry with the data in that file using the bootloader binary in the same directory as the file.

I’m guessing that RC is shorthand for “re-created”, but it should not be appended without a <space>, so should be reported as an efibootmgr issue.

1 Like
10 
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0001,0002,2001,2002,2003
Boot0000* Unknown Device:       HD(2,GPT,c0474f21-51f2-47dc-8b65-89eb81c6d09d,0x6000800,0xfa000)/\EFI\fedora\shim.efiRC
Boot0001* Windows Boot Manager  HD(1,GPT,7b1f1ac1-6b56-4aff-92f6-fc68eae5f5ae,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0002* Linux HD(1,GPT,83d54590-dcae-43cf-bd85-e3181b9429d6,0x800,0x1d355b0)/\EFI\Boot\grubx64.efiRC
Boot0003* Fedora        HD(2,GPT,c0474f21-51f2-47dc-8b65-89eb81c6d09d,0x6000800,0xfa000)/\EFI\fedora\shimx64.efi
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC
11

Thanks. Searching the text for efiRC shows 2 bad entries in your efibootmgr output.

12

So what should I do about it?

13

Create an issue at efibootmgr/issues to get the attention of the responsible developers.

14

As to minimize dragged communication and problems, what are the things I should address to them?

15

It is more likely it is some noise created by early version of efibootmgr or the fallback boot entry.

If you run efibootmr -v you can see the line starting with “data:” which show the hexidecimal encoding of “RC”. For the Microsoft entries you will get extra arguments used by the Microsoft boot loader instead.

If you remove the Fedora boot loader entry and create a new entry, you should not see the extra “RC”. At least, I don’t.

16

I installed a different linux distro other than fedora, uninstalled Windows and replaced with mint and suprisingly it also did not boot showing no boot, so I think in conclusion it might be a very specific issue I have on this old laptop, I’ll try using legacy instead

17

You see how other linux users fared with linux on your model using the LHDB. Sometimes users will add comments that provide details needed to install linux on a particular model.

A system from 2016 may have some non-obvious hardware issues such as a power supply that no longer keeps voltages within “spec”. I usually don’t invest much effort trying to sort out problems systems that are more than 7 years old – newer systems offer better reliability and vendor support. Currently with large enterprises downsizing and many “enterprise” grade systems that don’t officially support Windows 7 being dumped, you can find enterprise grade “refurbished” systems at very nice prices.

18

hi i have similar issues. can you show the solution you done on removing the bootloader and create the new entry. Didn’t really get a nice way on how to remove it from my acer aspire laptop

19

It can done using a terminal. See man efibootmgr and How to use efibootmgr – Examples.

20

thanks. will try and see is it solve my problem