Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

2007-07-16 Thread Rogier Wolff
On Sat, Jul 14, 2007 at 07:32:38PM -0700, Mr. James W. Laferriere wrote: > >So your disk throws a fit > > Actually it's brand new . Infant mortallity ? I at least have a > cold spare available . So Yes I am replacing that puppy . I'll drop > it > into another system & give it th

Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

2007-07-14 Thread Mr. James W. Laferriere
Hello Alan (& Justin) , On Sun, 15 Jul 2007, Alan Cox wrote: On Sat, 14 Jul 2007 17:08:27 -0700 (PDT) "Mr. James W. Laferriere" <[EMAIL PROTECTED]> wrote: Hello All , I was under the impression that a 'machine check' would be caused by some near to the CPU hardware failure ,

Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

2007-07-14 Thread Alan Cox
On Sat, 14 Jul 2007 17:08:27 -0700 (PDT) "Mr. James W. Laferriere" <[EMAIL PROTECTED]> wrote: > Hello All , I was under the impression that a 'machine check' would be > caused by some near to the CPU hardware failure , Not a bad disk ? It indicates a hardware failure > Jul 14 23:00:26 f

Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

2007-07-14 Thread Justin Piszcz
On Sat, 14 Jul 2007, Mr. James W. Laferriere wrote: Hello All , I was under the impression that a 'machine check' would be caused by some near to the CPU hardware failure , Not a bad disk ? I was also under the impression that software raid s/b a little more resilient than this . But the

raid5:md3: read error corrected , followed by , Machine Check Exception: .

2007-07-14 Thread Mr. James W. Laferriere
Hello All , I was under the impression that a 'machine check' would be caused by some near to the CPU hardware failure , Not a bad disk ? I was also under the impression that software raid s/b a little more resilient than this . But then maybe one or the other of the subsystems walked all ov