On Sun, 28 Aug 2022 18:34:56 -0700
stan via test <test(a)lists.fedoraproject.org> wrote:
Booted an older Fedora, and it had no problems mounting all the
drives
and swap. So, not the drives.
Booted F37 with older kernels that worked just fine before these
updates, now have the mount problem. So, the update changed something
in the boot process. It wasn't mount that changed, because that
wasn't updated (the util-linux-core package hasn't changed since Aug
5). I look at that list of packages, and I don't see anything in
there that should affect boot. systemd is the same, and that is what
handles the mounting of swap and drives. The same systemd worked
fine before a reboot after the updates, and still boots the system,
just doesn't mount anything but the root partition.
It looks like dracut is failing the pre-trigger, pre-mount, and mount
activities during boot. I checked, and none of the dracut files have
been modified.
~ 06:05 AM root 6
# systemctl status dracut-pre-udev.service
○ dracut-pre-udev.service - dracut pre-udev hook
Loaded: loaded (/usr/lib/systemd/system/dracut-pre-udev.service; static)
Active: inactive (dead) since Mon 2022-08-29 05:36:36 MST; 28min ago
Duration: 1.971s
Docs: man:dracut-pre-udev.service(8)
man:dracut.bootup(7)
Main PID: 303 (code=exited, status=0/SUCCESS)
CPU: 17ms
Aug 29 05:36:36 fedora systemd[1]: dracut-pre-udev.service: Deactivated successfully.
Aug 29 05:36:36 fedora systemd[1]: Stopped dracut-pre-udev.service - dracut pre-udev
hook.
~ 06:05 AM root 6
# systemctl status dracut-pre-trigger.service
○ dracut-pre-trigger.service - dracut pre-trigger hook
Loaded: loaded (/usr/lib/systemd/system/dracut-pre-trigger.service; static)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-08-29 05:36:35 MST; 28min ago
Docs: man:dracut-pre-trigger.service(8)
man:dracut.bootup(7)
Aug 29 05:36:35 fedora systemd[1]: dracut-pre-trigger.service - dracut pre-trigger hook
was skipped because all trigger condition checks failed.
~ 06:05 AM root 6
# systemctl status dracut-pre-mount.service
○ dracut-pre-mount.service - dracut pre-mount hook
Loaded: loaded (/usr/lib/systemd/system/dracut-pre-mount.service; static)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-08-29 05:36:35 MST; 28min ago
Docs: man:dracut-pre-mount.service(8)
man:dracut.bootup(7)
Aug 29 05:36:35 fedora systemd[1]: dracut-pre-mount.service - dracut pre-mount hook was
skipped because all trigger condition checks failed.
~ 06:05 AM root 6
# systemctl status dracut-mount.service
○ dracut-mount.service - dracut mount hook
Loaded: loaded (/usr/lib/systemd/system/dracut-mount.service; static)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-08-29 05:36:36 MST; 29min ago
Docs: man:dracut-mount.service(8)
man:dracut.bootup(7)
Aug 29 05:36:36 fedora systemd[1]: dracut-mount.service - dracut mount hook was skipped
because all trigger condition checks failed.
I checked in /etc for configuration files that were changed before this
happened, and got the following list. I truncated the gconf list, it
doesn't seem it would be relevant to the problem.
# find /etc -mtime 2 -print
/etc/sysconfig/network-scripts/readme-ifcfg-rh.txt
/etc/rwtab.d
/etc/rwtab.d/sssd
/etc/logrotate.d
/etc/logrotate.d/sssd
/etc/pam.d/sssd-shadowutils
/etc/pam.d/kde
/etc/krb5.conf.d/enable_sssd_conf_dir
/etc/krb5.conf.d/sssd_enable_idp
/etc/krb5.conf.d/kcm_default_ccache
/etc/rhsm/ca
/etc/xdg/startkderc
/etc/xdg/autostart/org.kde.plasmashell.desktop
/etc/xdg/qtchooser
/etc/samba
/etc/dbus-1/system.d/org.freedesktop.sssd.infopipe.conf
/etc/cifs-utils
/etc/highlight
/etc/X11/xinit/xinitrc.d
/etc/NetworkManager
/etc/NetworkManager/dispatcher.d
/etc/NetworkManager/dispatcher.d/pre-down.d
/etc/NetworkManager/dispatcher.d/no-wait.d
/etc/NetworkManager/dispatcher.d/pre-up.d
/etc/NetworkManager/dnsmasq-shared.d
/etc/NetworkManager/conf.d
/etc/NetworkManager/dnsmasq.d
/etc/NetworkManager/NetworkManager.conf
/etc/NetworkManager/system-connections
/etc/sssd
/etc/sssd/conf.d
/etc/sssd/pki
/etc/gconf/schemas
/etc/gconf/gconf.xml.defaults
/etc/gconf/gconf.xml.defaults/%gconf-tree-id.xml
/etc/gconf/gconf.xml.defaults/%gconf-tree-ca(a)valencia.xml
/etc/gconf/gconf.xml.defaults/%gconf-tree-da.xml
/etc/gconf/gconf.xml.defaults/%gconf-tree-kn.xml
/etc/gconf/gconf.xml.defaults/%gconf-tree-ko.xml
/etc/gconf/gconf.xml.defaults/%gconf-tree-en_GB.xml
...
I don't see a smoking gun in any of this. Why would the dracut checks
start failing if there wasn't some kind of configuration change? Or
are they just a red herring, and the actual problem is somewhere else?