I don't know specifically on this bug. But the 2 common mistakes fall into some piece failing and causing dracut to not properly detect what modules the boot device needs to use. And when that happens dracut times out looking for root. I have also seen bugs where the necessary module needed to boot is broken.
Best fix for the first one is to change dracut to use host-only = no (include all possible modules that may be needed to boot and don't rely on detection). There may be some other options in dracut to force tne needed pieces that you know your setup needs. This should eliminate the need to rely on the detection code to figure out what modules are needed. The disadvantage is that the initramfs will be 2-4x larger and that may impact the number of kernels you can have on boot. On Sun, Aug 18, 2024 at 7:33 AM User of Fedoras via users <[email protected]> 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. > 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 -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
