public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Francisco Rivas" <taken2k4@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] VFS: cannot open root device "hdd2" on unknown-block(0,0)
Date: Sat, 24 Mar 2007 09:58:40 -0400	[thread overview]
Message-ID: <2fcf3fa50703240658p771a1ee0nb833ccb350e7032f@mail.gmail.com> (raw)
In-Reply-To: <460523A7.4050908@herkild.dk>

Hi..

In my experience this error:

Error message on boot:
VFS: cannot open root device "hdd2" on 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)

is about bad configuration in grub/lilo, check the real number of your
root partition and remember: if you use Grub (great idea)  add the
real root partition number parameter to your kernel coniguration, plus
the init parameter.

This problem probably is the result of a change of your pool of disks
or changes in your partitions or bad parameter in you boot config
file..

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=10
That can help you i guess.

I hope help you...

P.D : Excuse me for my english i'm learning about it.

Have a VERY nice day.

On 3/24/07, Kristian Poul Herkild <kristian@herkild.dk> wrote:
> Oh well...
>
> I've been battleling with my Silicon Image PCI ATA-133 controller.
> I've spent the last 7-8 hours trying to compile a working kernel with
> support for the extra IDE controller. But so far I've failed. I've tried
> several combinations (with/without support for CMD0680 - with/without
> xtables - on 2.6.18 and 2.6.19) - and have tracked the problem to the
> PCI IDE controller.
>
> I've googled for hours as well, but I have no clues but one: Enabling
> support for the PCI IDE/PATA Controller apparently pushes the device
> names for the on-board IDE/PATA controller (e.g. /d_ev/hdd becomes
> /dev/hdh).
>
> Is that even possible? That the extra PCI ATA-Controller takes
> precedence over the on-board Controller?
>
> Kind Regards,
> Kristian Poul Herkild
>
> ---
>
> Output from lspci:
> 00:0a.0 Mass storage controller: Silicon Image, Inc. PCI0680 Ultra
> ATA-133 Host Controller (rev 02)
>
> Error message on boot:
> VFS: cannot open root device "hdd2" on 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)
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
['Cause without love I won't survive, I love you]. I

Francisco Rivas
2.6.19-gentoo-r5 x86
udev v087 gnome 2.16.2
xorg-x11-7.1 hotplug v20040923-r2
e-mail : fjrivas@uc.edu.ve
msn : taken2k4@gmail.com

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/E/IT/MU d-(+)@ s++: a-- C++++>++++ ULSC*()>+++ P+(++)>+++
L++(+++)>++++ !E--- W+>++ !N* !o-(--)>-- K--? !w--- !O !M !V PS@ !PE@
Y> PGP t 5 X R+>+ tv- b DI D G e++>+++ h-> r++>+++ y-
------END GEEK CODE BLOCK------
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2007-03-24 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-24 13:12 [gentoo-user] VFS: cannot open root device "hdd2" on unknown-block(0,0) Kristian Poul Herkild
2007-03-24 13:44 ` Neil Bothwick
2007-03-24 14:47   ` [gentoo-user] (SOLVED) " Kristian Poul Herkild
2007-03-24 13:58 ` Francisco Rivas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2fcf3fa50703240658p771a1ee0nb833ccb350e7032f@mail.gmail.com \
    --to=taken2k4@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox