Bug 679855

Summary: dracut-008.7 fails to find root file system
Product: [Fedora] Fedora Reporter: Thomas Meyer <thomas.mey>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: harald, jonathan
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-04 12:09:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Thomas Meyer 2011-02-23 17:38:51 UTC
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:

Comment 1 Thomas Meyer 2011-02-23 19:18:34 UTC
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...)

Comment 2 Harald Hoyer 2011-02-23 19:50:27 UTC
(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