Bug 594439 - No Root Device Found Boot Failed, Sleeping Forever
Summary: No Root Device Found Boot Failed, Sleeping Forever
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 12
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-20 16:58 UTC by codingfreak
Modified: 2010-12-03 14:31 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 14:31:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description codingfreak 2010-05-20 16:58:59 UTC
Description of problem:

I have installed FEDORA 12 in dual partition (VISTA) on HP DV6000 laptop which has a Nvidia GeoForce 7200 graphic card. Upgraded with latest kernel 2.6.32 using yum.

Recently installed Nvidia Proprietary Drivers for graphic card on 2.6.32 and successfully booted with Nvidia drivers without any problems and no other updates made after that.

Now if I try boot into Fedora 12 I get the following error saying

No Root Device Found
Boot Failed, Sleeping Forever.

Version-Release number of selected component (if applicable):


How reproducible:
Not sure if it can be reproduced on other machines.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Fedora 12 boot up stops saying

No Root Device Found
Boot Failed, Sleeping Forever.

Expected results:
Fedora 12 should successfully boot up.

Additional info:

Comment 1 codingfreak 2010-05-27 03:35:14 UTC
I tried to boot again with LIVE CD and with LIVE CD I am able to see my LINUX partitions available when I give fdisk -l command. Is there anything more I can try out or a workaround for making GRUB detect my ROOT DEVICE ??

Comment 2 codingfreak 2010-06-04 03:44:38 UTC
I tried with rescue mode where it is not able to automatically detect my linux partitions but if I try the command fdisk -l in command prompt it shows my linux partition naming it as LINUX .. hmmm strange ...

Comment 3 ggreen 2010-06-21 20:49:26 UTC
  I attempted to do a preupgrade. It loaded and then upon reboot the blue bar at the bottom of the screen appears and when finished this appears:

FATAL: Could not load /lib/modules/2.6.32.14-127.fc12.i686/modules.dep: 
No such file or directory 
/init: line 198: /sys/block/sr0:  Is a directory

No root device found
Boot has failed, sleeping forever

Comment 4 itsjustarumour 2010-08-12 13:37:59 UTC
Same problem here on Fedora 13, KDE spin (SC 4.5)


Had had problems with the NVidia driver on my fresh Fedora 13 install some time back, so used the standard "how-to" here to install the NVidia driver:

http://forums.fedoraforum.org/showthread.php?t=204752

All had been running fine for weeks, came back from 2 weeks holiday and installed all the automatic updates (unfortunately I don't recall what they included) and on rebooting max available screen resolution was 800x600.

I tried the above how-to again to reinstall the NVidia driver, and after rebooting get this bug. I enter the password for my encrypted drive, get the standard horizontal white and blue bar along the bottom of the screen to show Fedora is loading and when its complete get the error message as described by the OP.

Comment 5 Jeremy Whiting 2010-08-25 07:57:05 UTC
 Upgraded F12 install on 20th August. Started the OS on Monday morning to find these errors.

WARNING: Depreciated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
/init: 2: cannot create /sys/block/sr0: Is a directory
No root device found
Boot has failed, sleeping forever

 Using the recovery disk I have mounted and removed the file /etc/modprobe.conf. Additionally have applied the patch for the second message by following the instructions in https://bugzilla.redhat.com/show_bug.cgi?id=593830
 These messages still appear when booting up.

Jeremy

Comment 6 Jeremy Whiting 2010-09-02 07:44:24 UTC
(In reply to comment #5)
>  Upgraded F12 install on 20th August. Started the OS on Monday morning to find
> these errors.
> 
> WARNING: Depreciated config file /etc/modprobe.conf, all config files belong
> into /etc/modprobe.d/.
> /init: 2: cannot create /sys/block/sr0: Is a directory
> No root device found
> Boot has failed, sleeping forever
> 
>  Using the recovery disk I have mounted and removed the file
> /etc/modprobe.conf. Additionally have applied the patch for the second message
> by following the instructions in
> https://bugzilla.redhat.com/show_bug.cgi?id=593830
>  These messages still appear when booting up.
> 
> Jeremy

After some investigating this error on my machine is due to a defect in blkid. The blkid command is not reporting the correct file system type. It should be 'ext3' but reports 'silicon_medley_raid_member'.

Comment 7 Steve Retzlaff 2010-09-29 13:18:07 UTC
I had the same problem (No root device, sleeping forever) with the graphics_test_20100928-i686.iso LiveCD on a system which currently runs Ubuntu 10.04 LTS with no problem.

Comment 8 sawrub 2010-10-20 03:35:36 UTC
Getting the issue when trying to boot a Fedora 14 Beta live USB created from live USB creator under F12.
There was no error shown during the USB creation. Also the system boots up fine with USB, but after around 30 seconds the black [console] screen appears, with the message.
No idea what to do.The same USB installed my Fedora 12 successfully.

Comment 9 Bug Zapper 2010-11-03 14:31:25 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 10 Steve Retzlaff 2010-11-03 15:21:24 UTC
(In reply to comment #9)
> This message is a reminder that Fedora 12 is nearing its end of life.
> Approximately 30 (thirty) days from now Fedora will stop maintaining
> and issuing updates for Fedora 12.  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 '12'.
> 
> 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 12'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 12 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 please change the 'version' of this 
> bug to the applicable version.  If you are unable to change the version, 
> please add a comment here and someone will do it for you.
> 
> 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

Although this bug may have been for Fedora 12, my comment above on 2010-09-29 was for the "Fedora 14 graphics test week" live cd image which I read about on
http://lwn.net/Articles/407346/
so I presume this bug, which seems repeatable on the Dell Dimension 8200 PC, pertains more closely to the current Fedora 14, than to Fedora 12, so I would suggest the version for this bug be changed to Fedora 14.

Comment 11 itsjustarumour 2010-11-04 03:30:22 UTC
For info, I'm also still getting this bug sometimes on Fedora 13 (32-bit)

Comment 12 Adam Huffman 2010-11-12 14:13:09 UTC
I'm seeing exactly this on a Dell Precision 390 with an Intel BIOS RAID1 array.

The system had recently been upgraded to F13, which started showing this problem.  I tried upgrading to F14 and the error appeared.  Let me know if there's any more information I can send.

Comment 13 Bug Zapper 2010-12-03 14:31:23 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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