Bug 444931 - Boot Hangs because improper hard drive is selected.
Summary: Boot Hangs because improper hard drive is selected.
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-05-02 01:41 UTC by Lee Rumler
Modified: 2009-01-09 06:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 06:27:39 UTC
Type: ---

Attachments (Terms of Use)

Description Lee Rumler 2008-05-02 01:41:05 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080416 Fedora/ Firefox/

Description of problem:
Directly after updating to the new kernel (, I rebooted my computer and I got the message "Could not find filesystem '/dev/root'".  So I rebooted the computer again and took a look at the grub.  I found that there was a major difference in the old kernel and the new one (in the grub commands at least).  

In the old kernel, the ro root was pointed to /dev/VolGroup00/LogVol00 (kernel /vmlinuz- ro root=/dev/VolGroup00/LogVol00 rhgb quiet)  But in the new kernel it shows: ro root=UUID=448c9c30-4a09-40f6-8e01-d3c577cd250d

I have no idea what this means.  I have tried yum removing the kernel and yum installing again, but it keeps going back to the same commands.  On top of that, even after I alter the grub, I get the same message when I am trying to boot up:
"Unable to access resume device (UUID=0998d0dc-3163-48d6-a526-2a86736b3e76)"

I also have no idea what that means.

Fortunately for the time being I can boot to the old kernel and it works fine (except for the graphics card).  But if the next kernel doesn't fix this problem, I may be in deep trouble.

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

How reproducible:

Steps to Reproduce:
1.Hit Power Button
2.Encounter Problem
3.Force Computer Restart
4.Boot to Old Kernel
5.Remove new Kernel
6.Reinstall new Kernel
8.Encounter problem again

Actual Results:
I get five error messages:
Unable to access resume device (UUID=0998d0dc-3163-48d6-a526-2a86736b3e76)
and 4 other ones saying that it can't mount certain systems.

Expected Results:
The Volumes should have been mounted and the computer should have started with the new kernel.

Additional info:
Not much, I had to write everything down so...
Unable to access resume device (UUID=0998d0dc-3163-48d6-a526-2a86736b3e76)
Something about not being able to mount certain files
Could not find filesystem '/dev/root'

Comment 1 Bug Zapper 2008-11-26 10:37:25 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  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 '8'.

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 8'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 8 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: 

Comment 2 Bug Zapper 2009-01-09 06:27:39 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 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.