I occasionally see a problem where systemd-analyze reports that boot did not complete and it is suggested that I use systemctl list-jobs to find out more. That shows a .device service job and some sub-jobs (associated with udev rules) all waiting. They will wait for literal days in this state. When I accessed the system, it wasn’t apparent what the jobs were waiting on since all of the device symlinks and such were there and working. The systemctl status of the .device service was alive.
Any suggestions on what is going on and/or how to figure out what is going on? If you have followed my posts here previously, it should come as no surprise that the device that I observed this happen with was one of the emmc boot devices. alan _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
