On rebooting my machine, I got a dracut-initqueue timeout boot failure.
First, I had a blank screen with a blinking underscore in top left corner. Underscore was blinking may be a minute. Then my screen was flooded with warnings:
[ 291.489448] solus dracut-initqueue[260]: Warning: dracut-initqueue: starting timeout scripts
[ 292.006301] solus dracut-initqueue[260]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
[ 292.008628] solus dracut-initqueue[260]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f5b1f8e27-3f56-4448-b336-0926246b50e6.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 292.008628] solus dracut-initqueue[260]: [ -e "/dev/disk/by-uuid/5b1f8e27-3f56-4448-b336-0926246b50e6" ]
Then, system entered emergeny mode.
I copied journalctl log file and rdsosreport.txt
I turned off my laptop and booted again. This time, it made the impression to boot just fine.
Should I be concerned?
The boot delay and the blinking underscore I also observed once on boot after on of my random system freezes that I try to tackle in a different forum thread. Had 2 of those freezes on the same day this dracut-initqueue timeout occured. Will report on those freezes in the other thread. Might this boot failure be related to the system freezes?