bottom-posting, somewhat manually. On Sun, Aug 18, 2024 at 1:43 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote: > > 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. Thanks, applied. I did think, though, that was the default? -- _______________________________________________ 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
