* Re: failure to mount root fs
@ 2004-03-29 11:29 tigran
2004-03-29 11:38 ` Marco Baan
2004-03-29 12:00 ` Arjan van de Ven
0 siblings, 2 replies; 6+ messages in thread
From: tigran @ 2004-03-29 11:29 UTC (permalink / raw)
To: Marco Baan; +Cc: linux-kernel
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):
kernel /boot/bzImage-2.6.4 ro root=/dev/hda2
(this assumes that your root fs is on /dev/hda2, change it appropriately to match your situation)
Kind regards
Tigran
Freeserve AnyTime - HALF PRICE for the first 3 months - Save £7.50 a month
www.freeserve.com/anytime
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: failure to mount root fs
2004-03-29 11:29 failure to mount root fs tigran
@ 2004-03-29 11:38 ` Marco Baan
2004-03-29 12:00 ` Arjan van de Ven
1 sibling, 0 replies; 6+ messages in thread
From: Marco Baan @ 2004-03-29 11:38 UTC (permalink / raw)
To: linux-kernel
> > 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):
>
> kernel /boot/bzImage-2.6.4 ro root=/dev/hda2
>
> (this assumes that your root fs is on /dev/hda2, change it appropriately to match your situation)
>
Okay, changed it. Didnt make a difference however.
--
Marco Baan
"MacDonald has the gift on compressing the largest amount of words into
the smallest amount of thoughts."
-- Winston Churchill
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: failure to mount root fs
2004-03-29 11:29 failure to mount root fs tigran
2004-03-29 11:38 ` Marco Baan
@ 2004-03-29 12:00 ` Arjan van de Ven
2004-03-29 12:05 ` Marco Baan
2004-03-29 14:42 ` Marcos D. Marado Torres
1 sibling, 2 replies; 6+ messages in thread
From: Arjan van de Ven @ 2004-03-29 12:00 UTC (permalink / raw)
To: tigran; +Cc: Marco Baan, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Mon, 2004-03-29 at 13:29, tigran@aivazian.fsnet.co.uk wrote:
> 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)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: failure to mount root fs
2004-03-29 12:00 ` Arjan van de Ven
@ 2004-03-29 12:05 ` Marco Baan
2004-03-29 14:42 ` Marcos D. Marado Torres
1 sibling, 0 replies; 6+ messages in thread
From: Marco Baan @ 2004-03-29 12:05 UTC (permalink / raw)
To: linux-kernel
> > 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: failure to mount root fs
2004-03-29 12:00 ` Arjan van de Ven
2004-03-29 12:05 ` Marco Baan
@ 2004-03-29 14:42 ` Marcos D. Marado Torres
2004-03-29 21:47 ` Marco Baan
1 sibling, 1 reply; 6+ messages in thread
From: Marcos D. Marado Torres @ 2004-03-29 14:42 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: tigran, Marco Baan, linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 29 Mar 2004, Arjan van de Ven wrote:
> On Mon, 2004-03-29 at 13:29, tigran@aivazian.fsnet.co.uk wrote:
> > 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)
It doesn't solve the problem, I have the same issue... And seeing kerneltrap
forums, we're not the only ones.
I fixed that problem by changing .config (it seems that oldconfig messed it) to
show:
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
Now I don't get the
VFS: Unable to mount root fs on unknown-block(0,0)
but when booting, it shows:
VFS: Mounted root (ext3 filesystem) readonly.
and then just freezes.
Any thoughts on this?
(if needed, my config is in http://student.dei.uc.pt/~marado/.config )
Best regards,
Mind Booster Noori
- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@student.dei.uc.pt
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFAaDXgmNlq8m+oD34RAtjvAKD2c2CxntbDwIyTdlLbxcKpYCDmVwCg3Vzt
18I2v/gWkGYpr1qPlFsSCmA=
=B7uM
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: failure to mount root fs
2004-03-29 14:42 ` Marcos D. Marado Torres
@ 2004-03-29 21:47 ` Marco Baan
0 siblings, 0 replies; 6+ messages in thread
From: Marco Baan @ 2004-03-29 21:47 UTC (permalink / raw)
To: linux-kernel
> On Mon, 29 Mar 2004, Arjan van de Ven wrote:
>
> It doesn't solve the problem, I have the same issue... And seeing kerneltrap
> forums, we're not the only ones.
> I fixed that problem by changing .config (it seems that oldconfig messed it) to
> show:
>
> CONFIG_IDE=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_IDEDISK_MULTI_MODE=y
>
> Now I don't get the
> VFS: Unable to mount root fs on unknown-block(0,0)
>
> but when booting, it shows:
> VFS: Mounted root (ext3 filesystem) readonly.
>
I tried your config and the options. I dont get the readonly error though. Just the same error as before.
--
Marco Baan
On a paper submitted by a physicist colleague:
"This isn't right. This isn't even wrong."
-- Wolfgang Pauli
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-03-29 21:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-29 11:29 failure to mount root fs tigran
2004-03-29 11:38 ` Marco Baan
2004-03-29 12:00 ` Arjan van de Ven
2004-03-29 12:05 ` Marco Baan
2004-03-29 14:42 ` Marcos D. Marado Torres
2004-03-29 21:47 ` Marco Baan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox