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. 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. I've since reinstalled Fedora 40 so now my system is stable and working fine. 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. 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. Thanks, User of Fedoras -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
