After recent updates I ended with system unable to boot correctly. Currently it boots to message
Reached target Basic System
Then, after minute or two, it starts to output many times
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
It ends in dracut recovery shell. After exiting I get final words
Warning: Not all disks have been found.
Warning: You might want to regenerate your initramfs.
23fe245f-68fa-4619-8411-ba1aa5bbddfa is the UUID of my root partition. In dracut recovery shell I don’t have /dev/disk at all. I’ve tried chrooting from Tumbleweed Rescue DVD to this system and regenerating initrmfs with dracut --regenerate-all --force but system still doesn’t boot.
I’ve pasted contents of rdsosreport.txt - https://paste.opensuse.org/pastes/b0c8cca5eee2 and logs from dracut https://paste.opensuse.org/pastes/f3e4e3900030
I’ll appreciate any help with this.
Ooops!! Hope dracut isn’t broken for this update.
I’ve update four systems in the last couple hours, but haven’t booted them back up. One system is still running after applying the update , which consisted of about ten update packages.
I did notice that dracut is part of this update. I’m gonna leave the one desktop still running (not rebooted yet after update).
I’ll boot up a laptop in a few minutes, I’ve since updated and powered off, to see what happens (it also listed dracut as a package update).
…
UPDATE: laptop booted up with no problems.
Checked the Changelog for dracut:
Mon 10 Apr 2023 07:00:00 AM CDT
- Update to version 059+suse.368.g2e7ac134:
- chore(suse): remove mkinitrd wrapper (bsc#1202351) (jsc#PED-1919)
It seems that processing of every device by udev fails with
[ 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
so these links are not created. Right now I am not sure how this is even possible (I do not see how udev umport{parent} can return EPERM). May be someone have an idea. I may get a look later tonight.
Small correction: in emergency shell I don’t have /dev/disk
After this two answers I did upgrade dracut and udev hoping that maybe old versions have some bugs, but booting fails in the same way.
I think problem is related to udev as @arvidjaar pointed out, not with dracut. I don’t have any experience with udev and 73-seat-late.rules looks cryptic to me. From man udev also I don’t understand how IMPORT{parent} could work. Only hint to me was that man mentions attributes of parent. I tried udevadm info --attribute-walk --name=/dev/sda in emergency console but output looks very similar to output from other computer. I didn’t spot anything alarming me.
I’ve found something what could have contributed to this situation. Some time before problem I moved /usr/lib64/gcc to another partition and symlinked to it. Now it’s back in it’s right place, but that doesn’t helped. May it be a factor?
I will try to reinstall packages installed in april but maybe somebody knows it’s not necessary and the problem comes from something different.
(Under /usr/lib64/gcc I’ve symlink to itself gcc → gcc which looks odd to me)