Steven Haigh wrote:
> I have a bit of trouble with this, as the only person that can do it is
> around 30 minutes travel from the colo. As the system boots, I'm thinking of
> writing a script that will gather this, then reboot the system after
> changing the default=x line in /etc/grub.conf - howe
On Thu, 2008-02-14 at 14:57 +1100, Steven Haigh wrote:
> 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
> ...
> sys
>
On Thu, Feb 14, 2008 at 03:08:54PM +1100, Steven Haigh wrote:
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> > Behalf Of nate
> > Sent: Thursday, 14 February 2008 2:46 PM
> > To: centos@centos.org
> > Subject: Re: [Cen
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of nate
> Sent: Thursday, 14 February 2008 2:46 PM
> To: centos@centos.org
> Subject: Re: [CentOS] Kernel 2.6.18-53.1.13.el5 fails on network.
>
> Indunil Jayasooriya wrote:
>
Indunil Jayasooriya wrote:
> I also got this type of probles once before. pls check initrd image.
> pls performe below steps.
>
While it's always good to make sure your initrd is in a good state,
the network drivers don't need to be in the initrd (unless your booting
from NFS or something). They c
om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Indunil Jayasooriya
Sent: Thursday, 14 February 2008 2:34 PM
To: CentOS mailing list
Subject: Re: [CentOS] 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 m
> 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, t
7 matches
Mail list logo
