Bug 641770 - Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever
Summary: Fedora-14-Beta-x86_64-Live boot failures no root device found sleeping forever
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: 14
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-11 04:29 UTC by Phil V
Modified: 2013-01-10 06:16 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:14:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phil V 2010-10-11 04:29:01 UTC
Description of problem:
used Fedora LiveUSB Creator
and  Fedora-14-Beta-x86_64-Live.iso
to make a bootable USB.

Ordinary boot appears to fail, with keyboard becoming partially unresponsive
(Caps lock unresponsive, Cntl-Alt-Delete works for reboot)

Simple graphics boot has the 3 color progress bar advance most of the way to the right. But then screen blanks with message: 

    no root device found 
    Boot has failed, sleeping forever

How do I get troubleshoot this system and get it to boot?

The last kernel to boot successfully on this hardware is:
Linux amd.home 2.6.33.3-85.fc13.x86_64 #1 SMP Thu May 6 18:09:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Phil V 2010-10-11 19:40:39 UTC
changing the boot options to

root=live:LABEL=FEDORA     (from the USB's UUID)

does not seem to help.

Comment 2 Phil V 2010-10-11 20:22:57 UTC
Low graphics boot without  quiet rhgb

proceeds all the way to 

Starting HAL daemon
retrigger failed udev events
Adding udev persistent rules
Enabling BLuetooth devices:
Starting sendmail:
Starting sm-client:
Starting abrt daemon: eth0: no IPv6 routers present

after a pause, the screen goes blank and the keyboard is unresponsive.

Comment 3 Phil V 2010-10-11 20:25:06 UTC
(In reply to comment #2)

This was using a CD burnt with Fedora-14-Beta-x86_64-Live.iso

Comment 4 Phil V 2010-10-11 21:12:51 UTC
holding shift down and entering 'linux0' at boot also fails. 
(Text output scrolls past then screen goes blank and keyboard is unresponsive.)

Comment 5 Eric Rannaud 2010-10-18 19:16:55 UTC
It appears similar to https://bugzilla.redhat.com/show_bug.cgi?id=527514 for Fedora 12.

In my case, editing the GRUB command line, replacing root=live:UUID... by root=live:/dev/sdb1 (which is the usb partition where the image is) is a successful workaround.

Note, I have a i915 chipset, just like in the F12 bug https://bugzilla.redhat.com/show_bug.cgi?id=527514.

Comment 6 Phil V 2010-10-24 04:59:42 UTC
How did you make the usb? In Fedora 13? 
Did you use Fedora LiveUSBCreator version 3.9.2.1.fc13 ?

I ask because I think I tried this without success. Then I burned the CD but that didn't help either.

Comment 7 Eric Rannaud 2010-10-24 05:25:47 UTC
I used liveusb-creator-3.9.2-1.fc12.noarch (note that, for some reason, the version reported by the tool is different:
  $ liveusb-creator --version
  3.7.3
)

Make sure you specify the right /dev/sdXn device and partition to point to the USB key.

Comment 8 Matteo Settenvini 2010-11-03 12:55:33 UTC
I'm experiencing this too; it's a pity because I was planning to move away from Ubuntu and to Fedora. I've tried this: http://www.linuxreaders.com/2010/05/26/fc-13-12-live-cd-boot-error-no-root-device-found-fix/, but it didn't work.

Comment 9 Phil V 2010-11-04 18:26:05 UTC
I've been happy with RedHat/Fedora for many years. 

in the absence of advice from experts, I'd recommend:
Plan A: Try the F14 DVD or CD install or live CD.

Plan B: Hold off on F14 for now. Install with F13 which works, and use yum upgrade to keep current until F15 comes out.

Warning: I found the later F13 kernels troublesome for my videocards, so if you have a system which boots before but not after upgrade to 2.6.34 or 2.6.35 kernels, keep the F13original kernel. But 2.6.33 and 2.6.36++ work for me.

Unfortunately rumors are that 2.6.36 won't be in the F14 updates.

Comment 10 Eric Rannaud 2010-11-04 18:38:03 UTC
#8 (Matteo Settenvini) and #9 (Phil V): Can you comment on whether the workaround in comment #5 is working for you? Any error message to report?

"In my case, editing the GRUB command line, replacing root=live:UUID... by
root=live:/dev/sdb1 (which is the usb partition where the image is) is a
successful workaround."

Comment 11 Matteo Settenvini 2010-11-04 20:47:14 UTC
#10: I was finally able to boot it in low-graphics mode (unrelated issue with my ATI card, I think - but it's strange because using the opensource ati drivers in Ubuntu don't give me any problem), and specifying root=/dev/sr0.
It was a little bit difficult to guess, anyway.

Comment 12 Jonathan 2010-11-18 11:54:46 UTC
Same problem. Created a live-usb with live-usb-creator and F14-64 live cd on an F14 system. Then tried to use the live-usb to install to a 5 harddrive desktop with a one year old Gigabyte motherboard. Got the:
"no root device found 
    Boot has failed, sleeping forever"
a few seconds into the boot.

#5: "In my case, editing the GRUB command line, replacing root=live:UUID... by
root=live:/dev/sdb1 (which is the usb partition where the image is) is a
successful workaround." solved this for me, with the modification that the live-usb was on sdf1 for me.

Comment 13 Jonathan 2010-12-03 10:28:57 UTC
Got the same problem on a new HP laptop so it seems to be hardware independent.

Out of curiosity, is this related to the live-cd (meaning Fedora is stuck with it until that iso is deprecated) or can it be live-usb-creator?

Comment 14 Pasi Karkkainen 2011-03-03 19:45:57 UTC
Was this problem resolved? I'm seeing this same problem with current (fully updated as of 3rd of March 2011) Fedora 14 running livecd-creator generating f14 livecd image..

Comment 15 Pasi Karkkainen 2011-03-03 20:37:41 UTC
I've opened a new bug about my problem with livecd-creator here: https://bugzilla.redhat.com/show_bug.cgi?id=681999

Comment 16 Phil V 2011-03-03 22:12:09 UTC
I did not find a way to boot Fedora 14 successfully.

I am able to boot gfx_test_week_20110221_x86-64.iso but: 
only with the low quality graphics 'vesa' driver.
on the other hand, I reported in bug 679674 that booting with
'nomodeset drm.debug=0x04' results in:

No root device found


No root device found

Dropping to debug shell.

sh: can't access tty; job control turned off
dracut:/#"

Comment 17 wojnilowicz 2011-03-24 17:58:06 UTC
I've got the same error with pm-test-day-20110324.iso

Comment 18 Pasi Karkkainen 2011-04-29 17:34:45 UTC
In my case the problem is buggy virtual cdrom drive firmware, ie. bad "READ TOC" implementation, so udev fails to identify the CD and mount root.

udev version from el6 (udev-147-2.35.el6) works OK, and udev from f14 fails. So clearly something got broken in udev. Earlier versions were able to workaround the issue of buggy cdrom drive.

Patch should be added to udev to workaround the issue. 
More info from: https://bugzilla.redhat.com/show_bug.cgi?id=681999

Comment 19 Dino 2011-05-20 00:49:12 UTC
I get "No root device found", "sleeping forever" trying to boot Fedora 14 kernel/initramfs, version 2.6.35.13-91.fc14.x86_64.

Disabled all boot devices at the BIOS level, other than the disk. (Happens to be Intel 82801 SATA RAID Controller.)

Able to boot with Fedora 13 kernel/initramfs, and everything else Fedora 14.

Upgraded from Fedora 13 to Fedora 14 using preupgrade utility.

Any additional info needed?

Comment 20 Fedora End Of Life 2012-08-16 19:15:00 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


Note You need to log in before you can comment on or make changes to this bug.