There are a number of differences in the initrd, although nothing that I
would call obvious as causing an issue..
---------------------
# gunzip -cd /boot/initrd-2.6.18-8.1.8.el5.img |cpio -t |more
6097 blocks
bin
bin/modprobe
bin/insmod
bin/nash
dev
dev/tty6
dev/zero
dev/tty5
dev/console
dev/ram1
dev/ttyS3
dev/tty0
dev/ttyS0
dev/null
dev/tty3
dev/tty10
dev/ram0
dev/ptmx
dev/rtc
dev/tty
dev/tty8
dev/ttyS1
dev/systty
dev/ram
dev/tty7
dev/tty1
dev/tty11
dev/tty4
dev/tty2
dev/tty12
dev/tty9
dev/ttyS2
dev/mapper
proc
lib
lib/jbd.ko
lib/uhci-hcd.ko
lib/ext3.ko
lib/ohci-hcd.ko
lib/ehci-hcd.ko
init
sysroot
sbin
sys
etc
#
---------------------
# gunzip -cd /boot/initrd-2.6.18-53.1.13.el5.img |cpio -t |more
9679 blocks
bin
bin/dmraid
bin/modprobe
bin/insmod
bin/kpartx
bin/nash
dev
dev/tty6
dev/zero
dev/tty5
dev/console
dev/ram1
dev/ttyS3
dev/tty0
dev/ttyS0
dev/null
dev/tty3
dev/tty10
dev/ram0
dev/ptmx
dev/rtc
dev/tty
dev/tty8
dev/ttyS1
dev/systty
dev/ram
dev/tty7
dev/tty1
dev/tty11
dev/tty4
dev/tty2
dev/tty12
dev/tty9
dev/ttyS2
dev/mapper
proc
lib
lib/jbd.ko
lib/uhci-hcd.ko
lib/ext3.ko
lib/firmware
lib/ohci-hcd.ko
lib/ehci-hcd.ko
init
sysroot
sbin
sys
etc
#
---------------------
The obvious additions in .53 are kpartx and dmraid - however as I'm using a
plain HDD (hda) with no RAID, I don't really think that would cause an
issue.
--
Steven Haigh
Email: netwiz@xxxxxxxxx
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
-----Original Message-----
From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On Behalf
Of Indunil Jayasooriya
Sent: Thursday, 14 February 2008 2:34 PM
To: CentOS mailing list
Subject: Re: Kernel 2.6.18-53.1.13.el5 fails on network.
> After the latest lot of kernel security updates have come out, I updated
one
> of my colo boxes and rebooted. It didn't come back up and fails when
booting
> on:
> * CPU Microcode update
> * iptables
> * eth0
>
> The booting process completes, however as you can imagine, there is no
> network connectivity at all. The only config changes were installing the
new
> kernel. Booting back into 2.6.18-8.1.8.el5 make things work 100% again.
I also got this type of probles once before. pls check initrd image.
pls performe below steps.
gunzip -cd /boot/initrd-2.6.18-8.1.8.el5.img |cpio -t |more and see
then, check your newly installed kernel. as below
gunzip -cd /boot/initrd-2.6.18-53.1.13.el5.img |cpio -t |more and see
pls check what is missing. If found, All you have to make an initrd by
using mkinitrd command.
pls check below URL
http://readlist.com/lists/centos.org/centos/2/13952.html
--
Thank you
Indunil Jayasooriya
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
