[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: kernel whoops



Matt Whiteley wrote:

On Wed, 2003-07-23 at 18:38, Samuel Flory wrote:


That would be because you can't load your loop module as it was removed by rpm.



mkinitrd failed
error: %post(kernel-2.4.21-20.1.2024.2.1.nptl) scriptlet failed, exit status 1
[root alt html]# rpm -q kernel
kernel-2.6.0-0.test1.1.26
kernel-2.4.21-20.1.2024.2.1.nptl





Please tell me you haven't removed the 2.5 kernel you installed, and that it has a valid initrd in /boot? Other wise find a redhat install cdrom and boot it with "linux rescue".

PS- Why doesn't redhat build the loop driver directily into the kernel!!! People do this all the time.



No, I didn't remove the 2.6 test kernel and here is the directory listing at /boot: [root alt html]# ls /boot/ config-2.4.21-20.1.2024.2.1.nptl System.map config-2.6.0-0.test1.1.26 System.map-2.4.21-20.1.2024.2.1.nptl grub System.map-2.6.0-0.test1.1.26 initrd-2.6.0-0.test1.1.26.img vmlinux-2.4.21-20.1.2024.2.1.nptl kernel.h vmlinux-2.6.0-0.test1.1.26 lost+found vmlinuz message vmlinuz-2.4.21-20.1.2024.2.1.nptl message.ja vmlinuz-2.6.0-0.test1.1.26

So, what do I need to do to repair and make bootable the 2.4 kernel?



Well you can try to boot the 2.6 kernel and hope you don't run into any issues booting. Then try the following:
mkinitrd -v /boot/initrd-2.4.21-20.1.2024.2.1.nptl.img 2.4.21-20.1.2024.2.1.nptl


Otherwise you will need to boot some sort of rescue disk like the install in rescue mode, and try the following:
-chroot /mnt/sysimage
-mkinitrd -v /boot/initrd-2.4.21-20.1.2024.2.1.nptl.img 2.4.21-20.1.2024.2.1.nptl



-- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) Sam Flory <sflory rackable com>





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]