FC3T2 - 598 & 603 kernel fail boot
Matias Féliciano
feliciano.matias at free.fr
Sun Oct 10 02:29:54 UTC 2004
Le samedi 09 octobre 2004 à 13:59 -0400, John Soltow (Sabre) a écrit :
> My 541 kernel continues to boot, but since "yum --obsoletes update",
> the 598 and 603 kernels fail.
>
> ======boot snippet from the 603 kernel====== - hand copied so apologies
> for errors/typos
> Uncompressing Linux... OK, booting the kernel
> Audit (1097327214.140:0): initialized
> Red hat nash version 4.1.14 starting
> insmod: error inserting '/lib/ext3.ko': -1 Unknown Symbol in module
> ERROR: /bin/insmod exiting normally!
> mount: error 19 mounting ext3
> mount: error 2 mounting none
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel Panic - not syncing Attempted to kill init
>
>
> ==========end boot snippet===============
>
> First, ext3.ko is in /lib/modules/2.6.8.1.603/kernel/fs/ext3/ and
> not in /lib
>
> Can someone enlighten me as to what I've done wrong? As I said
> earlier, the 541 kernel works.
>
The boot sequence depend on initrd build by mkinitrd.
rebuild initrd :
mkinitrd /boot/initrd-2.6.8-1.603.img 2.6.8-1.603
Check the initrd image :
$ cd /boot
$ mkdir tmp
$ cd tmp
$ zcat ../initrd-2.6.8-1.603.img | cpio -iv -m -d
check if /lib/ext3.ko exist.
Use the latest mkinitrd :
# rpm -q mkinitrd
mkinitrd-4.1.14-1
> Also, can someone tell me where to look for an explanation on the
> "Audit (xxxx) line and its meaning?
>
> Thanks,
> John
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20041010/6c35f472/attachment.bin
More information about the test
mailing list