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
Created attachment 972540 [details] dmesg of successful boot of a f20 created initramfs
Created attachment 972541 [details] dmesg of a successful boot of a f21 initramfs by dev node
Created attachment 972542 [details] rdsosreport from failed boot
Created attachment 972543 [details] dracut create initramfs log
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.
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.
reassigning to the correct component. growroot is not part of the upstream dracut package.
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.
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.