From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 26 17:28:08 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E08E816A4CE for ; Mon, 26 Jan 2004 17:28:08 -0800 (PST) Received: from smtp.covadmail.net (mx08.covadmail.net [63.65.120.68]) by mx1.FreeBSD.org (Postfix) with SMTP id DB65C43D9B for ; Mon, 26 Jan 2004 17:27:11 -0800 (PST) (envelope-from strick@covad.net) Received: (covad.net 11049 invoked from network); 27 Jan 2004 01:26:45 -0000 Received: from unknown (HELO mist.nodomain) (strick@covad.net@68.164.174.1) by sun-qmail12 with SMTP; 27 Jan 2004 01:26:45 -0000 Received: from mist.nodomain (localhost [127.0.0.1]) by mist.nodomain (8.12.9p2/8.12.9) with ESMTP id i0R1Qmhn000464; Mon, 26 Jan 2004 17:26:48 -0800 (PST) (envelope-from dan@mist.nodomain) Received: (from dan@localhost) by mist.nodomain (8.12.9p2/8.12.9/Submit) id i0R1QmCW000463; Mon, 26 Jan 2004 17:26:48 -0800 (PST) (envelope-from dan) Date: Mon, 26 Jan 2004 17:26:48 -0800 (PST) From: Dan Strick Message-Id: <200401270126.i0R1QmCW000463@mist.nodomain> To: ken@FreeBSD.org cc: nsayer@quack.kfu.com cc: scsi@FreeBSD.org Subject: Re: kern/15608: acd0 / cd0 give inconsistent errors on empty tray open() X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 01:28:09 -0000 >> > Synopsis: acd0 / cd0 give inconsistent errors on empty tray open() > > State-Changed-From-To: feedback->closed > State-Changed-By: ken > State-Changed-When: Mon Jan 26 11:59:35 PST 2004 > State-Changed-Why: > Bruce said that ENXIO was the correct error to return, and we do return > that when media isn't present. Also, I believe that the issues that Bruce > brought up about the CDIOCCLOSE ioctl, etc., have been fixed. > > > Responsible-Changed-From-To: scsi->ken > Responsible-Changed-By: ken > Responsible-Changed-When: Mon Jan 26 11:59:35 PST 2004 > Responsible-Changed-Why: > Bruce said that ENXIO was the correct error to return, and we do return > that when media isn't present. Also, I believe that the issues that Bruce > brought up about the CDIOCCLOSE ioctl, etc., have been fixed. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=15608 >> ENXIO would be historically the correct error to return for nonexistant disk media, including an attempt to begin a read/write one or more sectors beyond the end of a disk. This should also be the error returned for an attempt to begin a read one or more sectors beyond the last written sector of a write-once medium (e.g. CD-R) though this might be difficult situation to recognize. It might be the correct error to return whenever a read produces a "blank check" though one might sometimes make a good argument for EIO in that situation. Of course, a read that begins at or before the end of the medium but extends past the end should simply result in a short read. I mention this because it works on FreeBSD with CD-ROM but not with CD-R. I don't think I have tested this on the most recent FreeBSD releases so it might have been fixed. (This glitch, present in both scsi and atapi cd drivers, also triggered a bug in ata/atapi dma code that the ata driver eventually resolved by timing out waiting for dma to complete and disabling dma for the device.) Dan Strick strick@covad.net From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 11:49:21 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3469B16A4CE for ; Tue, 27 Jan 2004 11:49:21 -0800 (PST) Received: from mail.asn.net (mail.asn.net [66.235.231.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F05243D82 for ; Tue, 27 Jan 2004 11:49:02 -0800 (PST) (envelope-from kris-fbsd@asn.net) Received: (qmail 77850 invoked by uid 80); 27 Jan 2004 19:48:26 -0000 Received: from 68.3.131.72 (SquirrelMail authenticated user kgale) by mail.asn.net with HTTP; Tue, 27 Jan 2004 12:48:26 -0700 (MST) Message-ID: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> Date: Tue, 27 Jan 2004 12:48:26 -0700 (MST) From: "Kris Gale" To: freebsd-scsi@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 19:49:21 -0000 If this question is better asked on a different list, just let me know. I'm using an Adaptec 2010S (0-Channel RAID) with raidutil (part of ports/sysutils/asr-utils). On all of my 4.x machines, it works just fine. However, I've recently purchased a couple of new servers (all the same hardware), and decided to give 5.2 a try. (Actually, I'm running -CURRENT as of 1/23/04) In order to get it to run, I had to create a symlink in /dev/ from rasr0 to dptr17. After doing this, it appears to run properly, but is unable to get any data off of the Adaptec card. Did something change in FreeBSD 5 that would have broken this tool? It seems like others are making this tool work under 5.1, based on the advice I found old mailing list posts that suggested making that symlink in /dev/. Maybe this problem is specific to the 2010S. Kris From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 12:17:24 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1723E16A4CF for ; Tue, 27 Jan 2004 12:17:24 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id B2EDF43D55 for ; Tue, 27 Jan 2004 12:17:20 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 64141 invoked by uid 1002); 27 Jan 2004 20:17:18 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 27 Jan 2004 20:17:18 -0000 Date: Tue, 27 Jan 2004 14:24:47 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: Kris Gale In-Reply-To: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> Message-ID: <20040127140607.H6614@pooker.samsco.home> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 20:17:24 -0000 On Tue, 27 Jan 2004, Kris Gale wrote: > If this question is better asked on a different list, just let me know. > > I'm using an Adaptec 2010S (0-Channel RAID) with raidutil (part of > ports/sysutils/asr-utils). On all of my 4.x machines, it works just fine. > However, I've recently purchased a couple of new servers (all the same > hardware), and decided to give 5.2 a try. (Actually, I'm running -CURRENT > as of 1/23/04) > > In order to get it to run, I had to create a symlink in /dev/ from rasr0 > to dptr17. After doing this, it appears to run properly, but is unable to > get any data off of the Adaptec card. > > Did something change in FreeBSD 5 that would have broken this tool? It The asr driver and asr userland tools do a lot of horribly wrong things that were never meant to work, let alone guaranteed to work. The driver used to do a lot of digging around in kernel internals (and ignoring the proper APIs to do the corret things) that might not work any more. The userland aps have special knowledge of how the driver does it's digging, and those assumptions might not be true anymore also. The 'symlink trick' that youy describe is a good example of having to deal with one of these problems. In any case, the source code to the asr command line tool and communications back-end (called the 'Engine') is available from Adaptec's website. It is certainly possible to fix these and the asr driver to work properly, but it is a significant task that isn't terribly rewarding. I know some people (myself included) that might be willing to do it under contract. > seems like others are making this tool work under 5.1, based on the advice > I found old mailing list posts that suggested making that symlink in > /dev/. Maybe this problem is specific to the 2010S. > The particular model of hardware has little to do with the problems inherent in the software. Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 12:28:59 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0384316A4CE for ; Tue, 27 Jan 2004 12:28:59 -0800 (PST) Received: from beck.quonix.net (dns1.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5256943D45 for ; Tue, 27 Jan 2004 12:28:07 -0800 (PST) (envelope-from essenz@beck.quonix.net) Received: from beck.quonix.net (localhost.quonix.net [127.0.0.1]) by beck.quonix.net (8.12.10/8.12.10) with ESMTP id i0RKRgEv064745 for ; Tue, 27 Jan 2004 15:27:42 -0500 (EST) Received: from localhost (essenz@localhost)i0RKRgS0064742 for ; Tue, 27 Jan 2004 15:27:42 -0500 (EST) Date: Tue, 27 Jan 2004 15:27:42 -0500 (EST) From: John Von Essen To: freebsd-scsi@freebsd.org In-Reply-To: <20040127140607.H6614@pooker.samsco.home> Message-ID: <20040127152341.V64702@beck.quonix.net> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> <20040127140607.H6614@pooker.samsco.home> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 20:28:59 -0000 Since most poeple use FreeBSD as a server platform, and most servers use RAID, and most RAID is done with the Apadtec cards.... Is there a reason why there is no interest in fixing these supposedly "wrong" things? Or is the intention to focus solely on the aac driver and support the newer U320 raid cards under the aac driver - which does things "correctly"? -john On Tue, 27 Jan 2004, Scott Long wrote: > On Tue, 27 Jan 2004, Kris Gale wrote: > > If this question is better asked on a different list, just let me know. > > > > I'm using an Adaptec 2010S (0-Channel RAID) with raidutil (part of > > ports/sysutils/asr-utils). On all of my 4.x machines, it works just fine. > > However, I've recently purchased a couple of new servers (all the same > > hardware), and decided to give 5.2 a try. (Actually, I'm running -CURRENT > > as of 1/23/04) > > > > In order to get it to run, I had to create a symlink in /dev/ from rasr0 > > to dptr17. After doing this, it appears to run properly, but is unable to > > get any data off of the Adaptec card. > > > > Did something change in FreeBSD 5 that would have broken this tool? It > > The asr driver and asr userland tools do a lot of horribly wrong > things that were never meant to work, let alone guaranteed to work. > The driver used to do a lot of digging around in kernel internals (and > ignoring the proper APIs to do the corret things) that might not work > any more. The userland aps have special knowledge of how the driver > does it's digging, and those assumptions might not be true anymore also. > The 'symlink trick' that youy describe is a good example of having to deal > with one of these problems. > > In any case, the source code to the asr command line tool and > communications back-end (called the 'Engine') is available from Adaptec's > website. It is certainly possible to fix these and the asr driver to work > properly, but it is a significant task that isn't terribly rewarding. I > know some people (myself included) that might be willing to do it under > contract. > > > seems like others are making this tool work under 5.1, based on the advice > > I found old mailing list posts that suggested making that symlink in > > /dev/. Maybe this problem is specific to the 2010S. > > > > The particular model of hardware has little to do with the problems > inherent in the software. > > Scott > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 13:03:35 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE5F416A4CE for ; Tue, 27 Jan 2004 13:03:34 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 2CBAF43D1F for ; Tue, 27 Jan 2004 13:02:39 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 77113 invoked by uid 1002); 27 Jan 2004 21:01:10 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 27 Jan 2004 21:01:10 -0000 Date: Tue, 27 Jan 2004 15:08:39 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: John Von Essen In-Reply-To: <20040127152341.V64702@beck.quonix.net> Message-ID: <20040127144842.H6614@pooker.samsco.home> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> <20040127152341.V64702@beck.quonix.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 21:03:35 -0000 On Tue, 27 Jan 2004, John Von Essen wrote: > Since most poeple use FreeBSD as a server platform, and most servers use > RAID, and most RAID is done with the Apadtec cards.... > > Is there a reason why there is no interest in fixing these > supposedly "wrong" things? Or is the intention to focus solely on the aac > driver and support the newer U320 raid cards under the aac driver - > which does things "correctly"? Apparently it hasn't been enough of an itch for people to scratch. I did all of the AAC work for two reasons: 1) I think that the AAC architecure and products are superior to ASR in practically every respect (as is witnessed by market pressures forcing Adaptec to abandon ASR and stick with AAC), 2) Adaptec believed that FreeBSD support for AAC was important enough that I was able to justify working on it as part of my normal job. I have no justification to work on ASR during paid hours, and it doesn't interest me enough to work on it in my free time. I and others here in my office feel somewhat guilty that the ASR code has languished so much, but it really is beyond our means to do more with it. If it was just a matter of fixing a few bugs, it would be a different matter. Unfortunately, making the ASR driver and tools work well requires more than just a few hours of random work. However, all of the source is available for someone to pick up and run with. Scott > > > -john > > On Tue, 27 Jan 2004, Scott Long wrote: > > > On Tue, 27 Jan 2004, Kris Gale wrote: > > > If this question is better asked on a different list, just let me know. > > > > > > I'm using an Adaptec 2010S (0-Channel RAID) with raidutil (part of > > > ports/sysutils/asr-utils). On all of my 4.x machines, it works just fine. > > > However, I've recently purchased a couple of new servers (all the same > > > hardware), and decided to give 5.2 a try. (Actually, I'm running -CURRENT > > > as of 1/23/04) > > > > > > In order to get it to run, I had to create a symlink in /dev/ from rasr0 > > > to dptr17. After doing this, it appears to run properly, but is unable to > > > get any data off of the Adaptec card. > > > > > > Did something change in FreeBSD 5 that would have broken this tool? It > > > > The asr driver and asr userland tools do a lot of horribly wrong > > things that were never meant to work, let alone guaranteed to work. > > The driver used to do a lot of digging around in kernel internals (and > > ignoring the proper APIs to do the corret things) that might not work > > any more. The userland aps have special knowledge of how the driver > > does it's digging, and those assumptions might not be true anymore also. > > The 'symlink trick' that youy describe is a good example of having to deal > > with one of these problems. > > > > In any case, the source code to the asr command line tool and > > communications back-end (called the 'Engine') is available from Adaptec's > > website. It is certainly possible to fix these and the asr driver to work > > properly, but it is a significant task that isn't terribly rewarding. I > > know some people (myself included) that might be willing to do it under > > contract. > > > > > seems like others are making this tool work under 5.1, based on the advice > > > I found old mailing list posts that suggested making that symlink in > > > /dev/. Maybe this problem is specific to the 2010S. > > > > > > > The particular model of hardware has little to do with the problems > > inherent in the software. > > > > Scott > > _______________________________________________ > > freebsd-scsi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 13:29:52 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DAB916A4CE for ; Tue, 27 Jan 2004 13:29:52 -0800 (PST) Received: from beck.quonix.net (dns1.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB4E043D31 for ; Tue, 27 Jan 2004 13:28:59 -0800 (PST) (envelope-from essenz@beck.quonix.net) Received: from beck.quonix.net (localhost.quonix.net [127.0.0.1]) by beck.quonix.net (8.12.10/8.12.10) with ESMTP id i0RLS5Ev065310 for ; Tue, 27 Jan 2004 16:28:05 -0500 (EST) Received: from localhost (essenz@localhost)i0RLS5JN065307 for ; Tue, 27 Jan 2004 16:28:05 -0500 (EST) Date: Tue, 27 Jan 2004 16:28:05 -0500 (EST) From: John Von Essen To: freebsd-scsi@freebsd.org In-Reply-To: <20040127144842.H6614@pooker.samsco.home> Message-ID: <20040127162232.P64803@beck.quonix.net> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> <20040127152341.V64702@beck.quonix.net> <20040127144842.H6614@pooker.samsco.home> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 21:29:52 -0000 Thanks Scott, thats sort of the answer I was hoping for. Correct me if I am wrong but the aac driver covers all U320 RAID cards that are 1-channel or higher (i.e, not including the zero channel stuff), right? -john On Tue, 27 Jan 2004, Scott Long wrote: > On Tue, 27 Jan 2004, John Von Essen wrote: > > Since most poeple use FreeBSD as a server platform, and most servers use > > RAID, and most RAID is done with the Apadtec cards.... > > > > Is there a reason why there is no interest in fixing these > > supposedly "wrong" things? Or is the intention to focus solely on the aac > > driver and support the newer U320 raid cards under the aac driver - > > which does things "correctly"? > > Apparently it hasn't been enough of an itch for people to scratch. I did > all of the AAC work for two reasons: 1) I think that the AAC architecure > and products are superior to ASR in practically every respect (as is > witnessed by market pressures forcing Adaptec to abandon ASR and stick > with AAC), 2) Adaptec believed that FreeBSD support for AAC was important > enough that I was able to justify working on it as part of my normal job. > > I have no justification to work on ASR during paid hours, and it doesn't > interest me enough to work on it in my free time. I and others here in > my office feel somewhat guilty that the ASR code has languished so much, > but it really is beyond our means to do more with it. If it was > just a matter of fixing a few bugs, it would be a different > matter. Unfortunately, making the ASR driver and tools work well > requires more than just a few hours of random work. However, all of the > source is available for someone to pick up and run with. > > Scott > > > > > > > > -john > > > > On Tue, 27 Jan 2004, Scott Long wrote: > > > > > On Tue, 27 Jan 2004, Kris Gale wrote: > > > > If this question is better asked on a different list, just let me know. > > > > > > > > I'm using an Adaptec 2010S (0-Channel RAID) with raidutil (part of > > > > ports/sysutils/asr-utils). On all of my 4.x machines, it works just fine. > > > > However, I've recently purchased a couple of new servers (all the same > > > > hardware), and decided to give 5.2 a try. (Actually, I'm running -CURRENT > > > > as of 1/23/04) > > > > > > > > In order to get it to run, I had to create a symlink in /dev/ from rasr0 > > > > to dptr17. After doing this, it appears to run properly, but is unable to > > > > get any data off of the Adaptec card. > > > > > > > > Did something change in FreeBSD 5 that would have broken this tool? It > > > > > > The asr driver and asr userland tools do a lot of horribly wrong > > > things that were never meant to work, let alone guaranteed to work. > > > The driver used to do a lot of digging around in kernel internals (and > > > ignoring the proper APIs to do the corret things) that might not work > > > any more. The userland aps have special knowledge of how the driver > > > does it's digging, and those assumptions might not be true anymore also. > > > The 'symlink trick' that youy describe is a good example of having to deal > > > with one of these problems. > > > > > > In any case, the source code to the asr command line tool and > > > communications back-end (called the 'Engine') is available from Adaptec's > > > website. It is certainly possible to fix these and the asr driver to work > > > properly, but it is a significant task that isn't terribly rewarding. I > > > know some people (myself included) that might be willing to do it under > > > contract. > > > > > > > seems like others are making this tool work under 5.1, based on the advice > > > > I found old mailing list posts that suggested making that symlink in > > > > /dev/. Maybe this problem is specific to the 2010S. > > > > > > > > > > The particular model of hardware has little to do with the problems > > > inherent in the software. > > > > > > Scott > > > _______________________________________________ > > > freebsd-scsi@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-scsi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > > From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 14:37:36 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BD7A16A4CE for ; Tue, 27 Jan 2004 14:37:36 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 8FE7843D62 for ; Tue, 27 Jan 2004 14:37:07 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 8344 invoked by uid 1002); 27 Jan 2004 22:36:23 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 27 Jan 2004 22:36:23 -0000 Message-ID: <4016E768.80008@freebsd.org> Date: Tue, 27 Jan 2004 15:34:16 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Von Essen References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> <20040127152341.V64702@beck.quonix.net> <20040127144842.H6614@pooker.samsco.home> <20040127162232.P64803@beck.quonix.net> In-Reply-To: <20040127162232.P64803@beck.quonix.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 22:37:36 -0000 John Von Essen wrote: > Thanks Scott, thats sort of the answer I was hoping for. Correct me if I > am wrong but the aac driver covers all U320 RAID cards that are > 1-channel or higher (i.e, not including the zero channel stuff), right? Well, there may be 0-channel cards in the future that don't follow this rule. For now, here is a brief list of Adaptec-branded RAID: ASR: 2000S 2005S 2010S 2015S 2100S 2110S 2400A 3200S 3210S 3400S 3410S AAC: 2120S 2200S 2410SA 2810SA 5400S Scott From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 14:52:47 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0963316A4CF for ; Tue, 27 Jan 2004 14:52:47 -0800 (PST) Received: from mail.asn.net (mail.asn.net [66.235.231.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 2011743D5C for ; Tue, 27 Jan 2004 14:52:10 -0800 (PST) (envelope-from kgale@asn.net) Received: (qmail 82903 invoked by uid 80); 27 Jan 2004 22:51:41 -0000 Received: from 68.3.131.72 (SquirrelMail authenticated user kgale) by mail.asn.net with HTTP; Tue, 27 Jan 2004 15:51:41 -0700 (MST) Message-ID: <54287.68.3.131.72.1075243901.squirrel@mail.asn.net> In-Reply-To: <20040127144842.H6614@pooker.samsco.home> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net><20040127152341.V64702@beck.quonix.net> <20040127144842.H6614@pooker.samsco.home> Date: Tue, 27 Jan 2004 15:51:41 -0700 (MST) From: "Kris Gale" To: "Scott Long" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 22:52:47 -0000 > I have no justification to work on ASR during paid hours, and it doesn't > interest me enough to work on it in my free time. I and others here in > my office feel somewhat guilty that the ASR code has languished so much, > but it really is beyond our means to do more with it. If it was > just a matter of fixing a few bugs, it would be a different > matter. Unfortunately, making the ASR driver and tools work well > requires more than just a few hours of random work. However, all of the > source is available for someone to pick up and run with. I disagree that it's not in Adaptec's interests. I've based my whole network around SuperMicro servers that support the ASR-based 0-channel RAID cards, because they were supported and had a command-line tool available on FreeBSD 4.x systems. Since I know I'm going to need KSE and other features of 5.x, this is a huge problem for me. I know I'm not alone in this. I just purchased 28 new servers, all with ASR-based 0-channel RAID cards, with the intention of installing 5-CURRENT on all of them. D'oh. Even if I move to different hardware (and therefore a different CLI), I already have many monitoring and alert systems built around raidutil that I'd have to rewrite or modify. It also eliminates many of the primary reasons I buy those SuperMicro systems, with their neat, pre-run, custom cables, integrated SCSI controllers, etc. I'm sure there's more people on this list in a similar bind, so can you make any suggestions about who we can contact at Adaptec to let them know that we really do use this hardware, and that we do indeed purchase it based on the availability of the configuration/monitoring CLI? I really wish I could take you up on the suggestion that someone run with the existing source code, but I'm much more of a perl guy than a C hacker. Kris From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 16:23:11 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE58916A4CE for ; Tue, 27 Jan 2004 16:23:11 -0800 (PST) Received: from beck.quonix.net (dns1.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FEA843D5D for ; Tue, 27 Jan 2004 16:22:56 -0800 (PST) (envelope-from john@essenz.com) Received: from essenz.com (pcp04571733pcs.neave01.pa.comcast.net [68.80.46.122]) by beck.quonix.net (8.12.10/8.12.10) with ESMTP id i0S0MpEv066425 for ; Tue, 27 Jan 2004 19:22:51 -0500 (EST) Date: Tue, 27 Jan 2004 19:17:44 -0500 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) From: John Von Essen To: freebsd-scsi@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <54287.68.3.131.72.1075243901.squirrel@mail.asn.net> Message-Id: <64E26D1C-5127-11D8-B6F7-0003933DDCFA@essenz.com> X-Mailer: Apple Mail (2.553) X-SpamAssassin-Score: 0/6 () X-MimeDefang: beck.quonix.net X-Scanned-By: MIMEDefang 2.39 Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 00:23:11 -0000 Thats sucks. A guess its a good thing I never liked zero-channel RAID, or better yet, Supermicro. -john On Tuesday, January 27, 2004, at 05:51 PM, Kris Gale wrote: >> I have no justification to work on ASR during paid hours, and it >> doesn't >> interest me enough to work on it in my free time. I and others here >> in >> my office feel somewhat guilty that the ASR code has languished so >> much, >> but it really is beyond our means to do more with it. If it was >> just a matter of fixing a few bugs, it would be a different >> matter. Unfortunately, making the ASR driver and tools work well >> requires more than just a few hours of random work. However, all of >> the >> source is available for someone to pick up and run with. > > I disagree that it's not in Adaptec's interests. I've based my whole > network around SuperMicro servers that support the ASR-based 0-channel > RAID cards, because they were supported and had a command-line tool > available on FreeBSD 4.x systems. Since I know I'm going to need KSE > and > other features of 5.x, this is a huge problem for me. I know I'm not > alone in this. > > I just purchased 28 new servers, all with ASR-based 0-channel RAID > cards, > with the intention of installing 5-CURRENT on all of them. D'oh. > Even if > I move to different hardware (and therefore a different CLI), I already > have many monitoring and alert systems built around raidutil that I'd > have > to rewrite or modify. It also eliminates many of the primary reasons I > buy those SuperMicro systems, with their neat, pre-run, custom cables, > integrated SCSI controllers, etc. > > I'm sure there's more people on this list in a similar bind, so can you > make any suggestions about who we can contact at Adaptec to let them > know > that we really do use this hardware, and that we do indeed purchase it > based on the availability of the configuration/monitoring CLI? > > I really wish I could take you up on the suggestion that someone run > with > the existing source code, but I'm much more of a perl guy than a C > hacker. > > Kris > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > John Von Essen (john@essenz.com) President, Essenz Consulting (www.essenz.com) Phone: (800) 248-1736 Fax: (800) 852-3387 From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 16:31:01 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F394F16A4CE for ; Tue, 27 Jan 2004 16:31:00 -0800 (PST) Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF46743D5C for ; Tue, 27 Jan 2004 16:30:57 -0800 (PST) (envelope-from gary@outloud.org) Received: from uranium-xkzwf96.outloud.org (69-160-74-173.frdrmd.adelphia.net [69.160.74.173]) by mail.webjockey.net (8.12.10/8.12.8) with ESMTP id i0S0ZHbD055511; Tue, 27 Jan 2004 19:35:17 -0500 (EST) (envelope-from gary@outloud.org) Message-Id: <6.0.1.1.2.20040127192109.02c6d400@208.141.46.3> X-Sender: ancient@208.141.46.3 X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Tue, 27 Jan 2004 19:30:57 -0500 To: "Kris Gale" From: Gary Stanley In-Reply-To: <54287.68.3.131.72.1075243901.squirrel@mail.asn.net> References: <53616.68.3.131.72.1075232906.squirrel@mail.asn.net> <20040127152341.V64702@beck.quonix.net> <20040127144842.H6614@pooker.samsco.home> <54287.68.3.131.72.1075243901.squirrel@mail.asn.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec's raidutil (asr-utils), 2010S and 5.2 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 00:31:01 -0000 I am in the same boat as you, some of our older SM servers have 2010S cards. But I can see his point tho, since Scott is on RE and other projects, it's very time consuming to work on something moderately old, however, I'm sure someone else will either pick it back up and mod it for 5, and then everyone will be happy. :) >I disagree that it's not in Adaptec's interests. I've based my whole >network around SuperMicro servers that support the ASR-based 0-channel >RAID cards, because they were supported and had a command-line tool >available on FreeBSD 4.x systems. Since I know I'm going to need KSE and >other features of 5.x, this is a huge problem for me. I know I'm not >alone in this. > >I just purchased 28 new servers, all with ASR-based 0-channel RAID cards, >with the intention of installing 5-CURRENT on all of them. D'oh. Even if >I move to different hardware (and therefore a different CLI), I already >have many monitoring and alert systems built around raidutil that I'd have >to rewrite or modify. It also eliminates many of the primary reasons I >buy those SuperMicro systems, with their neat, pre-run, custom cables, >integrated SCSI controllers, etc. > >I'm sure there's more people on this list in a similar bind, so can you >make any suggestions about who we can contact at Adaptec to let them know >that we really do use this hardware, and that we do indeed purchase it >based on the availability of the configuration/monitoring CLI? > >I really wish I could take you up on the suggestion that someone run with >the existing source code, but I'm much more of a perl guy than a C hacker. > >Kris >_______________________________________________ >freebsd-scsi@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-scsi >To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 27 18:19:50 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E0C516A4CE for ; Tue, 27 Jan 2004 18:19:50 -0800 (PST) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3930A43D58 for ; Tue, 27 Jan 2004 18:19:41 -0800 (PST) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id C17A53D005; Tue, 27 Jan 2004 22:15:44 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C0B1A3CE61 for ; Tue, 27 Jan 2004 22:15:44 -0400 (AST) Date: Tue, 27 Jan 2004 22:15:44 -0400 (AST) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20040127221402.M68358@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: probing iir raid controller ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 02:19:50 -0000 Without rebooting, is there any way of determining what model controller the following is? pluto# grep iir /var/run/dmesg.boot iir0: mem 0xfc8f0000-0xfc8f3fff irq 2 at device 9.0 on pci1 thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 28 04:57:55 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65B5916A4CE for ; Wed, 28 Jan 2004 04:57:55 -0800 (PST) Received: from smtp104.mail.sc5.yahoo.com (smtp104.mail.sc5.yahoo.com [66.163.169.223]) by mx1.FreeBSD.org (Postfix) with SMTP id 47D2243D2D for ; Wed, 28 Jan 2004 04:57:54 -0800 (PST) (envelope-from guardiao98@yahoo.com) Received: from unknown (HELO pentium4) (guardiao98@200.158.4.74 with login) by smtp104.mail.sc5.yahoo.com with SMTP; 28 Jan 2004 12:57:52 -0000 Message-ID: <019801c3e59e$56af5330$2101a8c0@pentium4> From: "guardiao98" To: Date: Wed, 28 Jan 2004 10:57:48 -0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailman-Approved-At: Wed, 28 Jan 2004 06:24:05 -0800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Raid mylex X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2004 12:57:55 -0000 I have a controler scsi Mylex acceleraid 170 Trying update version of bios came a erro mensagem and now It doesnt = work !=20 How May I do to clear the bios and restore the correct version ? =20 msg erro :=20 NOTICE - CHECKFILEFORSIEMENS ERROR IN GETCONTROLLERPARAMETER The bios doesnt run when I start the machine. Thanks . From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 29 05:50:26 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F360B16A4CE for ; Thu, 29 Jan 2004 05:50:25 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 029A643D31 for ; Thu, 29 Jan 2004 05:50:24 -0800 (PST) (envelope-from freebsd-scsi@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AmCYo-0002r0-00 for ; Thu, 29 Jan 2004 14:50:22 +0100 Received: from makrothumia.wingnet.net ([206.30.215.5]) by news.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu Jan 29 13:50:22 2004 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-scsi@freebsd.org From: Jesse Guardiani Date: Thu, 29 Jan 2004 08:50:17 -0500 Organization: WingNET Lines: 52 Message-ID: References: <200401240215.i0O2FY7E068846@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org Gmane-NNTP-Posting-Host: makrothumia.wingnet.net User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: adaptec 2940u/uw dump card state ends X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 13:50:26 -0000 Don Lewis wrote: [...] > My first guess would not be termination. I would think that a > termination problem would muck up data transfers and would affect all > attempts to use the changer. Well, it may be too soon to tell, but this past Monday (or maybe Sunday? I can't remember) the machine spontaneously rebooted on me during a backup cycle to the tape drive. It was midnight, but I decided to take a trip to the office and have a look at it anyway. In the adaptec SCSI controller, I had the termination set to OFF for the LOW and HIGH parts of the bus. I changed this to AUTO for LOW and AUTO for HIGH and I turned off Ultra SCSI capability on the controller. I'm not sure which of those changes fixed the problem, but so far - 3 or 4 days later - I haven't seen a single timeout and no spontaneous reboots. Hopefully it's fixed! > How long is the time from when you issue the changer command to when the > driver coughs up this error? I'm not familiar with this drive/changer > combination, but the DDS changer that I use takes a lot longer to swap > tapes if the tape currently in the drive is wound all the way to the > end, because the drive first has to rewind it before it can unload the > tape. Subsequent tape changes won't take as long if the tape currently > in the drive is still at the beginning ... > > How is the changer connected to the 2940u/uw? If you are using an eight > bit cable Not sure what "bit" count it has, but it's an external wide cable. 50 pin, maybe? > you'll want to configure the 2940u/uw to terminate the upper > 8 bits of the bus but not the lower 8. I think this may have been the problem. Setting both halves to "auto" probably fixed it. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 29 06:13:17 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D83A616A4CE for ; Thu, 29 Jan 2004 06:13:17 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96A6A43D5A for ; Thu, 29 Jan 2004 06:13:16 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0TED87E086929; Thu, 29 Jan 2004 06:13:12 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401291413.i0TED87E086929@gw.catspoiler.org> Date: Thu, 29 Jan 2004 06:13:08 -0800 (PST) From: Don Lewis To: jesse@wingnet.net In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-scsi@FreeBSD.org Subject: Re: adaptec 2940u/uw dump card state ends X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 14:13:18 -0000 On 29 Jan, Jesse Guardiani wrote: > Don Lewis wrote: > > > [...] > >> My first guess would not be termination. I would think that a >> termination problem would muck up data transfers and would affect all >> attempts to use the changer. > > Well, it may be too soon to tell, but this past Monday (or maybe Sunday? I > can't remember) the machine spontaneously rebooted on me during a backup > cycle to the tape drive. It was midnight, but I decided to take a trip to > the office and have a look at it anyway. > > In the adaptec SCSI controller, I had the termination set to OFF for the LOW > and HIGH parts of the bus. I changed this to AUTO for LOW and AUTO for HIGH > and I turned off Ultra SCSI capability on the controller. > > I'm not sure which of those changes fixed the problem, but so far - 3 or 4 > days later - I haven't seen a single timeout and no spontaneous reboots. > > Hopefully it's fixed! > > >> How is the changer connected to the 2940u/uw? If you are using an eight >> bit cable > > Not sure what "bit" count it has, but it's an external wide cable. 50 pin, > maybe? That would be narrow/8-bit SCSI. wide/16-bit SCSI uses a 68 pin cable. >> you'll want to configure the 2940u/uw to terminate the upper >> 8 bits of the bus but not the lower 8. > > I think this may have been the problem. Setting both halves to "auto" > probably fixed it. If you previously had both upper and lower termination turned off on the controller, the upper 8 bits of your SCSI bus were only terminated on one end of the bus ... From owner-freebsd-scsi@FreeBSD.ORG Fri Jan 30 08:52:55 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E85716A4CE for ; Fri, 30 Jan 2004 08:52:55 -0800 (PST) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F5E743D72 for ; Fri, 30 Jan 2004 08:52:36 -0800 (PST) (envelope-from l.ertl@univie.ac.at) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by mailbox.univie.ac.at (8.12.10/8.12.10) with ESMTP id i0UGiMw3357988 for ; Fri, 30 Jan 2004 17:44:24 +0100 Date: Fri, 30 Jan 2004 17:44:18 +0100 (CET) From: Lukas Ertl To: scsi@freebsd.org Message-ID: <20040130174030.G635@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mailbox 4261; Body=0 Fuz1=0 Fuz2=0 Subject: ahd(4) troubles X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2004 16:52:55 -0000 Hi, I'm having trouble with an external RAID box that's connected to an Adaptec 39320D adapter. Basically the setup works, but we get some cryptic SCSI register dump on the console quite often. The kernel is a 5.2-CURRENT from Jan 19th (with SCHED_4BSD, if that matters), and the adapter is probed as: ahd0: port 0xa400-0xa4ff,0xa000-0xa0ff mem 0xe2044000-0xe2045fff irq 16 at device 1.0 on pci2 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs The actual dump is quite lengthy, so I thought I put them on the web, you can find it here: I'd be glad if someone could have a look at it and help me decrypt it. Thanks, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/ From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 3 05:41:05 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD7BE16A4CE; Tue, 3 Feb 2004 05:41:05 -0800 (PST) Received: from aker.isnic.is (aker.isnic.is [193.4.58.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8B6443D31; Tue, 3 Feb 2004 05:41:04 -0800 (PST) (envelope-from oli@aker.isnic.is) Received: by aker.isnic.is (Postfix, from userid 1000) id 3D69A8D1D9; Tue, 3 Feb 2004 13:41:03 +0000 (GMT) Date: Tue, 3 Feb 2004 13:41:03 +0000 From: Olafur Osvaldsson To: freebsd-hardware@freebsd.org Message-ID: <20040203134103.GM12156@isnic.is> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: freebsd-scsi@freebsd.org Subject: HP Fibre Channel HBA (D8602A/B) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 13:41:06 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I couldn't find anything about it in the archives about it but is the HP Fibre Channel HBA (D8602A/B) controller supported in FreeBSD? /Oli P.S. Please Cc any answer as I'm not on the lists. --=20 Olafur Osvaldsson Systems Administrator Internet a Islandi hf. Tel: +354 525-5291 Email: oli@isnic.is --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAH6Tv8xNRBRknOFwRAvWQAJ0XjXc0cRk7FFabJerYpRuy2S+ZkgCfTdF+ rCNL7eXV7Hfhr8fr80zzTkU= =HfFL -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 3 10:10:55 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8244F16A4CE; Tue, 3 Feb 2004 10:10:55 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5023643D53; Tue, 3 Feb 2004 10:10:54 -0800 (PST) (envelope-from chuck_tuffli@agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id DC99F7502; Tue, 3 Feb 2004 11:10:53 -0700 (MST) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 6EF41F1; Tue, 3 Feb 2004 11:10:53 -0700 (MST) Received: from cre85086tuf.rose.agilent.com (cre85086tuf [130.30.174.150]) ESMTP id KAA06303; Tue, 3 Feb 2004 10:10:51 -0800 (PST) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id 6325B19E2B0; Tue, 3 Feb 2004 10:11:06 -0800 (PST) Date: Tue, 3 Feb 2004 10:11:06 -0800 From: Chuck Tuffli To: Olafur Osvaldsson Message-ID: <20040203181106.GI61476@cre85086tuf.rose.agilent.com> References: <20040203134103.GM12156@isnic.is> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040203134103.GM12156@isnic.is> User-Agent: Mutt/1.4i cc: freebsd-scsi@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: HP Fibre Channel HBA (D8602A/B) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2004 18:10:55 -0000 Oli- This is a 1Gb FC adapter based on the Tachyon TL chip. I have a closed source driver that might work, and someday hope to have time to write an open source one. Not that I'm advocating a different OS, but the Compaq driver on Linux should either work out of the box with this card or might need a couple of minor modifications to work. On Tue, Feb 03, 2004 at 08:41:03AM -0500, Olafur Osvaldsson wrote: > I couldn't find anything about it in the archives about it but is the > HP Fibre Channel HBA (D8602A/B) controller supported in FreeBSD? > > /Oli > > P.S. Please Cc any answer as I'm not on the lists. -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-scsi@FreeBSD.ORG Thu Feb 5 08:53:54 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E4C416A4CE for ; Thu, 5 Feb 2004 08:53:54 -0800 (PST) Received: from mailoff.mtu.edu (mailoff.mtu.edu [141.219.70.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5085443D39 for ; Thu, 5 Feb 2004 08:53:52 -0800 (PST) (envelope-from jamyles@mtu.edu) Received: from node40. (node40.mtu.edu [141.219.69.40]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id i15Gros01485 for ; Thu, 5 Feb 2004 11:53:50 -0500 (EST) Received: from node24 (node24.mtu.edu [141.219.68.124]) by node40. (8.12.8/8.12.8) with ESMTP id i15Grnta007416 for ; Thu, 5 Feb 2004 11:53:50 -0500 Received: from campus4.mtu.edu ([141.219.70.7]) by node24 (MailMonitor for SMTP v1.2.2 ) ; Thu, 5 Feb 2004 11:53:49 -0500 (EST) Received: from node21. (node21.mtu.edu [141.219.68.121]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id i15Grkx21136 for ; Thu, 5 Feb 2004 11:53:46 -0500 (EST) Received: from dev.ice.mtu.edu (dev.ice.mtu.edu [141.219.60.48]) i15Grk5R021857 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Thu, 5 Feb 2004 11:53:46 -0500 Date: Thu, 5 Feb 2004 11:53:40 -0500 (EST) From: Joshua Myles X-X-Sender: jamyles@dev.ice.mtu.edu To: freebsd-scsi@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Adaptec 3120S "Engine connect failed: Open" X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2004 16:53:54 -0000 Hi all, I'm using a 3120S (256 MB cache, battery) in a Dell PowerEdge 2650 running 4.9-RELEASE-p1. A few days after installing the controller (and successfully building arrays), raidutil (adptfbsd-3.14) stopped working, giving this error: Engine connect failed: Open Reinstalling the package didn't work; neither did rebooting. The arrays themselves are still working fine. Possibly relevant 'dmesg' output: asr0: mem 0xe0000000-0xefffffff irq 11 at device 6.0 on pci1 asr0: major=154 asr0: ADAPTEC 3210S FW Rev. 380E, 2 channel, 256 CCBs, Protocol I2O Any insight or troubleshooting hints? Thanks, Josh