启动期间系统登录到日志中
[ 4.604302] x-com (udev-worker)[359]: sda: /usr/lib/udev/rules.d/73-seat-late.rules:13 Failed to import properties 'ID_SEAT' from parent: Operation not permitted
[ 4.604326] x-com (udev-worker)[359]: sda: Failed to process device, ignoring: Operation not permitted
然后我得到
Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f23fe245f-68fa-4619-8411-ba1aa5bbddfa.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ -e "/dev/disk/by-uuid/23fe245f-68fa-4619-8411-ba1aa5bbddfa" ]
fi"
Warning: starting timeout scripts
最后它降落在紧急控制台上。我可以看到 /dev/disk 不存在。在紧急情况下运行udevadm test /dev/sda3会创建 /dev/disk/by-uuid/23fe245f-68fa-4619-8411-ba1aa5bbddfa 但它无助于将系统引导到可用状态。根据我的理解，这条路径应该由 udev 在 60-persistent-storage.rules 或 13-dm-disk.rules 中创建。在提到 73-seat-late.rules 的行之前我没有看到任何相关错误。这是rdsosreport.txt的内容：https://paste.opensuse.org/pastes/b0c8cca5eee2
为什么 udev 不创建 /dev/disk 路径？我怎样才能找到问题所在？