From owner-freebsd-stable Sat Jun 5 21: 4: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id AF251152C9 for ; Sat, 5 Jun 1999 21:04:04 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id XAA12495; Sat, 5 Jun 1999 23:27:05 -0500 (EST) Date: Sat, 5 Jun 1999 23:27:03 -0500 (EST) From: Alfred Perlstein To: "Ron 'The InSaNe One' Rosson" Cc: michael@alderete.com, freebsd-stable@FreeBSD.ORG Subject: Re: [HELP!] Crashing FreeBSD server with file system corruption In-Reply-To: <19990605202609.A46300@lunatic.oneinsane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Jun 1999, Ron 'The InSaNe One' Rosson wrote: > On Sat, Jun 05, 1999 at 10:58:07AM -0700, Michael A. Alderete wrote: > > > > * The disk subsystem is a SCSI RAID controller from > > DPT. It's a PCI card and has 4 drives attached, > > configured in a RAID 5 with one drive as a hot > > standby. > > > One possibility could be the DPT. You might want to try a SCSI to SCSI > raid solution. Reason why I say this is because a close friend of mine > was seeing the same thing with there DPT's moved over to an infortrend > scsi-scsi solution and the filesystem corruption went away. We tried for a month to get a DPT controller working with FreeBSD, and failed, we tried: 1) new card 2) new drives 3) new motherboard 4) new cables 5) crying 6) praying ... Well I really don't want to talk about things past "6" -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message