Bug 2480661

Summary: Fedora boot failure after unexpected reboot
Product: [Fedora] Fedora Reporter: Nathan <nathan95>
Component: dracutAssignee: Pavel Valena <pvalena>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 45CC: awilliam, dracut-maint-list, jamacku, lnykryn, pvalena
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nathan 2026-05-21 23:37:26 UTC 
After an unexpected machine reboot, the Fedora system hangs during boot in the dracut-initqueue phase. The initramfs cannot find a required block device referenced by UUID, causing repeated timeout warnings and preventing the system from completing boot.
Reproducible: Always

Steps to Reproduce:
1.start the virtaul machine 

Actual Results:
The system repeatedly prints timeout warnings during boot and waits indefinitely for a disk identified by UUID.

Main symptoms:

dracut-initqueue timeouts
missing /dev/disk/by-uuid/...
boot stuck during initqueue processing
timeout scripts started

Expected Results:
The machine starts up correctly and runs gboot 

Additional Information:
dracut-initqueue[438]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:

dracut-initqueue[438]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fd233f670-8c82-47d7-8e3f-d995f1dd8a7e.sh

dracut-initqueue[438]:
[ -e "/dev/disk/by-uuid/d233f670-8c82-47d7-8e3f-d995f1dd8a7e" ]

Job dracut-initqueue.service/start running
(2min 43s / no limit)

Job dev-disk-by\x2duuid-d2start running
(2min 45s / no limit)

dracut-initqueue[438]:
Warning: dracut-initqueue: starting timeout scripts
Comment 1 Adam Williamson 2026-05-27 18:34:51 UTC 
Monitoring for questionable agentic AI activity.