Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
10-18-2004, 01:38 AM
|
#1
|
LQ Newbie
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13
Rep:
|
Installing Kernel 2.6.8.1 - Kernel Panic error
I just installed the 2.6.8.1 kernel on my slackware system, everything went well until I rebooted, it made it to a kernel panic and halted this is the message that it showed:
VFS: Cannot open root device "2101" or unknown-block (33,1)
Please append a correct "root=" boot option
Kernel Panic: VFS: Unable to mount rootfs on unknown-block (33,1)
I don't know what setting in the .config file might be causing this, any help would be greatly appreciated, thanks.
|
|
|
10-18-2004, 08:51 AM
|
#2
|
Senior Member
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109
Rep:
|
Hi.
Try removing the root=xxx part from the kernel arguments in /boot/grub/grub.conf (or from lilo.conf, depending on whether you're using lilo or grub).
The kernel knows which partition should be '/' as long as the disks are in the same configuration as they were when the kernel was compiled.
Dave
|
|
|
10-18-2004, 05:27 PM
|
#3
|
LQ Newbie
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13
Original Poster
Rep:
|
Hey,
I just tried doing that, but i get the exact same error message, but it changes from VFS: Cannot open root device "2102" to VFS: Cannot open root device"<null>". Could it possibly be something I missed in the configuration? I was pretty thorough going through it.
Thanks,
Shaun
|
|
|
10-18-2004, 05:49 PM
|
#4
|
Member
Registered: Aug 2004
Distribution: Mandrake 10.1
Posts: 204
Rep:
|
Quote:
Originally posted by shaun85
Hey,
I just tried doing that, but i get the exact same error message, but it changes from VFS: Cannot open root device "2102" to VFS: Cannot open root device"<null>". Could it possibly be something I missed in the configuration? I was pretty thorough going through it.
Thanks,
Shaun
|
I recently had this happen compiling a new kernel.
Did you save your config file? Look inside and you'll probably find EXT3 or whatever your root filesystem is compiled as a module.
If you go back and recompile with it inside the kernel without *starting all over*, it won't take (in my expeirence), so your best bet is to save your config file to your desktop or somewhere, start over, and then pull the config file in again, and then go through it and check your filesystem settings.
|
|
|
10-18-2004, 05:54 PM
|
#5
|
Senior Member
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109
Rep:
|
Did you remove the whole of 'root=xx'?
E.g. my grub.conf reads:
Code:
default=0
title GNU/Linux-2.6.8.1/ILikeJam
root (hd0,0)
kernel /vmlinuz-2.6.8.1
That's all that should be needed if the kernel was compiled on the same system as it's running.
Dave
|
|
|
10-18-2004, 06:19 PM
|
#6
|
LQ Newbie
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13
Original Poster
Rep:
|
This is in my lilo.conf file:
image = /boot/vmlinuz
label = Linux-2.6.8.1
read-only
Am i missing anything there? I just removed the root= line, my other kernel lines are:
image = /boot/vmlinuz-ide-2.4.26
root = /dev/hde1
label = Linux-2.4.26
read-only
and it works fine to boot that kernel. I am going to try to recompile the kernel and see if it works, but I had ext2 and ext3 set as *'s not M, so i don't think that it would change any, are there any other settings that might cause it to halt like this?
|
|
|
10-18-2004, 06:31 PM
|
#7
|
Senior Member
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109
Rep:
|
Sorry, I'm not realy familiar with lilo. I'd disregard my previous advice.
Did you re-run lilo after changing lilo.conf?
Dave
|
|
|
10-18-2004, 06:32 PM
|
#8
|
LQ Newbie
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13
Original Poster
Rep:
|
yes, i re-ran lilo and it looked like it updated fine.
|
|
|
10-19-2004, 12:40 AM
|
#9
|
Member
Registered: Aug 2004
Distribution: Mandrake 10.1
Posts: 204
Rep:
|
Quote:
Originally posted by shaun85
This is in my lilo.conf file:
image = /boot/vmlinuz
label = Linux-2.6.8.1
read-only
Am i missing anything there? I just removed the root= line, my other kernel lines are:
image = /boot/vmlinuz-ide-2.4.26
root = /dev/hde1
label = Linux-2.4.26
read-only
and it works fine to boot that kernel. I am going to try to recompile the kernel and see if it works, but I had ext2 and ext3 set as *'s not M, so i don't think that it would change any, are there any other settings that might cause it to halt like this?
|
Is vmlinuz the name of the file in /boot with a .img ending for that kernel? your compiled kernel is called vmlinuz.img? Usually you call it something else so you know it is a custom job.
I would put the root thing back in and re-run lilo.
|
|
|
10-22-2004, 08:26 PM
|
#10
|
LQ Newbie
Registered: May 2004
Location: London / Uk
Distribution: Slackware 10.0
Posts: 11
Rep:
|
i have the same problem
hi everybody
now i have the same problem with slack 10 and kernel 2.6.8.1 i did read everything but i didnt understand is there any solution of this problem if there is a solution could sombedy tel me how thanks
VFS: Cannot open root device "2101" or unknown-block (33,1)
Please append a correct "root=" boot option
Kernel Panic: VFS: Unable to mount rootfs on unknown-block (33,1)
|
|
|
07-16-2007, 05:20 PM
|
#11
|
LQ Newbie
Registered: Oct 2005
Posts: 6
Rep:
|
issue resolved by replacing the RAM.
|
|
|
All times are GMT -5. The time now is 05:39 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|