Kernel Panic error after 2.6.7 compile - please help
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Kernel Panic error after 2.6.7 compile - please help
I've just finished compiling 2.6.7 on Slackware 10 but when I reboot I get the following error.
Kernel panic : VFS: Unable to mount root fs on unknown-block(8,3)
My root file system is mounted on an Ext2 partition on sda3. Do I have to edit any files to include 'root=/dev/sda3' as they may be set to hda1? I'm pretty sure I checked the right options in the menuconfig to enable support for Ext2. My compile went smoothly (I followed a number of excellent guides in the forums here) and it starts to boot fine until it gets to the error. I've searched the forums and have found similar posts but they didn't help me. I decided to post here in case it has anything to do with slackware. Please help.
"Have you checked the config file for your bootloader?"
Do you mean menuconfig? My bootloader is LILO and it seems to be working : ie it dual-boots between windows and Linux properly. Also I've checked the 'lilo.conf' file and it seems to be ok.
"Have you successfully upgraded a kernel before? (say 2.6.6?)"
No. this is my first kernel compile. I was using the 2.4.26 kernel that came with the installation. I did compile the kernel before, but in a seriously reduced capacity. I forgot to check some important fields at the 'make menuconfig' stage.
"Did you run /sbin/lilo as the last step in your compilation?"
No. I ran it now to see if it would work but it didn't. I think I saw the same output it created (Added Windows, added linux etc.) during the main compile though. Would I have to recompile before running /sbin/lilo?
"Also, can you get in your system via a floppy? (I hope you made one )"
Yeah I've made the floppy (I've learned the hard way before) and have since performed a recompile but to no avail.
I use a SATA hard drive which I believe 2.6.7 supports. I think I saw some files containing the word sata being listed during the compile. I don't use a SCSI drive. I still tried entering the above line but got an error message. However without the square brackets I got the following output.
# SCSI device support
# SCSI support type (disk, tape, CD-ROM)
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# SCSI Transport Attributes
# SCSI low-level drivers
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
# CONFIG_SCSI_EATA_TAGGED_QUEUE is not set
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
# PCMCIA SCSI adapter support
Repeater: Cedrik is guiding you down one path - based on some assumptions which may be all to the good. Follw that too, but I have a niggle... this exact thing happened to me during my first kernel ugrade attempt. In my case, the origin was a misidentified root partition as you have suggested in your first post.
Since you are using lilo, it wouldn't hurt to take a sqiz at /boot/lilo.conf to see what it says. You should see an entry for windows, an entry for the 2.6.7 kernel and (hopefully it isn't erased) an entry for the old kernel as well. Compare the old kernel entry to the new one and look what is different - paying especial attention to anything that looks like a root partition ID.
This shouldn't take long.
Cedrik thought you had an scsi hdd because you said the root partition was sda3 and sda would ordinarily denote a scsi hdd, while hda3 would be an ide hdd. (just making sure you two are talking the same language here.)
As a pointer - should you ever recompile, use the option to save the config options to a file and keep it where you can easily find it again (like /root) that way you'll never have to wrack your brains to remember if you've checked that pesky option.
I never checked the option for NTFS support in the menuconfig and my windows (XP) paritition is visible to linux and mounted on /dev/sda1. Could this have been the problem? Anyway my boot disk got corrupted and I had to do a complete reinstall. Doesn't really matter, though, as I've only recently installled Slackware 10. I'll keep this thread open for a while, in case the same thing happens after I compile 2.6.7 now.
Hi. Back again. I've been having problems compiling the kernel ever since. I'm attempting to compile 2.6.8.1 now and I'm getting the exact same error as I was in the initial post. To answer earlier questions these are my outputs for the following commands.
perl -ne 'print if /^([^#]).*(scsi)/i' /usr/src/linux/.config
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.