Hey all,
I have a P4 2.4 GHz CPU (hyper threading) and have been using the 2.4.21-20.EL.c0smp kernel and it works perfectly.
I installed the new kernel-smp (2.4.21-20.0.1.EL) kernel and it installed flawlessly. However, every time I boot I get a kernel panic and I must reboot to the older kernel.
The error I am getting is: (it seems to be failing on jbd.o and ext3.o)
Kernel requires old insmod, but couldn't run /bin/insmod.old No such file or directory
Then it can't find the initrd and Panics.
I am running a single partition on my software RAID1, the file system is ext3.
[root@admin /]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 115377576 2014940 107501728 2% /
none 512700 0 512700 0% /dev/shm
[root@admin /]#
I just can't seem to figure it out. I've done some searching online but the fixes people are posting just don't seem logical as my initrd IS there.
[root@admin /]# ls -al /boot/*2.4.21-20.0.1.EL*
-rw-r--r-- 1 root root 48514 Dec 2 18:38 /boot/config-2.4.21-20.0.1.ELsmp
-rw-r--r-- 1 root root 306034 Dec 3 16:13 /boot/initrd-2.4.21-20.0.1.ELsmp.img
-rw-r--r-- 1 root root 601959 Dec 2 18:38 /boot/System.map-2.4.21-20.0.1.ELsmp
-rwxr-xr-x 1 root root 3523220 Dec 2 18:38 /boot/vmlinux-2.4.21-20.0.1.ELsmp
-rw-r--r-- 1 root root 1353893 Dec 2 18:38 /boot/vmlinuz-2.4.21-20.0.1.ELsmp
[root@admin /]#
Any help would be greatly appreciated as I would like to put this machine into production soon.
Regards,
Josh
Josh,
Sounds like a strange problem indeed. Off the top of my head, try running mkinitrd manually for the new kernel (in verbose mode), to make sure that it is preloading all of the modules necessary to boot your / filesystem. Specifically make sure it is loading the raid1 module, and the ext3 module (assuming / is formatted ext3). Also, if your drives are other than regular IDE (scsi or sata), make sure the appropriate scsi or sata modules are getting loaded. To run mkinitrd in verbose mode, just pass it the -v flag. So in this case your command would look like this:
mkinitrd -f -v /boot/initrd-2.4.21-20.0.1.ELsmp.img 2.4.21-20.0.1.ELsmp
Try that first to make sure the modules are getting loaded.
-Ryan
That worked!
I guess the installation of the RPM had an issue with raid1, jbd, and ext3 modules and including them in initrd.
[root@admin root]# uname -a Linux admin.eleet-tech.com 2.4.21-20.0.1.ELsmp #1 SMP Thu Dec 2 23:06:40 GMT 2004 i686 i686 i386 GNU/Linux
Thanks for the help! If all goes well over the next few days of testing this box will become production!
Thanks, --Josh
-----Original Message----- From: centos-admin@caosity.org [mailto:centos-admin@caosity.org] On Behalf Of Ryan Lane Sent: Friday, December 10, 2004 8:19 AM To: Joshua Strzalko Cc: CentOS@caosity.org Subject: Re: [Centos] Kernel Panic on New Kernel Package
Josh,
Sounds like a strange problem indeed. Off the top of my head, try running mkinitrd manually for the new kernel (in verbose mode), to make sure that it is preloading all of the modules necessary to boot your / filesystem. Specifically make sure it is loading the raid1 module, and the ext3 module (assuming / is formatted ext3). Also, if your drives are other than regular IDE (scsi or sata), make sure the appropriate scsi or sata modules are getting loaded. To run mkinitrd in verbose mode, just pass it the -v flag. So in this case your command would look like this:
mkinitrd -f -v /boot/initrd-2.4.21-20.0.1.ELsmp.img 2.4.21-20.0.1.ELsmp
Try that first to make sure the modules are getting loaded.
-Ryan _______________________________________________ CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
-
Joshua Strzalko -
Ryan Lane