On Thu, 2022-01-06 at 09:23 +0100, Tomasz Torcz wrote:
On Wed, Jan 05, 2022 at 05:36:56PM -0800, Adam Williamson wrote:
So, my question is...do other Rawhide users have this problem, or is my system an outlier for some reason? I have not been able to figure out *what* created the problematic directories on my system. An earlier systemd rc may have created /boot/efi/(machine_id) if /boot/efi/loader/entries existed, but I don't know what might have created /boot/efi/loader/entries . I'm pretty sure I didn't do it myself, though.
My rawhide system seem to have both and boot even other kernel:
tree /boot/efi /boot/efi ├── 6a1b72cbb94d4c95a4ac9df2d581e371 │ ├── 0-rescue │ │ ├── initrd │ │ └── linux │ ├── 4.16.0-0.rc5.git2.1.fc29.x86_64 │ ├── 4.16.0-0.rc6.git2.1.fc29.x86_64 │ ├── 4.16.0-0.rc7.git1.1.fc29.x86_64 │ └── 5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64 │ ├── initrd │ └── linux ├── EFI │ ├── BOOT │ │ ├── BOOTX64.EFI │ │ └── fbx64.efi │ └── fedora │ ├── BOOTX64.CSV │ ├── grub.cfg │ ├── grub.cfg.rpmsave │ ├── grubenv.rpmsave │ ├── grubx64.efi │ ├── mmx64.efi │ ├── shim.efi │ └── shimx64.efi └── loader └── entries └── 6a1b72cbb94d4c95a4ac9df2d581e371-5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64.conf
# uname -r 5.16.0-0.rc4.20211207gitcd8c917a56f2.30.fc36.x86_64
Ah, yeah, so you can see, you've run into the bug - kernel 5.16.0- 0.rc5.20211216git2b14864acbaa.37.fc36 has been installed into /boot/efi and your system has booted to the older rc4 kernel. Unless my systemd patch gets merged, kernels won't install properly for you unless you wipe out /boot/efi/6a1b72cbb94d4c95a4ac9df2d581e371 and /boot/efi/loader . (After doing that you can run:
/bin/kernel-install add 5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64 /lib/modules/5.16.0-0.rc5.20211216git2b14864acbaa.37.fc36.x86_64/vmlinuz
to reinstall the rc5 kernel correctly, or just update to a newer one).
It's interesting that you have those very old fc29 folders in your /boot/efi/(machineid); now I think about it, my folder might have had very old entries like that in it too, but I stupidly wiped it without keeping a note. So perhaps there was a bug some time ago that led to these directories being created. I initially deployed this system as F25, it looks like.