Bug 165175 - Couldn't find valid ramdisk image starting at 0
Summary: Couldn't find valid ramdisk image starting at 0
Status: CLOSED DUPLICATE of bug 159026
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
(Show other bugs)
Version: 4
Hardware: i386 Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-04 22:00 UTC by Megan Quattrocchi
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-08-07 19:09:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Megan Quattrocchi 2005-08-04 22:00:27 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)

Description of problem:
I'm trying to install fc4 on a new system and it dies with the following error.
Ramdisk: Couldn't find valid randisk image starting at 0.

This is an Intel D865GLC mainboard with P4@2.4Ghz, 512M DDR.


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


How reproducible:
Always

Steps to Reproduce:
1. start install.
2.
3.
  

Actual Results:  About a page of messages then it dies at...
Ramdisk: Couldn't find valid randisk image starting at 0.
VFS: Cannot open root device "<NULL>" or unknown-block (8,3)
Kernal panic not syncing
VFS:Unable to mount root fs on unknown-block(8,3)



Additional info:
Comment 1 Gerwin Krist 2005-08-07 19:01:29 UTC 
can you try to use ide=nodma while booting up the setup? And see if something
changes?
Comment 2 Gerwin Krist 2005-08-07 19:09:12 UTC 
Read: http://forums.fedoraforum.org/showthread.php?t=62400

*** This bug has been marked as a duplicate of 159026 ***
Note You need to log in before you can comment on or make changes to this bug.