Description of problem: When booted, an install DVD for Fedora 16 x86_64 built by pungi+lorax(treebuilder) fails to find the root device. Version-Release number of selected component (if applicable): lorax-17.0 7f8a5e48b30a02afd6f9a71274a09ba73f892d60 (HEAD of treebuilder branch as of 2011-10-24 15:49:39) How reproducible: Steps to Reproduce: 1. compose install DVD for x86_64 using pungi+lorax(treebuilder) 2. burn and boot the DVD for Install 3. Actual results: ----- [snip] dracut Warning: No root device "live:/dev/disk/by-label/Fedorax2016x20x86_64" found dracut Warning: No root device "live:/dev/disk/by-label/Fedorax2016x20x86_64" found Dropping to debug shell. sh: can't access tty; job control turned off dracut:/# ----- Yes, the message appears twice, and appears exactly as above. The instances of "\x20" have not been replaced by " " [space]; instead the backslash merely has been elided. Neither does the tail of the string have any "\x20DVD" or similar. Expected results: finds root device and proceeds Additional info: Using the dracut shell and: # cd /dev/disk/by-label # ls -l | grep Fed then the relevant entry is: lrwxrwxrwx 1 root 0 9 Oct 25 03:02 Fedora\x2016\x20x86_64\x20DVD -> ../../sr0 which has the proper escapes and the "DVD" at the end. Changing the DVD boot argument to "root=live:/dev/sr0" proceeds to the first graphical screen (and beyond ...)
There's two bugs here: 1. dracut drops the backslashes from the device name. This is fixed upstream: http://thread.gmane.org/gmane.linux.kernel.initramfs/2159 https://git.kernel.org/?p=boot/dracut/dracut.git;a=commit;h=2cd4a8065ac2bb6bf3708d681de56bbe1984c3ce 2. pungi uses a ISO volume label that doesn't match the bootloader config The fix for this has been sent upstream. See bug 748939. (note that images/boot.iso will have the correct label (because it's also built by lorax) and should boot fine.) Since there's already a bug for the pungi thing, I'm reassigning this to dracut until we have a build including that patch.
dracut-013-17.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dracut-013-17.fc16
Package dracut-013-17.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-013-17.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15314 then log in and leave karma (feedback).
(In reply to comment #3) > Package dracut-013-17.fc16: [snip] > Update it with: > # su -c 'yum update --enablerepo=updates-testing dracut-013-17.fc16' That method of updating is not sufficient because it does not update the version of dracut that treebuilder puts into the initramfs that goes on the DVD. I did that "yum update ...", and the pungi patch of bug 748939, and composed a DVD. Upon boot of the DVD, then the kernel boot command parameter now has "root=live:/dev/disk/by-label/Fedora\x2016\x20x86_64" which is correct, but dracut still complains: Warning: No root device "live:/dev/disk/by-label/Fedorax2016x20x86_64" found and drops to a debug shell. Note that the "\x20" have not been interpreted correctly; instead the backslash has been elided without also removing the "20" and inserting a space character. What is the command, parameter, or other method of convincing treebuilder to use a different repo when downloading packages for, and building, the initramfs?
(In reply to comment #4) > That method of updating is not sufficient because it does not update [..] You may be a little confused. The Fedora Update System provides generic instructions - it doesn't have specific test instructions for every package, so there are some cases it might not apply. > What is the command, parameter, or other method of convincing treebuilder to > use a different repo when downloading packages for, and building, the > initramfs? Exactly the same procedure as all previous versions of pungi/lorax: * Put the updated packages you want in a directory. * Run 'createrepo' on that directory. * Add an appropriate 'repo' line to your kickstart. For example: repo --name=localrepo --baseurl=file:///[path to repo] --cost=1 http://fedoraproject.org/wiki/How_to_create_a_Fedora_install_ISO_for_testing might help.
This bug keeps me from being able to install from the DVD installer (not live) for Fedora 17. At least the symptoms of "\x20" stuff is the same.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.