I would check these modules in dracut: dracut --list-modules, some of
them are rescue and debug and a few other modules may help.
The tools may allow you to get a prompt inside the boot when it fails
and/or give you some tools to do some debugging.
On Tue, Jun 4, 2019 at 1:09 PM stan via users
<users(a)lists.fedoraproject.org> wrote:
>
> On Tue, 4 Jun 2019 12:37:04 -0500
> Roger Heflin <rogerheflin(a)gmail.com> wrote:
>
> > Did you check the kernel command line in grub.cfg to see what root= is
> > set to? That is the only place I know specifically references what
> > to look for on the switch root.
>
> Yep, converted all the old UUIDs for boot and root to the new UUIDs in
> grub.cfg, including that one.
>
> I tried having systemd print out to the terminal any error messages by
> changing the configuration in /etc/systemd/system.conf. But it didn't
> add anything, only saying that there were 27 printk messages not shown
> because of ratelimiting. Not sure what that is, but they might shed
> some light on the situation.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org