FC3T2 - 598 & 603 kernel fail boot

John Soltow (Sabre) soltowja at comcast.net
Mon Oct 11 11:30:55 UTC 2004


    After doing the zcat | cpio procedure, I now understand a fair 
amount more about what is going on.  I had originally thought the 
problem was that it was looking in the wrong area for the ext3.ko file.  
However, when the initrd file is built, it's placed in its own tree at 
/lib/ext3.ko   -  and the file was there (when I looked at the tree 
structure under /boot/tmp that the zcat | cpio created).

    The error is stating Unknown Symbol in module (/lib/ext3.ko).  So I 
ran "depmod -a -v 2.6.8-1.603" to rebuild 
/lib/modules/2.6.8-1.603/modules.dep file.  I'm still getting "Unknown 
Symbol" when booting the 603 modules (and presumably the 598 though I 
haven't tried it).

    I'm guessing that it's using ext3 for the initrd because my root and 
/boot partitions are ext3.  Is there a way to force the initrd to use 
ext2?  Or am I off on a wild goose chase?

    Is anyone else that has both their / and /boot partitions setup as 
ext3 having problems?

    Thanks,
    John


>Message: 11
>Date: Sun, 10 Oct 2004 04:29:54 +0200
>From: Matias F?liciano <feliciano.matias at free.fr>
>Subject: Re: FC3T2 - 598 & 603 kernel fail boot
>To: For testers of Fedora Core development releases
>	<fedora-test-list at redhat.com>
>Message-ID: <1097375395.27633.29.camel at localhost.localdomain>
>Content-Type: text/plain; charset="utf-8"
>
>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 : /archives/fedora-test-list/attachments/20041010/6c35f472/attachment.bin
>
>  
>





More information about the fedora-test-list mailing list