From owner-freebsd-questions Tue Sep 19 14: 4:15 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ogre.lib.muohio.edu (ogre.lib.muohio.edu [134.53.25.3]) by hub.freebsd.org (Postfix) with ESMTP id D557B37B424 for ; Tue, 19 Sep 2000 14:04:11 -0700 (PDT) Received: from localhost (jbfink@localhost) by ogre.lib.muohio.edu (8.11.0.Beta1/8.11.0.Beta1/Debian 8.11.0-1) with ESMTP id e8JM4J910462 for ; Tue, 19 Sep 2000 17:04:20 -0500 Date: Tue, 19 Sep 2000 17:04:17 -0500 (EST) From: "John B. Fink" X-Sender: jbfink@ogre.lib.muohio.edu To: freebsd-questions@freebsd.org Subject: problems with 29160 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (note -- this may be a repeat, or there may be another message after this one with the same content -- I apologize for the nearly-spamming; another machine outside of my control is trying to send this mail, but its sendmail is choking on it for some reason) Hey folks, First off, I apologize if this is going to the wrong group, but I am quite desperate and a search of the FreeBSD mailinglist archives nets me no usable results... so.. here goes. I am in the process of building a 1TB disk array using FreeBSD 4.1, two Adaptec 29160 adapters, and the vinum software raid manager. Although this is my first time setting up FreeBSD, I've got a fair amount of experience in other *nix like systems and I have set the same hw set up in Linux (but had to drop it because of problems with nfs)... The setup goes well; I am able to compile a new kernel, add the requisite support for hardware, set up vinum, etc. etc. etc and everything seems to be going swell until I actually start loading the disk array with data. I get error messages like this in /var/log/messages: Sep 19 11:04:37 charmed /CHARMED: (da2:ahc1:0:0:0): WRITE(10). CDB: 2a 0 1 28 9 68 0 0 10 0 Sep 19 11:04:37 charmed /CHARMED: (da2:ahc1:0:0:0): ABORTED COMMAND asc:47,0 Sep 19 11:04:37 charmed /CHARMED: (da2:ahc1:0:0:0): SCSI parity error field replaceable unit: 3 Sep 19 11:04:37 charmed /CHARMED: vinum0.p0.s0: fatal write I/O error Sep 19 11:04:37 charmed /CHARMED: vinum: vinum0.p0.s0 is stale by force Sep 19 11:04:37 charmed /CHARMED: (da2:ahc1:0:0:0): WRITE(10). CDB: 2a 0 1 28 a 98 0 0 10 0 Sep 19 11:04:38 charmed /CHARMED: (da2:ahc1:0:0:0): ABORTED COMMAND asc:47,0 Sep 19 11:04:38 charmed /CHARMED: (da2:ahc1:0:0:0): SCSI parity error field replaceable unit: 3 Sep 19 11:04:38 charmed /CHARMED: vinum0.p0.s0: fatal write I/O error Sep 19 11:04:38 charmed /CHARMED: (da2:ahc1:0:0:0): WRITE(10). CDB: 2a 0 1 28 a b8 0 0 10 0 Sep 19 11:04:38 charmed /CHARMED: (da2:ahc1:0:0:0): ABORTED COMMAND asc:47,0 Sep 19 11:04:38 charmed /CHARMED: (da2:ahc1:0:0:0): SCSI parity error field replaceable unit: 3 Sep 19 11:04:38 charmed /CHARMED: vinum0.p0.s0: fatal write I/O error and then vinum marks the drives as stale and I am stuck. I read somewhere that this might be a scsi timeout issue... if so, is there a fix? If you respond please respond to me directly as well as the list because I'm not sure I'm subscribed correctly. Thank you very much in advance, John Fink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message