FC3T2 - 598 & 603 kernel fail boot - was "FC3T1 - 598 & 603 kernel fail boot"

[Andrew]

Hi,

I don't know for sure what is the matter, but I would recommend you 
rebuild your initrd the ext3 module has to be loaded from the initial 
ram disk since its needed before the root file system is mounted

boot to the 541 kernel and as root
cd /boot
mv initrd-2.6.8-1.603.img initrd-2.6.8-1.603.bad.img
mkinitrd initrd-2.6.8-1.603.img 2.6.8-1.603

and

mv initrd-2.6.8-1.598.img initrd-2.6.8-1.598.bad.img
mkinitrd initrd-2.6.8-1.598.img 2.6.8-1.598

And see how that works.

No problem with 603 or 598 here.

HTH,

Andrew

John Soltow (Sabre) wrote:

>    Correction Subject line should have read FC3T2 vice FC3T1
>
> John Soltow (Sabre) wrote:
>
>>    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.
>>
>>    Also, can someone tell me where to look for an explanation on the 
>> "Audit (xxxx) line and its meaning?
>>
>>    Thanks,
>>    John
>>
>
>