LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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

Reply
 
Search this Thread
Old 10-18-2004, 12:38 AM   #1
shaun85
LQ Newbie
 
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13

Rep: Reputation: 0
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.
 
Old 10-18-2004, 07:51 AM   #2
ilikejam
Senior Member
 
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109

Rep: Reputation: 96
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
 
Old 10-18-2004, 04:27 PM   #3
shaun85
LQ Newbie
 
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13

Original Poster
Rep: Reputation: 0
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
 
Old 10-18-2004, 04:49 PM   #4
Linux24
Member
 
Registered: Aug 2004
Distribution: Mandrake 10.1
Posts: 204

Rep: Reputation: 30
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.
 
Old 10-18-2004, 04:54 PM   #5
ilikejam
Senior Member
 
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109

Rep: Reputation: 96
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
 
Old 10-18-2004, 05:19 PM   #6
shaun85
LQ Newbie
 
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13

Original Poster
Rep: Reputation: 0
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?
 
Old 10-18-2004, 05:31 PM   #7
ilikejam
Senior Member
 
Registered: Aug 2003
Location: Glasgow
Distribution: Fedora / Solaris
Posts: 3,109

Rep: Reputation: 96
Sorry, I'm not realy familiar with lilo. I'd disregard my previous advice.

Did you re-run lilo after changing lilo.conf?

Dave
 
Old 10-18-2004, 05:32 PM   #8
shaun85
LQ Newbie
 
Registered: Oct 2004
Location: Lexington, SC
Distribution: Slackware 10
Posts: 13

Original Poster
Rep: Reputation: 0
yes, i re-ran lilo and it looked like it updated fine.
 
Old 10-18-2004, 11:40 PM   #9
Linux24
Member
 
Registered: Aug 2004
Distribution: Mandrake 10.1
Posts: 204

Rep: Reputation: 30
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.
 
Old 10-22-2004, 07:26 PM   #10
imrel
LQ Newbie
 
Registered: May 2004
Location: London / Uk
Distribution: Slackware 10.0
Posts: 11

Rep: Reputation: 0
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)



 
Old 07-16-2007, 04:20 PM   #11
ahmad82pkn
LQ Newbie
 
Registered: Oct 2005
Posts: 6

Rep: Reputation: 0
issue resolved by replacing the RAM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic problem with all of my kernels after installing new kernel nosebleed Linux - Software 2 04-14-2006 09:48 PM
kernel panic error after rebooting new kernel image fiero Linux - General 4 07-13-2005 08:32 AM
Kernel panic after installing new kernel h8dk97 Linux - Software 0 10-25-2004 08:45 PM
kernel recompile error (kernel panic) tombaaaaa Linux - Newbie 4 08-04-2004 04:32 PM
Problem booting up new kernel. Kernel panic error... RHLinuxGUY Red Hat 2 04-11-2004 04:59 AM


All times are GMT -5. The time now is 05:04 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration