Bug 205348 - Kernel panic - Unable to boot system after installation [unable to mount root fs on unknown-block(0,0)] - rawhide
Summary: Kernel panic - Unable to boot system after installation [unable to mount root...
Status: CLOSED DUPLICATE of bug 205347
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords: Desktop
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-06 08:11 UTC by Mayank Jain
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-09-06 08:23:35 UTC


Attachments (Terms of Use)

Description Mayank Jain 2006-09-06 08:11:01 UTC
Description of problem:
Just after the installation (and reboot), the boot process fails with this 
message

VFS: cannot open rood device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Version-Release number of selected component (if applicable):
anaconda-11.1.0.89-1.x86_64.rpm   
kernel-2.6.17-1.2617.2.1.fc6.x86_64.rpm  
grub-0.97-11.x86_64.rpm 


How reproducible:
Everytime

Steps to Reproduce:
1. Install Rawhide (this *might* be the one which will fo for fc6t3 freeze)
2. Reboot as mentioned in the end of install process
3. Kernel Panic!
  
Actual results:
Kernel Panic

Expected results:
Correct bootup

Additional info:
I have an AMD athlon 64 bit processor (3500+), SATA disk & performed a network 
installation. I also changed the default name "Fedora Core" in the boot menu 
(during install) to "Rawhide".

Following was my disk structure
/dev/sda1 - / - 80000 M - EXT3
/dev/sda2 - swap - 512 M
/dev/sda3 - /data - ~=70000M - EXT3

Comment 1 A S Alam 2006-09-06 08:23:35 UTC

*** This bug has been marked as a duplicate of 205347 ***

Comment 2 Mayank Jain 2006-09-06 08:38:50 UTC
Oops, sorry, must have pressed commit twice :)


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