Got "Kernel panic" but WHY ?

nykey · 06-04-2006, 01:40 PM

Ok, so I get this message:

Quote:

VFS: Cannot open root device "1641" or unknown-block (22,65)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (22,65)

I just recompiled my kernel, I have 2 partitions with ext2 fs (wich I enabled in kernel .config with ext3 support also just in case). I have my slackware install on my second hard drive "hdd" and when I run lilo I get this error message

Quote:

root@nykey:~# lilo
Warning: The boot sector and map file are on different disks.
Added Slack-2.6.16.19 *
Added Slack-2.6.13
root@nykey:~#

Does this have something to do with my Kernel panic ? I don't even have the partitions from my first hard drive "hda" in fstab and that's not it cause my other kernel boots.Here is lilo.conf

Quote:

root@nykey:~# cat /etc/lilo.conf
boot = /dev/hda
prompt
timeout = 50
vga = 791
image = /boot/vmlinuz
root = /dev/hdd1
label = Slack-2.6.16.19
read-only # Non-UMSDOS filesystems should be mounted read-only for checking

image = /boot/vmlinuz.old
root = /dev/hdd1
label = Slack-2.6.13
read-only # Non-UMSDOS filesystems should be mounted read-only for checking

fstab

Quote:

root@nykey:~# cat /etc/fstab
/dev/hdd3 swap swap defaults 0 0
/dev/hdd1 / ext2 defaults 1 1
/dev/hdd2 /home ext2 defaults 1 2
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0

Hopefully someone will answer, untill then I'll play with options in kernel .config

MannyNix · 06-04-2006, 02:11 PM

may help with lilo, gotta go now
http://www.linuxquestions.org/questi...18#post2236518

nykey · 06-04-2006, 02:27 PM

Well the thing is that I've booted with lilo before even with that warning message. I just recompiled kernel to remove some unusefull stuff and beats me what I removed and now get Kernel Panic. It's not from the File System because I enabled all options under FS and still got the panic, so it looks like I have to do it again, and just be more carefull.

Bruce Hill · 06-04-2006, 06:44 PM

In your kernel you must have "CONFIG_EXT2_FS=Y" -- to boot EXT2, no matter what other fs options.

Code:

mingdao@james:~$ cat kernel/linux-2.6.16.19/.config | grep -i ext2
# CONFIG_EXT2_FS is not set
mingdao@james:~$ cat kernel/linux-2.6.16.19/.config | grep -i reiserfs
CONFIG_REISERFS_FS=y

Just two examples -- I user ReiserFS, not ext.

You also need support for your IDE controller built-in your kernel, such as:

Code:

mingdao@james:~$ cat kernel/linux-2.6.16.19/.config | grep -i PIIX
CONFIG_BLK_DEV_PIIX=y

which is for the Intel ICH5 controller on that box.

And LiLO should be installed to the MBR, which is on /dev/hda --
that warning message is just that, a warning -- LiLO will still
boot with the boot sector and map file on different disks.

osor · 06-04-2006, 07:42 PM

Make sure ext2/3 and ide drivers are built-in (NOT modules).

Also, too hard to resist:

Quote:

Originally Posted by nykey

...unusefull stuff...

should be useless stuff

.

cb951303 · 06-04-2006, 08:18 PM

Quote:

CONFIG_EXT2_FS=Y

that's not necessary if you're not using ext2.
in my config only fs enabled is reiserfs and it works like a charm....

you may get a Kernel Panic if you try to compile your root and boot filesystem as a Module (M)
if so try compiling them statically (built-in)

wini_g · 06-04-2006, 08:23 PM

I just read that CramFS needs to be included in some recent distros for you to boot successfully .