Hide Forgot
Description of problem: somesthing seems to be broken in dracut-008.7: the root file system cannot be found! starting with the update to dracut-008.5 I need to start with "selinux=0" (or in permissive mode to get a getty from systemd, otherwise systemd seems to fail to start the gettys! Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
okay, after some debugging I found the problem: dracut seems to be very strict about non-existing resume devices. I need to remove this option from my kernel command line: "resume=/dev/mapper/luks-swap". with the above option removed, the system boots correctly. with above option in place dracut tells me that it cannot find the root file system, which is not true. /dev/mapper/luks-swap is an LUKS encrypted swap device, that was not setup/mounted/existing while the dracut tool created the initramfs (because of some bug in plymouth/systemd that don't let my enter the password in the boot process...)
(In reply to comment #1) > okay, after some debugging I found the problem: > > dracut seems to be very strict about non-existing resume devices. I need to > remove this option from my kernel command line: "resume=/dev/mapper/luks-swap". > with the above option removed, the system boots correctly. with above option in > place dracut tells me that it cannot find the root file system, which is not > true. > > /dev/mapper/luks-swap is an LUKS encrypted swap device, that was not > setup/mounted/existing while the dracut tool created the initramfs (because of > some bug in plymouth/systemd that don't let my enter the password in the boot > process...) oh.. that might be a very valid point. 1. dracut has to be more verbose about what failed 2. dracut should not completely fail after it did not find the resume device