Date: Mon, 29 Mar 2004 14:05:19 +0200
From: Marco Baan <marco@freebsd.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: failure to mount root fs
Message-ID: <20040329120519.GA23337@maiden.localhost.nl>
References: <26889266.1080559781017.JavaMail.www@wwinf3002> <1080561608.3570.2.camel@laptop.fenrus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 8BIT
In-Reply-To: <1080561608.3570.2.camel@laptop.fenrus.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1038
Lines: 30

> > Hi Macro,
> > 
> > You wrote:
> > 
> > > VFS: Unable to mount root fs on unknown-block(0,0)
> > > ...
> > > kernel /boot/bzImage-2.6.4 ro root=LABEL=/
> > 
> > The "LABEL=/" is the attempt to mount root filesystem by label, so you can 
> > move it to another disk. I find these "clever" things not mature yet and always replace it by an explicit device name (and don't move/replace root disk):
> 
> it's ok as long as you remember to make an initrd (make install in the
> kernel source will do so automatic, at least on a RH/Fedora system)

I didnt try a make install, but i manually added the initrd section.

The same error popped up though:

VFS: Unable to mount root fs on unknown-block(0,0)

-- 
Marco Baan

There is no time like the present for postponing what you ought to be
doing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/