From owner-freebsd-scsi Fri Jul 7 2:47:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freenix.no (atreides.freenix.no [213.188.21.6]) by hub.freebsd.org (Postfix) with ESMTP id AA80537B7AC for ; Fri, 7 Jul 2000 02:47:48 -0700 (PDT) (envelope-from shamz@freenix.no) Received: (from shamz@localhost) by freenix.no (8.9.3/8.9.3) id LAA25683 for freebsd-scsi@FreeBSD.ORG; Fri, 7 Jul 2000 11:47:43 +0200 (CEST) (envelope-from shamz) Date: Fri, 7 Jul 2000 11:47:43 +0200 From: Shaun Jurrens To: freebsd-scsi@FreeBSD.ORG Subject: Re: adaptec 2940uw error message on -stable Message-ID: <20000707114743.A25559@atreides.freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-STABLE X-Philosophy: If you can read this, you're too close. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Guess it's time I get back to you on how I got to the root of a very similar problem. I too was plagued by the same problem for months. Changed every imaginable thing. In the end it was a bios setting for ram that I had changed from the default setting in an interrupted bios tuning/testing session. It seems to cause very small data corruption problems: copying large .tar files succeeded only rarely, daily checks caused errors too, but not always. A very tough bug to track down. Even building world didn't seem to be affected, but cvsup was a nightmare... Suggestion: set any bios changes for your ram back to default and change only those you know work under load (cvsup or cpio/tar | cp). I don't know if it's because the ram is marginal or not. Since I reset the setting (it was just one and I had forgotten that I changed it at all) I haven't had a single error, and I even have a lvd disk with adapter. I hope I have been of some help. -- Yours truly, Shaun D. Jurrens shaun@shamz.net shamz@freenix.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message