Re: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Garrick Staples
On Thu, Feb 14, 2008 at 01:28:14PM -0800, Timothy Selivanow alleged: > Yes, you are correct that RAID doesn't help with human failings. > However, LVM[1], backups, and change control management do ;) Then it's a good thing he has a nightly backup to an external harddrive. pgpknYveDEV5D.pgp Desc

RE: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Timothy Selivanow
On Fri, 2008-02-15 at 07:23 +1100, Steven Haigh wrote: > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of Scott Silva > > Sent: Friday, 15 February 2008 7:15 AM > > To: centos@centos.org > > Subject: [CentOS] Re

RE: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Steven Haigh
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Scott Silva > Sent: Friday, 15 February 2008 7:15 AM > To: centos@centos.org > Subject: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network. > > on 2/14/2008 10:38 A

[CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Scott Silva
on 2/14/2008 10:38 AM Steven Haigh spake the following: I have found the issue with this - and now I feel quite dumb. In this box, I keep a second HDD (/dev/hdc) which is mirrored nightly from the primary HDD (/dev/hda). This is an exact copy - initially created via dd, then kept up to date via

[CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Scott Silva
on 2/14/2008 10:06 AM Steven Haigh spake the following: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William L. Maltby Sent: Friday, 15 February 2008 4:19 AM To: CentOS General List Subject: Re: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network

RE: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Steven Haigh
I have found the issue with this - and now I feel quite dumb. In this box, I keep a second HDD (/dev/hdc) which is mirrored nightly from the primary HDD (/dev/hda). This is an exact copy - initially created via dd, then kept up to date via rsync on a nightly basis. This is so that if the primary

RE: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Steven Haigh
Just replying to myself for this - I realised that after a 'failed' boot, it would also overwrite the boot logs when the system came back up with the correct kernel/grub config ;) I've made a few changes and added a bit more to the script - and I think its about ready to use.

RE: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Steven Haigh
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of William L. Maltby > Sent: Friday, 15 February 2008 4:19 AM > To: CentOS General List > Subject: Re: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network. > > On Thu, 2008-02-

Re: [CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread William L. Maltby
On Thu, 2008-02-14 at 08:44 -0800, Scott Silva wrote: > on 2/14/2008 2:25 AM William L. Maltby spake the following: > > > > If grub had a "one time" next boot like LILO, I'd have some more > > thoughts, but <*sigh*> > > > I have been hoping for that option for years. I have used other options li

[CentOS] Re: Kernel 2.6.18-53.1.13.el5 fails on network.

2008-02-14 Thread Scott Silva
on 2/14/2008 2:25 AM William L. Maltby spake the following: 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.i