On Sun, Aug 18, 2024 at 9:33 AM User of Fedoras via users < users@lists.fedoraproject.org> wrote:
Hi, I had changed from Fedora to openSUSE due to an error on LUKS during boot (it would not see the correct devices, dracut would timeout). I could boot using an older kernel but couldn't figure out what the issue was/hadn't had the patience.
Which Fedora version?
Yesterday it happened on openSUSE and, in that case, no kernel would boot. So, again, I returned to Fedora. Do note the same thing had happened on another computer. This was approximately 1 month ago.
No-one else seems to have had this issue.
Fedora often leads other distros, so it is not unusual to encounter an issue in Fedora that is not present in other distros, then the same issue appears when the other distro catches up to the (now old) Fedora version that had the problem.
I've since reinstalled Fedora 40 so now my system is stable and working
fine.
There were issues with 6.10 kernels that have now been solved, so you chose a moment when Fedora was relatively stable.
Still, it puzzles me, so, does anyone have any hint of what may have gone wrong? Spurious internet searches suggested: buggy `blkid` update resulting in buggy `blkid` output which induced `grub-mkconfig` to output boot options missing the necessary UUID necessary for unlocking the correct partitions. But those results were from about a few months ago.
You need to find actual kernel versions and links to the change details. There were (and continue to be) instances of users following incorrect guidance found on the internet to run "grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg.".
If you have backups from the old Fedora version with the journalctl data there might be some hope of understanding the problem. A problem with distro shopping to solve problems is that you lose the opportunity to investigate and possibly contribute to a solution (often by testing a pre-release package).
Just FYI, my current, working, install was like this: I installed Fedora 39, upgraded to latest packages excluding=blkid, dracut, kernel, kernel-core-modules, kernel-core-extras, upgraded to all latest on 39, upgraded to Fedora 40 and the bug didn't happen again.
I assume that means the initial Fedora 39 installation worked and continued to work when upgraded. Fedora 39 gets most fixes until 41 has been released.