Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am getting a kernel panic messgae that says "kernel panic - not syncing: VFS : unable to mount root fs on unknown - block (3,3) here is a copy of my lilo.conf:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.13
initrd = /boot/initrd.gz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
I am getting a kernel panic messgae that says "kernel panic - not syncing: VFS : unable to mount root fs on unknown - block (3,3) here is a copy of my lilo.conf:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.13
initrd = /boot/initrd.gz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
Any ideas?
Compile the filesystems straight in the kernel instead as module.
Also the chipset and IDE drivers should be build in the kernel and not as modules
I am getting a kernel panic messgae that says "kernel panic - not syncing: VFS : unable to mount root fs on unknown - block (3,3) here is a copy of my lilo.conf:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.13
initrd = /boot/initrd.gz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends
Any ideas?
Did you make an initrd with the root partition's filesystem? Slack kernels from testing need that if you have a non ext2 root partition. There's a text file in /boot with info on that, something like README.initrd.
A "kernel panic" occurs when the system encounters a situation where it cannot continue. It halts and starts blinking the keyboard lights in (believe it or not...) morse code.
The phrase "not syncing" actually means that, when going into the panic, the kernel was able to write all unsaved information to disk before actually halting. The comma between "kernel panic" and "not syncing" does not mean "because..."
At this point in the process, the kernel is looking for a mountable filesystem on partition #3. This must be the root partition, not the boot partition! It must have a valid filesystem and the kernel must have a usable driver for it .. either because it was compiled-in or because the 'initrd' process found and loaded one.
Probably the best thing to look for at this point is .. a simple typographic error of some sort. Boot up a LiveCD and have a look around: what type of filesystem is it, where is it actually located, and so on. Carefully check the contents of the boot loader config-file, and don't forget to re-run lilo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.