From owner-freebsd-hackers Mon May 13 14: 9:35 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 27B6037B403 for ; Mon, 13 May 2002 14:09:31 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g4DL9Ji04372; Mon, 13 May 2002 14:09:20 -0700 (PDT) Date: Mon, 13 May 2002 14:09:19 -0700 (PDT) From: Doug White To: David =?ISO-8859-1?Q?Sieb=F6rger?= Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: What hardware do you use ? In-Reply-To: <20020513170501.81513.qmail@shell.rucus.ru.ac.za> Message-ID: <20020513131407.P99792-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT 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 On 13 May 2002, David [ISO-8859-1] Siebörger wrote: > That's hardly the worst of it. The ServerWorks OSB4 ATA controller > has been known to cause data corruption with Seagate drives. Have you isolated it to Seagates only? our problematic rackables have seagate drives, but I don't have any other mfr drives (maxtor, ibm) to test it with. > I've just had a very frustrating experience with this problem on an > Intel STL2-based 4.6-PRERELEASE system which experienced segfaults > and file system corruption. We tested the memory, checked the PSU, > heat in the system, replaced the IDE cable, replaced the drive > (unfortunately with another Seagate!) before I heard about this > issue. My testing showed that the problem only occurred while > writing to disk using UltraDMA. On the SCB2 Intel has a big warning in the manual to not use that IDE interface for system disks. I don't see it in the STL2 manual so I guess they learned their lesson later on. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message