From owner-freebsd-scsi Sun Aug 8 23: 3:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 7511614E29; Sun, 8 Aug 1999 23:03:18 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id CAA05955; Mon, 9 Aug 1999 02:01:18 -0400 (EDT) Message-Id: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 09 Aug 1999 02:14:07 -0400 To: questions@freebsd.org From: Mike Tancsa Subject: AHC errors. Bad disk or bad firmware, or bug in driver ? Cc: scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am running FreeBSD 2.2.8-STABLE #0: Thu Aug 5 box that ran into some disk problems tonight. All of a sudden on my console, it was filled with the following. Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 36 times Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Bu Aug 8 20:53:12 granite /kernel: sy Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 36 times Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Aug 8 20:53:12 granite /kernel: Busy Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 3 times Aug 8 20:53:12 granite /kernel: ahc0:A:2: ahc_intr - referenced scb not valid during seqint 0x71 scb(7) Aug 8 20:53:12 granite /kernel: ahc0: WARNING no command for scb 7 (cmdcmplt) Aug 8 20:53:12 granite /kernel: QOUTCNT == 1 Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 27 times Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Aug 8 20:53:12 granite /kernel: Busy Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 36 times Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Targ Aug 8 20:53:12 granite /kernel: et Busy Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:12 granite last message repeated 36 times Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): T Aug 8 20:53:12 granite /kernel: arget Busy Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:20 granite last message repeated 79 times Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:21 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:21 granite /kernel: Ordered Tag queued Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while recovery in progress Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xc timedout while recovery in progress Aug 8 20:53:26 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:47 granite /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Abort Message Sent Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 13 - Abort Tag Completed. Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): no longer in timeout Aug 8 20:53:47 granite /kernel: Ordered Tag sent Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:47 granite last message repeated 3 times Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:47 granite /kernel: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:47 granite /kernel: Ordered Tag queued Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while recovery in progress Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:47 granite /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Abort Message Sent Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 12 - Abort Tag Completed. Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): no longer in timeout Aug 8 20:53:47 granite /kernel: Ordered Tag sent Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:47 granite last message repeated 3 times Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:47 granite /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:47 granite /kernel: Ordered Tag queued Aug 8 20:53:47 granite /kernel: Ordered Tag sent Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Tar Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:47 granite last message repeated 36 times Aug 8 20:53:47 granite /kernel: sd2(ahc0:2:0): Target Bu Aug 8 20:53:47 granite /kernel: sy Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:48 granite last message repeated 36 times Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Aug 8 20:53:48 granite /kernel: Busy Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:48 granite last message repeated 11 times Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Aug 8 20:53:48 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Queueing an Abort SCB Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Abort Message Sent Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): SCB 0 - Abort Tag Completed. Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): no longer in timeout Aug 8 20:53:48 granite /kernel: sd2(ahc0:2:0): Target Busy Aug 8 20:53:48 granite last message repeated 14 times Aug 8 20:53:48 granite /kernel: s And then the target busy just keeps repeating itself over and over. I had to reboot the machine and unfortunately, it had a few errors, pretty well all of which we were able to recover. The drive in question is a Viking II (ahc0:2:0): "QUANTUM VIKING II 4.5WSE 4110" type 0 fixed SCSI 2 sd2(ahc0:2:0): Direct-Access 4350MB (8910423 512 byte sectors) ahc0: target 4 Tagged Queuing Device If it was simply a media error, would it not either recover or panic ? Why the seemingly endless loop of "Target Busy" Thanks, ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 10: 0:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id EB1691500E for ; Mon, 9 Aug 1999 10:00:18 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA29078; Mon, 9 Aug 1999 10:58:13 -0600 (MDT) (envelope-from ken) Message-Id: <199908091658.KAA29078@panzer.kdm.org> Subject: Re: management utilities for external array In-Reply-To: <37AB1619.945B8123@delanet.com> from "Stephen C. Comoletti" at "Aug 6, 1999 01:06:34 pm" To: stevec@delanet.com (Stephen C. Comoletti) Date: Mon, 9 Aug 1999 10:58:13 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephen C. Comoletti wrote... > I'm not sure if this is the right place for this..so if not, please let > me know where to send it. What I'm looking for is a set of raid > management utilities for an external array. My company recently > purchased a external Metastor raid5 array. It has a Symbios Logic Series > 3 differential controller with 64mb. With the package came bundled an NT > management/setup utility, and one for BSDI. The NFS server I put > together is a DEC 300i+ with 256mb ram, Qlogic fw-scsi adapter and > 100baseT ether running FreeBSD 3.2r. I took a look at the > BSDI package...it looks like a package made by Symbios.. It included the > following programs: drivutil* healthck* logutil* > parityck* raidutil* fwutil* lad* > nvutil* putplog* rmscript.sh* > Essentially, setup and monitoring utilities....While I can not run them, > I had man pages to go over..thats about it. Is there any equivalent type > of package for > FreeBSD? > > Please cc me in any replies as I am not on this list. I haven't heard of any FreeBSD utilities for that array. Unless the vendor supplies FreeBSD binaries, you'll need to boot NT or BSD/OS to run the configuration utilities. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 10:10:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 352BF15276; Mon, 9 Aug 1999 10:10:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA29115; Mon, 9 Aug 1999 11:05:02 -0600 (MDT) (envelope-from ken) Message-Id: <199908091705.LAA29115@panzer.kdm.org> Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? In-Reply-To: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> from Mike Tancsa at "Aug 9, 1999 02:14:07 am" To: mike@sentex.net (Mike Tancsa) Date: Mon, 9 Aug 1999 11:05:02 -0600 (MDT) Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa wrote... > > Hi, > I am running FreeBSD 2.2.8-STABLE #0: Thu Aug 5 box that ran into some > disk problems tonight. All of a sudden on my console, it was filled with > the following. > > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy > Aug 8 20:53:12 granite last message repeated 36 times > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Bu > Aug 8 20:53:12 granite /kernel: sy > Aug 8 20:53:12 granite /kernel: sd2(ahc0:2:0): Target Busy > Aug 8 20:53:12 granite last message repeated 36 times [ ... ] > Aug 8 20:53:21 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 > SSTAT1 = 0xa > Aug 8 20:53:21 granite /kernel: Ordered Tag queued > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while > recovery in progress > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xc timedout while > recovery in progress > Aug 8 20:53:26 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while [ ... ] > And then the target busy just keeps repeating itself over and over. I had > to reboot the machine and unfortunately, it had a few errors, pretty well > all of which we were able to recover. The drive in question is a Viking II > > (ahc0:2:0): "QUANTUM VIKING II 4.5WSE 4110" type 0 fixed SCSI 2 > sd2(ahc0:2:0): Direct-Access 4350MB (8910423 512 byte sectors) > ahc0: target 4 Tagged Queuing Device > > If it was simply a media error, would it not either recover or panic ? Why > the seemingly endless loop of "Target Busy" It smells like bogus firmware, but it's kinda hard to say. You might check to see whether there is new firmware available for that disk. Quantum has firmware and firmware loaders on their ftp site. You would probably do a lot better if you went to 3.x/CAM. The new CAM SCSI subsystem can generally handle unruly drives much better than the old SCSI subsystem. (In fact, we used Quantum Atlas II's with bogus firmware to test some of the error recovery code.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 10:12: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id D9D8815276; Mon, 9 Aug 1999 10:12:02 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA27913; Mon, 9 Aug 1999 13:09:58 -0400 (EDT) Message-Id: <3.0.5.32.19990809130844.00eb8d50@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 09 Aug 1999 13:08:44 -0400 To: "Kenneth D. Merry" From: Mike Tancsa Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG In-Reply-To: <199908091705.LAA29115@panzer.kdm.org> References: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >It smells like bogus firmware, but it's kinda hard to say. You might check >to see whether there is new firmware available for that disk. Quantum has >firmware and firmware loaders on their ftp site. > >You would probably do a lot better if you went to 3.x/CAM. The new CAM >SCSI subsystem can generally handle unruly drives much better than the >old SCSI subsystem. (In fact, we used Quantum Atlas II's with bogus >firmware to test some of the error recovery code.) Thanks for having a look. I do plan to upgrade the box to 3.x/CAM. However, its a big busy box with a lot of users and services, so it will take us a bit. We are also looking at a Legacy external RAID box to deploy with this new server. Hmmm... While on the topic, what would you reccomend as an external RAID box ? The Legacy is about $5-6K USD which I guess is reasonable with 4 8gig drives. If anyone knows SCSI, I guess it would be you and Justin ;-) Thanks again, ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 10:32:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6B2F8152FE; Mon, 9 Aug 1999 10:31:01 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA29302; Mon, 9 Aug 1999 11:28:25 -0600 (MDT) (envelope-from ken) Message-Id: <199908091728.LAA29302@panzer.kdm.org> Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? In-Reply-To: <3.0.5.32.19990809130844.00eb8d50@staff.sentex.ca> from Mike Tancsa at "Aug 9, 1999 01:08:44 pm" To: mike@sentex.net (Mike Tancsa) Date: Mon, 9 Aug 1999 11:28:25 -0600 (MDT) Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa wrote... > >It smells like bogus firmware, but it's kinda hard to say. You might check > >to see whether there is new firmware available for that disk. Quantum has > >firmware and firmware loaders on their ftp site. > > > >You would probably do a lot better if you went to 3.x/CAM. The new CAM > >SCSI subsystem can generally handle unruly drives much better than the > >old SCSI subsystem. (In fact, we used Quantum Atlas II's with bogus > >firmware to test some of the error recovery code.) > > Thanks for having a look. I do plan to upgrade the box to 3.x/CAM. > However, its a big busy box with a lot of users and services, so it will > take us a bit. We are also looking at a Legacy external RAID box to deploy > with this new server. Hmmm... While on the topic, what would you reccomend > as an external RAID box ? The Legacy is about $5-6K USD which I guess is > reasonable with 4 8gig drives. If anyone knows SCSI, I guess it would be > you and Justin ;-) Yeah, I understand, it takes a while to upgrade. As far as RAID boxes, I'm not sure I would recommend anything, because I don't have any direct experience with external RAID boxes. I will throw out a couple of things, though: - Charles Sprickman has had a fair bit of trouble with multiple channels on a single CMD array. I'm not sure whether he is still having problems. - On the other hand, Karl Denninger , has had good success with CMD controllers. - ftp.cdrom.com uses a Mylex external RAID controller, and I think other folks have gotten good results with them as well. For a small caveat (i.e. you shouldn't normally run into this problem, but you could) see my mail exchange with Joe Greco from early July. Just search for "DAC960SX" and you should see it. The bug in question was a FreeBSD bug, not really a bug with the controller. - I've seen various people mention other external RAID controllers on the lists, but I can't remember which. I'd suggest looking through the freebsd-scsi archives. I've never heard of a Legacy RAID box. Does the 5-6K include the drives or not? And 8 gig drives? One thing you don't want to skimp on is drive quality...most 8 gig SCSI drives I remember seeing are pretty low-end. I would recommend sticking with high-end Seagate or IBM disks. You'll want something that does tagged queueing, and handles a reasonable number of transactions. And, most importantly, you'll want a controller without nasty firmware bugs. :) FreeBSD/CAM has a tendency to expose problems that don't crop up as often in other OSes. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 11:17:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id DA9D514A13; Mon, 9 Aug 1999 11:17:07 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id OAA15953; Mon, 9 Aug 1999 14:13:35 -0400 (EDT) Message-Id: <3.0.5.32.19990809141220.01086510@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 09 Aug 1999 14:12:20 -0400 To: "Kenneth D. Merry" From: Mike Tancsa Subject: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) Cc: scsi@freebsd.org, questions@freebsd.org In-Reply-To: <199908091728.LAA29302@panzer.kdm.org> References: <3.0.5.32.19990809130844.00eb8d50@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:28 AM 8/9/99 -0600, Kenneth D. Merry wrote: >Mike Tancsa wrote... >> >You would probably do a lot better if you went to 3.x/CAM. The new CAM >> >SCSI subsystem can generally handle unruly drives much better than the >> >old SCSI subsystem. (In fact, we used Quantum Atlas II's with bogus >> >firmware to test some of the error recovery code.) >> >> Thanks for having a look. I do plan to upgrade the box to 3.x/CAM. >> However, its a big busy box with a lot of users and services, so it will >> take us a bit. We are also looking at a Legacy external RAID box to deploy >> with this new server. Hmmm... While on the topic, what would you reccomend >> as an external RAID box ? The Legacy is about $5-6K USD which I guess is >> reasonable with 4 8gig drives. If anyone knows SCSI, I guess it would be >> you and Justin ;-) > >Yeah, I understand, it takes a while to upgrade. > >As far as RAID boxes, I'm not sure I would recommend anything, because I >don't have any direct experience with external RAID boxes. > >I will throw out a couple of things, though: > >- Charles Sprickman has had a fair bit of trouble with > multiple channels on a single CMD array. I'm not sure whether he is > still having problems. > >- On the other hand, Karl Denninger , has had good > success with CMD controllers. > >- ftp.cdrom.com uses a Mylex external RAID controller, and I think other > folks have gotten good results with them as well. For a small caveat > (i.e. you shouldn't normally run into this problem, but you could) see > my mail exchange with Joe Greco from early July. Just search for > "DAC960SX" and you should see it. The bug in question was a FreeBSD bug, > not really a bug with the controller. > >- I've seen various people mention other external RAID controllers on the > lists, but I can't remember which. I'd suggest looking through the > freebsd-scsi archives. > >I've never heard of a Legacy RAID box. Does the 5-6K include the drives or >not? And 8 gig drives? One thing you don't want to skimp on is drive >quality...most 8 gig SCSI drives I remember seeing are pretty low-end. I >would recommend sticking with high-end Seagate or IBM disks. The exact price was $4700 Canadian, and then they wanted to charge me about $900 CDN per Segate Medalist or $1000CDN for I think the IBM Deskstar. So I guess, ~6500 USD with 5 drives >You'll want something that does tagged queueing, and handles a reasonable >number of transactions. And, most importantly, you'll want a controller >without nasty firmware bugs. :) FreeBSD/CAM has a tendency to expose >problems that don't crop up as often in other OSes. Before making any commitments, I do plan to dejanews through as many threads as possible. The legacy (www.legacy.ca) box looks nice in that the warrentee is decent (overnight replacement from down the road from us for 3yrs), and the price seems nice. But stability is what I am looking for most of all. +-$1K at that range is not that critical.. stability is the key for me. I am not sure what I would end up paying for in the equiv. Mylex device. Thanks again for your input, I appriciate anything you can share on this topic. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 12: 6:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id CECFE14D4E; Mon, 9 Aug 1999 12:06:19 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA29799; Mon, 9 Aug 1999 13:04:00 -0600 (MDT) (envelope-from ken) Message-Id: <199908091904.NAA29799@panzer.kdm.org> Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-Reply-To: <3.0.5.32.19990809141220.01086510@staff.sentex.ca> from Mike Tancsa at "Aug 9, 1999 02:12:20 pm" To: mike@sentex.net (Mike Tancsa) Date: Mon, 9 Aug 1999 13:04:00 -0600 (MDT) Cc: scsi@freebsd.org, questions@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa wrote... > At 11:28 AM 8/9/99 -0600, Kenneth D. Merry wrote: > >Yeah, I understand, it takes a while to upgrade. > > > >As far as RAID boxes, I'm not sure I would recommend anything, because I > >don't have any direct experience with external RAID boxes. > > > >I will throw out a couple of things, though: > > > >- Charles Sprickman has had a fair bit of trouble with > > multiple channels on a single CMD array. I'm not sure whether he is > > still having problems. > > > >- On the other hand, Karl Denninger , has had good > > success with CMD controllers. > > > >- ftp.cdrom.com uses a Mylex external RAID controller, and I think other > > folks have gotten good results with them as well. For a small caveat > > (i.e. you shouldn't normally run into this problem, but you could) see > > my mail exchange with Joe Greco from early July. Just search for > > "DAC960SX" and you should see it. The bug in question was a FreeBSD bug, > > not really a bug with the controller. > > > >- I've seen various people mention other external RAID controllers on the > > lists, but I can't remember which. I'd suggest looking through the > > freebsd-scsi archives. > > > >I've never heard of a Legacy RAID box. Does the 5-6K include the drives or > >not? And 8 gig drives? One thing you don't want to skimp on is drive > >quality...most 8 gig SCSI drives I remember seeing are pretty low-end. I > >would recommend sticking with high-end Seagate or IBM disks. > > The exact price was $4700 Canadian, and then they wanted to charge me about > $900 CDN per Segate Medalist or $1000CDN for I think the IBM Deskstar. So I > guess, ~6500 USD with 5 drives Hmm, it sounds like they're going with low-end drives. I'd stay away from the Seagate Medalists, we've got quirk entries in the CAM transport layer to attest to the firmware "quality" on the Medalist Pro. I'd go with the IBM Deskstar, although I can't guarantee they're good, there's probably a better chance of their firmware being okay than the Seagate Medalists. Most likely they've qualified both types of drive with their hardware, and therefore they're sure those drives will work. > >You'll want something that does tagged queueing, and handles a reasonable > >number of transactions. And, most importantly, you'll want a controller > >without nasty firmware bugs. :) FreeBSD/CAM has a tendency to expose > >problems that don't crop up as often in other OSes. > > Before making any commitments, I do plan to dejanews through as many > threads as possible. The legacy (www.legacy.ca) box looks nice in that > the warrentee is decent (overnight replacement from down the road from us > for 3yrs), and the price seems nice. But stability is what I am looking > for most of all. +-$1K at that range is not that critical.. stability is > the key for me. I am not sure what I would end up paying for in the equiv. > Mylex device. Yes, I think stability is very important. I would be slightly concerned with Legacy's choice of drives. More important than that, though, is how good/stable the firmware on their RAID controller is. i.e. how they handle under load. If you want to go with that solution, you may want to try to get an evaluation unit first, so you can subject it to a higher than normal operating load and see what happens. Other folks have had success with Mylex controllers, and it might be worthwhile going with one of those, along with some nice high-end drives. Like I said before, though, I haven't had any direct experience with external RAID boxes, so all I can talk about is what other folks have mentioned. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 13: 4:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.eclipse.net.uk (proteus.eclipse.net.uk [195.188.32.118]) by hub.freebsd.org (Postfix) with ESMTP id EE81B1543A; Mon, 9 Aug 1999 13:04:09 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by proteus.eclipse.net.uk (Postfix) with ESMTP id DFEE79B05; Mon, 9 Aug 1999 21:01:49 +0100 (BST) Message-ID: <37AF3420.370FB158@eclipse.net.uk> Date: Mon, 09 Aug 1999 21:03:44 +0100 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: en-GB MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Mike Tancsa , scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) References: <199908091904.NAA29799@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Other folks have had success with Mylex controllers, and it might be > worthwhile going with one of those, along with some nice high-end drives. Based on what I found in raid.pdf, I think it might be worth asking Legacy if they use raid controllers made by Mylex in their arrays. A lot of RAID kit is oem'd and that model number sounds very familiar :) > Management Port > Cause: The SmartARRAY cannot establish > communication with the DAC960 hardware > RAID controller through the AEMI > management port. > Warning: Panel flashes and audible alarm sounds. > Solution: Ensure that the server is turned on after > SmartARRAY is turned on and that the server is > turned off before the SmartARRAY is turned > off. It is normal for this error condition to > appear when the SmartARRAY is turned on > before the server or when the server is turned off > before the SmartARRAY. If the condition is not > a result of the above, contact Technical Support > (see Chapter 5 - Customer Support for contact > information). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 13:44:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 87900152AF for ; Mon, 9 Aug 1999 13:44:55 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA00283 for ; Mon, 9 Aug 1999 13:41:44 -0700 Date: Mon, 9 Aug 1999 13:41:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: scsi@freebsd.org Subject: NCR/Multia Problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org nopilt.feral.com > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (mem 4458e000:c0000004). ncr0: regdump: da 00 00 13 47 08 06 1f 75 08 86 00 80 00 0f 02. ncr0: restart (fatal error). ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth 84:88080000). ncr0: script cmd = 88080000 ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. ncr0: restart (fatal error). ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth a0:c0000004). ncr0: script cmd = c0000004 ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. ncr0: restart (fatal error). (da1:ncr0:0:6:0): COMMAND FAILED (9 ff) @0xfffffe000058e400. What is this error? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 13:47:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DE1AB152AF for ; Mon, 9 Aug 1999 13:47:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA00299 for ; Mon, 9 Aug 1999 13:45:15 -0700 Date: Mon, 9 Aug 1999 13:45:14 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: scsi@FreeBSD.ORG Subject: Sorry- more info ...Re: NCR/Multia Problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -current as of today, and this is also followed by: Aug 9 13:40:28 nopilt sshd[384]: log: ROOT LOGIN as 'root' from farrago ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (script c:7810ff00). ncr0: script cmd = 7810ff00 ncr0: regdump: da 00 00 13 47 08 06 1f 75 08 86 00 80 00 0f 02. ncr0: restart (fatal error). ncr0:6: ERROR (a0:0) (0-a7-80) (8/13) @ (script 5a4:80000000). ncr0: script cmd = 80000000 ncr0: regdump: da 10 80 13 47 08 06 1f 35 00 86 a7 80 00 07 02. ncr0: restart (fatal error). (da1:ncr0:0:6:0): COMMAND FAILED (9 ff) @0xfffffe000058e400. nopilt.feral.com > nopilt.feral.com > nopilt.feral.com > nopilt.feral.com > sync ^Cncr0: timeout nccb=0xfffffe000058e400 (skip) ncr0: timeout nccb=0xfffffe000058e800 (skip) ncr0: timeout nccb=0xfffffe000058ec00 (skip) ncr0: timeout nccb=0xfffffe000058f000 (skip) ncr0: timeout nccb=0xfffffe000058e400 (skip) ncr0: timeout nccb=0xfffffe000058e800 (skip) ncr0: timeout nccb=0xfffffe000058ec00 (skip) Setup is a simple one: Internal Toshiba 335MB External Seagate 4GB. Both narrow. Active terminator. > > nopilt.feral.com > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (mem > 4458e000:c0000004). > ncr0: regdump: da 00 00 13 47 08 06 1f 75 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth 84:88080000). > ncr0: script cmd = 88080000 > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth a0:c0000004). > ncr0: script cmd = c0000004 > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > (da1:ncr0:0:6:0): COMMAND FAILED (9 ff) @0xfffffe000058e400. > > > What is this error? > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 13:53: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 857791523B; Mon, 9 Aug 1999 13:53:05 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id QAA26979; Mon, 9 Aug 1999 16:50:09 -0400 (EDT) Message-Id: <3.0.5.32.19990809164854.01c08750@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 09 Aug 1999 16:48:54 -0400 To: Stuart Henderson From: Mike Tancsa Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) Cc: scsi@FreeBSD.ORG, questions@FreeBSD.ORG In-Reply-To: <37AF3420.370FB158@eclipse.net.uk> References: <199908091904.NAA29799@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Based on what I found in raid.pdf, I think it might be worth asking >Legacy if they use raid controllers made by Mylex in their arrays. > >A lot of RAID kit is oem'd and that model number sounds very familiar :) > >> Management Port >> Cause: The SmartARRAY cannot establish >> communication with the DAC960 hardware Wow! As my hockey coach used to yell, "Good eye!". Thanks for pointing that out. What I am not clear on from glancing at the mylex site is that they seem to be cards only and cards with boxes ? Am I right in thinking that you supply the case ? From the .pdf file "The DAC960S is designed to fit anywhere inside a disk array enclosure, including in a 5-1/4" inch drive bay. And you don't need disk driver software, because it interfaces directly through a SCSI adapter. An optional DBX960S distribution board fits together with the DAC960SU edge connectors, and provides standard connection for both the host and drive channels and the serial and I/O ports. Or, the DAC960SU can be plugged directly into the array's backplane. " Do you save substantially 'putting it together' yourself ? What sort of price have people paid (in USD), and who is generally a good outlet to buy from ? Thanks for any input anyone can provide on this topic. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 9 22: 4:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id CDD5114FBE for ; Mon, 9 Aug 1999 22:04:46 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11E2yR-0005Ds-00; Mon, 9 Aug 1999 20:53:15 -0700 Date: Mon, 9 Aug 1999 20:52:56 -0700 (PDT) From: Tom To: Mike Tancsa Cc: "Kenneth D. Merry" , scsi@freebsd.org Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-Reply-To: <3.0.5.32.19990809141220.01086510@staff.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 9 Aug 1999, Mike Tancsa wrote: > The exact price was $4700 Canadian, and then they wanted to charge me about > $900 CDN per Segate Medalist or $1000CDN for I think the IBM Deskstar. So I > guess, ~6500 USD with 5 drives > > >You'll want something that does tagged queueing, and handles a reasonable > >number of transactions. And, most importantly, you'll want a controller > >without nasty firmware bugs. :) FreeBSD/CAM has a tendency to expose > >problems that don't crop up as often in other OSes. > > Before making any commitments, I do plan to dejanews through as many > threads as possible. The legacy (www.legacy.ca) box looks nice in that > the warrentee is decent (overnight replacement from down the road from us > for 3yrs), and the price seems nice. But stability is what I am looking > for most of all. +-$1K at that range is not that critical.. stability is > the key for me. I am not sure what I would end up paying for in the equiv. > Mylex device. Legacy make some pretty amusing stuff. They sell direct and via various wholesellers (ie Globelle). I can get Legacy stuff cheaper from Globelle than I can direct from Legacy. Legacy is basically just an integrator. They slap a RAID controller, and some drives together in a box, and then put their name on it. In fact, I think Legacy uses CMD RAID units in their boxes. There is nothing that Legacy is doing that you can't do yourself. Overnight replacement is no concern for me, as overnight is still too long! And if you've lost data because of the failure... There should be a enough resilency so that failures aren't a problem. All high-end drives have 5yr warranties, BTW. If I was going to setup a high-avail box, I'd use two CMD raid units. They have some kind of fail over mode where one can take over if one fails (I don't belive Legacy gives you this as an option, but you can if you build it yourself). Disks would combined with RAID-5, and an online spare (or two). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 0: 1: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 60C0D14FC6; Tue, 10 Aug 1999 00:01:02 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id JAA23693; Tue, 10 Aug 1999 09:58:54 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id E1BFFCA; Tue, 10 Aug 1999 09:59:06 +0300 (EEST) Date: Tue, 10 Aug 1999 09:59:06 +0300 From: Vallo Kallaste To: "Kenneth D. Merry" Cc: Mike Tancsa , questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? Message-ID: <19990810095906.A2512@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <4.1.19990808234210.03c6b2d0@granite.sentex.ca> <199908091705.LAA29115@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908091705.LAA29115@panzer.kdm.org>; from Kenneth D. Merry on Mon, Aug 09, 1999 at 11:05:02AM -0600 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Aug 09, 1999 at 11:05:02AM -0600, "Kenneth D. Merry" wrote: > > Aug 8 20:53:21 granite /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 > > SSTAT1 = 0xa > > Aug 8 20:53:21 granite /kernel: Ordered Tag queued > > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0x0 timedout while > > recovery in progress > > Aug 8 20:53:21 granite /kernel: sd2(ahc0:2:0): SCB 0xc timedout while > > recovery in progress > > Aug 8 20:53:26 granite /kernel: sd2(ahc0:2:0): SCB 0xd - timed out while > [ ... ] > > > > And then the target busy just keeps repeating itself over and over. I had > > to reboot the machine and unfortunately, it had a few errors, pretty well > > all of which we were able to recover. The drive in question is a Viking II > > > > (ahc0:2:0): "QUANTUM VIKING II 4.5WSE 4110" type 0 fixed SCSI 2 > > sd2(ahc0:2:0): Direct-Access 4350MB (8910423 512 byte sectors) > > ahc0: target 4 Tagged Queuing Device > > > > If it was simply a media error, would it not either recover or panic ? Why > > the seemingly endless loop of "Target Busy" > > It smells like bogus firmware, but it's kinda hard to say. You might check > to see whether there is new firmware available for that disk. Quantum has > firmware and firmware loaders on their ftp site. I do have two of these drives and upgraded the firmware quite a while ago, had problems with older firmware, possibly relative to my ncr based controller. For now I'm running with these about a year without any problems. For what it's worth, they have working 64 tags also. I'm satisfied :) da0 at ncr0 bus 0 target 5 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ncr0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 10: 7: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 02F1314E87 for ; Tue, 10 Aug 1999 10:07:02 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 180 invoked by uid 1825); 10 Aug 1999 17:04:16 -0000 Date: Tue, 10 Aug 1999 13:04:16 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: freebsd-scsi@freebsd.org Subject: Adaptec ARO-1130 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I searched the website, documentation and mailing list archives, but came up empty. I see that FreeBSD supports the Adaptec AIC-7896 on-board SCSI, but I can find no mention of the ARO-1130U2, which is a RAID subsystem add-on for the AIC-7896. Is it supported? If not, is anyone known to be working on it? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 10: 7:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id E76E814E87 for ; Tue, 10 Aug 1999 10:07:36 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA17561; Tue, 10 Aug 1999 13:05:59 -0400 (EDT) Message-Id: <4.1.19990810125322.042afb60@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 10 Aug 1999 13:19:02 -0400 To: Tom From: Mike Tancsa Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) Cc: scsi@freebsd.org In-Reply-To: References: <3.0.5.32.19990809141220.01086510@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Legacy make some pretty amusing stuff. They sell direct and via various >wholesellers (ie Globelle). I can get Legacy stuff cheaper from Globelle >than I can direct from Legacy. > > Legacy is basically just an integrator. They slap a RAID controller, >and some drives together in a box, and then put their name on it. In >fact, I think Legacy uses CMD RAID units in their boxes. Someone else pointed out that from the docs on Legacy's web site, they seem to be OEM'ing Mylex "Management Port Cause: The SmartARRAY cannot establish communication with the DAC960 hardware" > There is nothing that Legacy is doing that you can't do yourself. >Overnight replacement is no concern for me, as overnight is still too >long! And if you've lost data because of the failure... There should be >a enough resilency so that failures aren't a problem. All high-end drives >have 5yr warranties, BTW. > > If I was going to setup a high-avail box, I'd use two CMD raid units. >They have some kind of fail over mode where one can take over if one >fails (I don't belive Legacy gives you this as an option, but you can if >you build it yourself). Disks would combined with RAID-5, and an online >spare (or two). Unfortunately my budget is limited. I dont want to go with the cheapest solution out there, nor can I afford the most expensive. For me, an external RAID box will be a step up rather than relying on tape backups and retiring old drives before they might have a chance to fail. As for the CMD units, have you had any direct experience with them ? Thanks, ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 10:14:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id DA6D914E87; Tue, 10 Aug 1999 10:14:29 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA19779; Tue, 10 Aug 1999 13:14:28 -0400 (EDT) Message-Id: <4.1.19990810131923.042d25e0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 10 Aug 1999 13:27:30 -0400 To: vallo@matti.ee From: Mike Tancsa Subject: Re: AHC errors. Bad disk or bad firmware, or bug in driver ? Cc: questions@FreeBSD.ORG, scsi@FreeBSD.ORG In-Reply-To: <19990810095906.A2512@myhakas.matti.ee> References: <199908091705.LAA29115@panzer.kdm.org> <4.1.19990808234210.03c6b2d0@granite.sentex.ca> <199908091705.LAA29115@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > If it was simply a media error, would it not either recover or panic ? Why >> > the seemingly endless loop of "Target Busy" >> >> It smells like bogus firmware, but it's kinda hard to say. You might check >> to see whether there is new firmware available for that disk. Quantum has >> firmware and firmware loaders on their ftp site. > >I do have two of these drives and upgraded the firmware quite a while >ago, had problems with older firmware, possibly relative to my ncr based >controller. For now I'm running with these about a year without any >problems. For what it's worth, they have working 64 tags also. I'm >satisfied :) Hi, Thanks for the response. The drive had been running fine for almost a year as well until those errors. The server is relativly busy pushing out 40K of email a day as well as user web pages. I still have the drive, but its not being used in the server as I put our 'cold' spare in until I can sort out what we will do for a better overall plan with RAID in a month or so. When that happens, I will try and get a better look at the drive and perhaps upgrade its firmware and reformat etc. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 10:33:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from euclid.earthbroadcasting.com (euclid.earthbroadcasting.com [207.135.131.139]) by hub.freebsd.org (Postfix) with ESMTP id 7205A150AA for ; Tue, 10 Aug 1999 10:33:54 -0700 (PDT) (envelope-from chris@earthbroadcasting.com) Received: from ezln23.thedial.com ([207.135.131.130] helo=earthbroadcasting.com) by euclid.earthbroadcasting.com with esmtp (Exim 2.12 #1) id 11EFn0-000DvY-00 for scsi@freebsd.org; Tue, 10 Aug 1999 11:34:18 -0600 Message-ID: <37B0623C.401BA58F@earthbroadcasting.com> Date: Tue, 10 Aug 1999 11:32:44 -0600 From: Christopher Taylor X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Tape backup solutions Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm thinking about using the Spectra-Logic AIT TreeFrog product for backups under FreeBSD. Below is a list of backup software that works with this product. http://www.spectralogic.com/isv/TreeFrogpartners.htm Do any of you have experience with this, or any other tape library hardware under FreeBSD? Can I use this product or am I stuck with using a single AIT-2 drive? --Chris -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Christopher Taylor Technical Director Earth Broadcasting Corporation (EBC) 415 East 200 South Salt Lake City, Utah 84111 phone: (801) 322-3949 cell: (801) 541-8287 email: chris@thedial.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 11: 9:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id DF46A15095 for ; Tue, 10 Aug 1999 11:09:32 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA36506; Tue, 10 Aug 1999 12:09:01 -0600 (MDT) (envelope-from ken) Message-Id: <199908101809.MAA36506@panzer.kdm.org> Subject: Re: Tape backup solutions In-Reply-To: <37B0623C.401BA58F@earthbroadcasting.com> from Christopher Taylor at "Aug 10, 1999 11:32:44 am" To: chris@earthbroadcasting.com (Christopher Taylor) Date: Tue, 10 Aug 1999 12:09:01 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher Taylor wrote... > I'm thinking about using the Spectra-Logic AIT TreeFrog product for > backups under FreeBSD. Below is a list of backup software that works > with this product. > > http://www.spectralogic.com/isv/TreeFrogpartners.htm > > Do any of you have experience with this, or any other tape library > hardware under FreeBSD? Can I use this product or am I stuck with using > a single AIT-2 drive? Most standard SCSI tape libraries should work fine under FreeBSD with the ch(4) driver and chio(1). I've got a Qualstar changer with an AIT-1 drive in use daily, an Exabyte 10-i that I used to port the ch(4) driver, and I've even used the ch(4) driver on an Ampex DST 712 changer. I've never used a Spectra Logic changer, but it's possible someone else on the lists has. My guess is that it will work, but you might want to see if you can get it on an evaluation basis to make sure it works before you actually pay for it. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 11:21:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 0BE9414E7F for ; Tue, 10 Aug 1999 11:21:31 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 79804F818; Tue, 10 Aug 1999 14:21:12 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 6D6019B17; Tue, 10 Aug 1999 14:21:12 -0400 (EDT) Date: Tue, 10 Aug 1999 14:21:12 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Christopher Taylor Cc: scsi@freebsd.org Subject: Re: Tape backup solutions In-Reply-To: <37B0623C.401BA58F@earthbroadcasting.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 10 Aug 1999, Christopher Taylor wrote: > I'm thinking about using the Spectra-Logic AIT TreeFrog product for > backups under FreeBSD. Below is a list of backup software that works > with this product. > > http://www.spectralogic.com/isv/TreeFrogpartners.htm > > Do any of you have experience with this, or any other tape library > hardware under FreeBSD? Can I use this product or am I stuck with using > a single AIT-2 drive? > I've worked with TreeFrogs and found them to be somewhat fitful in their operations. From a hardware standpoint, they aren't as reliable as, say, a comparable Exabyte or Qualstar product. However, their price may outweigh their occasional problems. Search for Spectra in the freebsd-scsi mailing list for some references. Personally, I would highly recommend Exabyte or Qualstar. I know Qualstar supports the AIT-2's (and both the AIT-1's). In addition, most SCSI changers should be supported under FreeBSD using chio(1) and ch(4). ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 14: 1:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CFC0714BF8 for ; Tue, 10 Aug 1999 14:01:26 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA03766; Tue, 10 Aug 1999 14:01:02 -0700 Date: Tue, 10 Aug 1999 14:01:02 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Christopher Taylor , scsi@FreeBSD.ORG Subject: Re: Tape backup solutions In-Reply-To: <199908101809.MAA36506@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org my recollection of spectralogic was that they were very well behaved. On Tue, 10 Aug 1999, Kenneth D. Merry wrote: > Christopher Taylor wrote... > > I'm thinking about using the Spectra-Logic AIT TreeFrog product for > > backups under FreeBSD. Below is a list of backup software that works > > with this product. > > > > http://www.spectralogic.com/isv/TreeFrogpartners.htm > > > > Do any of you have experience with this, or any other tape library > > hardware under FreeBSD? Can I use this product or am I stuck with using > > a single AIT-2 drive? > > Most standard SCSI tape libraries should work fine under FreeBSD with the > ch(4) driver and chio(1). > > I've got a Qualstar changer with an AIT-1 drive in use daily, an Exabyte > 10-i that I used to port the ch(4) driver, and I've even used the ch(4) > driver on an Ampex DST 712 changer. > > I've never used a Spectra Logic changer, but it's possible someone else on > the lists has. My guess is that it will work, but you might want to see if > you can get it on an evaluation basis to make sure it works before you > actually pay for it. > > Ken > -- > Kenneth Merry > ken@kdm.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 15:11:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id 4C01114D41 for ; Tue, 10 Aug 1999 15:11:40 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 72924 invoked from network); 10 Aug 1999 22:12:12 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 10 Aug 1999 22:12:12 -0000 Message-ID: <37B0A329.6A11562E@delanet.com> Date: Tue, 10 Aug 1999 18:09:45 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Problems with 100Base on Qlogic 1040b Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've recently upgraded to a 100base switch and put all of our main servers on it. Some of the servers are running FreeBSD 3.2r with a Qlogic 1040b controller on the MB (DEC 300i+ workstations). Problem I am having is that they refuse to negotiate at 100base on powerup or reboot. I added a 'ifconfig de0 media 100BaseTX' to the rc.conf for them, and while I have a green light on the switch, until I ifconfig down, then up the interface, it is not active. My 3.1 boxes seem somewhat more tollerant to this problem. I've put new cables in to be sure they were not an issue. I also have several MS NT4 machines on the same hardware which do not have any problems at all, which leads me to believe it's unique to this paticular driver....Are there any updates to this driver and/or changes I can make to fix this? Otherwise I'm stuck with a machine that is unable to have an unattended reboot or I run at 10Base again. Please cc me in any replies as I'm not on this list. Thanks in advance, -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 15:13:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dialup124.zpr.uni-koeln.de (1-29.K.dial.o-tel-o.net [212.144.1.29]) by hub.freebsd.org (Postfix) with ESMTP id 1B50A14D41; Tue, 10 Aug 1999 15:13:37 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: by dialup124.zpr.uni-koeln.de (Postfix, from userid 200) id B7688D23; Wed, 11 Aug 1999 00:04:20 +0200 (CEST) Date: Wed, 11 Aug 1999 00:04:20 +0200 From: Stefan Esser To: Matthew Jacob Cc: scsi@FreeBSD.ORG, Stefan Esser , stefan.esser@o-tel-o.de Subject: Re: NCR/Multia Problems? Message-ID: <19990811000420.A587@dialup124.zpr.uni-koeln.de> Reply-To: se@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Matthew Jacob on Mon, Aug 09, 1999 at 01:41:42PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-08-09 13:41 -0700, Matthew Jacob wrote: > > nopilt.feral.com > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (mem > 4458e000:c0000004). You have DSTAT=0xa0, meaning DFE + BF. DFE is not an error condition (DMA fifo empty) but just an indicator of no ongoing DMA. But BF is Bus Fault, i.e. the DMA engine (or the instruction or indirect address fetch) aborted a transfer because of a bus error. I have no idea what can trigger that kind of failure in a multia. There are a number of conditions mentioned in the NCR data books. I can look them up tomorrow, if required. Anyway: This is an indication of a hardware problem. Either the chip-set doesn't deal correctly with multiple bus masters (and there was another bus-master active), or there was a problem with memory (invalid address touched, ...). The first problem existed with early PC chip-sets, but can be worked around in some cases (disable PCI buffers, PCI bursts, ...). But I never heard that the Multia had this fault. The second scenario may be caused by hardware or software. Either there is bad memory or access to memory is blocked for extended periods of time, or the address may have been wrong and the PCI transfer was not successful for that reason. > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth 84:88080000). Same DMA status code (0xa0), but different SCRIPTS address. This points towards a hardware problem, IMHO. > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth a0:c0000004). Again. I don't have time to investigate that further, right now. Please let me know, whether this problem was caused by a software upgrade or other configuration change, or whether you never had the NCR chip working on that particular box. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 15:14:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B183C14D41 for ; Tue, 10 Aug 1999 15:14:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA03948; Tue, 10 Aug 1999 15:14:01 -0700 Date: Tue, 10 Aug 1999 15:14:01 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Stephen C. Comoletti" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problems with 100Base on Qlogic 1040b In-Reply-To: <37B0A329.6A11562E@delanet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm very confused as to why you think this is a SCSI problem. The Qlogic 1040B drives SCSI. 100BaseT is ethernet. Perhaps you've directed this question to the wrong list? On Tue, 10 Aug 1999, Stephen C. Comoletti wrote: > I've recently upgraded to a 100base switch and put all of our main > servers on it. Some of the servers are running FreeBSD 3.2r with a > Qlogic 1040b controller on the MB (DEC 300i+ workstations). Problem I am > having is that they refuse to negotiate at 100base on powerup or reboot. > I added a 'ifconfig de0 media 100BaseTX' to the rc.conf for them, and > while I have a green light on the switch, until I ifconfig down, then up > the interface, it is not active. My 3.1 boxes seem somewhat more > tollerant to this problem. I've put new cables in to be sure they were > not an issue. I also have several MS NT4 machines on the same hardware > which do not have any problems at all, which leads me to believe it's > unique to this paticular driver....Are there any updates to this driver > and/or changes I can make to fix this? Otherwise I'm stuck with a > machine that is unable to have an unattended reboot or I run at 10Base > again. > > Please cc me in any replies as I'm not on this list. > > Thanks in advance, > > -- > Stephen Comoletti > Systems Administrator > Delanet, Inc. http://www.delanet.com > ph: (302) 326-5800 fax: (302) 326-5802 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 15:20:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id 80D7815486 for ; Tue, 10 Aug 1999 15:20:49 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 76459 invoked from network); 10 Aug 1999 22:20:39 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 10 Aug 1999 22:20:39 -0000 Message-ID: <37B0A524.A7AC0866@delanet.com> Date: Tue, 10 Aug 1999 18:18:12 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problems with 100Base on Qlogic 1040b References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Apologies to all and please disregard the previous post..yes the wrong list. This is what I get for clicking too fast in my addressbook. Steve Matthew Jacob wrote: > I'm very confused as to why you think this is a SCSI problem. The Qlogic > 1040B drives SCSI. 100BaseT is ethernet. Perhaps you've directed this > question to the wrong list? > > On Tue, 10 Aug 1999, Stephen C. Comoletti wrote: > > > I've recently upgraded to a 100base switch and put all of our main > > servers on it. Some of the servers are running FreeBSD 3.2r with a > > Qlogic 1040b controller on the MB (DEC 300i+ workstations). Problem I am > > having is that they refuse to negotiate at 100base on powerup or reboot. > > I added a 'ifconfig de0 media 100BaseTX' to the rc.conf for them, and > > while I have a green light on the switch, until I ifconfig down, then up > > the interface, it is not active. My 3.1 boxes seem somewhat more > > tollerant to this problem. I've put new cables in to be sure they were > > not an issue. I also have several MS NT4 machines on the same hardware > > which do not have any problems at all, which leads me to believe it's > > unique to this paticular driver....Are there any updates to this driver > > and/or changes I can make to fix this? Otherwise I'm stuck with a > > machine that is unable to have an unattended reboot or I run at 10Base > > again. > > > > Please cc me in any replies as I'm not on this list. > > > > Thanks in advance, > > > > -- > > Stephen Comoletti > > Systems Administrator > > Delanet, Inc. http://www.delanet.com > > ph: (302) 326-5800 fax: (302) 326-5802 > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 19:56:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 99B0514E7F for ; Tue, 10 Aug 1999 19:56:38 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-133.dialup.HiWAAY.net [216.180.15.133]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA21671; Tue, 10 Aug 1999 21:54:59 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA50838; Tue, 10 Aug 1999 21:31:43 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908110231.VAA50838@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Tancsa Cc: Tom , scsi@FreeBSD.ORG From: David Kelly Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-reply-to: Message from Mike Tancsa of "Tue, 10 Aug 1999 13:19:02 EDT." <4.1.19990810125322.042afb60@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Aug 1999 21:31:43 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa writes: > Unfortunately my budget is limited. I dont want to go with the cheapest > solution out there, nor can I afford the most expensive. For me, an > external RAID box will be a step up rather than relying on tape backups and > retiring old drives before they might have a chance to fail. At the prices I've seen tossed about, one could purchase twice as many drives and use vinum in a simple mirrored mode. Or better yet, buy a RAID-5 module from Greg Lehey? About 6 months ago when I last looked, big bad 7 or 9 bay SCSI boxes with dual redundant power supplies were under $600US. Or $300 with a single power supply. Add a couple of Adaptec 2940U2W's for $300 each. Or maybe the dual version is available? These days a new MB with built-in Adaptec controller(s) is about the same price as an Adaptec PCI card. Another $200 to be covered with SCSI cables and terminators. Kingston removable trays are about $200 per drive (get the hot swap version, or is this needed or available for LVD?). Kingston is good stuff but expensive, others are less but of unknown quality. You can do without removable trays if you can schedule downtime to replace the bad drive. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 20:25:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E530014C4E for ; Tue, 10 Aug 1999 20:25:28 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA09745; Wed, 11 Aug 1999 12:55:29 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA47129; Wed, 11 Aug 1999 12:55:28 +0930 (CST) Date: Wed, 11 Aug 1999 12:55:28 +0930 From: Greg Lehey To: David Kelly Cc: Mike Tancsa , Tom , scsi@FreeBSD.ORG Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) Message-ID: <19990811125527.R31076@freebie.lemis.com> References: <199908110231.VAA50838@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908110231.VAA50838@nospam.hiwaay.net>; from David Kelly on Tue, Aug 10, 1999 at 09:31:43PM -0500 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 10 August 1999 at 21:31:43 -0500, David Kelly wrote: > Mike Tancsa writes: >> Unfortunately my budget is limited. I dont want to go with the cheapest >> solution out there, nor can I afford the most expensive. For me, an >> external RAID box will be a step up rather than relying on tape backups and >> retiring old drives before they might have a chance to fail. > > At the prices I've seen tossed about, one could purchase twice as many > drives and use vinum in a simple mirrored mode. Or better yet, buy a > RAID-5 module from Greg Lehey? Better still, get one for free :-) I released the source to -CURRENT last week. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 22:20:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 176FC14F00 for ; Tue, 10 Aug 1999 22:20:45 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11EPfp-00064x-00; Tue, 10 Aug 1999 21:07:33 -0700 Date: Tue, 10 Aug 1999 21:07:32 -0700 (PDT) From: Tom To: Mike Tancsa Cc: scsi@freebsd.org Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-Reply-To: <4.1.19990810125322.042afb60@granite.sentex.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 10 Aug 1999, Mike Tancsa wrote: > > Legacy make some pretty amusing stuff. They sell direct and via various > >wholesellers (ie Globelle). I can get Legacy stuff cheaper from Globelle > >than I can direct from Legacy. > > > > Legacy is basically just an integrator. They slap a RAID controller, > >and some drives together in a box, and then put their name on it. In > >fact, I think Legacy uses CMD RAID units in their boxes. > > Someone else pointed out that from the docs on Legacy's web site, they seem > to be OEM'ing Mylex > > "Management Port Cause: The SmartARRAY cannot establish communication with > the DAC960 hardware" That appears to be for the one's that require host cards. Those won't likely work under FreeBSD, unless FreeBSD has a driver for Mylex PCI RAID cards. > > There is nothing that Legacy is doing that you can't do yourself. > >Overnight replacement is no concern for me, as overnight is still too > >long! And if you've lost data because of the failure... There should be > >a enough resilency so that failures aren't a problem. All high-end drives > >have 5yr warranties, BTW. > > > > If I was going to setup a high-avail box, I'd use two CMD raid units. > >They have some kind of fail over mode where one can take over if one > >fails (I don't belive Legacy gives you this as an option, but you can if > >you build it yourself). Disks would combined with RAID-5, and an online > >spare (or two). > > Unfortunately my budget is limited. I dont want to go with the cheapest > solution out there, nor can I afford the most expensive. For me, an > external RAID box will be a step up rather than relying on tape backups and > retiring old drives before they might have a chance to fail. > > As for the CMD units, have you had any direct experience with them ? If budget is very important, use a DPT RAID card instead. > Thanks, > > ---Mike > ********************************************************************** > Mike Tancsa, Network Admin * mike@sentex.net > Sentex Communications Corp, * http://www.sentex.net/mike > Cambridge, Ontario * 01.519.651.3400 > Canada * Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 22:23:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 61E8914E03 for ; Tue, 10 Aug 1999 22:23:15 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11EPkN-00065A-00; Tue, 10 Aug 1999 21:12:15 -0700 Date: Tue, 10 Aug 1999 21:12:14 -0700 (PDT) From: Tom To: David Kelly Cc: Mike Tancsa , scsi@FreeBSD.ORG Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?) In-Reply-To: <199908110231.VAA50838@nospam.hiwaay.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 10 Aug 1999, David Kelly wrote: > Mike Tancsa writes: > > Unfortunately my budget is limited. I dont want to go with the cheapest > > solution out there, nor can I afford the most expensive. For me, an > > external RAID box will be a step up rather than relying on tape backups and > > retiring old drives before they might have a chance to fail. > > At the prices I've seen tossed about, one could purchase twice as many > drives and use vinum in a simple mirrored mode. Or better yet, buy a > RAID-5 module from Greg Lehey? Except for failure of the boot or swap drive. Can swap be located within vinum volumes? Vinum is ok to prevent data loss. Not much better than a standalone disk for uptime. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 10 23:44:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E146714DE9 for ; Tue, 10 Aug 1999 23:44:27 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA10387; Wed, 11 Aug 1999 16:12:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA47909; Wed, 11 Aug 1999 16:12:20 +0930 (CST) Date: Wed, 11 Aug 1999 16:12:20 +0930 From: Greg Lehey To: Tom Cc: David Kelly , Mike Tancsa , scsi@FreeBSD.ORG Subject: Vinum (was: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?)) Message-ID: <19990811161220.U31076@freebie.lemis.com> References: <199908110231.VAA50838@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Tom on Tue, Aug 10, 1999 at 09:12:14PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 10 August 1999 at 21:12:14 -0700, Tom wrote: > > On Tue, 10 Aug 1999, David Kelly wrote: > >> Mike Tancsa writes: >>> Unfortunately my budget is limited. I dont want to go with the cheapest >>> solution out there, nor can I afford the most expensive. For me, an >>> external RAID box will be a step up rather than relying on tape backups and >>> retiring old drives before they might have a chance to fail. >> >> At the prices I've seen tossed about, one could purchase twice as many >> drives and use vinum in a simple mirrored mode. Or better yet, buy a >> RAID-5 module from Greg Lehey? > > Except for failure of the boot or swap drive. Can swap be located > within vinum volumes? Yes, at least theoretically. I don't know if anybody has done it, but I haven't heard of any problems. > Vinum is ok to prevent data loss. Not much better than a standalone > disk for uptime. I don't understand what you mean here. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 3:41:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id C9FEA150D3 for ; Wed, 11 Aug 1999 03:41:27 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id FAA94114; Wed, 11 Aug 1999 05:41:25 -0500 (CDT) From: Joe Greco Message-Id: <199908111041.FAA94114@aurora.sol.net> Subject: Re: External RAID boxes (was Re: AHC errors. Bad disk or bad In-Reply-To: <3.0.5.32.19990809164854.01c08750_staff.sentex.ca@ns.sol.net> from Mike Tancsa at "Aug 9, 1999 8:51:10 pm" To: mike@sentex.net (Mike Tancsa) Date: Wed, 11 Aug 1999 05:41:24 -0500 (CDT) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Based on what I found in raid.pdf, I think it might be worth asking > >Legacy if they use raid controllers made by Mylex in their arrays. > > > >A lot of RAID kit is oem'd and that model number sounds very familiar :) > > > >> Management Port > >> Cause: The SmartARRAY cannot establish > >> communication with the DAC960 hardware > > Wow! As my hockey coach used to yell, "Good eye!". Thanks for pointing > that out. > > What I am not clear on from glancing at the mylex site is that they seem to > be cards only and cards with boxes ? Am I right in thinking that you > supply the case ? From the .pdf file > > "The DAC960S is designed to fit anywhere inside a disk array enclosure, > including in a 5-1/4" inch drive bay. And you don't need disk driver > software, because it interfaces directly through a SCSI adapter. An > optional DBX960S distribution board fits together with the DAC960SU edge > connectors, and provides standard connection for both the host and drive > channels and the serial and I/O ports. Or, the DAC960SU can be plugged > directly into the array's backplane. " Here's the deal. Mylex makes the DAC960 series controllers. There are a number of options, including differential, UW, etc. AFAICT, their primary market is the OEM market, which integrates Mylex controller cards into custom arrays. Lots of companies like MTI are doing this. The OEM versions often have various different firmware changes, etc. Mylex also makes the DAC960 in a "standalone module", i.e. something you can integrate into a disk subsystem yourself, or that smaller OEM's can integrate without getting quite down to the board level. This is a 5.25" FH deep form factor "can" which has a bunch of connectors on the back and an LCD panel on the front. The back will have your SCSI connectors and power, serial ports, and other signalling (if you use/need it). The DAC card inside slides in from the front into a card edge connector in the back, very straightforward design, you can open the front and take out the DAC controller itself (upgr, replace, etc) without disassembling your server. You can get either product, canned or just board-level. If you get board- level, I believe that you can get parts of the can (like the PC board in the back that has the card edge connector to accept the actual DAC card, which has the SCSI/power/serial/etc on the other side of it) separately. That's your "distribution board", and you'll need one. Now, I've been buying these suckers, but only two variants... The DACSXIH-2W-16M-MYL is a canned ultra-wide controller that has 2 drive chains and a host chain, and 16MB RAM. I order these all with minimal RAM since I pull the factory RAM and recycle some of the 64MB parity SIMM's we have laying around - the unit requires two SIMM's and you can go up to two 128's, but for my uses, 128MB total is great. The Mylex RAM is relatively expensive, IIRC. This board essentially has 3 SCSI controllers, and is the same as the next controller except it lacks an additional 3 controller daughtercard. The distribution board (either alone or part of the can) will have all six connectors regardless. The DACSXIH-5W-16M-MYL is the above controller with an additional 3 controller daughtercard. However, this adds an option: you may use it either as a 1-host 5-drive SCSI bus setup or a 2-host 4-drive SCSI bus setup (meaning you connect two hosts to two separate ports, allowing the hosts to share the Mylex). The daughtercard plugs in to the DAC card, and also has a card edge connector to plug in to the distribution board. In both of these hardware configurations, you may "double up" and buy an additional SXI to act as a redundant controller, you can hook them together and they'll also work together to increase performance. Most of the OEM's (MTI, etc) do this. I don't use this myself so I won't comment beyond saying that my one-Mylex-RAID-array was performing as well as a dual-Mylex-OEM-RAID-array I had access to for a while. Probably limited mostly by disk I/O more than anything else. There are other variants too. Visit the Mylex web site for details. Now, the advantages I see in getting the SXI over the SX board level product: 1) It's self-contained. You supply power and SCSI interconnects, and maybe a serial port for console. 2) It can be configured (not tweaked, but configured) from the front LCD panel or the serial port. 3) It looks cool. The disadvantage I've seen: It's a 5.25" FH _deep_ form factor, meaning that it is longer than your typical bigass 5.25" FH drive. I can barely put one of these into an Enlight midtower ATX or an Antec rackmount ATX case along with an ASUS P2B-DS motherboard (it can be done but your choices are limited and the result is a bit annoying). A more general disadvantage to the whole DAC960 is that the number of things that you can get to from the LCD/serial port is a bit disappointing. You can do all basic admin operations (create/initialize/change state/check consistency/etc) but some of the more obscure tunables aren't available in this manner. My own solution was to cobble together a DOS boot disk that has Mylex RAIDFX for DOS on it, along with the Adaptec ASPI driver for the P2B-DS, which I use for configuring the controller initially. This sucks since I recently inflicted some "damage" to my array that required the use of the utility to fix it, and had it been a thousand miles away I would have been a bit ticked off. In defense of the Mylex, I did something rather bizarre that I knew I shouldn't have, and besides, the controller _can_ be talked to via the SCSI bus (RAIDFX does), so it'd just be nice to see a FreeBSD RAIDFX utility (I'll keep wishing and praying). This doesn't reflect poorly on Mylex, though, IMHO. I've seen horribly unusable LCD displays on lots of equipment: the Mylex LCD/serial is _very_ useful, functional, and easy to use. I just can't tune some things I'd like to. > Do you save substantially 'putting it together' yourself ? Dunno. I don't think you'll save anything in terms of frustration spent trying to get it to work, if you're missing something that you need. > What sort of price have people paid (in USD), and who is generally a good > outlet to buy from ? Been getting the DACSXIH-2W-16M for ~$2050 from Tech Data or Ingram (Ingram? I think...?) The -5W goes for $500-$800 more. Tech Data doesn't seem to carry them in stock, Ingram does but Ingram charges a bit more. The last two -5W's I got from TD arrived about two weeks after ordering, but some previous -2W's that were ordered went on backorder for over a month before we cancelled the order and bought from Ingram. If I recall correctly, the suggested markup on these is _fantastic_. :-/ > Thanks for any input anyone can provide on this topic. They're good units and I'm very happy with mine. As with any RAID5 controller, the performance isn't necessarily everything you could hope for, but it is several times better than the DPT PC card controllers I tried out, and as far as I can tell the limiting factor with the DAC is the drive array - not the controller. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 8: 8:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 1BFA315527 for ; Wed, 11 Aug 1999 08:08:46 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11EYsR-0006RL-00; Wed, 11 Aug 1999 06:57:11 -0700 Date: Wed, 11 Aug 1999 06:57:09 -0700 (PDT) From: Tom To: Greg Lehey Cc: David Kelly , Mike Tancsa , scsi@FreeBSD.ORG Subject: Re: Vinum (was: External RAID boxes (was Re: AHC errors. Bad disk or bad firmware, or bug in driver ?)) In-Reply-To: <19990811161220.U31076@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 11 Aug 1999, Greg Lehey wrote: > > Vinum is ok to prevent data loss. Not much better than a standalone > > disk for uptime. > > I don't understand what you mean here. Well, if your swap fails, the system will stop until swap is put onto another disk. The same for boot disk failure. No data will be lost, but the system will be down until root and/or swap is relocated. Hardware solutions don't have this problem. > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 9: 4: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 1D55415585 for ; Wed, 11 Aug 1999 09:03:42 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA08656; Wed, 11 Aug 1999 12:03:37 -0400 (EDT) Message-ID: <19990811120335.A8339@netmonger.net> Date: Wed, 11 Aug 1999 12:03:35 -0400 From: Christopher Masto To: scsi@freebsd.org Subject: Good non-RAID controller? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I see a lot of information on which RAID devices to get, but it's all a bit more expensive than I'm looking for at the moment. I'm thinking of doing mirroring with Vinum, but the last SCSI FreeBSD machine I was involved with was several years ago. At the time, we put an Adaptec 3940 dual-channel controller in it. I have a bit of an aversion to using that card again, since it's been around since the stone age, and I don't think its performance is particularly good. Does anyone have a better recommendation for a relatively inexpensive SCSI card that works well with FreeBSD? Dual-channel would be nice, but I suppose I could just get two cards if the price is right. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 9:15: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id C6F4214E03 for ; Wed, 11 Aug 1999 09:14:28 -0700 (PDT) (envelope-from jrs@enteract.com) Received: (qmail 71110 invoked from network); 11 Aug 1999 16:12:58 -0000 Received: from shell-2.enteract.com (jrs@207.229.143.41) by pop3-3.enteract.com with SMTP; 11 Aug 1999 16:12:58 -0000 Date: Wed, 11 Aug 1999 11:12:58 -0500 (CDT) From: John Sconiers To: Christopher Masto Cc: scsi@freebsd.org Subject: Re: Good non-RAID controller? In-Reply-To: <19990811120335.A8339@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone have a better recommendation for a relatively inexpensive > SCSI card that works well with FreeBSD? Dual-channel would be nice, > but I suppose I could just get two cards if the price is right. Diamond Multimedia Fireport 40 Dual. Works great. JOHN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 9:39:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1B1B2155D0 for ; Wed, 11 Aug 1999 09:39:36 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA48167; Wed, 11 Aug 1999 10:39:16 -0600 (MDT) (envelope-from ken) Message-Id: <199908111639.KAA48167@panzer.kdm.org> Subject: Re: Good non-RAID controller? In-Reply-To: <19990811120335.A8339@netmonger.net> from Christopher Masto at "Aug 11, 1999 12:03:35 pm" To: chris@netmonger.net (Christopher Masto) Date: Wed, 11 Aug 1999 10:39:16 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher Masto wrote... > I see a lot of information on which RAID devices to get, but it's all > a bit more expensive than I'm looking for at the moment. I'm thinking > of doing mirroring with Vinum, but the last SCSI FreeBSD machine I was > involved with was several years ago. At the time, we put an Adaptec > 3940 dual-channel controller in it. I have a bit of an aversion to > using that card again, since it's been around since the stone age, and > I don't think its performance is particularly good. > > Does anyone have a better recommendation for a relatively inexpensive > SCSI card that works well with FreeBSD? Dual-channel would be nice, > but I suppose I could just get two cards if the price is right. I wouldn't call it inexpensive, but the Adaptec 3950U2B would be a good choice. It's a dual channel Ultra-2 controller. If you get the kit version, you get two Ultra-2 cables and a 50-pin cable. The Ultra-2 cables alone are probably worth the extra money for the kit. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 11: 1:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 20DC415673 for ; Wed, 11 Aug 1999 11:01:20 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA28097; Wed, 11 Aug 1999 19:49:37 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00797; Wed, 11 Aug 1999 19:27:05 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908111727.TAA00797@yedi.iaf.nl> Subject: Re: Good non-RAID controller? In-Reply-To: from John Sconiers at "Aug 11, 1999 11:12:58 am" To: jrs@enteract.com (John Sconiers) Date: Wed, 11 Aug 1999 19:27:05 +0200 (CEST) Cc: chris@netmonger.net, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As John Sconiers wrote ... > > Does anyone have a better recommendation for a relatively inexpensive > > SCSI card that works well with FreeBSD? Dual-channel would be nice, > > but I suppose I could just get two cards if the price is right. > > Diamond Multimedia Fireport 40 Dual. > > Works great. And is no longer being produced :-( -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 16: 8:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id 6BC8E14DB3 for ; Wed, 11 Aug 1999 16:08:35 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 43808 invoked from network); 11 Aug 1999 23:09:32 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 11 Aug 1999 23:09:32 -0000 Message-ID: <37B20364.A20AF9C5@delanet.com> Date: Wed, 11 Aug 1999 19:12:36 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Adaptec 2944uw on 3.2r Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having trouble with 3.2r detecting the adaptec aha-2944uw differential controllers... Has anyone used this controller on 3.2? only posts I saw were on 4.0 current.. My hardware is a DEC 300i+ with a Qlogic 1040b on the mb (with the boot drive), and the adaptec 2944uw for an external metastor raid array which has a symbios differential raid controller and 4 18gig seagate hvd drives. The card is detected by win98 (had to install it on an ide to update the bios on the host)..so I know the card is not bad. And from the adaptec bios util I can see the drives. I have ahc0 enabled in the kernel..However I'm not very familiar with running multiple scsi controllers in the same pc. Any other options I need to enable in the kernel for this or is it a matter of using 4.0 current? Thanks and please cc: me as I'm not on the list... -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 16:19:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7911815628 for ; Wed, 11 Aug 1999 16:19:48 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA50307; Wed, 11 Aug 1999 17:17:09 -0600 (MDT) (envelope-from ken) Message-Id: <199908112317.RAA50307@panzer.kdm.org> Subject: Re: Adaptec 2944uw on 3.2r In-Reply-To: <37B20364.A20AF9C5@delanet.com> from "Stephen C. Comoletti" at "Aug 11, 1999 07:12:36 pm" To: stevec@delanet.com (Stephen C. Comoletti) Date: Wed, 11 Aug 1999 17:17:09 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephen C. Comoletti wrote... > I'm having trouble with 3.2r detecting the adaptec aha-2944uw > differential controllers... Has anyone used this controller on 3.2? only > posts I saw were on 4.0 current.. My hardware is a DEC 300i+ with a > Qlogic 1040b on the mb (with the boot drive), and the adaptec 2944uw for > an external metastor raid array which has a symbios differential raid > controller and 4 18gig seagate hvd drives. The card is detected by win98 > (had to install it on an ide to update the bios on the host)..so I know > the card is not bad. And from the adaptec bios util I can see the > drives. I have ahc0 enabled in the kernel..However I'm not very familiar > with running multiple scsi controllers in the same pc. Any other options > I need to enable in the kernel for this or is it a matter of using 4.0 > current? > > Thanks and please cc: me as I'm not on the list... Can you try a newer FreeBSD-stable snapshot? There was a fix that went into the tree in late May, after 3.2 went out, that might fix your problem. There are up-to-date snapshots here: ftp://current.FreeBSD.ORG/pub/FreeBSD/snapshots/i386 You can probably just download the boot disk and see if it detects your 2944. If it does, I'd suggest installing a snapshot instead of 3.2. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 17: 8:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.delanet.com (hermes.delanet.com [208.9.136.62]) by hub.freebsd.org (Postfix) with SMTP id EE88815674 for ; Wed, 11 Aug 1999 17:08:21 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 61666 invoked from network); 12 Aug 1999 00:08:50 -0000 Received: from unknown (HELO delanet.com) (208.9.136.123) by mail.delanet.com with SMTP; 12 Aug 1999 00:08:50 -0000 Message-ID: <37B2114B.EAE7B538@delanet.com> Date: Wed, 11 Aug 1999 20:11:55 -0400 From: "Stephen C. Comoletti" Organization: DelaNET, Inc. X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2944uw on 3.2r References: <199908112317.RAA50307@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok..this produced interesting results. I used the snapshot for todays date. DMESG output as follows: changing root device to fdda0 at ahc0 bus 0 target 5 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 34652MB (70969088 512 byte sectors: 255h 63S/T 4417C) rootfs is 2880 Kbyte compiled in MFS da1 at isp0 bus 0 tatrget 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2007MB (4110480 512 byte sectors: 255H 63S/T 255C) What the snapshot detected as da1 is currently da0 (my boot device) in the system now. Am I correct in assuming I can update to this snapshot via cvsup? And if so...what would I use instead of RELENG_3? or is that correct? Other question is why only 20MB transfer rate on a drive capable of 40 (on ahc0)? "Kenneth D. Merry" wrote: > Stephen C. Comoletti wrote... > > I'm having trouble with 3.2r detecting the adaptec aha-2944uw > > differential controllers... Has anyone used this controller on 3.2? only > > posts I saw were on 4.0 current.. My hardware is a DEC 300i+ with a > > Qlogic 1040b on the mb (with the boot drive), and the adaptec 2944uw for > > an external metastor raid array which has a symbios differential raid > > controller and 4 18gig seagate hvd drives. The card is detected by win98 > > (had to install it on an ide to update the bios on the host)..so I know > > the card is not bad. And from the adaptec bios util I can see the > > drives. I have ahc0 enabled in the kernel..However I'm not very familiar > > with running multiple scsi controllers in the same pc. Any other options > > I need to enable in the kernel for this or is it a matter of using 4.0 > > current? > > > > Thanks and please cc: me as I'm not on the list... > > Can you try a newer FreeBSD-stable snapshot? There was a fix that went > into the tree in late May, after 3.2 went out, that might fix your > problem. There are up-to-date snapshots here: > > ftp://current.FreeBSD.ORG/pub/FreeBSD/snapshots/i386 > > You can probably just download the boot disk and see if it detects your > 2944. If it does, I'd suggest installing a snapshot instead of 3.2. > > Ken > -- > Kenneth Merry > ken@kdm.org -- Stephen Comoletti Systems Administrator Delanet, Inc. http://www.delanet.com ph: (302) 326-5800 fax: (302) 326-5802 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 17:14:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from weenix.guru.org (weenix.guru.org [209.241.220.18]) by hub.freebsd.org (Postfix) with ESMTP id 2AB4415827 for ; Wed, 11 Aug 1999 17:14:19 -0700 (PDT) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.9.3/8.9.3) id UAA90211 for scsi@freebsd.org; Wed, 11 Aug 1999 20:14:25 -0400 (EDT) (envelope-from kmitch) Date: Wed, 11 Aug 1999 20:14:25 -0400 From: Keith Mitchell To: scsi@freebsd.org Subject: CAM (driver devel) question Message-ID: <19990811201425.A89846@weenix.guru.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am starting to work on writing a SCSI device driver for FreeBSD and have been looking at some of the other drivers to try and figure out the interface to the device driver and came up with a few questions that I couldn't find an answer to (either in the source code or in the mailing list archives). Right now my development focus is on the 3.2 tree and my system is a 3.2-STABLE system from early 8/99. (1) It appears from looking at the other drivers that the CAM subsystem will handle scatter gather. If (ccb_h->flags & CAM_SCATTER_VALID) != 0 then the data pointer refers to a scatter/gather list. The problem is I couldn't find anywhere in the kernel that sets this value. Does CAM reslly support scatter/gather at this point in time and if so where does the structure get allocated and passed down. (2) I see that most (if not all) of the SCSI drivers have been switched over to the new bus_dma methods. Whenever the drivers send data down to the card they always do a bus_dmamap_sync() on a DMA map in the controller specific CCB structures. My question is do I need to do that on every piece of DMA?? I have to DMA a structure to the controller to start a command (command can be an I/O request or an internal command). That structure also usually has a data pointer (or two) there. Do I need to keep a map to handle syncs to every structure that I DMA to the adapter (adapter CCBs and data included)?? Thanks. -- Keith Mitchell Email: kmitch@guru.org PGP key available upon request To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 17:20:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id DA5C914DF1 for ; Wed, 11 Aug 1999 17:20:04 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA50620; Wed, 11 Aug 1999 18:18:53 -0600 (MDT) (envelope-from ken) Message-Id: <199908120018.SAA50620@panzer.kdm.org> Subject: Re: Adaptec 2944uw on 3.2r In-Reply-To: <37B2114B.EAE7B538@delanet.com> from "Stephen C. Comoletti" at "Aug 11, 1999 08:11:55 pm" To: stevec@delanet.com (Stephen C. Comoletti) Date: Wed, 11 Aug 1999 18:18:53 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stephen C. Comoletti wrote... > Ok..this produced interesting results. I used the snapshot for todays date. > DMESG output as follows: > > changing root device to fdda0 at ahc0 bus 0 target 5 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled > da0: 34652MB (70969088 512 byte sectors: 255h 63S/T 4417C) > rootfs is 2880 Kbyte compiled in MFS > da1 at isp0 bus 0 tatrget 0 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da1: 2007MB (4110480 512 byte sectors: 255H 63S/T 255C) > > > What the snapshot detected as da1 is currently da0 (my boot device) in the > system now. Am I correct in assuming I can update to this snapshot via > cvsup? And if so...what would I use instead of RELENG_3? or is that correct? > Other question is why only 20MB transfer rate on a drive capable of 40 (on > ahc0)? Yes, you can upgrade via cvsup. And yes, you'll want to use RELENG_3. Since you are at 3.2-R now, I assume you won't want to go to -current. (not if you're trying to build any sort of production box) Of course once you cvsup RELENG_3, you'll need to do a buildworld and installworld in addition to building a new kernel. The reason the device is reporting a 20MB/sec transfer rate is because it doesn't see da0 as a wide device for some reason. I'm not sure why. You'll want to make sure your cabling and termination are correct for that device, that could have an impact on whether it negotiates wide or not. If you would rather have da1 be da0, you may be able to accomplish it by swapping the Adaptec and QLogic controllers around. (i.e. swap slots) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 17:24:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9B88414DF1 for ; Wed, 11 Aug 1999 17:24:22 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA50716; Wed, 11 Aug 1999 18:24:19 -0600 (MDT) (envelope-from ken) Message-Id: <199908120024.SAA50716@panzer.kdm.org> Subject: Re: Adaptec 2944uw on 3.2r In-Reply-To: <199908120018.SAA50620@panzer.kdm.org> from "Kenneth D. Merry" at "Aug 11, 1999 06:18:53 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Wed, 11 Aug 1999 18:24:19 -0600 (MDT) Cc: stevec@delanet.com (Stephen C. Comoletti), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote... > Stephen C. Comoletti wrote... > > Ok..this produced interesting results. I used the snapshot for todays date. > > DMESG output as follows: > > > > changing root device to fdda0 at ahc0 bus 0 target 5 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled > > da0: 34652MB (70969088 512 byte sectors: 255h 63S/T 4417C) > > rootfs is 2880 Kbyte compiled in MFS > > da1 at isp0 bus 0 tatrget 0 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > > Enabled > > da1: 2007MB (4110480 512 byte sectors: 255H 63S/T 255C) > > > > > > What the snapshot detected as da1 is currently da0 (my boot device) in the > > system now. Am I correct in assuming I can update to this snapshot via > > cvsup? And if so...what would I use instead of RELENG_3? or is that correct? > > Other question is why only 20MB transfer rate on a drive capable of 40 (on > > ahc0)? [ ... ] > If you would rather have da1 be da0, you may be able to accomplish it by > swapping the Adaptec and QLogic controllers around. (i.e. swap slots) One other way to do it would be to hard-wire the devices in your kernel config file. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 11 20:31:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from weenix.guru.org (weenix.guru.org [209.241.220.18]) by hub.freebsd.org (Postfix) with ESMTP id 5C25A15631 for ; Wed, 11 Aug 1999 20:31:25 -0700 (PDT) (envelope-from kmitch@weenix.guru.org) Received: (from kmitch@localhost) by weenix.guru.org (8.9.3/8.9.3) id XAA96110 for scsi@freebsd.org; Wed, 11 Aug 1999 23:31:11 -0400 (EDT) (envelope-from kmitch) Date: Wed, 11 Aug 1999 22:33:15 -0400 From: Keith Mitchell To: "Kenneth D. Merry" Subject: Re: CAM (driver devel) question Message-ID: <19990811223315.A93634@weenix.guru.org> References: <19990811201425.A89846@weenix.guru.org> <199908120100.TAA51068@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908120100.TAA51068@panzer.kdm.org>; from Kenneth D. Merry on Wed, Aug 11, 1999 at 07:00:44PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 11, 1999 at 07:00:44PM -0600, Kenneth D. Merry wrote: > Not all of the drivers support S/G. And you're right, it isn't used in any > of the upper level code at the moment. All of the drivers I looked at (aic7xxx, dpt, buslogic) all supported scatter/gather. But it looked like they only supported scatter/gather if they were passed a scatter/gather buffer from the upper layer (and since it doesn't look like the upper layer sends down a scatter gather list then I am guessing that scatter/gather never occurs). It looks like from the drivers they take whatever buffer they get passed from the upper layer and pass it down to the card (if its a physical address or maps it into DMAable memory via bus_dmamap_load() if its a virtual address). So my initial conclusion was the drivers were architected so that when the upper layer supported S/G they would too without modification. but I wanted to be sure before I coded everything. > You can probably get away with not supporting it, but it would probably be > a good idea to do so if you can. Yeah its a very good thing to have (especially for large transfers). > Just out of curiosity, what card are you writing a driver for? It would be > nice to know, to make sure you aren't duplicating any effort... I'm working on a driver for the IBM ServeRAID card but unfortunately I don't have the necessary approval to distribute any of it when I'm done. I need to convince management that its worthwhile to support FreeBSD -- right now most of them have never heard of it let alone feel the need to support it. Thats something I plan on trying to fix but its uncertain if I'll succeed (especially if very few people request it). If lots of people buying the ServeRAID card / Netfinity servers were to call IBM and request BSD that might help... That seemed to work for Linux ;-> -- Keith Mitchell Email: kmitch@guru.org PGP key available upon request To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 8:52:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from xenetserver.harz.de (xenetserver.harz.de [193.159.181.125]) by hub.freebsd.org (Postfix) with ESMTP id 642B415817 for ; Thu, 12 Aug 1999 08:52:07 -0700 (PDT) (envelope-from frank@vogon.agala.harz.de) Received: (from uucp@localhost) by xenetserver.harz.de (8.9.1/8.9.1) with UUCP id RAA16221 for freebsd-scsi@freebsd.org; Thu, 12 Aug 1999 17:52:16 +0200 (CEST) Received: (from frank@localhost) by vogon.agala.harz.de (8.9.3/8.8.8) id RAA91480 for freebsd-scsi@freebsd.org; Thu, 12 Aug 1999 17:40:48 +0200 (CEST) (envelope-from frank) Date: Thu, 12 Aug 1999 17:40:48 +0200 From: "Frank J. Beckmann" To: freebsd-scsi@freebsd.org Subject: zones on a disc Message-ID: <19990812174048.A91181@vogon.agala.harz.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Address: Frank J. Beckmann, Steinkampring 16, D-38667 Bad Harzburg X-Phone: +49-5322-80008 X-Fax: +49-5322-80082 X-PGP-Fingerprint-1: (1024R/66DC397D) = 25 34 D7 8A 69 04 12 CA 6E 55 DD 63 F6 A3 0E 06 X-PGP-Fingerprint-2: (1024D/46DE66CA) = 7D06 0DFB 23D9 01BA 11EB 88C3 DE8C C167 46DE 66CA Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, the tracks in the outer zones of a hard disc have more sectors then the tracks in the inner zones. So the drive is faster when it accesses tracks in the outer zones. How can I find where a zone begins and where it ends? Frank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 9:17: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 29430157FC for ; Thu, 12 Aug 1999 09:17:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA10256; Thu, 12 Aug 1999 09:15:08 -0700 Date: Thu, 12 Aug 1999 09:15:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Frank J. Beckmann" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: zones on a disc In-Reply-To: <19990812174048.A91181@vogon.agala.harz.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This the 'notch' mode page. On Thu, 12 Aug 1999, Frank J. Beckmann wrote: > Hi, > > the tracks in the outer zones of a hard disc have more sectors > then the tracks in the inner zones. So the drive is faster when it > accesses tracks in the outer zones. How can I find where a zone begins > and where it ends? > > Frank > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 15:13:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 177B5157B2 for ; Thu, 12 Aug 1999 15:13:31 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 4492 invoked by uid 1825); 12 Aug 1999 22:12:52 -0000 Date: Thu, 12 Aug 1999 18:12:52 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: freebsd-scsi@freebsd.org Subject: Adaptec AIC-7896 flakyness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to get 3 IBM 9.1GB LVD SCSI drives to work with a new install using an Adaptec AIC-7896 (imbedded on an Intel L440GX+ motherboard). The ONLY way I got all 3 drives working was the following: SCSI ID 0 -> P7 (furthest from the controller) connector " " 1 -> P6 (next connector in) " " 2 (terminator jumper in) -> P5 (and so on...) with P1 going to the controller (motherboard in this case) The only problem with that is that I need to move the last drive (SCSI ID 2) to a drive bay that the P5 connector can't reach. I've tried every other connector on the SCSI ribbon cable with no luck; I either get panics as soon as the install tries to start, or everything hangs before I even get that far. Is this normal behavior? Is there a fix? Perhaps a jumper setting on the drives (the "disable parity" jumper is off by default, for example)? Thanks in advance, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 15:34:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id 3704A15055 for ; Thu, 12 Aug 1999 15:34:24 -0700 (PDT) (envelope-from matt@ns2.michweb.net) Received: (qmail 16244 invoked by uid 101); 12 Aug 1999 22:34:41 -0000 Date: Thu, 12 Aug 1999 18:34:41 -0400 (EDT) From: Matt Simerson To: up@3.am Cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec AIC-7896 flakyness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org James, This sounds a lot like a SCSI termination issue to me. Are you sure you're in compliance with all the laws of SCSI that THOU SHALT FOLLOW in order to make it work right? For instance, you must always have the first and last devices in a SCSI chain terminated. What type of termination do you have set up on the Adaptec card? From your sketchy diagram, I'll guess you've got no termination set up on the card and are use the drive at SCSI ID 2 as the first device. This will be problematic. Matt "I have books written only about SCSI" Simerson On Thu, 12 Aug 1999 up@3.am wrote: > I'm trying to get 3 IBM 9.1GB LVD SCSI drives to work with a new install > using an Adaptec AIC-7896 (imbedded on an Intel L440GX+ motherboard). The > ONLY way I got all 3 drives working was the following: > > SCSI ID 0 -> P7 (furthest from the controller) connector > " " 1 -> P6 (next connector in) > " " 2 (terminator jumper in) -> P5 (and so on...) > > with P1 going to the controller (motherboard in this case) > > The only problem with that is that I need to move the last drive (SCSI ID > 2) to a drive bay that the P5 connector can't reach. I've tried every > other connector on the SCSI ribbon cable with no luck; I either get > panics as soon as the install tries to start, or everything hangs before I > even get that far. > > Is this normal behavior? Is there a fix? Perhaps a jumper setting on the > drives (the "disable parity" jumper is off by default, for example)? > > Thanks in advance, > > James Smallacombe PlantageNet, Inc. CEO and Janitor > up@3.am http://3.am > ========================================================================= > ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans > 3 days of clues, news, and views from the industry's best and brightest. > Visit for information and registration. > ========================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com Better to dare Mighty Things and fail, than to live in __o a gray twilight where there is neither victory or _-\<,_ defeat. -- attributed to Theodore Roosevelt ......(_)/ (_) `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 15:39:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 38CE8156A9 for ; Thu, 12 Aug 1999 15:39:30 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id SAA29714; Thu, 12 Aug 1999 18:38:32 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Thu, 12 Aug 1999 18:38:32 -0400 (EDT) From: Chuck Robey To: up@3.am Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec AIC-7896 flakyness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 12 Aug 1999 up@3.am wrote: > > I'm trying to get 3 IBM 9.1GB LVD SCSI drives to work with a new install > using an Adaptec AIC-7896 (imbedded on an Intel L440GX+ motherboard). The > ONLY way I got all 3 drives working was the following: > > SCSI ID 0 -> P7 (furthest from the controller) connector > " " 1 -> P6 (next connector in) > " " 2 (terminator jumper in) -> P5 (and so on...) Huh? The IBM LVD drives don't offer termination, how did you get that? If you don't have a non-LVD drive on the chain, you must have a terminator on the cable, else you're running a non-terminated chain. What's the model # of the IBM drive? > > with P1 going to the controller (motherboard in this case) > > The only problem with that is that I need to move the last drive (SCSI ID > 2) to a drive bay that the P5 connector can't reach. I've tried every > other connector on the SCSI ribbon cable with no luck; I either get > panics as soon as the install tries to start, or everything hangs before I > even get that far. > > Is this normal behavior? Is there a fix? Perhaps a jumper setting on the > drives (the "disable parity" jumper is off by default, for example)? > > Thanks in advance, > > James Smallacombe PlantageNet, Inc. CEO and Janitor > up@3.am http://3.am > ========================================================================= > ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans > 3 days of clues, news, and views from the industry's best and brightest. > Visit for information and registration. > ========================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 15:45:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 94C2215055 for ; Thu, 12 Aug 1999 15:45:45 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id SAA15458; Thu, 12 Aug 1999 18:45:14 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id PAA26854; Thu, 12 Aug 1999 15:44:55 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id PAA23186; Thu, 12 Aug 1999 15:45:37 -0700 (PDT) Message-Id: <199908122245.PAA23186@mina.sr.hp.com> To: Matt Simerson Cc: up@3.am, freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec AIC-7896 flakyness Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 12 Aug 1999 18:34:41 EDT." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 12 Aug 1999 15:45:37 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt Simerson wrote: > For instance, you must always have the first and last devices in a SCSI > chain terminated. What type of termination do you have set up on the > Adaptec card? From your sketchy diagram, I'll guess you've got no > termination set up on the card and are use the drive at SCSI ID 2 as the > first device. This will be problematic. Also, LVD drives have no provision for on-drive termination (at least, none that I've heard of, and I know that the IBM 9ES 9.1GB drives, don't -- I've got a couple). You've got to explicitly add a terminator to the end of the LVD cable. [ In the case of the IBM 9ES drive, the wide SE version has a "termination" jumper. In the LVD version, the jumper that was used for termination, on the wide SE version, is used to switch between wide SE and LVD modes. For more details, see the IBM support docs at their web site. ] -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 16:17:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 9E67914CC9 for ; Thu, 12 Aug 1999 16:17:28 -0700 (PDT) (envelope-from up@pil.net) Received: (qmail 11792 invoked by uid 1825); 12 Aug 1999 23:17:26 -0000 Date: Thu, 12 Aug 1999 19:17:25 -0400 (EDT) From: X-Sender: up@richard2.pil.net To: Darryl Okahata Cc: Matt Simerson , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec AIC-7896 flakyness In-Reply-To: <199908122245.PAA23186@mina.sr.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 12 Aug 1999, Darryl Okahata wrote: > Matt Simerson wrote: > > > For instance, you must always have the first and last devices in a SCSI > > chain terminated. What type of termination do you have set up on the > > Adaptec card? From your sketchy diagram, I'll guess you've got no > > termination set up on the card and are use the drive at SCSI ID 2 as the > > first device. This will be problematic. Hi Matt: No, I have the card's termination on....it protested loudly when I turned it off (SCSI BIOS wouldn't come up). > Also, LVD drives have no provision for on-drive termination (at > least, none that I've heard of, and I know that the IBM 9ES 9.1GB > drives, don't -- I've got a couple). You've got to explicitly add a > terminator to the end of the LVD cable. > > [ In the case of the IBM 9ES drive, the wide SE version has a > "termination" jumper. In the LVD version, the jumper that was used > for termination, on the wide SE version, is used to switch between > wide SE and LVD modes. For more details, see the IBM support docs at > their web site. ] Hmmm...this is odd indeed...I'm looking at the drive and on the right-hand set of jumpers, jumper "G" is marked "TERM. POWER ON". I assumed this provided termination for the end of the chain if used. Flipping the drive over, we have model: DNES-309170 E182115HG further down on the label, it says: SCSI LVD/SE I'll check out IBM's site. Thanks to everyone who responded! James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= ISPF 3 - The Forum for ISPs by ISPs(tm) || Nov 15-17, 1999, New Orleans 3 days of clues, news, and views from the industry's best and brightest. Visit for information and registration. ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 16:40:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (Postfix) with ESMTP id 7FDF214F88 for ; Thu, 12 Aug 1999 16:40:12 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from postal.sr.hp.com (root@postal.sr.hp.com [15.4.46.173]) by atlrel2.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id TAA06650; Thu, 12 Aug 1999 19:39:52 -0400 (EDT) Received: from mina.sr.hp.com (root@mina.sr.hp.com [15.4.42.247]) by postal.sr.hp.com with ESMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0) id QAA01068; Thu, 12 Aug 1999 16:39:34 -0700 (PDT) Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0) id QAA23750; Thu, 12 Aug 1999 16:40:16 -0700 (PDT) Message-Id: <199908122340.QAA23750@mina.sr.hp.com> To: up@3.am Cc: Matt Simerson , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec AIC-7896 flakyness Reply-To: Darryl Okahata In-reply-to: Your message of "Thu, 12 Aug 1999 19:17:25 EDT." Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Thu, 12 Aug 1999 16:40:16 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org up@3.am wrote: > Hmmm...this is odd indeed...I'm looking at the drive and on the right-hand > set of jumpers, jumper "G" is marked "TERM. POWER ON". I assumed this > provided termination for the end of the chain if used. That's the "termination power" jumper. If enabled, the drive provides power for the terminator ... which doesn't exist on your drive. I guess the jumper is there for external terminators that need power and don't provide their own. > Flipping the drive over, we have model: > > DNES-309170 E182115HG I think this is an IBM Ultrastar 18ES. See: http://www.storage.ibm.com/hardsoft/diskdrdl/prod/us18es.htm If so, this drive definitely doesn't have on-drive termination. See the detailed installation manual at: http://www.storage.ibm.com/techsup/hddtech/dnes/dnes_di.pdf > SCSI LVD/SE This means that this is an LVD-capable drive. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 17:30:23 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 69DDD14A2D for ; Thu, 12 Aug 1999 17:30:19 -0700 (PDT) (envelope-from wolman@cs.washington.edu) Received: from miles.cs.washington.edu (miles.cs.washington.edu [128.95.4.177]) by june.cs.washington.edu (8.8.7+CS/7.2ju) with ESMTP id RAA03884 for ; Thu, 12 Aug 1999 17:30:30 -0700 Received: from miles.cs.washington.edu (localhost [127.0.0.1]) by miles.cs.washington.edu (8.9.2/8.9.2) with ESMTP id RAA53343 for ; Thu, 12 Aug 1999 17:30:29 -0700 (PDT) (envelope-from wolman@miles.cs.washington.edu) Message-Id: <199908130030.RAA53343@miles.cs.washington.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org Subject: OS bug or hardware problem? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Aug 1999 17:30:29 -0700 From: "Alec Wolman" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just recently upgraded a machine from 3.1-19990403-STABLE to 3.2-19990810-STABLE. After the upgrade, I now get SCSI parity errors when I attempt to use one of the disks (da3): Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 11 10 80 0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 1a 10 80 0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 2f 90 80 0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error These look to me like the disk has a hardware problem, but its a little surprising that the disk errors were introduced at exactly the same time at which I performed the OS upgrade. Is it possible that in the old version of the OS these errors were occuring but not being reported? Anyway, here is the relevant hardware info extracted from dmesg: Aug 12 02:44:04 laver /kernel: chip0: rev 0x02 on pci0.0.0 Aug 12 02:44:04 laver /kernel: chip1: rev 0x02 on pci0.1.0 Aug 12 02:44:04 laver /kernel: chip2: rev 0x02 on pci0.7.0 Aug 12 02:44:04 laver /kernel: chip3: rev 0x02 on pci0.7.3 Aug 12 02:44:04 laver /kernel: ahc0: rev 0x04 int a irq 10 on pci0.14.0 Aug 12 02:44:04 laver /kernel: ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs Aug 12 02:44:04 laver /kernel: ahc1: rev 0x04 int b irq 10 on pci0.14.1 Aug 12 02:44:04 laver /kernel: ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Aug 12 02:44:04 laver /kernel: da1 at ahc0 bus 0 target 3 lun 0 Aug 12 02:44:04 laver /kernel: da1: Fixed Direct Access SCSI-3 device Aug 12 02:44:04 laver /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Aug 12 02:44:04 laver /kernel: da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Aug 12 02:44:04 laver /kernel: da2 at ahc1 bus 0 target 0 lun 0 Aug 12 02:44:04 laver /kernel: da2: Fixed Direct Access SCSI-3 device Aug 12 02:44:04 laver /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Aug 12 02:44:04 laver /kernel: da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Aug 12 02:44:04 laver /kernel: da4 at ahc1 bus 0 target 6 lun 0 Aug 12 02:44:04 laver /kernel: da4: Fixed Direct Access SCSI-2 device Aug 12 02:44:04 laver /kernel: da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Aug 12 02:44:04 laver /kernel: da4: 22130MB (45322644 512 byte sectors: 255H 63S/T 2821C) Aug 12 02:44:04 laver /kernel: da3 at ahc1 bus 0 target 5 lun 0 Aug 12 02:44:04 laver /kernel: da3: Fixed Direct Access SCSI-3 device Aug 12 02:44:04 laver /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Aug 12 02:44:04 laver /kernel: da3: 35239MB (72170879 512 byte sectors: 255H 63S/T 4492C) Aug 12 02:44:04 laver /kernel: da0 at ahc0 bus 0 target 0 lun 0 Aug 12 02:44:04 laver /kernel: da0: Fixed Direct Access SCSI-2 device Aug 12 02:44:04 laver /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Aug 12 02:44:04 laver /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Any helpful hints would be most appreicated? Alec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 19: 6:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3812C14CCD for ; Thu, 12 Aug 1999 19:06:24 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA57880; Thu, 12 Aug 1999 20:06:24 -0600 (MDT) (envelope-from ken) Message-Id: <199908130206.UAA57880@panzer.kdm.org> Subject: Re: OS bug or hardware problem? In-Reply-To: <199908130030.RAA53343@miles.cs.washington.edu> from Alec Wolman at "Aug 12, 1999 05:30:29 pm" To: wolman@cs.washington.edu (Alec Wolman) Date: Thu, 12 Aug 1999 20:06:24 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alec Wolman wrote... > > I just recently upgraded a machine from 3.1-19990403-STABLE to > 3.2-19990810-STABLE. After the upgrade, I now get SCSI parity > errors when I attempt to use one of the disks (da3): > > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 11 10 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 1a 10 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 2f 90 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > > > These look to me like the disk has a hardware problem, but its a little surprising > that the disk errors were introduced at exactly the same time at which > I performed the OS upgrade. Is it possible that in the old version > of the OS these errors were occuring but not being reported? > > Anyway, here is the relevant hardware info extracted from dmesg: [ ... ] > Aug 12 02:44:04 laver /kernel: da3 at ahc1 bus 0 target 5 lun 0 > Aug 12 02:44:04 laver /kernel: da3: Fixed Direct Access SCSI-3 device > Aug 12 02:44:04 laver /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Aug 12 02:44:04 laver /kernel: da3: 35239MB (72170879 512 byte sectors: 255H 63S/T 4492C) [ ... ] > Any helpful hints would be most appreicated? My guess is that it is what it appears to be -- a parity error. I'm not sure why it didn't show up before. I would look for bent connector pins or other cabling type problems. Another possibility is a connector problem on the drive, like a loose solder point or something. Since that drive is the only one complaining, it could just be a bent pin on the connector for that drive. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 21:51:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id E1A3C1565A for ; Thu, 12 Aug 1999 21:50:44 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 779D97C55; Thu, 12 Aug 1999 23:50:12 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14259.41988.384974.93185@celery.zuhause.org> Date: Thu, 12 Aug 1999 23:50:12 -0500 (CDT) To: freebsd-scsi@freebsd.org Subject: Adaptec AIC7895 termination issue X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a Gigabyte 6BXDS running dual Celerons (immaterial, I believe), that FreeBSD complains about my SCSI termination. It's got one Ultra SCSI connector (8 bit, 50 pin) for port A, which is connected to a CDROM with termination enabled, and a Ultra SCSI2 connector (16 bit, 68 pin) for port A which has nothing connected to it, and a Ultra SCSI2 connecter (16 bit, 68 pin) for port B to which I have an IBM Ultrastar LVD drive with a LVD/SE terminator on the end of the cable. No matter what termination settings I use in the BIOS, FreeBSD always tells me that port A is incorrectly terminated. The current BIOS termination settings are for termination on for port A, and port B enabled, which seems to be what the manual recommends if I only had 8 bit or only had 16 bit SCSI on port A. Do I need to move the Ultra SCSI2 cable from port B to port A, and set up the termination to high byte only to match the example in for internal 8 + 16 bit devices? Just how independent are the two ports, anyway? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 12 22:21:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from modgud.nordicrecords.com (h21-168-107.nordicdms.com [207.21.168.107]) by hub.freebsd.org (Postfix) with SMTP id 67A89158F8 for ; Thu, 12 Aug 1999 22:21:06 -0700 (PDT) (envelope-from walton@nordicrecords.com) Received: (qmail 18100 invoked by alias); 13 Aug 1999 05:19:44 -0000 Message-ID: <19990813051944.18097.qmail@modgud.nordicrecords.com> Received: (qmail 18086 invoked from network); 13 Aug 1999 05:19:43 -0000 Received: from unknown (HELO walton) (207.21.168.137) by mail.nordicdms.com with SMTP; 13 Aug 1999 05:19:43 -0000 From: "Dave Walton" To: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Date: Thu, 12 Aug 1999 22:17:59 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Adaptec AEC-4412 SCSI-SCSI RAID Reply-To: walton@nordicrecords.com In-reply-to: <199908052105.PAA05911@panzer.kdm.org> References: <19990805204226.21354.qmail@modgud.nordicrecords.com> from Dave Walton at "Aug 5, 1999 01:40:45 pm" X-mailer: Pegasus Mail for Win32 (v3.11) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5 Aug 99, at 15:05, Kenneth D. Merry wrote: > Dave Walton wrote... > > On 3 Aug 99, at 20:49, Kenneth D. Merry wrote: > > > > > Dave Walton wrote... > > > > > > > > (ahc0:0:0): "Adaptec AEC-4412BS 1.2." type 0 fixed SCSI 2 > > > > sd0(ahc0:0:0): Direct-Access 8999MB (70420800 134 byte > > > > sectors) > > > > > > > > The problem? The array on LUN 0 has a capacity of 34381MB, not > > > > 8999MB. For some reason, it's reporting 134 byte sectors, instead > > > > of the standard 512 byte sectors (which would produce the correct > > > > disk size). What could be causing this, and how can I correct it? > > > > > > > You might try booting with a 3.2 boot floppy, just to see if it comes up > with the same sector size. Just for the record (and the archive, should anyone else need this info), that solved it. Both 3.1-R and 3.2-R have no problems with the AEC-4412. It was just something in 2.2.x that couldn't deal with it. The only question remaining is... How best to partition a 68GB array... :) Thanks, Dave ---------------------------------------------------------------------- Dave Walton Webmaster, Postmaster Nordic Entertainment Worldwide walton@nordicdms.com http://www.nordicdms.com ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 0:28:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C1E7C14DAC for ; Fri, 13 Aug 1999 00:28:45 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA59141; Fri, 13 Aug 1999 01:28:53 -0600 (MDT) (envelope-from ken) Message-Id: <199908130728.BAA59141@panzer.kdm.org> Subject: Re: Adaptec AIC7895 termination issue In-Reply-To: <14259.41988.384974.93185@celery.zuhause.org> from Bruce Albrecht at "Aug 12, 1999 11:50:12 pm" To: bruce@zuhause.mn.org (Bruce Albrecht) Date: Fri, 13 Aug 1999 01:28:53 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bruce Albrecht wrote... > I've got a Gigabyte 6BXDS running dual Celerons (immaterial, I believe), > that FreeBSD complains about my SCSI termination. It's got one Ultra SCSI > connector (8 bit, 50 pin) for port A, which is connected to a CDROM with > termination enabled, and a Ultra SCSI2 connector (16 bit, 68 pin) for port > A which has nothing connected to it, and a Ultra SCSI2 connecter (16 bit, > 68 pin) for port B to which I have an IBM Ultrastar LVD drive with a LVD/SE > terminator on the end of the cable. No matter what termination settings I > use in the BIOS, FreeBSD always tells me that port A is incorrectly > terminated. The current BIOS termination settings are for termination on > for port A, and port B enabled, which seems to be what the manual > recommends if I only had 8 bit or only had 16 bit SCSI on port A. > > Do I need to move the Ultra SCSI2 cable from port B to port A, and set up > the termination to high byte only to match the example in for internal 8 + > 16 bit devices? Just how independent are the two ports, anyway? Well, from looking at the terminology in the manual for that board, I'd say you should set the termination like this: Port A: Both (i.e., high on, low on) Port B: enabled (i.e. high on, low on) If that's what you have turned on now, and it's giving you trouble, I suppose you could try putting the disk on port A and just enabling high byte termination. It could indicate a driver problem of some sort, though. If you are using the settings above, and FreeBSD is complaining, you should probably talk to Justin Gibbs . If there is a problem with the driver, he'll want to hear about it. The two ports on a 7895 are completely independent. It appears to the OS as two separate SCSI adapters. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 6:58:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cybernet.in.th (www.cybernet.in.th [203.149.3.222]) by hub.freebsd.org (Postfix) with SMTP id 4F8B314ECD for ; Fri, 13 Aug 1999 06:58:33 -0700 (PDT) (envelope-from bunlu@cybernet.in.th) Received: (qmail 30539 invoked by uid 555); 13 Aug 1999 13:56:29 -0000 Message-ID: <19990813135629.30548.qmail@cybernet.in.th> Date: 13 Aug 1999 20:56:29 +0700 Reply-To: From: Bunlu Nantaeng To: freebsd-scsi@freebsd.org Subject: nead help on Compaq ida disk. X-Sender: bunlu@cybernet.in.th (via http://mail.cybernet.in.th/) X-Client: 203.149.3.217 MIME-Version: 1.0 Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --- Probing for devices on PCI bus 2: ida0: rev 0x03 int a irq 11 on pci2.0.0 ida0: drvs=1 firm_rev=3.22 ida0: unit 0 (id0): id0: 20467MB (41917920 total sec), 5137 cyl, 255 head, 32 sec, bytes/sec 512 ida: wdc vector stealing off (mode = never, boot major = 4) --- How can I mount my id0 disk? Thank in advance, -- bunlu@cybernet.in.th To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 7:46:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 9FA4714EEE for ; Fri, 13 Aug 1999 07:46:15 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id JAA05222; Fri, 13 Aug 1999 09:46:28 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id JAA27293; Fri, 13 Aug 1999 09:46:27 -0500 (CDT) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id JAA28600; Fri, 13 Aug 1999 09:46:27 -0500 (CDT) Date: Fri, 13 Aug 1999 09:46:27 -0500 (CDT) From: Jonathan Lemon Message-Id: <199908131446.JAA28600@free.pcs> To: bunlu@cybernet.in.th, scsi@freebsd.org Subject: Re: nead help on Compaq ida disk. X-Newsgroups: local.mail.freebsd-scsi In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >--- >Probing for devices on PCI bus 2: >ida0: rev 0x03 int a irq 11 on pci2.0.0 >ida0: drvs=1 firm_rev=3.22 >ida0: unit 0 (id0): >id0: 20467MB (41917920 total sec), 5137 cyl, 255 head, 32 sec, bytes/sec 512 >ida: wdc vector stealing off (mode = never, boot major = 4) >--- >How can I mount my id0 disk? Since you're not doing vector stealing here, you need to mount the drives with the id0 device nodes. The following patch to MAKEDEV should allow creation of the appropriate /dev entries. -- Jonathan Index: MAKEDEV =================================================================== RCS file: /tuna/ncvs/src/etc/etc.i386/MAKEDEV,v retrieving revision 1.200 retrieving revision 1.201 diff -u -r1.200 -r1.201 --- MAKEDEV 1999/07/05 08:39:00 1.200 +++ MAKEDEV 1999/07/05 09:18:57 1.201 @@ -48,6 +48,7 @@ # vn* "vnode disks" # od* "optical disks" # fla* "M-Systems DiskOnChip" +# ida* "Compaq Smart-2 RAID" # # Console ports: # vty* virtual console devices for syscons/pcvt/codrv @@ -127,7 +128,7 @@ # ipl ipfilter control devices (ipl, ipnat, ipstate, ipauth) # kbd keyboard devices # -# $Id: MAKEDEV,v 1.200 1999/07/05 08:39:00 jkh Exp $ +# $Id: MAKEDEV,v 1.201 1999/07/05 09:18:57 msmith Exp $ # PATH=/sbin:/bin/:/usr/bin:/usr/sbin:$PATH @@ -297,11 +298,12 @@ ;; # Individual slices. -ad*s*|od*s*|sd*s*|da*s*|vn*s*|wd*s*|afd*s*|wfd*s*|fla*s*) +ad*s*|od*s*|sd*s*|da*s*|vn*s*|wd*s*|afd*s*|wfd*s*|fla*s*|ida*s*) umask $disk_umask case $i in ad*s*) name=ad; blk=30; chr=116;; afd*s*) name=afd; blk=32; chr=118;; + ida*s*) name=ida; blk=29; chr=109;; fla*s*) name=fla; blk=28; chr=102;; od*s*) name=od; blk=4; chr=13;; sd*s*) name=sd; blk=4; chr=13;; @@ -311,7 +313,7 @@ wfd*s*) name=wfd; blk=1; chr=87;; esac case $i in - afd*s*|fla*s*|wfd*s*) + afd*s*|ida*s*|fla*s*|wfd*s*) unit=`expr $i : '...\([0-9]*\)s'` slice=`expr $i : '...[0-9]*s\([0-9]*\)'` part=`expr $i : '...[0-9]*s[0-9]*\(.*\)'` @@ -470,11 +472,12 @@ umask 77 ;; -ad*|sd*|od*|da*|vn*|wd*|afd*|wfd*|fla*) +ad*|sd*|od*|da*|vn*|wd*|afd*|wfd*|fla*|ida*) umask $disk_umask case $i in ad*) name=ad; blk=30; chr=116;; afd*) name=afd; blk=32; chr=118;; + ida*) name=ida; blk=29; chr=109;; fla*) name=fla; blk=28; chr=102;; sd*) name=sd; blk=4; chr=13;; od*) name=od; blk=4; chr=13;; @@ -484,7 +487,7 @@ wfd*) name=wfd; blk=1; chr=87;; esac case $i in - afd*|fla*|wfd*) + afd*|ida*|fla*|wfd*) unit=`expr $i : '...\(.*\)'` ;; *) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 16: 0:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0FB3B1506D for ; Fri, 13 Aug 1999 16:00:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA00749; Wed, 11 Aug 1999 09:34:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908111634.JAA00749@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: scsi@FreeBSD.ORG Subject: Re: NCR/Multia Problems? In-reply-to: Your message of "Mon, 09 Aug 1999 13:41:42 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Aug 1999 09:34:25 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've concluded that this is "Baked Multia Sydrome". > nopilt.feral.com > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (mem > 4458e000:c0000004). > ncr0: regdump: da 00 00 13 47 08 06 1f 75 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth 84:88080000). > ncr0: script cmd = 88080000 > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth a0:c0000004). > ncr0: script cmd = c0000004 > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > ncr0: restart (fatal error). > (da1:ncr0:0:6:0): COMMAND FAILED (9 ff) @0xfffffe000058e400. > > > What is this error? > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 16: 5:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E3D5115033 for ; Fri, 13 Aug 1999 16:05:08 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA14378; Fri, 13 Aug 1999 16:04:02 -0700 Date: Fri, 13 Aug 1999 16:04:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: NCR/Multia Problems? In-Reply-To: <199908111634.JAA00749@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have to agree. However, the NCR driver gets zero points for clarity, negative 10 points for diagnostic messages and the author only 5 points for responsiveness. Not a passing grade. If I wasn't running too late on other tasks, I'd do a rewrite myself. If there were no other SCSI HBA drivers available, I'd start championing IDE/ATA. On Wed, 11 Aug 1999, Mike Smith wrote: > > I've concluded that this is "Baked Multia Sydrome". > > > nopilt.feral.com > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (mem > > 4458e000:c0000004). > > ncr0: regdump: da 00 00 13 47 08 06 1f 75 08 86 00 80 00 0f 02. > > ncr0: restart (fatal error). > > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth 84:88080000). > > ncr0: script cmd = 88080000 > > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > > ncr0: restart (fatal error). > > ncr0:6: ERROR (a0:0) (0-0-0) (8/13) @ (scripth a0:c0000004). > > ncr0: script cmd = c0000004 > > ncr0: regdump: da 00 00 13 47 08 06 1f 35 08 86 00 80 00 0f 02. > > ncr0: restart (fatal error). > > (da1:ncr0:0:6:0): COMMAND FAILED (9 ff) @0xfffffe000058e400. > > > > > > What is this error? > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 16:57:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp.inreach.com (mail2.inreach.com [209.142.0.6]) by hub.freebsd.org (Postfix) with ESMTP id 631D815070; Fri, 13 Aug 1999 16:57:04 -0700 (PDT) (envelope-from dburr@pobox.com) Received: from relay (209-209-19-236.oak.inreach.net [209.209.19.236]) by smtp.inreach.com (8.9.3/8.9.3) with SMTP id QAA29055; Fri, 13 Aug 1999 16:40:51 -0700 (PDT) Message-ID: <001701bee5e8$92ce0060$ec13d1d1@relay> From: "Donald Burr" To: Cc: , References: <199908132251.RAA09931@nospam.hiwaay.net> Subject: Speaking about serial numbers... (was Re: On freezes in 3.2-Stable ) Date: Fri, 13 Aug 1999 17:04:06 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ bounced back to -SCSI, since this is actually a bona fide SCSI question ] You know, I've always wondered about this... Whenever someone posts dmesg output on one of the lists, I always look at it just out of curiosity. and in many cases I have seen the serial number of SCSI disks printed out. (heck, I seeem to recall once seeing an IDE disk print its serial number.) But in none of my systems am I getting any serial number output. One of my boxen, a PII400 (Abit BX6 R2.0 motherboard) has an Adaptec AHA-2940U2W controller, to which I have just added a brand-new, shiny IBM DDRS-39130 9GB LVD disk to it... and yet I get no serial number! (see dmesg below) Am I doing something wrong? do I need to enable any kernel config options for serial numbers to print? (the only SCSI options I have enabled are SCSI_REPORT_GEOMETRY and SCSI_DELAY) Or am I just cursed? :) Enquiring minds want to know! Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #1: Thu Aug 5 16:42:45 PDT 1999 dburr@Generator.Circuit.Powered-By.AC:/usr/src/sys/compile/GENERATOR Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127148032 (124168K bytes) Preloaded elf kernel "kernel" at 0xc0317000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 uhci0: rev 0x01 int d irq 15 on pci0.7.2 chip3: rev 0x02 on pci0.7.3 pn0: <82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 10 on pci0.11.0 pn0: Ethernet address: 00:a0:cc:29:16:c2 pn0: autoneg complete, link status good (half-duplex, 100Mbps) ahc0: rev 0x00 int a irq 11 on pci0.13.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs bktr0: rev 0x12 int a irq 15 on pci0.17.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 smbus1: on bti2c0 smb1: on smbus1 Miro TV, Temic NTSC tuner. Probing for devices on PCI bus 1: vga0: rev 0x5c int a irq 9 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x19507fdd Comp ID: PNPb02f [0x2fb0 d041] Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <12 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 lppps0: on ppbus 0 plip0: on ppbus 0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (atapi): , removable, acc el, dma, iordis acd0: drive speed 4134KB/sec, 2048KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc0: unit 1 (atapi): , removable, ac cel, dma, iordis acd1: drive speed 4125KB/sec, 512KB cache acd1: supported read types: CD-R, CD-RW, CD-DA, packet track acd1: Audio: play, 255 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick apm0 on isa apm: found APM BIOS version 1.2 usb0: uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ccd0-3: Concatenated disk drivers Waiting 8 seconds for SCSI devices to settle pass2 at ahc0 bus 0 target 5 lun 0 pass2: Fixed Scanner SCSI-2 device pass2: 3.300MB/s transfers da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) changing root device to da0s2a Donald Burr web: http://more.at/dburr/ ----- Original Message ----- From: David Kelly To: Kenneth D. Merry Cc: Mike Meyer ; Sent: Friday, August 13, 1999 3:51 PM Subject: Re: On freezes in 3.2-Stable > "Kenneth D. Merry" writes: > > Believe it or not, we've got something similar to the Ultrix spin-up stuff. > > > > FreeBSD/CAM will spin up drives on boot that are not already spinning. > > Generally, this happens in the probe stage, at the serial number inquiry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 17: 5:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id E01D615085 for ; Fri, 13 Aug 1999 17:05:01 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (5987 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Fri, 13 Aug 1999 17:05:17 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Fri, 13 Aug 1999 17:05:17 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD SCSI Subject: dump to dlt gets write error Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org asus p2b-ds 2x350mhz, 128mb two barracudas quantum dlt2000 4.0-currnt of 99.04.03 rip.psg.com:/# /do-dump ... DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 2951716 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.37% done, finished in 0:38 DUMP: 25.73% done, finished in 0:28 DUMP: 39.41% done, finished in 0:23 DUMP: 51.77% done, finished in 0:18 DUMP: 64.66% done, finished in 0:13 DUMP: 76.19% done, finished in 0:09 DUMP: 88.92% done, finished in 0:04 DUMP: write error 2700020 blocks into volume 1 DUMP: Do you want to restart?: ("yes" or "no") usually a LOT more fits on a tape, like four machines more. i ran the cleaning tape. i tried different tapes from different batches, including one that worked in the past. it breaks at different places, but always much of the way through that partition. clues solicited. randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jun 13 16:30:40 PDT 1999 root@rip.psg.com:/usr/src/sys/compile/RIP-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183fbff real memory = 134217728 (131072K bytes) config> USERCONFIG Invalid command or syntax. Type `?' for help. config> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 config> pnp 1 1 enable os port0 0x200 config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config> quit avail memory = 127676416 (124684K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02bc000. Preloaded userconfig_script "/kernel.config" at 0xc02bc09c. ccd0-5: Concatenated disk drivers Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 19 on pci0.9.0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: rev 0x02 int a irq 18 on pci0.10.0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only iicsmb0: on iicbus0 smbus0: on iicsmb0 smb0: on smbus0 iic0: on iicbus0 smbus1: on bti2c0 smb1: on smbus1 Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, msp3400c stereo. Detected a MSP3430G-A1 Probing for devices on PCI bus 1: vga0: rev 0x00 int a irq 16 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wl0 at 0x300-0x30f irq 7 on isa wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [140956 x 2048 byte records] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 17:15:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1445615070; Fri, 13 Aug 1999 17:15:15 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA63354; Fri, 13 Aug 1999 18:14:30 -0600 (MDT) (envelope-from ken) Message-Id: <199908140014.SAA63354@panzer.kdm.org> Subject: Re: Speaking about serial numbers... (was Re: On freezes in 3.2-Stable ) In-Reply-To: <001701bee5e8$92ce0060$ec13d1d1@relay> from Donald Burr at "Aug 13, 1999 05:04:06 pm" To: dburr@pobox.com (Donald Burr) Date: Fri, 13 Aug 1999 18:14:29 -0600 (MDT) Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Donald Burr wrote... > [ bounced back to -SCSI, since this is actually a bona fide SCSI question ] > > You know, I've always wondered about this... > > Whenever someone posts dmesg output on one of the lists, I always look at it > just out of curiosity. and in many cases I have seen the serial number of > SCSI disks printed out. (heck, I seeem to recall once seeing an IDE disk > print its serial number.) > > But in none of my systems am I getting any serial number output. > > One of my boxen, a PII400 (Abit BX6 R2.0 motherboard) has an Adaptec > AHA-2940U2W controller, to which I have just added a brand-new, shiny IBM > DDRS-39130 9GB LVD disk to it... and yet I get no serial number! (see dmesg > below) > > Am I doing something wrong? do I need to enable any kernel config options > for serial numbers to print? (the only SCSI options I have enabled are > SCSI_REPORT_GEOMETRY and SCSI_DELAY) Or am I just cursed? :) > > Enquiring minds want to know! Serial numbers are only printed out when you boot with -v. You can also get the serial number of your disk with camcontrol. e.g.: # camcontrol inquiry da1 pass1: Fixed Direct Access SCSI-3 device pass1: Serial Number 13102562NC pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled # camcontrol inquiry da1 -S 13102562NC Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 17:16:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 4314A150E2 for ; Fri, 13 Aug 1999 17:16:32 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id TAA57465; Fri, 13 Aug 1999 19:16:46 -0500 (CDT) Message-ID: <19990813191646.A57450@Denninger.Net> Date: Fri, 13 Aug 1999 19:16:46 -0500 From: Karl Denninger To: Randy Bush , FreeBSD SCSI Subject: Re: dump to dlt gets write error References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Randy Bush on Fri, Aug 13, 1999 at 05:05:17PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've seen this kind of stupidity before and you're not going to like the problem or solution. Put the DLT on a different SCSI bus (different host adapter) from the disks. Specifically, separate the fast/wide and narrow SCSI devices. I've seen both DLTs and other "non-wide" devices have kittens with disks running fast/wide on the same SCSI bus. It usually manifests itself as an I/O error on the narrow device - which is exactly what you're getting. My guess is that the hardware on the narrow (and not-so-fast) device gets mightily confused by the shorter signal times (even though they're not aimed at that target) and randomly "freaks out" enough to botch an operation. Do you get any kind of DMESG log when the write *fails* (check it) or a console log of the actual error? -- -- Karl Denninger (karl@denninger.net) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page On Fri, Aug 13, 1999 at 05:05:17PM -0700, Randy Bush wrote: > asus p2b-ds 2x350mhz, 128mb > two barracudas > quantum dlt2000 > 4.0-currnt of 99.04.03 > > rip.psg.com:/# /do-dump > ... > DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999 > DUMP: Date of last level 0 dump: the epoch > DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0 > DUMP: mapping (Pass I) [regular files] > DUMP: mapping (Pass II) [directories] > DUMP: estimated 2951716 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: 11.37% done, finished in 0:38 > DUMP: 25.73% done, finished in 0:28 > DUMP: 39.41% done, finished in 0:23 > DUMP: 51.77% done, finished in 0:18 > DUMP: 64.66% done, finished in 0:13 > DUMP: 76.19% done, finished in 0:09 > DUMP: 88.92% done, finished in 0:04 > DUMP: write error 2700020 blocks into volume 1 > DUMP: Do you want to restart?: ("yes" or "no") > > usually a LOT more fits on a tape, like four machines more. > > i ran the cleaning tape. i tried different tapes from different batches, > including one that worked in the past. it breaks at different places, but > always much of the way through that partition. > > clues solicited. > > randy > > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Sun Jun 13 16:30:40 PDT 1999 > root@rip.psg.com:/usr/src/sys/compile/RIP-SMP > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II/Xeon/Celeron (686-class CPU) > Origin = "GenuineIntel" Id = 0x651 Stepping=1 > Features=0x183fbff > real memory = 134217728 (131072K bytes) > config> USERCONFIG > Invalid command or syntax. Type `?' for help. > config> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 > config> pnp 1 1 enable os port0 0x200 > config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 > config> quit > avail memory = 127676416 (124684K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, > at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc02bc000. > Preloaded userconfig_script "/kernel.config" at 0xc02bc09c. > ccd0-5: Concatenated disk drivers > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x02 on pci0.1.0 > chip2: rev 0x02 on pci0.4.0 > chip3: rev 0x02 on pci0.4.3 > ahc0: rev 0x00 int a irq 19 on pci0.6.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > fxp0: rev 0x05 int a irq 19 on pci0.9.0 > fxp0: Ethernet address 00:a0:c9:df:c8:4e > bktr0: rev 0x02 int a irq 18 on pci0.10.0 > bti2c0: > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > iicsmb0: on iicbus0 > smbus0: on iicsmb0 > smb0: on smbus0 > iic0: on iicbus0 > smbus1: on bti2c0 > smb1: on smbus1 > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, msp3400c stereo. > Detected a MSP3430G-A1 > Probing for devices on PCI bus 1: > vga0: rev 0x00 int a irq 16 on pci1.0.0 > Probing for PnP devices: > CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] > pcm1 (SB16pnp sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <4 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > psm0 irq 12 on isa > psm0: model Generic PS/2 mouse, device ID 0 > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > pcm0 not probed due to drq conflict with pcm1 at 1 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wl0 at 0x300-0x30f irq 7 on isa > wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > wl0 XXX: driver didn't set ifq_maxlen > Waiting 15 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 5.000MB/s transfers (5.000MHz, offset 15) > changing root device to da0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 16) > cd0: Attempt to query device size failed: NOT READY, Medium not present > cd1 at ahc0 bus 0 target 5 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 8.333MB/s transfers (8.333MHz, offset 31) > cd1: cd present [140956 x 2048 byte records] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 19:20:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 97E2914C57; Fri, 13 Aug 1999 19:20:46 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-41.dialup.HiWAAY.net [216.180.14.41]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA24290; Fri, 13 Aug 1999 21:20:19 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA13492; Fri, 13 Aug 1999 21:20:17 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908140220.VAA13492@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: dburr@pobox.com (Donald Burr), freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG From: David Kelly Subject: Re: Speaking about serial numbers... (was Re: On freezes in 3.2-Stable ) In-reply-to: Message from "Kenneth D. Merry" of "Fri, 13 Aug 1999 18:14:29 MDT." <199908140014.SAA63354@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 21:20:17 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > You can also get the serial number of your disk with camcontrol. e.g.: > > # camcontrol inquiry da1 > pass1: Fixed Direct Access SCSI-3 device > pass1: Serial Number 13102562NC > pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Ena bled > # camcontrol inquiry da1 -S > 13102562NC Did the syntax change between -stable and -current? # camcontrol inquiry da1 camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed cam_lookup_pass: No such file or directory cam_lookup_pass: either the pass driver isn't in your kernel cam_lookup_pass: or da1 doesn't exist # camcontrol inquiry pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 68210913 pass2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled # camcontrol inquiry -S 68210913 # uname -a FreeBSD nospam.hiwaay.net 3.2-STABLE FreeBSD 3.2-STABLE #0: Sun Jun 13 08:28:04 CDT 1999 dkelly@nospam.hiwaay.net:/usr/src/sys/compile/REEBOK i386 -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 19:35:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 35C0714C57 for ; Fri, 13 Aug 1999 19:35:54 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-41.dialup.HiWAAY.net [216.180.14.41]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA04057; Fri, 13 Aug 1999 21:33:55 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA13520; Fri, 13 Aug 1999 21:33:53 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908140233.VAA13520@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger Cc: Randy Bush , FreeBSD SCSI From: David Kelly Subject: Re: dump to dlt gets write error In-reply-to: Message from Karl Denninger of "Fri, 13 Aug 1999 19:16:46 CDT." <19990813191646.A57450@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Aug 1999 21:33:53 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Denninger writes: > I've seen this kind of stupidity before and you're not going to like the > problem or solution. > > Put the DLT on a different SCSI bus (different host adapter) from the disks. > > Specifically, separate the fast/wide and narrow SCSI devices. > > I've seen both DLTs and other "non-wide" devices have kittens with disks > running fast/wide on the same SCSI bus. It usually manifests itself as > an I/O error on the narrow device - which is exactly what you're getting. > > My guess is that the hardware on the narrow (and not-so-fast) device gets > mightily confused by the shorter signal times (even though they're not > aimed at that target) and randomly "freaks out" enough to botch an > operation. I'd go a bit in the other direction and ask, "How is the transition between narrow and wide being handled?" Specifically people tend to purchase "narrow to wide" SCSI cables and simply plug things up with narrow devices at the tail end of the SCSI bus. Narrow terminator on the far end, wide terminator on the SCSI card. Nothing in the middle terminating the high bits of the wide bus. There are special terminators made just for that purpose. I'd like to think problems are caused by the device having problems. But we're talking about electrons here, and those little guys are sneaky. It may very well be a wide device is causing the narrow device to have problems. You are supposed to be safe if the internal narrow devices are connected to the 2940UW on the narrow connector, and the wide devices are connected the same, as long as you don't put a Tee in your SCSI bus by adding an external device. Just because the 2940UW has 3 connectors doesn't mean you can use all of them at once. Another good way to deal with everything internal is to route wide cable everywhere but use wide-to-narrow IDC-like adapters right at each device. About $15 each. Don't use the narrow connector on the 2940. The external wide connector is still usable this way. An old used narrow Adaptec 2940, or Symbios '810, or a new Adaptec 2930, might be a very good solution for the tape and CDROM. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 19:38:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6D81514C57; Fri, 13 Aug 1999 19:38:50 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA63955; Fri, 13 Aug 1999 20:37:20 -0600 (MDT) (envelope-from ken) Message-Id: <199908140237.UAA63955@panzer.kdm.org> Subject: Re: Speaking about serial numbers... (was Re: On freezes in 3.2-Stable ) In-Reply-To: <199908140220.VAA13492@nospam.hiwaay.net> from David Kelly at "Aug 13, 1999 09:20:17 pm" To: dkelly@hiwaay.net (David Kelly) Date: Fri, 13 Aug 1999 20:37:20 -0600 (MDT) Cc: dburr@pobox.com (Donald Burr), freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Kelly wrote... > "Kenneth D. Merry" writes: > > You can also get the serial number of your disk with camcontrol. e.g.: > > > > # camcontrol inquiry da1 > > pass1: Fixed Direct Access SCSI-3 device > > pass1: Serial Number 13102562NC > > pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Ena > bled > > # camcontrol inquiry da1 -S > > 13102562NC > > Did the syntax change between -stable and -current? Nope, it didn't change. > # camcontrol inquiry da1 > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or da1 doesn't exist > # camcontrol inquiry > pass2: Fixed Direct Access SCSI-2 device > pass2: Serial Number 68210913 > pass2: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > # camcontrol inquiry -S > 68210913 > # uname -a > FreeBSD nospam.hiwaay.net 3.2-STABLE FreeBSD 3.2-STABLE #0: Sun Jun 13 08:28:04 CDT 1999 dkelly@nospam.hiwaay.net:/usr/src/sys/compile/REEBOK i386 You don't have a da1, evidently. When you don't specify a device name, the default is da0. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 20:12: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id A6F4F1509C for ; Fri, 13 Aug 1999 20:11:56 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id WAA57911; Fri, 13 Aug 1999 22:09:50 -0500 (CDT) Message-ID: <19990813220950.A57905@Denninger.Net> Date: Fri, 13 Aug 1999 22:09:50 -0500 From: Karl Denninger To: David Kelly Cc: Randy Bush , FreeBSD SCSI Subject: Re: dump to dlt gets write error References: <199908140233.VAA13520@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199908140233.VAA13520@nospam.hiwaay.net>; from David Kelly on Fri, Aug 13, 1999 at 09:33:53PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Aug 13, 1999 at 09:33:53PM -0500, David Kelly wrote: > Karl Denninger writes: > > I've seen this kind of stupidity before and you're not going to like the > > problem or solution. > > > > Put the DLT on a different SCSI bus (different host adapter) from the disks. > > > > Specifically, separate the fast/wide and narrow SCSI devices. > > > > I've seen both DLTs and other "non-wide" devices have kittens with disks > > running fast/wide on the same SCSI bus. It usually manifests itself as > > an I/O error on the narrow device - which is exactly what you're getting. > > > > My guess is that the hardware on the narrow (and not-so-fast) device gets > > mightily confused by the shorter signal times (even though they're not > > aimed at that target) and randomly "freaks out" enough to botch an > > operation. > > I'd go a bit in the other direction and ask, "How is the transition > between narrow and wide being handled?" Specifically people tend to > purchase "narrow to wide" SCSI cables and simply plug things up with > narrow devices at the tail end of the SCSI bus. Narrow terminator on > the far end, wide terminator on the SCSI card. Nothing in the middle > terminating the high bits of the wide bus. There are special > terminators made just for that purpose. Correct. There are also guidelines on this in general related to the adapter. I'm assuming they are being followed. > You are supposed to be safe if the internal narrow devices are connected > to the 2940UW on the narrow connector, and the wide devices are > connected the same, as long as you don't put a Tee in your SCSI bus by > adding an external device. Just because the 2940UW has 3 connectors > doesn't mean you can use all of them at once. Correct, but not necessarily the issue at hand. > An old used narrow Adaptec 2940, or Symbios '810, or a new Adaptec > 2930, might be a very good solution for the tape and CDROM. Yep. -- -- Karl Denninger (karl@denninger.net) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 22:13:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2008C15054 for ; Fri, 13 Aug 1999 22:13:36 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (2363 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Fri, 13 Aug 1999 22:13:52 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Fri, 13 Aug 1999 22:13:52 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: David Kelly Cc: FreeBSD SCSI Subject: Re: dump to dlt gets write error References: <19990813191646.A57450@Denninger.Net> <199908140233.VAA13520@nospam.hiwaay.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i can dump the same partition if it is the first thing on the tape. e.g. DUMP: estimated 26937 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 26929 tape blocks on 1 volumes(s) DUMP: finished in 21 seconds, throughput 1282 KBytes/sec DUMP: level 0 dump on Fri Aug 13 16:06:44 1999 DUMP: Closing /dev/nrsa0 DUMP: DUMP IS DONE DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 2951716 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 11.37% done, finished in 0:38 DUMP: 25.73% done, finished in 0:28 DUMP: 39.41% done, finished in 0:23 DUMP: 51.77% done, finished in 0:18 DUMP: 64.66% done, finished in 0:13 DUMP: 76.19% done, finished in 0:09 DUMP: 88.92% done, finished in 0:04 DUMP: write error 2700020 blocks into volume 1 DUMP: Do you want to restart?: ("yes" or "no") yes DUMP: Closing this volume. Prepare to restart with new media; DUMP: this dump volume will be rewritten. DUMP: Closing /dev/nrsa0 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 8.74% done, finished in 0:52 DUMP: 22.95% done, finished in 0:33 DUMP: 36.06% done, finished in 0:26 DUMP: 48.98% done, finished in 0:20 DUMP: 62.22% done, finished in 0:15 DUMP: 73.78% done, finished in 0:10 DUMP: 86.91% done, finished in 0:05 DUMP: 98.23% done, finished in 0:00 DUMP: DUMP: 2954076 tape blocks on 1 volumes(s) DUMP: finished in 2456 seconds, throughput 1202 KBytes/sec DUMP: level 0 dump on Fri Aug 13 16:07:11 1999 DUMP: Closing /dev/nrsa0 DUMP: DUMP IS DONE randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 13 23:38: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2D7CE14E94 for ; Fri, 13 Aug 1999 23:38:02 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id XAA15422; Fri, 13 Aug 1999 23:38:04 -0700 Date: Fri, 13 Aug 1999 23:38:03 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Karl Denninger Cc: Randy Bush , "Justin T. Gibbs" Subject: Re: dump to dlt gets write error In-Reply-To: <19990813191646.A57450@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've seen this kind of stupidity before and you're not going to like the > problem or solution. > > Put the DLT on a different SCSI bus (different host adapter) from the disks. > > Specifically, separate the fast/wide and narrow SCSI devices. It isn't even fast/wide && narrow- look at the messages- it is claiming LVD Ultra2 speeds *AND* 5 MB/s sync mode. That cannot possibly be right- as far as I know you cannot actually do this. Justin? > > I've seen both DLTs and other "non-wide" devices have kittens with disks > running fast/wide on the same SCSI bus. It usually manifests itself as > an I/O error on the narrow device - which is exactly what you're getting. > > My guess is that the hardware on the narrow (and not-so-fast) device gets > mightily confused by the shorter signal times (even though they're not > aimed at that target) and randomly "freaks out" enough to botch an > operation. > > Do you get any kind of DMESG log when the write *fails* (check it) or a > console log of the actual error? > > -- > -- > Karl Denninger (karl@denninger.net) Web: childrens-justice.org > Tired of the broken divorce system in the United States and what it's doing > to our kids? SIGN the online petition for equal parental - and children's - > rights at the above URL. Make a difference in a kid's life today. > Real-time chat now available from the above web page > > > On Fri, Aug 13, 1999 at 05:05:17PM -0700, Randy Bush wrote: > > asus p2b-ds 2x350mhz, 128mb > > two barracudas > > quantum dlt2000 > > 4.0-currnt of 99.04.03 > > > > rip.psg.com:/# /do-dump > > ... > > DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999 > > DUMP: Date of last level 0 dump: the epoch > > DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0 > > DUMP: mapping (Pass I) [regular files] > > DUMP: mapping (Pass II) [directories] > > DUMP: estimated 2951716 tape blocks. > > DUMP: dumping (Pass III) [directories] > > DUMP: dumping (Pass IV) [regular files] > > DUMP: 11.37% done, finished in 0:38 > > DUMP: 25.73% done, finished in 0:28 > > DUMP: 39.41% done, finished in 0:23 > > DUMP: 51.77% done, finished in 0:18 > > DUMP: 64.66% done, finished in 0:13 > > DUMP: 76.19% done, finished in 0:09 > > DUMP: 88.92% done, finished in 0:04 > > DUMP: write error 2700020 blocks into volume 1 > > DUMP: Do you want to restart?: ("yes" or "no") > > > > usually a LOT more fits on a tape, like four machines more. > > > > i ran the cleaning tape. i tried different tapes from different batches, > > including one that worked in the past. it breaks at different places, but > > always much of the way through that partition. > > > > clues solicited. > > > > randy > > > > > > Copyright (c) 1992-1999 The FreeBSD Project. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > FreeBSD 4.0-CURRENT #0: Sun Jun 13 16:30:40 PDT 1999 > > root@rip.psg.com:/usr/src/sys/compile/RIP-SMP > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium II/Xeon/Celeron (686-class CPU) > > Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > Features=0x183fbff > > real memory = 134217728 (131072K bytes) > > config> USERCONFIG > > Invalid command or syntax. Type `?' for help. > > config> pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 > > config> pnp 1 1 enable os port0 0x200 > > config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 > > config> quit > > avail memory = 127676416 (124684K bytes) > > Programming 24 pins in IOAPIC #0 > > FreeBSD/SMP: Multiprocessor motherboard > > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > > cpu1 (AP): apic id: 0, version: 0x00040011, > > at 0xfee00000 > > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > > Preloaded elf kernel "kernel" at 0xc02bc000. > > Preloaded userconfig_script "/kernel.config" at 0xc02bc09c. > > ccd0-5: Concatenated disk drivers > > Probing for devices on PCI bus 0: > > chip0: rev 0x02 on pci0.0.0 > > chip1: rev 0x02 on pci0.1.0 > > chip2: rev 0x02 on pci0.4.0 > > chip3: rev 0x02 on pci0.4.3 > > ahc0: rev 0x00 int a irq 19 on pci0.6.0 > > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > > fxp0: rev 0x05 int a irq 19 on pci0.9.0 > > fxp0: Ethernet address 00:a0:c9:df:c8:4e > > bktr0: rev 0x02 int a irq 18 on pci0.10.0 > > bti2c0: > > iicbb0: on bti2c0 > > iicbus0: on iicbb0 master-only > > iicsmb0: on iicbus0 > > smbus0: on iicsmb0 > > smb0: on smbus0 > > iic0: on iicbus0 > > smbus1: on bti2c0 > > smb1: on smbus1 > > Hauppauge WinCast/TV, Philips FR1236 NTSC FM tuner, msp3400c stereo. > > Detected a MSP3430G-A1 > > Probing for devices on PCI bus 1: > > vga0: rev 0x00 int a irq 16 on pci1.0.0 > > Probing for PnP devices: > > CSN 1 Vendor ID: CTL00c3 [0xc3008c0e] Serial 0x1fd0a682 Comp ID: PNPb02f [0x2fb0d041] > > pcm1 (SB16pnp sn 0x1fd0a682) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa > > Probing for devices on the ISA bus: > > sc0 on isa > > sc0: VGA color <4 virtual consoles, flags=0x0> > > atkbdc0 at 0x60-0x6f on motherboard > > atkbd0 irq 1 on isa > > psm0 irq 12 on isa > > psm0: model Generic PS/2 mouse, device ID 0 > > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > > sio0: type 16550A > > sio1 at 0x2f8-0x2ff irq 3 on isa > > sio1: type 16550A > > pcm0 not probed due to drq conflict with pcm1 at 1 > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > fdc0: FIFO enabled, 8 bytes threshold > > fd0: 1.44MB 3.5in > > wl0 at 0x300-0x30f irq 7 on isa > > wl0: address 08:00:6a:2b:dd:a7, NWID 0xaaaa > > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > > npx0 on motherboard > > npx0: INT 16 interface > > APIC_IO: Testing 8254 interrupt delivery > > APIC_IO: routing 8254 via pin 2 > > wl0 XXX: driver didn't set ifq_maxlen > > Waiting 15 seconds for SCSI devices to settle > > SMP: AP CPU #1 Launched! > > sa0 at ahc0 bus 0 target 6 lun 0 > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 5.000MB/s transfers (5.000MHz, offset 15) > > changing root device to da0s1a > > da0 at ahc0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled > > da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > > da1 at ahc0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled > > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > > cd0 at ahc0 bus 0 target 4 lun 0 > > cd0: Removable CD-ROM SCSI-2 device > > cd0: 20.000MB/s transfers (20.000MHz, offset 16) > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > cd1 at ahc0 bus 0 target 5 lun 0 > > cd1: Removable CD-ROM SCSI-2 device > > cd1: 8.333MB/s transfers (8.333MHz, offset 31) > > cd1: cd present [140956 x 2048 byte records] > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 14 2:32: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8FC3314E2A for ; Sat, 14 Aug 1999 02:31:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id LAA23168; Sat, 14 Aug 1999 11:25:50 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id LAA53941; Sat, 14 Aug 1999 11:20:11 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908140920.LAA53941@yedi.iaf.nl> Subject: Re: dump to dlt gets write error In-Reply-To: <19990813191646.A57450@Denninger.Net> from Karl Denninger at "Aug 13, 1999 7:16:46 pm" To: karl@Denninger.Net (Karl Denninger) Date: Sat, 14 Aug 1999 11:20:11 +0200 (CEST) Cc: randy@psg.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Karl Denninger wrote ... > I've seen this kind of stupidity before and you're not going to like the > problem or solution. > > Put the DLT on a different SCSI bus (different host adapter) from the disks. > > Specifically, separate the fast/wide and narrow SCSI devices. > > I've seen both DLTs and other "non-wide" devices have kittens with disks > running fast/wide on the same SCSI bus. It usually manifests itself as > an I/O error on the narrow device - which is exactly what you're getting. I've been doing this for years and it works just fine: FreeBSD 3.2-STABLE #5: Sun Aug 8 17:13:28 CEST 1999 root@yedi.iaf.nl:/usr/freebsd-stable-src/src/sys/compile/YEDI [....] da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 17365MB (35565080 512 byte sectors: 255H 63S/T 2213C) evice to da0s2a cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present sa3 at ahc0 bus 0 target 2 lun 0 sa3: Removable Sequential Access SCSI-2 device sa3: 5.000MB/s transfers (5.000MHz, offset 15) sa2 at ahc0 bus 0 target 5 lun 0 sa2: Removable Sequential Access SCSI-2 device sa2: 10.000MB/s transfers (10.000MHz, offset 15) sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers The TZ88 is a DLT4000 btw, I also used a TZ87 which is a DLT2000. All my tapes are in a Storageworks shelf. > My guess is that the hardware on the narrow (and not-so-fast) device gets > mightily confused by the shorter signal times (even though they're not > aimed at that target) and randomly "freaks out" enough to botch an > operation. A DLT4000 is also a fast scsi device. My DLT2000 which is 5 Mb/sec also worked just fine. If I had to guess this is bad interconnect of some kind, or lousy termination. > Do you get any kind of DMESG log when the write *fails* (check it) or a > console log of the actual error? You can also pull the error logs from within the DLT drive itself. Try the script below: #!/bin/sh # dltinfo: get more information out of your DLT tape drive. # # (C) 1996, Wilko Bulte, wilko@freebsd.org # # Warning: This script has only been tested on a DEC TZ87 & TZ88 DLT # # You need the DLT drive's OEM manual (or similar) to make # sense out of some of the data reported. # Please send any constructive comments by email to wilko@freebsd.org Unit=2 ## camcontrol(8) setup Verbose="-v" TimeOut="-t 3" get_write_error_log() { RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 42 0 0 0 0 0 3f 0" \ -i 63 \ "{skip} *i4 \ {skip} *i4 \ {Corrected errors without substantial delay} i4 \ {skip} *i4 \ {Corrected errors with possible delay } i4 \ {skip} *i4 \ {Total errors } i4 \ {skip} *i4 \ {Total errors corrected } i4 \ {skip} *i4 \ {Total times correction algorithm processed} i4 \ {skip} *i4 \ {Total bytes processed } i8 \ {skip} *i4 \ {Total uncorrected errors } i4" ` set $RetVal echo "--- write errors ---" printf "Corrected errors without substantial delay = %d\n" $1 printf "Corrected errors with possible delay = %d\n" $2 printf "Total errors = %d\n" $3 printf "Total errors corrected = %d\n" $4 printf "Total times correction algorithm processed = %d\n" $5 printf "Total bytes processed = %d\n" $6 printf "Total uncorrected errors = %d\n" $7 } get_read_error_log() { RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 43 0 0 0 0 0 3f 0" \ -i 63 \ "{skip} *i4 \ {skip} *i4 \ {Corrected errors without substantial delay} i4 \ {skip} *i4 \ {Corrected errors with possible delay } i4 \ {skip} *i4 \ {Total errors } i4 \ {skip} *i4 \ {Total errors corrected } i4 \ {skip} *i4 \ {Total times correction algorithm processed} i4 \ {skip} *i4 \ {Total bytes processed } i8 \ {skip} *i4 \ {Total uncorrected errors } i4" ` set $RetVal echo "--- read errors ---" printf "Corrected errors without substantial delay = %d\n" $1 printf "Corrected errors with possible delay = %d\n" $2 printf "Total errors = %d\n" $3 printf "Total errors corrected = %d\n" $4 printf "Total times correction algorithm processed = %d\n" $5 printf "Total bytes processed = %d\n" $6 printf "Total uncorrected errors = %d\n" $7 } get_compression_log() { # Assumption: from the results observed in testing it lookse # like the residual counts are in kBytes (and not # in Mbytes as the TZ87 manual tells us). RetVal=`camcontrol cmd -n sa -u $Unit \ $Verbose \ $Timeout \ -c "4d 0 72 0 0 0 0 0 4c 0" \ -i 76 \ "{skip} *i4 \ {skip } *i4 \ {Read compression ratio (* 100 %) } i2 \ {skip } *i4 \ {Write compression ratio (* 100 %) } i2 \ {skip } *i4 \ {Total host Mbytes reads } i4 \ {skip } *i4 \ {Total host kbytes read residual } i4 \ {skip } *i4 \ {On tape Mbytes read } i4 \ {skip} *i4 \ {On tape kbytes read residual } i4 \ {skip} *i4 \ {Host requested Mbytes written } i4 \ {skip} *i4 \ {Host requested kbytes written residual } i4 \ {skip} *i4 \ {On tape Mbytes written } i4 \ {skip} *i4 \ {On tape kbytes written residual } i4 " ` set $RetVal echo "--- compression statistics ---" printf "Read compression ratio = %d %%\n" $1 printf "Write compression ratio = %d %%\n" $2 printf "Total host Mbytes read = %d\n" $3 printf "Total host kbytes read residual = %d\n" $4 printf "On tape Mbytes read = %d\n" $5 printf "On tape kbytes read residual = %d\n" $6 printf "Host requested Mbytes written = %d\n" $7 printf "Host requested kbytes written residual = %d\n" $8 printf "On tape Mbytes written = %d\n" $9 printf "On tape kbytes written residual = %d\n" $10 } get_read_error_log echo get_write_error_log echo get_compression_log echo It is a quick hack but it works for me. Like in: Mon Aug 9 00:32:07 CEST 1999 DUMP: Date of this level 0 dump: Mon Aug 9 00:32:07 1999 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rda1c (/local2) to /dev/nrsa2 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 2685410 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 12.18% done, finished in 0:36 DUMP: 27.84% done, finished in 0:25 DUMP: 43.49% done, finished in 0:19 DUMP: 59.02% done, finished in 0:13 DUMP: 73.04% done, finished in 0:09 DUMP: 86.80% done, finished in 0:04 DUMP: 99.85% done, finished in 0:00 DUMP: DUMP: 2686684 tape blocks on 1 volumes(s) DUMP: finished in 2104 seconds, throughput 1276 KBytes/sec DUMP: level 0 dump on Mon Aug 9 00:32:07 1999 DUMP: Closing /dev/nrsa2 DUMP: DUMP IS DONE Mon Aug 9 01:07:41 CEST 1999 --- read errors --- Corrected errors without substantial delay = 0 Corrected errors with possible delay = 0 Total errors = 0 Total errors corrected = 0 Total times correction algorithm processed = 0 Total bytes processed = 0 Total uncorrected errors = 0 --- write errors --- Corrected errors without substantial delay = 0 Corrected errors with possible delay = 0 Total errors = 105 Total errors corrected = 105 Total times correction algorithm processed = 0 Total bytes processed = 0 Total uncorrected errors = 0 --- compression statistics --- Read compression ratio = 0 % Write compression ratio = 100 % Total host Mbytes read = 0 Total host kbytes read residual = 0 On tape Mbytes read = 0 On tape kbytes read residual = 0 Host requested Mbytes written = 9196 Host requested kbytes written residual = 196608 On tape Mbytes written = 9196 On tape kbytes written residual = 0 The most interesting part is the Total errors thingy. I've seen that sky rocket with bad media or DLT drives with a bad head. IMHO this kind of errorlogging would be cool to have in any standard shape. Like VMS does, or in a quite different form, DEC Unix, eh Tru64. Really useful in case you have hardware problems. > Karl Denninger (karl@denninger.net) Web: childrens-justice.org > > > On Fri, Aug 13, 1999 at 05:05:17PM -0700, Randy Bush wrote: > > asus p2b-ds 2x350mhz, 128mb > > two barracudas > > quantum dlt2000 > > 4.0-currnt of 99.04.03 > > > > rip.psg.com:/# /do-dump > > ... > > DUMP: Date of this level 0 dump: Fri Aug 13 16:07:11 1999 > > DUMP: Date of last level 0 dump: the epoch > > DUMP: Dumping /dev/rccd5c (/usr) to /dev/nrsa0 > > DUMP: mapping (Pass I) [regular files] > > DUMP: mapping (Pass II) [directories] > > DUMP: estimated 2951716 tape blocks. > > DUMP: dumping (Pass III) [directories] > > DUMP: dumping (Pass IV) [regular files] > > DUMP: 11.37% done, finished in 0:38 > > DUMP: 25.73% done, finished in 0:28 > > DUMP: 39.41% done, finished in 0:23 > > DUMP: 51.77% done, finished in 0:18 > > DUMP: 64.66% done, finished in 0:13 > > DUMP: 76.19% done, finished in 0:09 > > DUMP: 88.92% done, finished in 0:04 > > DUMP: write error 2700020 blocks into volume 1 > > DUMP: Do you want to restart?: ("yes" or "no") > > > > usually a LOT more fits on a tape, like four machines more. > > > > i ran the cleaning tape. i tried different tapes from different batches, Don't ever run cleaning tapes on a DLT drive unless the 'Use cleaning tape' LED comes on. Cleaning tapes are really bad news for the DLT heads if they are run on a regular basis. They consist of a more or less normal data tape that did not get it's final polishing steps in manufacturing. They are quite abrasive and do bad things to non-dirty heads. > > including one that worked in the past. it breaks at different places, but > > always much of the way through that partition. > > > > clues solicited. > > > > randy > > -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 14 4:58:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cybernet.in.th (www.cybernet.in.th [203.149.3.222]) by hub.freebsd.org (Postfix) with SMTP id E455B14C2D for ; Sat, 14 Aug 1999 04:58:23 -0700 (PDT) (envelope-from bunlu@cybernet.in.th) Received: (qmail 19757 invoked by uid 555); 14 Aug 1999 11:56:16 -0000 Message-ID: <19990814115616.19642.qmail@cybernet.in.th> Date: 14 Aug 1999 18:56:16 +0700 Reply-To: From: Bunlu Nantaeng To: Jonathan Lemon Cc: freebsd-scsi@freebsd.org Subject: Re: Re: nead help on Compaq ida disk. X-Sender: bunlu@cybernet.in.th (via http://mail.cybernet.in.th/) X-Client: 203.149.3.217 MIME-Version: 1.0 Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Fri, 13 Aug 1999 09:46:27 -0500 (CDT) > From: Jonathan Lemon > Subject: Re: nead help on Compaq ida disk. > > >--- > >Probing for devices on PCI bus 2: > >ida0: rev 0x03 int a irq 11 on pci2.0.0 > >ida0: drvs=1 firm_rev=3.22 > >ida0: unit 0 (id0): > >id0: 20467MB (41917920 total sec), 5137 cyl, 255 head, 32 sec, bytes/sec 512 > >ida: wdc vector stealing off (mode = never, boot major = 4) > >--- > >How can I mount my id0 disk? > > Since you're not doing vector stealing here, you need to mount > the drives with the id0 device nodes. The following patch to > MAKEDEV should allow creation of the appropriate /dev entries. > -- > Jonathan > Thank you very for your help. But your patch below make ida0(not id0), right? I tried and got kernel panic when I enter "fdisk /dev/ida0". So, I edit your patch for make "/dev/id0". Result is the same panic! I'm running 3.2-STABLE on Compaq Proliant 1600 with Compaq Samart Array 221 Controller. Any idea? -- Bunlu Nantaeng > Index: MAKEDEV > =================================================================== > RCS file: /tuna/ncvs/src/etc/etc.i386/MAKEDEV,v > retrieving revision 1.200 > retrieving revision 1.201 > diff -u -r1.200 -r1.201 > --- MAKEDEV 1999/07/05 08:39:00 1.200 > +++ MAKEDEV 1999/07/05 09:18:57 1.201 > @@ -48,6 +48,7 @@ > # vn* "vnode disks" > # od* "optical disks" > # fla* "M-Systems DiskOnChip" > +# ida* "Compaq Smart-2 RAID" > # > # Console ports: > # vty* virtual console devices for syscons/pcvt/codrv > @@ -127,7 +128,7 @@ > # ipl ipfilter control devices (ipl, ipnat, ipstate, ipauth) > # kbd keyboard devices > # > -# $Id: MAKEDEV,v 1.200 1999/07/05 08:39:00 jkh Exp $ > +# $Id: MAKEDEV,v 1.201 1999/07/05 09:18:57 msmith Exp $ > # > > PATH=/sbin:/bin/:/usr/bin:/usr/sbin:$PATH > @@ -297,11 +298,12 @@ > ;; > > # Individual slices. > -ad*s*|od*s*|sd*s*|da*s*|vn*s*|wd*s*|afd*s*|wfd*s*|fla*s*) > +ad*s*|od*s*|sd*s*|da*s*|vn*s*|wd*s*|afd*s*|wfd*s*|fla*s*|ida*s*) > umask $disk_umask > case $i in > ad*s*) name=ad; blk=30; chr=116;; > afd*s*) name=afd; blk=32; chr=118;; > + ida*s*) name=ida; blk=29; chr=109;; > fla*s*) name=fla; blk=28; chr=102;; > od*s*) name=od; blk=4; chr=13;; > sd*s*) name=sd; blk=4; chr=13;; > @@ -311,7 +313,7 @@ > wfd*s*) name=wfd; blk=1; chr=87;; > esac > case $i in > - afd*s*|fla*s*|wfd*s*) > + afd*s*|ida*s*|fla*s*|wfd*s*) > unit=`expr $i : '...\([0-9]*\)s'` > slice=`expr $i : '...[0-9]*s\([0-9]*\)'` > part=`expr $i : '...[0-9]*s[0-9]*\(.*\)'` > @@ -470,11 +472,12 @@ > umask 77 > ;; > > -ad*|sd*|od*|da*|vn*|wd*|afd*|wfd*|fla*) > +ad*|sd*|od*|da*|vn*|wd*|afd*|wfd*|fla*|ida*) > umask $disk_umask > case $i in > ad*) name=ad; blk=30; chr=116;; > afd*) name=afd; blk=32; chr=118;; > + ida*) name=ida; blk=29; chr=109;; > fla*) name=fla; blk=28; chr=102;; > sd*) name=sd; blk=4; chr=13;; > od*) name=od; blk=4; chr=13;; > @@ -484,7 +487,7 @@ > wfd*) name=wfd; blk=1; chr=87;; > esac > case $i in > - afd*|fla*|wfd*) > + afd*|ida*|fla*|wfd*) > unit=`expr $i : '...\(.*\)'` > ;; > *) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 14 8:59:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0499E1504F for ; Sat, 14 Aug 1999 08:59:51 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (1549 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 14 Aug 1999 08:59:19 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 14 Aug 1999 08:59:19 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Wilko Bulte Cc: freebsd-scsi@freebsd.org Subject: Re: dump to dlt gets write error References: <19990813191646.A57450@Denninger.Net> <199908140920.LAA53941@yedi.iaf.nl> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Put the DLT on a different SCSI bus (different host adapter) from the disks. >> >> Specifically, separate the fast/wide and narrow SCSI devices. >> >> I've seen both DLTs and other "non-wide" devices have kittens with disks >> running fast/wide on the same SCSI bus. It usually manifests itself as >> an I/O error on the narrow device - which is exactly what you're getting. > > I've been doing this for years and it works just fine: i have been doing it for many months, and it was fine. i suddenly hit the problem yesterday. i was very frustrated, so went and ate some sushi. i came back, and it worked just fine. no other changes except sushi (not a hot day, tape was not preloaded in drive to heat up in any of the tests, ...). and i tried again this morning, now using -CURRENT as of last night, and it backs up just fine, and on one of the same tapes that failed last afternoon. > You can also pull the error logs from within the DLT drive itself. Try > the script below: thank you! > Don't ever run cleaning tapes on a DLT drive unless the 'Use cleaning tape' > LED comes on. again, thanks. seems wise advice. randy, aka hamachi-breath To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 14 9:18:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id CE0901504F for ; Sat, 14 Aug 1999 09:18:51 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id LAA62533; Sat, 14 Aug 1999 11:18:56 -0500 (CDT) Message-ID: <19990814111856.B62519@Denninger.Net> Date: Sat, 14 Aug 1999 11:18:56 -0500 From: Karl Denninger To: Randy Bush , Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: dump to dlt gets write error References: <19990813191646.A57450@Denninger.Net> <199908140920.LAA53941@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Randy Bush on Sat, Aug 14, 1999 at 08:59:19AM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 14, 1999 at 08:59:19AM -0700, Randy Bush wrote: > >> Put the DLT on a different SCSI bus (different host adapter) from the disks. > >> > >> Specifically, separate the fast/wide and narrow SCSI devices. > >> > >> I've seen both DLTs and other "non-wide" devices have kittens with disks > >> running fast/wide on the same SCSI bus. It usually manifests itself as > >> an I/O error on the narrow device - which is exactly what you're getting. > > > > I've been doing this for years and it works just fine: > > i have been doing it for many months, and it was fine. i suddenly hit the > problem yesterday. > > i was very frustrated, so went and ate some sushi. i came back, and it > worked just fine. no other changes except sushi (not a hot day, tape was > not preloaded in drive to heat up in any of the tests, ...). > > and i tried again this morning, now using -CURRENT as of last night, and it > backs up just fine, and on one of the same tapes that failed last afternoon. It'll come back. This problem is one that is I/O pattern-related. I've seen it before and its a m****f***** to nail down. I finally gave up and just put in a second adapter. Since doing that I haven't had a SINGLE problem like this. > > You can also pull the error logs from within the DLT drive itself. Try > > the script below: > > thank you! Ditto. That's a cool script :-) > > Don't ever run cleaning tapes on a DLT drive unless the 'Use cleaning tape' > > LED comes on. > > again, thanks. seems wise advice. Yep. > randy, aka hamachi-breath Hmmm... what's this Sushi thing with FreeBSD geeks? I love the damn stuff! -- -- Karl Denninger (karl@denninger.net) Web: childrens-justice.org Tired of the broken divorce system in the United States and what it's doing to our kids? SIGN the online petition for equal parental - and children's - rights at the above URL. Make a difference in a kid's life today. Real-time chat now available from the above web page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 14 15: 2:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F4041154DD; Sat, 14 Aug 1999 15:02:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA17328; Sat, 14 Aug 1999 15:00:12 -0700 Date: Sat, 14 Aug 1999 15:00:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Vince Vielhaber Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Onstream? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Release and development of this driver has been delayed. It has been impossible to get a stable -current platform to work with each time I've tried to update my working -current tree over the last two weeks. I guess I've picked the wrong days to update... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message