(please help) Kernel Panic: unable to mount root FS -- boot problems with 2.4.2x
Howdy, I'm having a lot of trouble booting after installing the latest kernel rpm. I keep getting kernel panics if I try to boot linux_2.4. It works fine if I boot the image named "suse". I've tried manually giving it the root=/dev/sda4 option but it doesn't like that either. I also tried using the CDs "boot installed system" option, and it tells me that /dev/sda4 isn't a valid root device. I tried using the rescue system to mount that partition and is says it isn't a valid block device, however I think that's a module problem i.e. there's not a SCSI module included in the rescue system. As I said, I can boot if I use the "suse" lilo image, but I get lots of errors about modules. What is the "suse" image? I do not have a 2.2.x kernel installed. Is it safe to run depmod while booted into the "suse" image? Or will that make things worse? Everything was working fine until installed the latest 2.4.2x kernel from the update dir of ftp.suse.com. BTW /dev/sda4 is where / is, and it's a ReiserFS partition. /dev/sda3 is /boot and dev/sda2 is swap. Any help/advise would be greatly appreciated TIA, ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
I had the similar problem with 2.4.2 rpm's, on some machines it choked while loading image, while on others it panicked; I've decided it's not worth my time, since custom compile from 2.4.3 sources worked like a charm. j. Jonathan Wilson wrote:
Howdy,
I'm having a lot of trouble booting after installing the latest kernel rpm. I keep getting kernel panics if I try to boot linux_2.4. It works fine if I boot the image named "suse".
I've tried manually giving it the root=/dev/sda4 option but it doesn't like that either.
I also tried using the CDs "boot installed system" option, and it tells me that /dev/sda4 isn't a valid root device. I tried using the rescue system to mount that partition and is says it isn't a valid block device, however I think that's a module problem i.e. there's not a SCSI module included in the rescue system.
As I said, I can boot if I use the "suse" lilo image, but I get lots of errors about modules.
What is the "suse" image? I do not have a 2.2.x kernel installed. Is it safe to run depmod while booted into the "suse" image? Or will that make things worse?
Everything was working fine until installed the latest 2.4.2x kernel from the update dir of ftp.suse.com.
BTW /dev/sda4 is where / is, and it's a ReiserFS partition. /dev/sda3 is /boot and dev/sda2 is swap.
Any help/advise would be greatly appreciated
TIA,
---------------------------------------------------- Jonathan Wilson System Administrator
Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- ("`-''-/").___..--''"`-._ Jerzy Prekurat `o_ o ) `-. ( ).`-.__.`) Director of Network Development (_Y_.)' ._ ) `._ `. ``-..-' Canadian Bank Note Co. Ltd. _..`--'_..-_/ /--'_.' .' 613-225-6566 ext. 350 (il).-'' (li).' ((!.-' jerzy@cbnco.com ------------------------------------------------------------------ Life is just a feature of EMACS.
Howdy,
I'm having a lot of trouble booting after installing the latest kernel rpm. I keep getting kernel panics if I try to boot linux_2.4. It works fine if I boot the image named "suse".
I've tried manually giving it the root=/dev/sda4 option but it doesn't
Jonathan, like that either.
I also tried using the CDs "boot installed system" option, and it tells
me that /dev/sda4 isn't a valid root device. I tried using the rescue system to mount that partition and is says it isn't a valid block device, however I think that's a module problem i.e. there's not a SCSI module included in the rescue system.
As I said, I can boot if I use the "suse" lilo image, but I get lots of
errors about modules.
What is the "suse" image? I do not have a 2.2.x kernel installed. Is it
safe to run depmod while booted into the "suse" image? Or will that make things worse?
Everything was working fine until installed the latest 2.4.2x kernel
from the update dir of ftp.suse.com.
BTW /dev/sda4 is where / is, and it's a ReiserFS partition. /dev/sda3
is /boot and dev/sda2 is swap.
Any help/advise would be greatly appreciated
This sounds very like the problem i had updating the kernel from RPMs and I am also running 2.4.2-64GB-SMP kernel from the k_deflt24 rpm. In my case the problem was that the SCSI driver module is not compiled into the kernel, but in a module that has to be loaded, which it can't do if /lib/modules is on the SCSI drive. On the advice of someone from this list I did mk_initrd to create an initial ramdisk then put the Initrd file in the /boot directory (which is in a separate partition on an IDE drive). You then need to put the line initrd = /boot/initrd.suse24 (or whatever you called it) in the /etc/lilo.conf file and re-run lilo. I don't know how you get round this problem if the /boot partition is on a SCSI drive, maybe someone out there with an all SCSI machine can enlighten us. Hope this helps, Mark
participants (3)
-
Jerzy Prekurat -
Mark Daglish -
wilson＠claborn.net