Bug 207837 - FC6T3 on vmware: boot panic -- unable to mount root
FC6T3 on vmware: boot panic -- unable to mount root
Status: CLOSED DUPLICATE of bug 206453
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2006-09-24 05:58 EDT by Saikat Guha
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-25 11:28:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Saikat Guha 2006-09-24 05:58:14 EDT
Description of problem:
FC6T3 doesn't boot on VMware server after install. Console log:

  VFS: Cannot open root device "VolGroup00/LogVol00" 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)

FC5 works correctly on the exact same configuration. Configuration details below.

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

How reproducible: 

Steps to Reproduce:
1. Install FC6T3 on VMware server 1.0.1 (DVD or PXE -- both show this behavior)
2. Default options (click next until installtion completes)
3. Reboot as part of installation procedure
4. Doesn't boot - Panic

(this exact same procedure works for FC5)
Additional info:

After FC6 installation: /etc/grub.conf is
 root (hd0,0)
 kernel /vmlinuz-2.6.17-1.2630.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet

VMware is set to emulate a 20gb SCSI disk at 0:0 and an IDE CD-Rom on 1:0
(default options)

The *same set* of VMware options, FC installation media, and default FC
installation options works correctly for FC5.
Comment 1 Jeremy Katz 2006-09-25 11:28:22 EDT

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

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