failure to mount root fs
Hi Macro,
Quoted 3 lines · You
VFS: Unable to mount root fs on unknown-block(0,0)
...
kernel/boot/bzImage-2.6.4ro 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
Quoted 11 lines
Quoted 3 lines
VFS: Unable to mount root fs on unknown-block(0,0)
...
kernel/boot/bzImage-2.6.4ro 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.4ro 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.
Signature · 5 lines
Marco Baan "MacDonald has the gift on compressing the largest amount of words into the smallest amount of thoughts." -- Winston Churchill
Quoted 10 lines · On Mon, 2004-03-29 at 13:29, [email protected] wrote:
Hi Macro,
Quoted 3 lines · You
VFS: Unable to mount root fs on unknown-block(0,0)
...
kernel/boot/bzImage-2.6.4ro 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)
Quoted 8 lines
Quoted 8 lines
Hi Macro,
Quoted 3 lines · You
VFS: Unable to mount root fs on unknown-block(0,0)
...
kernel/boot/bzImage-2.6.4ro root=LABEL=/
Quoted 5 lines
Quoted 2 lines
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)
Signature · 4 lines
Marco Baan There is no time like the present for postponing what you ought to be doing.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 9 lines · Arjan van de Ven
Quoted 8 lines · On Mon, 2004-03-29 at 13:29, [email protected] wrote:
Hi Macro,
Quoted 3 lines · You
VFS: Unable to mount root fs on unknown-block(0,0)
...
kernel/boot/bzImage-2.6.4ro root=LABEL=/
Quoted 5 lines
Quoted 2 lines
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=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_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
\ / [email protected]
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-----
Quoted 12 lines · Arjan van de Ven
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=yCONFIG_BLK_DEV_IDE=yCONFIG_BLK_DEV_IDEDISK=yCONFIG_IDEDISK_MULTI_MODE=y
Quoted 6 lines
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.
Signature · 6 lines
Marco Baan On a paper submitted by a physicist colleague: "This isn't right. This isn't even wrong." -- Wolfgang Pauli