kernel panic

Diminished7th · 05-28-2005, 09:11 PM

Yesterday evening I attempted to enable scsi emulation, as that's what xcdroast had been hassling me about. Anyways, one of the steps required was to add

Code:

append="hdc=ide-scsi"

into /etc/lilo.conf. So, I did that, saved and then restarted my box. And then, to my surprise, I get hit with

Code:

kmod: failed to exec /sbin/modprobe/ -s -k ide-disk, errno =2
           vfs: cannot open root device "303 or 03:03 
           Please append a correct "root=" boot option
           kernel panic: vfs: unable to mount root fs on 03:03
             <6>keyboard: unknown scancode    e0 7a

This takes place right after I boot "Linux-2.4.29" from lilo.

Now, does anyone have an idea as to what the hell is happening? I've been try to correct my error for about 4 hours. Removing that simple line seems to do nothing, so I most likely have altered a different file.

iggy_mon · 05-28-2005, 09:36 PM

from,
http://www.xcdroast.org/xcdr098/faq-a15.html#2

Note about configuring SCSI-emulation in Linux:
The trick are these two lines (Examples for two drives which are connected as master and slave on the secondary IDE controller):
Line for /etc/modules.conf
options ide-cd ignore='hdc hdd'
(This tells the IDE-driver to ignore the two devices you want to use within X-CD-Roast)
-
Line for /etc/lilo.conf (add anywhere before any "image=" lines)
append="hdc=ide-scsi hdd=ide-scsi" (Kernel 2.2.x and most 2.4.x)
or
append="hdc=scsi hdd=scsi" (Kernel 2.4.x only, if the above line does not work)
(And this tells the kernel to install scsi-emulation for two drives)

seems, maybe, you missed a step. also, check the default lilo.conf file to see if you messed up the "root=" line. just a few things to try.

--cheers
iggy_mon

Diminished7th · 05-28-2005, 09:55 PM

Thanks for the fast reply.

Well, recently I found out that I haven't compiled my kernel for scsi emulation support. I need ide-scsi.o and sg.o in "/lib/modules/2.4.29/kernel/drivers/scsi" which I do not. So, I've decided to abandon scsi-emulation, for a short while.

However, I still need to find out what adding append="hdc=ide-scsi" to lilo.conf has done to my setup. I can't even boot my kernel.

Quote:

check the default lilo.conf file to see if you messed up the "root=" line.

That was my original plan, but somehow I've managed to alter the default lilo.conf file. So, I don't really know what I use to have specified.

*EDIT*

Does anyone know what

Code:

append="hdc=ide-scsi"

has done to my lilo config?

Diminished7th · 05-29-2005, 02:11 PM

Maybe my question isn't clear enough? Please let me know.

I'm looking to restore my system to its state previous to

Code:

append="hdc=ide-scsi"

What has that line done and how can I repair its effects?

keefaz · 05-29-2005, 02:26 PM

Where did you add this line ? at the bottom of a kernel boot section ?
Is it the only thing you changed ?

Diminished7th · 05-29-2005, 05:03 PM

I added the line as shown in this example

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda3
prompt
timeout = 300
append="hdc=ide-scsi"
# VESA framebuffer console @ 1024x768x256
vga = 773

So, to answer, I added it at the top of my lilo.conf, and it is the only thing that I added.

egag · 05-29-2005, 05:06 PM

you've got the wrong spot...

---------
# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.11.7
root = /dev/hdb2
label = Linux-2.6.11.7
append="pci=usepirqmask idebus=66"
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
-----------

add it as shown above.

egag

Diminished7th · 05-29-2005, 05:20 PM

Wasn't paying attention...

Diminished7th · 05-29-2005, 09:33 PM

Yes well that doesn't seem to have worked, as I'm still greeted with

Code:

kmod: failed to exec /sbin/modprobe/ -s -k ide-disk, errno =2
           vfs: cannot open root device "303 or 03:03 
           Please append a correct "root=" boot option
           kernel panic: vfs: unable to mount root fs on 03:03
             <6>keyboard: unknown scancode    e0 7a

gbonvehi · 05-29-2005, 10:47 PM

Try removing the line and rerunning lilo, if you only changed that line, then your system will be like before.
As they suggested you've to put that line after the image= line that matches the kernel you want that paramater to be append.

Diminished7th · 05-29-2005, 11:02 PM

Maybe this is of importance:

I've been using a live-cd known as "Auditor," and that's how I've been able to edit my lilo.conf file this whole time.
However, attempting tp run lilo on this live-cd has failed. How else might I run lilo after I've appended my config?

*NOTE* I'm having to make these posts in a seperate windows partition that I luckily spared.

Namaseit · 05-29-2005, 11:19 PM

when you edit the file in order to run lilo on that partition you need to be "in" it so to speak. So you will need to do the following.
This is assuming you already have the partition mounted somwhere in /mnt on the livecd

user@comp# : mount -t proc proc /mnt/<whatever>/proc
user@comp# : chroot /mnt/<whatever>
user@# : lilo
user@# : exit

You should see the normal output of lilo
then just reboot

That is of course assuming you have lilo setup correctly, and/or your kernel is right.

Diminished7th · 05-29-2005, 11:41 PM

Hey Namaseit,

Things were looking good until i tried lilo and got

Code:

Fatal:   open   /dev/hda3  : Permission Denied

Any ideas?

It's indicating that it's a read-only file system.

gbonvehi · 05-30-2005, 01:25 AM

Which command are you using to mount your partition?

Diminished7th · 05-30-2005, 01:48 AM

I'm mounting with

Code:

mount /mnt/hda3

and then

Code:

mount -t proc proc /mnt/hda3/proc

followed by

Code:

chroot /mnt/hda3

and finally

Code:

lilo

which results in

Code:

fatal:  open  /dev/hda3:  permission denied