Once upon a time, Chris Murphy <[email protected]> said: > On Fri, Oct 10, 2025, at 2:02 PM, Chris Adams wrote: > > Yep, I got bit by this once when I did updates and then something (don't > > know what) happened that caused the grub2.cfg update (pre BLS) to still > > be in the XFS log. The system would just boot to a grub prompt... I was > > on a trip and sitting in a hotel room (so no access to another system, a > > rescue USB drive, etc.), and basically hadn't had to mess much with boot > > loaders in a long time, so didn't really remember any GRUB2 commands. I > > eventually puzzled out enough to get the system booted, but it was a bit > > of a pain. > > Unintuitively, booting with rd.break=pre-mount and then merely mounting the > xfs boot volume and then rebooting would have fixed it. Log replay would have > happened on mount, making the grub.cfg appear in the metadata that GRUB can > read.
That requires remembering how to boot from the GRUB2 command-line, what the necessary kernel arguments were, etc. Once I got past that, I could boot normally, I didn't need to do anything extra. -- Chris Adams <[email protected]> -- _______________________________________________ devel 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
