Date:  Wed, 04 Jun 2008 13:54:17 +0100
From:  Dogsbody <dan (at mark) dogsbody.org>
Subject:  [coba-e:13153] Re: No grub after latest kernel upgrade
To:  coba-e (at mark) bluequartz.org
Message-Id:  <48469079.9070103 (at mark) dogsbody.org>
In-Reply-To:  <4845AF95.4040000 (at mark) theanchoragesylvania.com>
References:  <000301c88ac8$d0e72280$14001fac (at mark) DELLP4TACO> <200803210209.44015.bq (at mark) solarspeed.net> <4843F42C.6000905 (at mark) dogsbody.org> <200806021811.11952.bq (at mark) solarspeed.net> <4845AF95.4040000 (at mark) theanchoragesylvania.com>
X-Mail-Count: 13153


> I remember reading this fix when it was first published. Can someone 
> explain what the root cause of the problem was? I was just pondering to 
> myself that if it happened to me, I'd be seriously in a flap, with my 
> mail archives dependent on the box that would have failed..... (Yes, I 
> know there are web mirrors of the group.... but....)

I don't know either as it has just happened to me the once on one box.

I don't know for sure but mine seemed to be caused by one of the 
drives on my software RAID starting to fail but not solidly.  After I 
fixed the error (using instructions) it happened again when rebooting 
so I fixed it again and then the second drive started throwing up read 
errors.  I took out the second drive and everything seems to be fine 
since!  I haven't got a blank drive to put back in the box yet.

The main problem is that I don't actually know when the error is 
happening, it could be in bootup but you don't see the fault until you 
reboot and try to access the MBR.

Dan