Created attachment 895418 [details] Attaching an patch, which helped me to build working initramfs. Description of problem: When trying to build initramfs on Fedora 20 an error is displayed and when trying to boot my system, boot fails with an kernel panic because of unable to find root filesystem. Version-Release number of selected component (if applicable): dracut-037-11.git20140402.fc20.x86_64 How reproducible: always Steps to Reproduce: 1. dracut --print-cmdline 2. dracut -f /boot/initramfs-3.14.3-200.fc20.x86_64.img 3.14.3-200.fc20.x86_64 Actual results: [root@ftp ~]# dracut --print-cmdline /usr/lib/dracut/modules.d/90mdraid/module-setup.sh: line 58: _activated: bad array subscript rd.md.uuid=/usr/lib/dracut/modules.d/90mdraid/module-setup.sh: line 60: _activated["${UUID}"]: bad array subscript (same error for dracut -f ...) Expected results: working boot Additional info: When trying to display "${!host_fs_types[@]}", this is an result on my machine: /dev/sdb /dev/sdc /dev/sda /dev/md0 /dev/cciss/c0d0p3 /dev/sdc1 /dev/cciss/c0d0p1 /dev/sda1 /dev/sdb1 mdadm --examine don't work on /dev/sda and other partitioned devices. May be problem is in detection of these devices, but patch below helped me to fix this problem.
good catch! Thank you! http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=19bb14c3467233f8c98f76b3fa57047a3a31e1a3
Jut hit this on fresh f2, I guess the fix never got released?
Yes, just hit this on a yum upgrade of a RAID1 root system from F19 to F20. System won't reboot in new F20. Checking the initramfs for F20 shows that mdadm stuff is all missing. I see the error as above. Even --mdadmconf to dracut won't make it include mdadm.conf! What hasn't this bug errata been released?
Just hit this on another yum upgrade (same situation, different computer, as my comment #3). I knew to check the initramfs before reboot and /sbin/mdadm was there but not /etc/mdadm.conf. I applied the hack manually to the script and re-dracutted and rebooted ok. The fix needs to be pushed out to F20 so yum upgrades from 19 to 20 stop hitting this bug!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.