Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - General
User Name
Linux - General This 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.


  Search this Thread
Old 02-03-2004, 10:36 AM   #1
Registered: Oct 2003
Location: MN
Distribution: CentOS, Fedora
Posts: 182

Rep: Reputation: 30
More kernel panic errors on 2.6.1

Like others, I am trying to successfully compile and run the new 2.6.1 kernel, but I'm running into some problems. Specifically, I'm hitting this when I try to boot into the new kernel:

VFS: Cannot open root device "sda2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
This seems to be a pretty common error, as it came up a lot when I was searching. So far then, I've recompiled several times, trying the following:

- compile SCSI card directly in, and as a module
- compile ext3 fs in and as a module
- compile SCSI support and disk access in and as modules

Right now, my SCSI card is set up as a module, only because when I initially installed the OS (RedHat Enterprise Server 3), it loaded it as a module, and the only way to get the new kernel to compile is to comment out the SCSI card line in the modules.conf file. I can see it load the megaraid.ko modules before it hits the kernel panic, so I think it's loading the module correctly.. I just don't know why it's not able to mount it now. Support for all filesystems (ext3 on root), SCSI support and disk access are all compiled in. And no matter what combo I try, I just can't seem to get this thing to boot up. So, I'm looking for any advice on what else I can try. Relevant hardware info is:

RH ES 3 (Kernel 2.4.21-9 running ok)
LSI MegaRAID Ultra 320-1 (1 array, RAID 5, 140GB)
- designated /dev/sda
- sda1 = boot (ext3)
- sda2 = / (ext3)
- sda3 - swap

Grub.conf (relevant lines):

title Red Hat Enterprise Linux ES (2.6.1)
root (hd0,0)
kernel /vmlinuz-2.6.1 ro root=/dev/sda2
initrd /initrd-2.6.1.img

Any advice anyone could provide would be very much appreciated.

Old 02-03-2004, 02:38 PM   #2
Registered: Oct 2003
Location: MN
Distribution: CentOS, Fedora
Posts: 182

Original Poster
Rep: Reputation: 30
Just to update this... I contacted LSI about it, asking if they had any suggestions on how to get it working under the new kernel. This was their reply:

I put this question to one of my linux driver developers, and below is his response. It seems that the 2.6.1 kernel just doesn't have vendor and device id's for our newer controllers.


They should add the controller's vendor and device id in the driver code.
This is very straightforward.
But, for something that is supposedly so straightforward, they didn't include any suggestions. So, now it seems that I'm close to getting this to work, but I don't know where to find these ID numbers, and I don't know where to put them (driver code?). Might anyone know how to go about doing this?
Old 02-03-2004, 05:07 PM   #3
Registered: Oct 2003
Distribution: Mandrake 10
Posts: 160

Rep: Reputation: 30
I had this problem and it was because my root filesystem wasn't compiled in. Triple check that /boot is on an ext3 partition, and make sure that ext3 is compiled in.
Old 02-04-2004, 08:30 AM   #4
Registered: Oct 2003
Location: MN
Distribution: CentOS, Fedora
Posts: 182

Original Poster
Rep: Reputation: 30
Ok, I went back through my kernel config, and ext3 is definitely compiled in, and my / partition is definitely on an ext3 filesystem. However, I heard back from LSI about the driver for my SCSI card and changed 1 line in the source file and recompiled again, which got me past the original error about being unable to mount the root filesystem. Here is the new error I'm getting now when I try to boot:

Mounting root filesystem
mount: missing device
ERROR: failed in exec of defaults
ERROR: failed in exec of ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd)failed: 2
umount /initrd/proc failed: 2
ERROR: ext3 exited abnormally
Kernel panic: No init found. Try passing init= option to kernel.
It looks to me like the "mount: missing device" error is the cause, but I don't know why it would be having that problem. I see it identify the SCSI card before it gets to this point. I have tried changing the grub.conf file to point to the device itself (root=/dev/sda2) as well as the default (root=LABEL=/) but they both come back with this same error. Any ideas on this new error?

EDIT: Nevermind... Just downloaded and compiled the newly released 2.6.2 kernel and everything worked right away. I didn't have to do anything different even! It looks like there were some PCI ID issues fixed in the newest version though for the MegaRAID cards, so I'm thinking that was the cause all along. At least it works now though!

Last edited by Phaethar; 02-04-2004 at 09:51 AM.


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 On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
apt-get errors and kernel panic kdogksu Debian 4 04-18-2005 09:16 PM
Kernel panic puts me in a panic theeeg Linux - Software 2 07-31-2004 04:46 PM
Errors during filesystem check with one kernel while no errors with other kernel Potentials Linux - General 11 12-30-2003 04:24 AM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 03:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 12:31 AM > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 09:39 AM.

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