On Sat, 2021-06-12 at 18:54 +0100, Patrick O'Callaghan wrote: > On Sat, 2021-06-12 at 11:31 -0400, Frank McCormick wrote: > > I found and fixed the problem. The key was in my systemd log. > > > > 1.825245] udevadm[363]: systemd-udev-settle.service is deprecated. > > Please fix nm-initrd.service not to pull it in > > > > > > Personally I think this should be spread more...it seems there are > > quite > > a few with this problem > > Not my case. I don't have systemd-udev-settle.service. This is a fresh > install of F34. I spoke too soon. A grep on the journal log (posted earlier) shows: $ grep settle journal.log [ 1.763070] udevadm[412]: systemd-udev-settle.service is deprecated. Please fix nm-initrd.service not to pull it in. [ 32.655548] systemd[1]: systemd-udev-settle.service: Deactivated successfully. [ 34.383171] udevadm[626]: systemd-udev-settle.service is deprecated. Please fix multipathd.service not to pull it in. I have no idea what this means. What does NM have to do with anything and how do I "fix" it? I also don't have an /etc/multipath.conf file. Could that be the problem? poc _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
