Fedora boot entry not present in its own grub bootloader

Ask Fedora
,
41

thx, but I can only provides answer tomorrow ( I’m at UTC 8).

Guess we are close to the issue, and I should still be safe to reinstall grub or even the system,

1 Like
42 
        Machine ID: 98f74e40ccfa41ccbfff534304b034ee
 Kernel Image Type: pe
            Layout: bls
         Boot Root: /boot/efi
  Entry Token Type: machine-id
       Entry Token: 98f74e40ccfa41ccbfff534304b034ee
   Entry Directory: /boot/efi/98f74e40ccfa41ccbfff534304b034ee/6.15.10-200.fc42.x86_64
    Kernel Version: 6.15.10-200.fc42.x86_64
            Kernel: /usr/lib/modules/6.15.10-200.fc42.x86_64/vmlinuz
           Initrds: (unset)
  Initrd Generator: (unset)
     UKI Generator: (unset)
           Plugins: /usr/lib/kernel/install.d/10-devicetree.install
                    /usr/lib/kernel/install.d/20-grub.install
                    /usr/lib/kernel/install.d/50-depmod.install
                    /usr/lib/kernel/install.d/50-dracut.install
                    /usr/lib/kernel/install.d/51-dracut-rescue.install
                    /usr/lib/kernel/install.d/60-kdump.install
                    /usr/lib/kernel/install.d/90-loaderentry.install
                    /usr/lib/kernel/install.d/90-uki-copy.install
                    /usr/lib/kernel/install.d/92-crashkernel.install
                    /usr/lib/kernel/install.d/92-tuned.install
                    /usr/lib/kernel/install.d/95-akmodsposttrans.install
                    /usr/lib/kernel/install.d/95-kernel-hooks.install
                    /usr/lib/kernel/install.d/99-grub-mkconfig.install
Plugin Environment: LC_COLLATE=C.UTF-8
                    KERNEL_INSTALL_VERBOSE=0
                    KERNEL_INSTALL_IMAGE_TYPE=pe
                    KERNEL_INSTALL_MACHINE_ID=98f74e40ccfa41ccbfff534304b034ee
                    KERNEL_INSTALL_ENTRY_TOKEN=98f74e40ccfa41ccbfff534304b034ee
                    KERNEL_INSTALL_BOOT_ROOT=/boot/efi
                    KERNEL_INSTALL_LAYOUT=bls
                    KERNEL_INSTALL_INITRD_GENERATOR=
                    KERNEL_INSTALL_UKI_GENERATOR=
                    KERNEL_INSTALL_STAGING_AREA=/tmp/kernel-install.staging.XXXXXX
  Plugin Arguments: add|remove
                    6.15.10-200.fc42.x86_64
                    /boot/efi/98f74e40ccfa41ccbfff534304b034ee/6.15.10-200.fc42.x86_64
                    /usr/lib/modules/6.15.10-200.fc42.x86_64/vmlinuz
                    [INITRD...]
~
lines 1-40/40 (END)

didn’t aware this guid style machine id the layout, was it the installation program made it ?

43

It looks like you may be using systemd boot which would require that Entry Directory.

If you are using grub instead then that /boot/efi/98f74e40ccfa41ccbfff534304b034ee directory seems it may be the problem.
There may be others with better advice, but as I understand it removing that directory then running kernel-install add-all should recover the entries into /boot and then boot properly.

1 Like
44

I’m not sure whether the installer creates it or whether systemd creates it on first boot.

1 Like
45

tried, rm folder & kernel-install add-all and it somehow creates the exact same folder , and didn’t affects os-prober output, maybe try reinstall grub could help, but seems i can still (weirdly) work, ( choose boot via motherboard uefi / rEFInd, instead of grub ), may leave it here and play what’s inside, many thanks for the warm support from community : )

46

yea, could be ( telling by the naming convention ), i only know systemd had a fight on the init / process & service control, but didn’t know it can inject boot and took the job from grub, so now my boot worked in a unconventional way, hh, thx for your warm assist as well : )