From owner-freebsd-hackers Thu Jul 25 6: 8:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB9FB37B400 for ; Thu, 25 Jul 2002 06:08:50 -0700 (PDT) Received: from spxgate.servplex.com (66-105-58-82.customer.algx.net [66.105.58.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE8AF43E75 for ; Thu, 25 Jul 2002 06:08:49 -0700 (PDT) (envelope-from peter@servplex.com) Received: from peter.servplex.com ([192.168.0.61]) by spxgate.servplex.com (8.11.6/8.11.1) with ESMTP id g6PDEwg83585; Thu, 25 Jul 2002 08:14:58 -0500 (CDT) (envelope-from peter@servplex.com) Message-Id: <5.1.0.14.2.20020725080547.00a40c20@mail.servplex.com> X-Sender: peter@mail.servplex.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 25 Jul 2002 08:08:40 -0500 To: John Engelhart From: Peter Elsner Subject: Re: Serious File System problems (4.6-Release) Cc: freebsd-hackers@freebsd.org In-Reply-To: References: <20020725001049.B67097@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_685776==_.ALT" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=====================_685776==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed We had a similar problem with a bad motherboard... Only problem is it kept trashing the hard drives. We went through 4 new hard drives within 3 months total. With each hard drive replacement, we also replaced some other component, first was the memory, then the CPU, and finally before putting the 5th drive in place, I had changed out the motherboard, and the system has been up for 6 months now. At 03:42 PM 7/24/2002 -0700, you wrote: >On Thu, 25 Jul 2002, Wilko Bulte wrote: > > > On Wed, Jul 24, 2002 at 02:32:25PM -0700, John Engelhart wrote: > > > > > > Thoughts? Is it memory? Is it CPU? One of the CPU's is brand new. One > > > of the CPU's is left over from one of the original systems. I've just > > > purchased another CPU to rule that out. I've also picked up a stick of > > > 128 megs of ram, one with and one without ECC, to see if that's causing > > > the problem. Or am I on to some insidous SMP bug? > > > > > > > Guessing (obviously): power supply? > >Good suggestion. I've been through four, however. All with the same >problem. The original 2460 was kinda particular about it's power >supplies, the 2466 seems less so as it's got the P4 extra power supply >connector to help with the dual proc power needs. No special voltage >requirements are specificed for the 2466. > >I'm wondering if it's not the CPU. If it were the RAM, I'd figure that >ECC would trip up before it allowed for that kind of corruption. *sigh*. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------------------------------------------------------------------------------- Peter Elsner Vice President Of Customer Service (And System Administrator) 1835 S. Carrier Parkway Grand Prairie, Texas 75051 (972) 263-2080 - Voice (972) 263-2082 - Fax (972) 489-4838 - Cell Phone (425) 988-8061 - eFax Unix IS user friendly... It's just selective about who its friends are. System Administration - It's a dirty job, but somebody said I had to do it. If you receive something that says 'Send this to everyone you know, pretend you don't know me. Standard $500/message proofreading fee applies for UCE. --=====================_685776==_.ALT Content-Type: text/html; charset="us-ascii" We had a similar problem with a bad motherboard...  Only problem is it kept trashing the hard drives.
We went through 4 new hard drives within 3 months total.  With each hard drive replacement, we also
replaced some other component, first was the memory, then the CPU, and finally before putting the 5th drive in place,
I had changed out the motherboard, and the system has been up for 6 months now.





At 03:42 PM 7/24/2002 -0700, you wrote:
On Thu, 25 Jul 2002, Wilko Bulte wrote:

> On Wed, Jul 24, 2002 at 02:32:25PM -0700, John Engelhart wrote:
> >
> > Thoughts?  Is it memory?  Is it CPU?  One of the CPU's is brand new.  One
> > of the CPU's is left over from one of the original systems.  I've just
> > purchased another CPU to rule that out.  I've also picked up a stick of
> > 128 megs of ram, one with and one without ECC, to see if that's causing
> > the problem.  Or am I on to some insidous SMP bug?
> >
>
> Guessing (obviously): power supply?

Good suggestion.  I've been through four, however.  All with the same
problem.  The original 2460 was kinda particular about it's power
supplies, the 2466 seems less so as it's got the P4 extra power supply
connector to help with the dual proc power needs.  No special voltage
requirements are specificed for the 2466.

I'm wondering if it's not the CPU.  If it were the RAM, I'd figure that
ECC would trip up before it allowed for that kind of corruption.  *sigh*.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message

----------------------------------------------------------------------------------------------------------
Peter Elsner <peter@servplex.com>
Vice President Of Customer Service (And System Administrator)
1835 S. Carrier Parkway
Grand Prairie, Texas 75051
(972) 263-2080 - Voice
(972) 263-2082 - Fax
(972) 489-4838 - Cell Phone
(425) 988-8061 - eFax

Unix IS user friendly... It's just selective about who its friends are.
System Administration - It's a dirty job, but somebody said I had to do it.
If you receive something that says 'Send this to everyone you know,
pretend you don't know me.

Standard $500/message proofreading fee applies for UCE.

--=====================_685776==_.ALT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message