When I boot from the live cd (Fedora-17-Beta-x86_64-Live-Desktop.iso) I see a message that reads "dracut Warning: /dev/disk/by-label/Fedora-17-Beta-x86_64-Live-Deskt does not exist". The /dev/disk/by-label directory is missing entirely. I went to /dev/disk/by-label and discovered a symlink to /dev/sr0 for the CDROM drive I wanted to use. I rebooted and changed the boot parameter from root=live:CDLABEL=Fedora-17-Beta-x86_64-Live-Deskt to root=live:/dev/sr0. From there I was able to continue the installation process. I have seen this in previous Fedora versions as well. I am listing the details below. Here is the output from F17. [pre] udevd[195]: RUN+="socket:..." support will be removed from future udev release . Please remove it from: /usr/lib/udev/rules.d/40-multipath.rules:16 and use lib udev to subscribe to events. dracut Warning: Unable to process initqueue dracut Warning: /dev/disk/by-label/Fedora-17-Beta-x86_64-Live-Deskt does not exi st dracut Warning: /dev/mapper/live-rw does not exist Dropping to debug shell dracut:/# [/pre] Here is the output from F16. [pre] dracut Warning: No root device "live:/dev/disk/by-label/Fedora-16-x86_64-Live-De sktop.is" found Dropping to debug shell. sh: can't access tty; job control turned off dracut:/# [/pre] Here is the output from F15. [pre] Dropping to debug shell. sh: can't access tty; job control turned off dracut:/# [/pre] Here is the output from F14. [pre] No root device found Boot has failed, sleeping forever. [/pre]
TYPO: I should have said "I went to /dev/disk/by-id and discovered a symlink to /dev/sr0 for the CDROM drive I wanted to use."
when you are in the dracut shell, what is the output of: # /lib/udev/cdrom_id --debug /dev/sr0 # blkid -o udev -p --noraid /dev/sr0
you can attach a photo
Created attachment 587454 [details] cdrom_id
Created attachment 587455 [details] blkid error
Created attachment 587457 [details] blkid
I attached the output of the first command. The second command reports an error so I'm attached a screenshot of the error, omitted "--noraid" to avoid the error and attached a screen shot of those results.
Also, my first report was produced using the Beta version of F17. The information I'm producing this morning is done using the latest released copy of F17.
# udevadm info --query=all --name=/dev/sr0 # ls -l /dev/disk/by-label
Created attachment 587787 [details] udevadm page1
Created attachment 587788 [details] udevadm page2
I've attached the information you requested.
Thanks for the debug info. I guess this is some virtual machine. It does not seem to have a proper CDROM emulation. Workaround for you: edit the kernel command line in the grub entry of the installer DVD/CD and change: "root=LIVE:LABEL=...." to "root=LIVE:/dev/sr0"
Yes that works perfectly as a workaround. The motherboard has a controller that I can connect to using a web browser. I can open a KVM and map an ISO file as a CDROM drive. It's not a virtual machine but it is a virtual CDROM drive.
Created attachment 588587 [details] Output of debug commands Same thing happens on Fedora 17 i686 DVD final on my Samsung R522 laptop Downloaded ISO with torrent - dowload verified with torrent check then supplied checksum. Burned twice with k3b, bot verified - disk is correct. At boot it chokes on floppy module (who these days use floppy, shouldn't it be skipped btw?) then spits out warning that /dev/disk/by-label/Fedora\x2017\x20i386 is not present and so on. Boot process ends up with dracut debug shell /dev/disk/by-label/Fedora\x2017\x20i386 Symlink is present and poitns correctly to ../../sr0 Is it problem with label using special char (not very smart thing on it's own imo)? Output of the reuested commands in attachement. Assuming there are bugs with upgrade from DVD not updating grub config properly, maybe DVD images should be respun?
I can confirm; same for me (as in Comment 15) for Dell Latitude E4300.
(In reply to comment #15) > Created attachment 588587 [details] > Output of debug commands > > Same thing happens on Fedora 17 i686 DVD final on my Samsung R522 laptop > Downloaded ISO with torrent - dowload verified with torrent check then > supplied checksum. Burned twice with k3b, bot verified - disk is correct. > > At boot it chokes on floppy module (who these days use floppy, shouldn't it > be skipped btw?) then spits out warning that > /dev/disk/by-label/Fedora\x2017\x20i386 is not present and so on. > Boot process ends up with dracut debug shell > > /dev/disk/by-label/Fedora\x2017\x20i386 Symlink is present and poitns > correctly to ../../sr0 > Is it problem with label using special char (not very smart thing on it's > own imo)? > > Output of the reuested commands in attachement. > Assuming there are bugs with upgrade from DVD not updating grub config > properly, maybe DVD images should be respun? just use the same workaround: Workaround for you: edit the kernel command line in the grub entry of the installer DVD/CD and change: "root=LIVE:LABEL=...." to "root=LIVE:/dev/sr0"
Created attachment 589164 [details] debug output I saw the same problem with Fedora-17-i686-Live-Desktop.iso - all kinds of debug info attached. The prescribed workaround did not work - panic both with lower and upper case 'LIVE'. 'root=/dev/sr0' worked better but still failed on /dev/mapper/live-rw does not exist. Copying the CD to USB worked fine.
[ 25.562564] dracut Warning: /dev/disk/by-label/Fedora-17-i686-Live-Desktop.iso does not exist but + ls -l /dev/disk/by-label total 0 lrwxrwxrwx 1 root root 9 Jun 4 15:14 Fedora-17-i686-Live-Desktop.iso -> ../../sr0 ... so this means, the kernel was not reporting a medium in the drive before. Can be a faulty firmware. The dracut in the installer and live CD should probably have been built with the "pollcdrom" dracut module. Can somebody try and generate a dracut initramfs with # dracut -a 'pollcdrom dmsquash-live' initramfs.img and boot with the DVD/CDROM inserted and the initramfs.img and with the root=LIVE:LABEL=... kernel command line?
For me, the work-around worked. If I remember correctly, I used LIVE uncapitalized, i.e. rule=live:/dev/sr0" and the "original" version, i.e., before I edited for the work-around, started "root=live:CDLABEL= ... " not "LABEL" as indicated in Comment 17. Martin
ok, sorry. so the workaround is to replace "root=...." with "root=live:/dev/sr0"
*** Bug 827513 has been marked as a duplicate of this bug. ***
workaround: edit the kernel command line of the DVD and specify: root=live:/dev/sr0 instead of the old root=live:.... argument
*** Bug 829056 has been marked as a duplicate of this bug. ***
(In reply to comment #24) > *** Bug 829056 has been marked as a duplicate of this bug. *** I followed your advice and edited the kernel commmand line of the my DVD and specified "root=live/dev/sr0". I tried it with two different cd's with different downloads of F17. The response was 2 times : mount: /dev/loop2 : can't read superblock umount /run/initramfs/squashfs : not mounted mount : unknown filesystem 'DM _snapshot_cow' (21 times) dracut warning : Can't mount root filesystem Droppoing to debugs shell Dracut:# Maybe this is helpfull. Chrit
(In reply to comment #25) > (In reply to comment #24) > > *** Bug 829056 has been marked as a duplicate of this bug. *** > > I followed your advice and edited the kernel commmand line of the my DVD > and specified "root=live/dev/sr0". I tried it with two different cd's with > different downloads of F17. I hope, you did not forget the ":" after live
(In reply to comment #26) > (In reply to comment #25) > > (In reply to comment #24) > > > *** Bug 829056 has been marked as a duplicate of this bug. *** > > > > I followed your advice and edited the kernel commmand line of the my DVD > > and specified "root=live/dev/sr0". I tried it with two different cd's with > > different downloads of F17. > > I hope, you did not forget the ":" after live Sorry for the typo in my above report. I did change the string under GRUB TAB as you specified to "root=live:/dev/sr0". I checked it again a minute ago with the same result as reported. Chrit
To be very precise i substituted "root=live:/dev/sr0" in the string under GRUB Tab for the old "root=live:..." . Chrit
(In reply to comment #25) > mount: /dev/loop2 : can't read superblock > umount /run/initramfs/squashfs : not mounted > mount : unknown filesystem 'DM _snapshot_cow' (21 times) > this sounds odd.. did you run a mediacheck? anyway.. if you are in the dracut shell, please do: # ls -l /dev/sr0 # blkid /dev/sr0 # ls -l /run/initramfs/livedev # ls -l /run/initramfs/live and report the output. I would try "livecd-iso-to-disk" with an USB stick.
The results are as follows. 1. brw------- 1 root root 11, 0 Jun 8 12:49 /dev/sr0 2. /dev/sr0: LABEL="Fedora-17-x86_64-Live-Desktop.is" TYPE= "iso9660" 3. lrwxrwrxwrx 1 root root 8 Jun 8 12:49 /run/initramfs/livedev -> /dev/sr0 4. total 24 dr-xr-xr-x 3 root root 2048 May 22 20;46 EFI -r--r--r-- 1 root root 18092 May 22 20;46 GPL dr-xr-xr-x 2 root root 2048 May 22 20;46 LiveOS dr-xr-xr-x 2 root root 2048 May 22 20;46 isolinux End of results. I tried another cd burner "Windows hulprogramma voor het branden van schijven" ("Windows supportprogram for burning on discs") that comes with Windows 7 Professional SP 1 and this solved my problem. Without further intervention this cd splashed the new fedora 17 screen. The cd causing all the trouble was burned with CDBurnerXP version 4. CDBurnerXP was proposed by Firefox for burning the downloaded F17 iso image. I checked the properties of my Dvd-rw station with this faulty cd in it with result : used 0 bytes available 0 bytes. It is the very same cd that produced the above 4 results. Maybe this is helpfull. Thanks to your suggestion i can now install F17.
(In reply to comment #28) > To be very precise i substituted "root=live:/dev/sr0" in the string under > GRUB Tab for the old "root=live:..." . > > Chrit I also faced these error but when i used "root=live:/dev/sr1" it successfully boots. So may can try these. Thanks
(In reply to comment #31) > (In reply to comment #28) > > To be very precise i substituted "root=live:/dev/sr0" in the string under > > GRUB Tab for the old "root=live:..." . > > > > Chrit > > I also faced these error but when i used "root=live:/dev/sr1" it > successfully boots. > So may can try these. > Thanks The CD burned with CDBurnerXP version 4 reported the following error messages when i followed your advice to use "root=live:/dev/sr1". dracut warning : unable to process initqueue dracut warning: /dev/mapper/live-rw does not exist dracut warning /dev/sr1 does not exist Dropping to debugshell dracut: The cd burned with the above mentioned Windows disc burning software gave exactly the same error messages when i tried your advice with that cd. With that cd i installed F17 succesfully as reported earlier. Conclusion : your advice did not splash the F17 screen on my PC. Thanks anyway.
(In reply to comment #32) > (In reply to comment #31) > > (In reply to comment #28) > > > To be very precise i substituted "root=live:/dev/sr0" in the string under > > > GRUB Tab for the old "root=live:..." . > > > > > > Chrit > > > > I also faced these error but when i used "root=live:/dev/sr1" it > > successfully boots. > > So may can try these. > > Thanks > > The CD burned with CDBurnerXP version 4 reported the following error > messages when i followed your advice to use "root=live:/dev/sr1". > > dracut warning : unable to process initqueue > dracut warning: /dev/mapper/live-rw does not exist > dracut warning /dev/sr1 does not exist > Dropping to debugshell > dracut: > > The cd burned with the above mentioned Windows disc burning software gave > exactly the same error messages when i tried your advice with that cd. > > With that cd i installed F17 succesfully as reported earlier. > > Conclusion : your advice did not splash the F17 screen on my PC. > Thanks anyway. /dev/sr1 is the first cdrom device /dev/sr1 is the second cdrom device
(In reply to comment #32) > (In reply to comment #31) > > (In reply to comment #28) > > > To be very precise i substituted "root=live:/dev/sr0" in the string under > > > GRUB Tab for the old "root=live:..." . > > > > > > Chrit > > > > I also faced these error but when i used "root=live:/dev/sr1" it > > successfully boots. > > So may can try these. > > Thanks > > The CD burned with CDBurnerXP version 4 reported the following error > messages when i followed your advice to use "root=live:/dev/sr1". > > dracut warning : unable to process initqueue > dracut warning: /dev/mapper/live-rw does not exist > dracut warning /dev/sr1 does not exist > Dropping to debugshell > dracut: > > The cd burned with the above mentioned Windows disc burning software gave > exactly the same error messages when i tried your advice with that cd. > > With that cd i installed F17 succesfully as reported earlier. > > Conclusion : your advice did not splash the F17 screen on my PC. > Thanks anyway. /dev/sr0 is the first cdrom device /dev/sr1 is the second cdrom device
Does anyone know what one would change the "root=live:/dev/sr0" part to if you were using a USB drive to boot from for the install? I'm seeing this issue on my Thinkpad X121e.
(In reply to comment #35) > Does anyone know what one would change the "root=live:/dev/sr0" part to if > you were using a USB drive to boot from for the install? > > I'm seeing this issue on my Thinkpad X121e. If you are using a USB drive, then root=live:LABEL="labelofthepartition" should work root=live:LABEL=Fedora-17-x86_64-Live-Desktop.is
(In reply to comment #35) > Does anyone know what one would change the "root=live:/dev/sr0" part to if > you were using a USB drive to boot from for the install? > > I'm seeing this issue on my Thinkpad X121e. Harald I had the same issue and I used root=live:/dev/sdb1 and booted just fine. with fedora 17 x86_64 in an usb
Created attachment 642102 [details] error log for this issue on recent F18 iso To participate in the GNOME test days I downloaded a very recent Fedora GNOME x86-64 Live image here: https://fedoraproject.org/wiki/Test_Day:2012-11-08_GNOME_3.6#Live_image I put the image on a USB flash drive and booted my laptop with it to encounter this bug as well. I also remember being affected by this issue when I tried an earlier alpha of Fedora 18, back then I didn't bother to report it. The funny thing is that Fedora 17 installed on this same laptop without any issue. There is a small difference in the error message I get though, as can also be seen in the log I have attached: dracut-initqueue[197]: Warning: Could not boot. dracut-initqueue[197]: Warning: /dev/disk/by-uuid/507D-9499 does not exist dracut-initqueue[197]: Warning: /dev/mapper/live-rw does not exist Just like in comment #37, changing the command to boot to root=live:/dev/sdb1 is an effective workaround for me.
Same problems as OP with Fedora 17 DVD AND Fedora 18 Alpha Live CD using a LaCie USB external drive. Workaround of /dev/sr0 on command line fails too, with a message something like, 'need file system type'. 'Failed to mount block device of live image'. There is a kernel panic right thereafter and message is lost, and the system hard locks. I *SERIOUSLY* think that this problem is caused by the packaging of the ISO and a parsing failure in dracut . When I burned the Fedora-17-x86_64-DVD.iso with k3b, the Volume Id was given as 'Fedora 17 x86_64'. Dracut failed with a 'Fedora\x2017\x20x86_64' does not exist error. The /dev/disk/by-label listing was for 'Fedorax2017x20x86_64' So the Volume ID and file name do NOT match. The 'escaping' backslash points to some sort of parsing error; I tried 'Fedora\\x2017....' and 'Fedora\\\x2017... as if this were a sed substitution. No joy. I tried 'Fedora‗...' to substitute the full hex code for a space...Nope. k3b would not let me change the Volume ID. I opened the iso with isomaster and changed the boot line in isolinux.cfg to read 'Fedora-17-x86_64' and changed the iso file name to Fedora-17-x86_64-DVD.iso. That is, I made the command line match the file name. I also burned the DVD with brasero this time. dracut says 'Warning: /dev/disk/by-label/Fedora-17-x86_64 does not exist' while an ls of /dev/disk/by-label shows 'Fedora-17-x86_64' (as a link pointing to ../../sr0 So dracut does not understand 'YES' for an answer! Note that throughout, these lines are followed by /dev/mapper/live-rw does not exist. Not sure if that is a symptom or the actual cause. So I'm not a happy camper here! I was actually trying the DVD to see if I could get around anaconda crapping out later in the install when using a USB stick.
Does anyone else experience that this bug no longer occurs for some reason with Fedora 18 beta? Today I put F18 beta on a USB flash drive with liveusb-creator and it just worked, no workaround needed.
I'm having the same difficulties as well. I'm working on creating a modified Fedora 17 x86_64 ISO using livecd-tools. The created ISO is remotely mounted and appears to the system as a USB CDROM. When the system boots, it drops into the emergency dracut shell stating 'dracut Warning: Unable to process initqueue'. The above suggestion to change the kernel cmdline string to change the "root=" section to "root=live:/dev/sr0" failed for me. I also tried setting rd_retry=400 thinking that udev was taking longer than expected, but that failed as well. I still do not know why dracut/udev is failing but after lots of testing and debugging, I came up with another workaround. First, the kernel is updated to make the usb-storage driver built-in. Second, the initramfs was updated to install the following script into /lib/dracut/hooks/pre-trigger/ -- START 99fix-dracut-udev-bug.sh -- #!/bin/sh # -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*- # ex: ts=8 sw=4 sts=4 et filetype=sh # Re-run dmsquash-live-root and force the link to the label cd_label=$(getarg root) cd_label=${cd_label#*live:CDLABEL=} if [ -n "$cd_label" ]; then info "Fixing dracut/udev bug:" cd_dev=`blkid | grep $cd_label | sed -e 's/^\([^:]*\):.*/\1/'` cd_devrel=`echo $cd_dev | sed -e 's/\/dev/..\/../'` dmsquash-live-root $cd_dev ln -s $cd_devrel /dev/disk/by-label/$cd_label unset cd_label cd_dev cd_devrel fi -- END 99fix-dracut-udev-bug.sh -- Hopefully this lends some insight as to the true source of failure.
(In reply to comment #41) > I'm having the same difficulties as well. > > I'm working on creating a modified Fedora 17 x86_64 ISO using livecd-tools. > The created ISO is remotely mounted and appears to the system as a USB > CDROM. When the system boots, it drops into the emergency dracut shell > stating 'dracut Warning: Unable to process initqueue'. > > The above suggestion to change the kernel cmdline string to change the > "root=" section to "root=live:/dev/sr0" failed for me. > > I also tried setting rd_retry=400 thinking that udev was taking longer than > expected, but that failed as well. > > I still do not know why dracut/udev is failing but after lots of testing and > debugging, I came up with another workaround. > > First, the kernel is updated to make the usb-storage driver built-in. > > Second, the initramfs was updated to install the following script into > /lib/dracut/hooks/pre-trigger/ > > -- START 99fix-dracut-udev-bug.sh -- > #!/bin/sh > # -*- mode: shell-script; indent-tabs-mode: nil; sh-basic-offset: 4; -*- > # ex: ts=8 sw=4 sts=4 et filetype=sh > > # Re-run dmsquash-live-root and force the link to the label > cd_label=$(getarg root) > cd_label=${cd_label#*live:CDLABEL=} > > if [ -n "$cd_label" ]; then > info "Fixing dracut/udev bug:" > > cd_dev=`blkid | grep $cd_label | sed -e 's/^\([^:]*\):.*/\1/'` > cd_devrel=`echo $cd_dev | sed -e 's/\/dev/..\/../'` > > dmsquash-live-root $cd_dev > ln -s $cd_devrel /dev/disk/by-label/$cd_label > > unset cd_label cd_dev cd_devrel > fi > -- END 99fix-dracut-udev-bug.sh -- > > Hopefully this lends some insight as to the true source of failure. all just a workaround around buggy CDROM drives and firmwares should be enough to include the "pollcdrom" dracut module in the livecd initramfs, which was forgotten.
(In reply to comment #42) > all just a workaround around buggy CDROM drives and firmwares > > should be enough to include the "pollcdrom" dracut module in the livecd > initramfs, which was forgotten. I forgot to mention, I tried the "pollcdrom" option and it didn't work for me.
(In reply to comment #43) > (In reply to comment #42) > > all just a workaround around buggy CDROM drives and firmwares > > > > should be enough to include the "pollcdrom" dracut module in the livecd > > initramfs, which was forgotten. > > I forgot to mention, I tried the "pollcdrom" option and it didn't work for > me. How did you do it?
(In reply to comment #44) > How did you do it? sudo dracut -v --add "dmsquash-live pollcdrom" --force initramfs.img `uname -r` I'm running on x86_64 systems. I get the same failure when booting the ISO on a real system (dual Xeon E7-2803) as well as on qemu (qemu-system-x86_64).
(In reply to comment #45) > (In reply to comment #44) > > How did you do it? > > sudo dracut -v --add "dmsquash-live pollcdrom" --force initramfs.img `uname > -r` > > I'm running on x86_64 systems. I get the same failure when booting the ISO > on a real system (dual Xeon E7-2803) as well as on qemu (qemu-system-x86_64). And you constructed a boot entry with initramfs.img and the kernel-`uname -r` and the "root=live:LABEL=Fedora-17-x86_64-Live-Desktop" command line?
(In reply to comment #46) > And you constructed a boot entry with initramfs.img and the kernel-`uname > -r` and the "root=live:LABEL=Fedora-17-x86_64-Live-Desktop" command line? Yes, when I build the ISO, my actual initramfs filename is initrd0.img and my kernel file is vmlinuz0. My /proc/cmdline is: initrd=initrd0.img root=live:CDLABEL=Cisco-Diags rootfstype=auto ro liveimg console=ttyS0,115200 console=tty0 rd.luks=0 rd.md=0 rd.dm=0 vga=0x314 BOOT_IMAGE=vmlinuz0 Also note that I've updated the kernel to a custom 3.5.0 kernel in the ISO. The usb-storage kernel module is built-in to allow the kernel to know about the USB CDROM a bit earlier, before udev starts. However, the udev rules which create the symlink for /dev/disk/by-label/<CDLABEL> are failing to run or something is removing it. The hook I posted forces the symlink to be created and lets the boot continue. So I know that I am providing the correct label in the command line.
(In reply to comment #47) > (In reply to comment #46) > > And you constructed a boot entry with initramfs.img and the kernel-`uname > > -r` and the "root=live:LABEL=Fedora-17-x86_64-Live-Desktop" command line? > > Yes, when I build the ISO, my actual initramfs filename is initrd0.img and > my kernel file is vmlinuz0. My /proc/cmdline is: > > initrd=initrd0.img root=live:CDLABEL=Cisco-Diags rootfstype=auto ro liveimg > console=ttyS0,115200 console=tty0 rd.luks=0 rd.md=0 rd.dm=0 vga=0x314 > BOOT_IMAGE=vmlinuz0 > > Also note that I've updated the kernel to a custom 3.5.0 kernel in the ISO. > The usb-storage kernel module is built-in to allow the kernel to know about > the USB CDROM a bit earlier, before udev starts. However, the udev rules > which create the symlink for /dev/disk/by-label/<CDLABEL> are failing to run > or something is removing it. > > The hook I posted forces the symlink to be created and lets the boot > continue. So I know that I am providing the correct label in the command > line. ok, one thing to try: remove the "if" clause in the main block in /usr/lib/dracut/modules.d/98pollcdrom/pollcdrom.sh and recreate the initramfs with the pollcdrom module. Would be nice, if you can try that out.
It exists in Fedora19 Alpha
I'm also seeing this error when trying to boot a UCS blade with the ISO as virtual media. This is with Fedora 18. I tried the /dev/sr0 workaround, which worked one time, but did not work after that.
I am having this issue with Fedora 19 Beta with a USB stick. It expects the volume label of the fat filesystem to be 'LIVE', and when it is not, it fails. I wrote the ISO image to the USB stick with liveusb-creator-3.11.8-1.fc18.noarch. liveusb-creator did not change the filesystem label to LIVE. So I'm not sure if I should count this as a bug against the installer for failing the find the image, or against liveusb-creator for failing to change the volume label to 'LIVE'. In the end, I changed the label using mlabel and the install worked. sudo mlabel -i /dev/sdb1 ::LIVE
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
I can confirm it on Fedora 19.
(In reply to LiZhenbo from comment #54) > I can confirm it on Fedora 19. What can you confirm? USB or CDROM boot? What is the label of the partition/CDROM? What is the kernel command line?
Created attachment 786766 [details] Screen in fedora19.jpeg (In reply to Harald Hoyer from comment #55) > (In reply to LiZhenbo from comment #54) > > I can confirm it on Fedora 19. > > What can you confirm? > USB or CDROM boot? > What is the label of the partition/CDROM? > What is the kernel command line? I used liveusb-creator in Fedora to create a liveUSB. Default command line is vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 sdriver=vesa nomodeset I changed to CDLABEL=LIVE to /dev/sdb4 , and got a workaround
(In reply to LiZhenbo from comment #56) > Created attachment 786766 [details] > Screen in fedora19.jpeg > > (In reply to Harald Hoyer from comment #55) > > (In reply to LiZhenbo from comment #54) > > > I can confirm it on Fedora 19. > > > > What can you confirm? > > USB or CDROM boot? > > What is the label of the partition/CDROM? > > What is the kernel command line? > > I used liveusb-creator in Fedora to create a liveUSB. > Default command line is > > vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro > rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 sdriver=vesa nomodeset > > I changed to CDLABEL=LIVE to /dev/sdb4 , and got a workaround What is the filesystem label of /dev/sdb4? # blkid -o udev /dev/sdb4 | fgrep ID_FS_LABEL
(In reply to Harald Hoyer from comment #57) > (In reply to LiZhenbo from comment #56) > > Created attachment 786766 [details] > > Screen in fedora19.jpeg > > > > I used liveusb-creator in Fedora to create a liveUSB. > > Default command line is > > > > vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro > > rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 sdriver=vesa nomodeset > > > > I changed to CDLABEL=LIVE to /dev/sdb4 , and got a workaround > > What is the filesystem label of /dev/sdb4? > > # blkid -o udev /dev/sdb4 | fgrep ID_FS_LABEL It's said that there's no command called 'fgrep', so I used 'grep' instead ID_FS_LABEL=Fedora-Live ID_FS_LABEL_ENC=Fedora-Live
(In reply to LiZhenbo from comment #58) > (In reply to Harald Hoyer from comment #57) > > (In reply to LiZhenbo from comment #56) > > > Created attachment 786766 [details] > > > Screen in fedora19.jpeg > > > > > > I used liveusb-creator in Fedora to create a liveUSB. > > > Default command line is > > > > > > vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro > > > rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 sdriver=vesa nomodeset > > > > > > I changed to CDLABEL=LIVE to /dev/sdb4 , and got a workaround > > > > What is the filesystem label of /dev/sdb4? > > > > # blkid -o udev /dev/sdb4 | fgrep ID_FS_LABEL > > > It's said that there's no command called 'fgrep', so I used 'grep' instead > > ID_FS_LABEL=Fedora-Live > ID_FS_LABEL_ENC=Fedora-Live so the correct parameter would be: root=live:CDLABEL=Fedora-Live and not root=live:CDLABEL=LIVE
(In reply to Harald Hoyer from comment #59) > (In reply to LiZhenbo from comment #58) > > (In reply to Harald Hoyer from comment #57) > > > (In reply to LiZhenbo from comment #56) > > > > Created attachment 786766 [details] > > > > Screen in fedora19.jpeg > > > > > > > > I used liveusb-creator in Fedora to create a liveUSB. > > > > Default command line is > > > > > > > > vmlinuz0 initrd=initrd0.img root=live:CDLABEL=LIVE rootfstype=vfat ro > > > > rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 sdriver=vesa nomodeset > > > > > > > > I changed to CDLABEL=LIVE to /dev/sdb4 , and got a workaround > > > > > > What is the filesystem label of /dev/sdb4? > > > > > > # blkid -o udev /dev/sdb4 | fgrep ID_FS_LABEL > > > > > > It's said that there's no command called 'fgrep', so I used 'grep' instead > > > > ID_FS_LABEL=Fedora-Live > > ID_FS_LABEL_ENC=Fedora-Live > > so the correct parameter would be: root=live:CDLABEL=Fedora-Live and not > root=live:CDLABEL=LIVE Thank you. Is it a dracut bug? Or a liveusb-creator bug?
(In reply to LiZhenbo from comment #60) > Thank you. > Is it a dracut bug? Or a liveusb-creator bug? liveusb-creator bug Either it should create the image with the correct filesystem labels or correct the kernel command line. Please open a new bug against component liveusb-creator.