This is still happening, and it feels like a race. I've enabled debug logging and captured the journal from good and bad boots. Comparing them hasn't told me a whole lot; on the whole the udev debug logging isn't very applicable. I do see that in both cases udev starts up and reads the exact same set of rule files, and the statistics it prints about the rule files are identical. Both have read in /lib/udev/rules.d/99-systemd.rules which contains the rule for adding the systemd tag. Nothing else has really stood out yet, but they are pretty difficult to compare.
I also find that if I run 'udevadm trigger -c add /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sda' from recovery mode that udev does add the systemd tag at that point. I'll attach my logs and udev databases from the good and bad boots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625217 Title: udev sometimes doesn't apply systemd tag to devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
