English Spanish
How to debug Dracut problems
If you are experiencing a problem with system initialization due to Dracut, please see the link:Bugs/Common[common bugs] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.
Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.
Identifying your problem area
Remove `rhgb` and `quiet` from the kernel command line
Add `rd.shell` to the kernel command line. This will present a shell
in case dracut is unable to locate your root device
Add `rd.shell rd.debug log_buf_len=1M` to the kernel command line so
that dracut shell commands are printed as they are executed
Inspect the system logs:
# less /run/initramfs/rdsosreport.txt
# journalctl -a
# dmesg
# less /run/initramfs/init.log
Information to include in your report
All bug reports
In all cases, the following should be mentioned and attached to your bug report:
The exact kernel command-line used. Typically from the bootloader configuration file (e.g. `/etc/grub.conf`) or from `/proc/cmdline`
A copy of your disk partition information from `/etc/fstab`
A device listing from device-mapper. This can be obtained by running the command `dmsetup ls -- tree`
A list of block device attributes including vol_id compatible mode. This can be obtained by running the commands `blkid` and `blkid -o udev`
Turn on dracut debugging (see link:How_to_debug_Dracut_problems#Debugging[the 'debugging dracut'
section]), and attach all relevant information from the boot log. This
can be obtained by running the command `dmesg|grep dracut`