Bug 1177043

Summary: Dracut fails to mount btrfs root filesystem by label or uuid
Product: [Fedora] Fedora Reporter: George Joseph <g.devel>
Component: cloud-initramfs-toolsAssignee: Juerg Haefliger <juergh>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 21CC: dracut-maint-list, g.devel, harald, Jan.van.Eldik, jonathan, juergh, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: armhfp   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 06:25:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg of a failed f21 boot by label
none
dmesg of successful boot of a f20 created initramfs
none
dmesg of a successful boot of a f21 initramfs by dev node
none
rdsosreport from failed boot
none
dracut create initramfs log none

Description George Joseph 2014-12-23 22:49:08 UTC
Created attachment 972539 [details]
dmesg of a failed f21 boot by label

Description of problem:

After upgrading my Cubox-i4pro to Fedora 21, initramfses created with dracut fail to mount my root filesystem either by label or uuid.  After being dropped to the emergency shell, I can clearly see the /dev/disk/by-label and /dev/disk/by-uuid entries.  

This was not an issue with the Fedora 20 dracut version and I can still boot correctly with an initramfs previously created by F20.

Version-Release number of selected component (if applicable):

dracut.armv7hl  038-31.git20141204.fc21

How reproducible:

Constant

Steps to Reproduce:
1.  Run dracut to create an initramfs
2.  Modify cmdline to find root by label:  root=LABEL=root
3.  reboot

Actual results:

Get dropped into an emergency shell (see boot-fail-f21-by-label.txt and rdsosreport.txt)

Expected results:

Normal boot.  (See boot-ok-f20-by-label.txt and boot-ok-f21-by-dev.txt

Additional info:

Dracut command line and build output is in dracut.log

Comment 1 George Joseph 2014-12-23 22:50:27 UTC
Created attachment 972540 [details]
dmesg of successful boot of a f20 created initramfs

Comment 2 George Joseph 2014-12-23 22:51:19 UTC
Created attachment 972541 [details]
dmesg of a successful boot of a f21 initramfs by dev node

Comment 3 George Joseph 2014-12-23 22:51:51 UTC
Created attachment 972542 [details]
rdsosreport from failed boot

Comment 4 George Joseph 2014-12-23 22:52:46 UTC
Created attachment 972543 [details]
dracut create initramfs log

Comment 5 George Joseph 2014-12-24 16:40:21 UTC
I found a workaround...   Specifying "--add-fstab /etc/fstab" on the dracut command line works.  Just specifying "--fstab" or not specifying any fstab options does not work.

Comment 6 George Joseph 2014-12-24 23:40:16 UTC
Well, doing add-fstab solved the root problem but my boot partition now fails to mount.  Worse, there's an entry in /proc/mounts for "/dev/mmcblk0p1 /boot" so even though /boot appears to not be mounted, you can't run any filesystem tools on it.

ANYWAY...

After much gnashing of teeth, I figured out that it's the growroot module that's the root of all evil.  Once I omit that, everything returns to normal.  No need for any fstab options.

Comment 7 Harald Hoyer 2015-01-28 13:11:29 UTC
reassigning to the correct component.
growroot is not part of the upstream dracut package.

Comment 8 Fedora End Of Life 2015-11-04 13:55:29 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2015-12-02 06:25:11 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.