i get kernel panic - not syncing: vfs:...while booting

[Sovtek]

I missed putting that space in (between the root and hd). So yeah, it's already there, and there's still the kernel panic.

Could I have done something wrong during the install process? Should I just reformat and reinstall or something?

Thanks

[junkman4547]

on your grub.conf file....shouldn't

real_root=/dev/hda3 ?

[drakebasher]

Good eye, junkman4547, If the fstab that jaboua shows a few posts up is right, real_root=/dev/hda3

Additionally, since /boot is on /dev/hda1, the kernel statement should not include a path through /boot:

kernel /kernel-genkernel-x86-2.6.12-gentoo-r6 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3

But apparently, since the kernel loads, this isn't a serious problem. But misplacing real_root is.

[shinkschn]

I had the same problem and the solution was to change root=/dev/ram0 by root=/dev/hda3

As far as I know this is uncorrect and shouldn't work ... but it's actually working on my computer ...

I really don't understand why you should put your /dev/ram0 as root and specify a real_root when you use genkernelall and not when manually compiling the kernel ...

Perhaps it will cause me serious problems laters using root as my real_root and not the ram, I'm currently gathering infos about genkernel ...

Either way perhaps you should test ...

[Sovtek]

So I made the appropriate changes to the grub.conf and still no joy. I've been told by one source, that I NEED to have an initrd. I know this has been discussed already, but once again, what would it do if I re-emerged and ran genkernel all?

Would it damage anything, or create any duplicates? Would it overwrite anything?

Is it even advisable or would it be a logical step?

I would exectue it like this:

mount /dev/hda3 /mnt/gentoo
mount /dev/hda1 /mnt/gentoo/boot
mount -t proc none /mnt/gentoo/proc
chroot /mnt/gentoo /bin/bash
env-update
(and finally)
emerge genkernel
genkernel all

The idea behind this would be in hopes of genkernel actually creating an initrd, or perhaps config-ing something correctly this time... Any opinions?

[jaboua]

It will probably not duplicate anything.

It won't damage anything.

It will overwrite the current kernel.

I would advise you to try, if not perhaps trying to roll your own kernel...

[Sovtek]

Jaboua, you're right on the money. I fixed this sucker. So here's the answer folks...

DON'T USE GENKERNEL.

I completely reformatted, reinstalled a stage 3, and config-ed my own kernel in like, a few hours.

Works just fine now, So I know it was genkernel that was causing the issues. It seems that it's not so good at auto configing.

Anyhow, THANK YOU to anyone and everyone who posted here.

(Resolved)

[drakebasher]

DON'T USE GENKERNEL.

That's a bit harsh. I'm sure I'm not the only one who has sucessfully installed with Genkernel! I don't think there is any system/method that works for all without some allowance.

[asquante]

Hello all!
I'm trying to install gentoo now, but get same messange as in the first post:
Please append a correct "root=" boot option
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Here's my grub.conf:
timeout 7
default 0
title Gentoo
root (hd0,0)
kernel /boot/gentoo-2.6.17 root=/dev/hda1

Here's my fstab:
/dev/hda1 / ext3 noatime,noauto,notail 0 1
/dev/hda2 none swap sw 0 0
/dev/hda3 /root reiserfs user,noatime 0 0

I use menuconfig to set up the kernel. I build reiser and ext2 / ext3 support into the kernel (not as module) and have tried everything i could think of, but still get the same error.
Any ideas will be appreciated.

mARGO