I'm not quite sure this is discoverable enough. I kind of wonder if kernel could say if it is booting with or without initrd; before it panics about unable to find rootfs or `/sbin/init`.
And I wonder if our grub-common.service should actually log something to console & journal. I.e. the fact that GRUB_FORCE_UUID was set, and yet booting without initrd failed. And maybe like unset GRUB_FORCE_UUID? or add something in grubenv to not attempt initrdless boot the next time? Ideally i'd like to warn about failure to boot initrdless; and maybe not attempt it again, unless manually cleared? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901553 Title: Improve documentation around initrdless boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1901553/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
