Closed
Description
This is seen in QEMU aarch64-softmmu target:
[ OK ] Reached target basic.target - Basic System.
Starting dracut-initqueue.service - dracut initqueue hook...
[ OK ] Finished dracut-initqueue.service - dracut initqueue hook.
[ OK ] Reached target remote-fs-pre.targe…reparation for Remote File Systems.
[ OK ] Reached target remote-cryptsetup.target - Remote Encrypted Volumes.
[ OK ] Reached target remote-fs.target - Remote File Systems.
Starting dracut-pre-mount.service - dracut pre-mount hook...
[ OK ] Finished dracut-pre-mount.service - dracut pre-mount hook.
[ OK ] Reached target initrd-root-fs.target - Initrd Root File System.
Starting initrd-parse-etc.service …ints Configured in the Real Root...
[ OK ] Finished initrd-parse-etc.service …points Configured in the Real Root.
[ OK ] Reached target initrd-fs.target - Initrd File Systems.
[ OK ] Reached target initrd.target - Initrd Default Target.
Starting dracut-mount.service - dracut mount hook...
[ 20.055748] dracut-mount[284]: Warning: Can't mount root filesystem
Starting dracut-emergency.service - Dracut Emergency Shell...
[ 24.873937][ C1] random: crng init done
[ 25.725951][ T360] device-mapper: ioctl: 4.49.0-ioctl (2025-01-17) initialised: [email protected]
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
Press Enter for maintenance
(or press Control-D to continue):
I wonder X86 centric scripting causes this or not. Any clue to look for x86 dependencies of the dracut part would be appreciated.
Metadata
Metadata
Assignees
Labels
No labels