From owner-freebsd-scsi Mon May 8 12:38: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125]) by hub.freebsd.org (Postfix) with ESMTP id 77CDB37BBA6; Mon, 8 May 2000 12:38:00 -0700 (PDT) (envelope-from ddw@cortex.NSMA.Arizona.EDU) Received: from cortex (localhost [127.0.0.1]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id MAA16581; Mon, 8 May 2000 12:50:36 -0700 (MST) Message-Id: <200005081950.MAA16581@cortex.NSMA.Arizona.EDU> Reply-To: ddw@NSMA.Arizona.EDU X-Mailer: nmh - The "True to Unix" mail handler To: freebsd-scsi@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Problems with 36GB SCSI drives... Date: Mon, 08 May 2000 12:50:35 -0700 From: Doug Wellington Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org OK, I've been working on various incarnations of this problem for a week now... I have another day or two and then I'm gonna have to go back to NT... Sigh... [Help me, PLEASE...!] I have a PC (550 MHZ P-III, Asus P3B-F, 256 MB) with two Adaptec 2940U2W boards with six IBM DMVS36V 36GB drives. I also have a four gig internal SCSI drive attached to the first 2940U2W to boot from. The goal is to use vinum and create a RAID5 system... OK, I have installed FreeBSD 4.0 from the CD that I was shipped. I then try to use disklabel to put a label onto the first 36GB drive, like so: disklabel -Brw da1 auto but the SCSI bus times out and then I'm hosed. I get the following messages: (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5d (da1:ahc0:0:1:0) BDR message in message buffer (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5e (da1:ahc0:0:1:0) BDR message in message buffer (da1:ahc0:0:1:0) no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted And a screen full of similar messages. (I have to copy them over by hand, but I'll do it if it means solving this problem.) The internal disk seems to go into a timeout as well. (da0:ahc0:0:0:0) After a few minutes, the command prompt comes back, and I can type "disklabel da1" and get what looks like a valid reply. I can also run disklabel -e and add another partition, but if I try to use newfs, I get the same timeout problems. I've tried this with disks attached to the other 2940 with the same results. (Except that the internal drive doesn't time out in that case...) If I try to reboot the computer at this (or any other) point, it freezes with the following message: int=00000000 err=00000000 efl=00030246 eip=00001b54 eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 system halted I get this message whether I reboot immediately after the first disklabel command, or if I reboot after using disklabel to add a partition, or after using newfs. I get the same message whether I try to boot from the system on the hard disk or from the 4.0 CD-ROM. I get a similar message when trying to boot from a 3.4 CD. At this point, the only way I can do anything is to reboot, hit ctrl-A to get into the Adaptec diagnostics and reformat the 36 GB hard disk at that level. Then I can reboot and FreeBSD starts right up from the internal hard disk where it was originally installed. What gives? Anybody have any ideas? -Doug -- Doug Wellington System and Network Administrator ddw@nsma.arizona.edu The University of Arizona, Tucson, AZ, USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 13:14:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 9E4F537BBFF; Mon, 8 May 2000 13:14:26 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id QAA70043; Mon, 8 May 2000 16:14:17 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005082014.QAA70043@larryboy.graphics.cornell.edu> To: ddw@NSMA.Arizona.EDU Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: Message from Doug Wellington of "Mon, 08 May 2000 12:50:35 PDT." <200005081950.MAA16581@cortex.NSMA.Arizona.EDU> Date: Mon, 08 May 2000 16:14:17 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >OK, I've been working on various incarnations of this problem for a week >now... I have another day or two and then I'm gonna have to go back to >NT... Sigh... [Help me, PLEASE...!] NO, anything but that! I hope you won't feel insulted if I ask if you've made extra certain that you don't have 2 devices using the same scsi address. Not just by looking at the switch or jumper settings, but reading through the boot messages to make sure they're all registering differently. Maybe even try disconnecting power from the ones not currently being used to see if that gets you through disklabel. And double-check termination and cabling distance rules. (Somehow this doesn't sound like the sort of thing NT is going to solve.) -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 14: 3: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125]) by hub.freebsd.org (Postfix) with ESMTP id E6C2537B663; Mon, 8 May 2000 14:02:54 -0700 (PDT) (envelope-from ddw@cortex.NSMA.Arizona.EDU) Received: from cortex (localhost [127.0.0.1]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id OAA17706; Mon, 8 May 2000 14:15:36 -0700 (MST) Message-Id: <200005082115.OAA17706@cortex.NSMA.Arizona.EDU> Reply-To: ddw@NSMA.Arizona.EDU X-Mailer: nmh - The "True to Unix" mail handler To: Mitch Collinsworth Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 16:14:17 -0400." <200005082014.QAA70043@larryboy.graphics.cornell.edu> Date: Mon, 08 May 2000 14:15:36 -0700 From: Doug Wellington Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Previously: >[NT] >NO, anything but that! Yeah... That's what *I* said... >I hope you won't feel insulted if I ask if you've made extra certain >that you don't have 2 devices using the same scsi address. Not just >by looking at the switch or jumper settings, but reading through the >boot messages to make sure they're all registering differently. No insult at all. I'm actually hoping it's something really stupid that I'm doing wrong! As for the scsi addresses, I set the jumpers myself, watched as each Adaptec board probed its address range and listed the drives it found during boot and then checked the logs. I even scribbled a little matrix out with the adapters and scsi id numbers and checked each one off... I originally had the scsi cards in different slots, but I thought there was an IRQ problem, (you know, the AGP slot shares an IRQ with PCI slot #1 kinda thAng) so I swapped cards around and I don't think that's an issue... Hmmmm, funny thing is that when I had the 2940 in slot #1, I was able to get all the way to using vinum and trying the "init" command before it failed... >Maybe >even try disconnecting power from the ones not currently being used to >see if that gets you through disklabel. Yeah, I'm down to where I have one external case turned on (with three drives in it. The other drives are turned off. After lunch, I guess I'll just open that case up and pull the power off of the other two drives. After that, I guess I'll have to try putting one of the disks on the internal SCSI connector... [Drumming fingers] I'm wondering if it's the motherboard... Wish I had another one to test. (I have tried different 2940U2W boards already.) >And double-check termination and cabling distance rules. FWIW, the light on the active terminator is on. I only have a three foot cable going from the computer to the external box... >(Somehow this doesn't sound like the sort of thing NT is going to solve.) Well, the weird thing is that just for grins, I DID boot up NT once and I was able to see and format one of the external disks... That was one of my first attempts to get past that boot up error message, before I started using the built in (ctrl-A) adaptec formatting routines. (Since I couldn't boot from the FreeBSD CD or the internal hard disk, I had to try something to get rid of the partitions on the disk...) The problem is that since NT worked, that makes me wonder if it is the motherboard after all...? Is there a disk size limit with FreeBSD? Is 36 GB too big? SIGH... Thanks, -Doug -- Doug Wellington System and Network Administrator ddw@nsma.arizona.edu The University of Arizona, Tucson, AZ, USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 14:19:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 707EE37B5DC; Mon, 8 May 2000 14:19:24 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id RAA70490; Mon, 8 May 2000 17:19:20 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005082119.RAA70490@larryboy.graphics.cornell.edu> To: ddw@NSMA.Arizona.EDU Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: Message from Doug Wellington of "Mon, 08 May 2000 14:15:36 PDT." <200005082115.OAA17706@cortex.NSMA.Arizona.EDU> Date: Mon, 08 May 2000 17:19:20 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Is there a disk size limit with FreeBSD? Is 36 GB too big? No I don't think it's that. I have 2 50 GB drives on a 2940u2w running just fine under FBSD 3.4. There have been some problems with large disks but so far they've all been with ATA. I was about to ask why you need 2 controllers for 7 disks but I think I see why you did that. Just for grins though it might be interesting to see if pulling one controller and putting them all on the same bus would make things happier. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 15:38:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from charon.khoral.com (charon.khoral.com [209.75.155.97]) by hub.freebsd.org (Postfix) with SMTP id 7353A37B91B; Mon, 8 May 2000 15:38:09 -0700 (PDT) (envelope-from steve@khoral.com) Received: from zen.alb.khoral.com by charon.khoral.com via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 8 May 2000 22:38:08 UT Received: from benson (benson.alb.khoral.com [10.1.2.11]) by zen.alb.khoral.com (8.9.3/8.9.3) with ESMTP id QAA07052; Mon, 8 May 2000 16:37:39 -0600 (MDT) From: Steve Jorgensen Date: Mon, 8 May 2000 16:37:29 -0600 (MDT) Message-Id: <200005082237.QAA29923@benson> To: ddw@NSMA.Arizona.EDU Cc: Mitch Collinsworth , freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yeah, I'm down to where I have one external case turned on (with three > drives in it. The other drives are turned off. After lunch, I guess I'll > just open that case up and pull the power off of the other two drives. After > that, I guess I'll have to try putting one of the disks on the internal > SCSI connector... You don't by chance have devices connected to both internal connectors AND something connected to the external connector? I don't have a u2w, but my adaptec 2940uw says you can't do that. Of course that little fact is buried in the small print of their manual, but I have had experience myself where things would look like their working and then just flake out after it ran for a while. Hope this helps.. Steve ----------------------------------------------------------- Steven Jorgensen steve@khoral.com steve@spukhaus.com ------------------------------+---------------------------- Khoral Research Inc. | PHONE: (505) 837-6500 6200 Uptown Blvd, Suite 200 | FAX: (505) 881-3842 Albuquerque, NM 87110 | URL: http://www.khoral.com/ ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 15:39:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 6DCE337B91B for ; Mon, 8 May 2000 15:39:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA16259; Mon, 8 May 2000 15:48:43 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005082248.PAA16259@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: ddw@NSMA.Arizona.EDU Cc: freebsd-scsi@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 12:50:35 PDT." <200005081950.MAA16581@cortex.NSMA.Arizona.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 May 2000 15:48:43 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One list is probably enough. > I have a PC (550 MHZ P-III, Asus P3B-F, 256 MB) with two Adaptec 2940U2W > boards with six IBM DMVS36V 36GB drives. I also have a four gig internal > SCSI drive attached to the first 2940U2W to boot from. The goal is to use > vinum and create a RAID5 system... > > OK, I have installed FreeBSD 4.0 from the CD that I was shipped. I then > try to use disklabel to put a label onto the first 36GB drive, like so: > > disklabel -Brw da1 auto > > but the SCSI bus times out and then I'm hosed. > > I get the following messages: > > (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5d > (da1:ahc0:0:1:0) BDR message in message buffer > (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5e > (da1:ahc0:0:1:0) BDR message in message buffer > (da1:ahc0:0:1:0) no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 4 SCBs aborted Cabling or termination. Probably the latter, given that you're using both internal and external connectors, but it's also possible that you're using cabling that's just not up to LVD snuff. > If I try to reboot the computer at this (or any other) point, it freezes with > the following message: > > int=00000000 err=00000000 efl=00030246 eip=00001b54 > eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 > esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 > cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd > cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 > system halted When exactly do you get this message? It's typically indicative of your system being royally screwed (this is inside the Adaptec BIOS, by the looks of it). > to boot from a 3.4 CD. At this point, the only way I can do anything is to > reboot, hit ctrl-A to get into the Adaptec diagnostics and reformat the 36 GB > hard disk at that level. Then I can reboot and FreeBSD starts right up from > the internal hard disk where it was originally installed. You could probably just power-cycle the machine as well (depends on the actual nature of the problem, might have to do with the Adaptec BIOS trying to be smart). Formatting the disk is *definitely* the wrong thing to do. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Mon May 8 16:30:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C346937BD78; Mon, 8 May 2000 16:30:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA26862; Mon, 8 May 2000 16:29:21 -0700 Date: Mon, 8 May 2000 16:30:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: ddw@NSMA.Arizona.EDU, freebsd-scsi@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: <200005082248.PAA16259@mass.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 > > > > int=00000000 err=00000000 efl=00030246 eip=00001b54 > > eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 > > esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 > > cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd > > cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > > ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 > > system halted > > When exactly do you get this message? It's typically indicative of your > system being royally screwed (this is inside the Adaptec BIOS, by the > looks of it). I saw this recently when apparently something in the boot chain was broken. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 16:37:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 3BE3937B8FA for ; Mon, 8 May 2000 16:37:21 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA16487; Mon, 8 May 2000 16:46:16 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005082346.QAA16487@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 16:30:30 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 May 2000 16:46:16 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > > int=00000000 err=00000000 efl=00030246 eip=00001b54 > > > eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 > > > esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 > > > cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd > > > cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > > > ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 > > > system halted > > > > When exactly do you get this message? It's typically indicative of your > > system being royally screwed (this is inside the Adaptec BIOS, by the > > looks of it). > > I saw this recently when apparently something in the boot chain was broken. Lots of things can cause this; typically you'd just get a freeze or spontaneous reboot if BTX wasn't in the picture. In this case, the key incriminating evidence is the code segment; 0xd000 means that we're in the BIOS somewhere, probably an add-on BIOS ROM. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Mon May 8 17:16:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125]) by hub.freebsd.org (Postfix) with ESMTP id 4722C37B60C; Mon, 8 May 2000 17:16:39 -0700 (PDT) (envelope-from ddw@cortex.NSMA.Arizona.EDU) Received: from cortex (localhost [127.0.0.1]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id RAA19432; Mon, 8 May 2000 17:29:21 -0700 (MST) Message-Id: <200005090029.RAA19432@cortex.NSMA.Arizona.EDU> Reply-To: ddw@NSMA.Arizona.EDU X-Mailer: nmh - The "True to Unix" mail handler To: Mike Smith Cc: freebsd-scsi@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 15:48:43 MST." <200005082248.PAA16259@mass.cdrom.com> Date: Mon, 08 May 2000 17:29:20 -0700 From: Doug Wellington Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Previously: >Cabling or termination. Probably the latter, given that you're using >both internal and external connectors, but it's also possible that you're >using cabling that's just not up to LVD snuff. I'll check into this some more. I'm going to try putting a couple disks on the internal bus to see if that changes anything... >> int=00000000 err=00000000 efl=00030246 eip=00001b54 >> eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 >> esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 >> cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd >> cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff >> ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 >> system halted > >When exactly do you get this message? It's typically indicative of your >system being royally screwed (this is inside the Adaptec BIOS, by the >looks of it). This is at the point where FreeBSD should be taking over. The POST has completed, the Adaptec adapters have done their thing, the screen has cleared and I've seen a list of all the PCI devices. Then this thing happens. When I try to boot from the CD, there is actually a message about booting from the CD, then wham-o, this message pops up. >You could probably just power-cycle the machine as well (depends on the >actual nature of the problem, might have to do with the Adaptec BIOS >trying to be smart). Formatting the disk is *definitely* the wrong thing >to do. Well, I've done the ctrl-alt-del thing, the reset button on the front of the computer, AND killing the power and it ALWAYS gets stuck at that same point, until I use the adaptec bios to format the disk. (Well, or until I turn off the external case that contains that disk...) If it's the wrong thing, I'm definitely open to learning what the right thing is, 'cause it takes 35 minutes for the format. (I'm only messing with one disk at a time now - the first time I ran through this, I had to format all of them to get the system to boot...) :-( Thanks! -Doug -- Doug Wellington System and Network Administrator ddw@nsma.arizona.edu The University of Arizona, Tucson, AZ, USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 8 17:32:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id A357937BC90; Mon, 8 May 2000 17:32:20 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA16675; Mon, 8 May 2000 17:41:12 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005090041.RAA16675@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: ddw@NSMA.Arizona.EDU Cc: Mike Smith , freebsd-scsi@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 17:29:20 PDT." <200005090029.RAA19432@cortex.NSMA.Arizona.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 May 2000 17:41:12 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Previously: > >Cabling or termination. Probably the latter, given that you're using > >both internal and external connectors, but it's also possible that you're > >using cabling that's just not up to LVD snuff. > > I'll check into this some more. I'm going to try putting a couple disks > on the internal bus to see if that changes anything... Er, don't just wave dead chickens around. Examine your actual configuration and *check* it. > >> int=00000000 err=00000000 efl=00030246 eip=00001b54 > >> eax=00000000 ebx=00000386 ecx=00000000 edx=00000000 > >> esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382 > >> cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd > >> cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff > >> ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0 > >> system halted > > > >When exactly do you get this message? It's typically indicative of your > >system being royally screwed (this is inside the Adaptec BIOS, by the > >looks of it). > > This is at the point where FreeBSD should be taking over. The POST has > completed, the Adaptec adapters have done their thing, the screen has > cleared and I've seen a list of all the PCI devices. Then this thing > happens. When I try to boot from the CD, there is actually a message > about booting from the CD, then wham-o, this message pops up. I forgot to ask about the CDROM; is this an IDE or SCSI CDROM? If the latter, how is it connected? Is this a "new" 2940 with a separate LVD and non-LVD bus? If so, are all the disks on the LVD bus? At any rate, the trap you're getting above comes from BTX, and the offending code is somewhere in the BIOS; probably on a plug-in card. > If it's the wrong thing, I'm definitely open to learning what the right > thing is, 'cause it takes 35 minutes for the format. (I'm only messing > with one disk at a time now - the first time I ran through this, I had to > format all of them to get the system to boot...) :-( Boot on a system that doesn't have a broken BIOS and write zeroes over the first part of the disk. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Mon May 8 19: 9: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125]) by hub.freebsd.org (Postfix) with ESMTP id BBA1D37B884; Mon, 8 May 2000 19:08:57 -0700 (PDT) (envelope-from ddw@cortex.NSMA.Arizona.EDU) Received: from cortex (localhost [127.0.0.1]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id TAA20026; Mon, 8 May 2000 19:21:40 -0700 (MST) Message-Id: <200005090221.TAA20026@cortex.NSMA.Arizona.EDU> Reply-To: ddw@NSMA.Arizona.EDU X-Mailer: nmh - The "True to Unix" mail handler To: Mike Smith Cc: freebsd-scsi@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-reply-to: Your message of "Mon, 08 May 2000 17:41:12 MST." <200005090041.RAA16675@mass.cdrom.com> Date: Mon, 08 May 2000 19:21:39 -0700 From: Doug Wellington Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Previously: >Er, don't just wave dead chickens around. Examine your actual >configuration and *check* it. Heehee, I like that, dead chickens... I'm getting INTIMATELY acquanted with the entire actual configuration. I have unplugged and replugged everything at least once. I'm not sure I trust the cables, so I'm going to try to find some different ones. (Any suggestions for where and/or brand?) In the meantime, I have unplugged one of the drives and I'll plug it in with the internal cable to see what happens. (These users keep getting in my way and making me do other things around here!) >I forgot to ask about the CDROM; is this an IDE or SCSI CDROM? IDE. I'm thinking about getting an IDE drive to boot from. I'm not sure what that will gain me, as I even tried to configure everything with the internal 4GB on one of the adaptecs and an external case with three of the 36GB drives attached to the other adaptec. (Same result...) >Boot on a system that doesn't have a broken BIOS and write zeroes over >the first part of the disk. Got any spare systems? ;-) (Actually, I'll bring in my box from home...) Thanks again, -Doug -- Doug Wellington System and Network Administrator ddw@nsma.arizona.edu The University of Arizona, Tucson, AZ, USA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 7:42:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 49E9B37B5C1; Tue, 9 May 2000 07:42:38 -0700 (PDT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Tue, 9 May 2000 15:42:31 +0100 Received: from localhost (cmjg@localhost) by mail.ilrt.bris.ac.uk (8.8.7/8.8.8) with ESMTP id PAA09067; Tue, 9 May 2000 15:42:30 +0100 (BST) Date: Tue, 9 May 2000 15:42:30 +0100 (BST) From: Jan Grant To: Doug Wellington Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: <200005081950.MAA16581@cortex.NSMA.Arizona.EDU> 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, 8 May 2000, Doug Wellington wrote: > I have a PC (550 MHZ P-III, Asus P3B-F, 256 MB) with two Adaptec 2940U2W > boards with six IBM DMVS36V 36GB drives. I also have a four gig internal > SCSI drive attached to the first 2940U2W to boot from. The goal is to use > vinum and create a RAID5 system... ... > I get the following messages: > > (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5d > (da1:ahc0:0:1:0) BDR message in message buffer > (da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5e > (da1:ahc0:0:1:0) BDR message in message buffer > (da1:ahc0:0:1:0) no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 4 SCBs aborted ... > What gives? Anybody have any ideas? I'd look very closely at the physical setup: particularly termination. The Adaptec boards do autodetection for termination settings and suchlike; I've seen this cause trouble before. Drop into the Adaptec BIOS on boot using ^A and try setting the termination settings explicitly (internal and external) for both boards. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Unfortunately, I have a very good idea how fast my keys are moving. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 8: 6: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 0BAF337B618; Tue, 9 May 2000 08:06:03 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id LAA73368; Tue, 9 May 2000 11:04:46 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005091504.LAA73368@larryboy.graphics.cornell.edu> To: ddw@NSMA.Arizona.EDU Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: Message from Doug Wellington of "Mon, 08 May 2000 14:15:36 PDT." <200005082115.OAA17706@cortex.NSMA.Arizona.EDU> Date: Tue, 09 May 2000 11:04:46 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >[Drumming fingers] I'm wondering if it's the motherboard... Wish I had >another one to test. (I have tried different 2940U2W boards already.) I was just thumbing through the 2940u2w User's Reference Manual and found a few things worth taking a look at. Specifically: - The Troubleshooting Checklist on pages 4-5. - Common Error Messages on p. 9. Under "time-out failure during..." after verify termination and verify cable connections, the last choice says one of your peripherals may be defective. - Page 12 has a section on Installing Multiple SCSI Cards and how to set your BIOS settings correctly. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 8:12:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 2061A37B8E5; Tue, 9 May 2000 08:12:31 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id LAA73400; Tue, 9 May 2000 11:11:08 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005091511.LAA73400@larryboy.graphics.cornell.edu> To: Steve Jorgensen Cc: ddw@NSMA.Arizona.EDU, freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Problems with 36GB SCSI drives... In-Reply-To: Message from Steve Jorgensen of "Mon, 08 May 2000 16:37:29 MDT." <200005082237.QAA29923@benson> Date: Tue, 09 May 2000 11:11:07 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > You don't by chance have devices connected to both internal > connectors AND something connected to the external connector? > > I don't have a u2w, but my adaptec 2940uw says you can't > do that. The 2940u2w User's Reference manual, last diagram on page 26, indicates that it's ok to use all four connectors simultaneously. But if I understood Doug's setup right he has one internal disk on one controller and 6 external disks on the other controller, so he's not there yet. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 11:25:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.malawi.net (mail.malawi.net [208.148.169.7]) by hub.freebsd.org (Postfix) with ESMTP id 3EC8037BEB4 for ; Tue, 9 May 2000 11:25:31 -0700 (PDT) (envelope-from ganizani@malawi.net) Received: from two (two.malawi.net [208.148.169.2]) by mail.malawi.net (8.10.0/8.10.0) with SMTP id e49KPtw01925 for ; Tue, 9 May 2000 22:26:31 +0200 (CAT) Message-ID: <002701bfb9e3$f02dee80$02a994d0@malawi.net> From: "ganizani phiri" To: Subject: No Disks Found Date: Tue, 9 May 2000 20:24:46 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01BFB9F4.9E4A6E20" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0022_01BFB9F4.9E4A6E20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am installing FreeBsd on a Compaq Proliant Server which I want to use = as a=20 mail server for our domain. However after booting from the FreeBSD CD the setup does not find the = drives. The system has three 4.3-GB Wide-Ultra SCSI Disk Drives. However the NT used to see all Discs. Could you please assist on how this can be solved. Ganizani. ------=_NextPart_000_0022_01BFB9F4.9E4A6E20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am installing FreeBsd on a Compaq Proliant = Server which=20 I want to use as a
mail server for our domain.
However after booting from the FreeBSD CD the = setup does=20 not find the drives.
The system has three 4.3-GB Wide-Ultra SCSI = Disk=20 Drives.
 
However the NT used to see all = Discs.
 
Could you please assist on how this can be=20 solved.
 
 
Ganizani.
------=_NextPart_000_0022_01BFB9F4.9E4A6E20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 11:44: 0 2000 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 9AF8937B99E for ; Tue, 9 May 2000 11:43:57 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA07181; Tue, 9 May 2000 12:43:39 -0600 (MDT) (envelope-from ken) Date: Tue, 9 May 2000 12:43:39 -0600 From: "Kenneth D. Merry" To: ganizani phiri Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: No Disks Found Message-ID: <20000509124339.A7163@panzer.kdm.org> References: <002701bfb9e3$f02dee80$02a994d0@malawi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <002701bfb9e3$f02dee80$02a994d0@malawi.net>; from ganizani@malawi.net on Tue, May 09, 2000 at 08:24:46PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 09, 2000 at 20:24:46 +0200, ganizani phiri wrote: > I am installing FreeBsd on a Compaq Proliant Server which I want to use as a > mail server for our domain. > However after booting from the FreeBSD CD the setup does not find the drives. > The system has three 4.3-GB Wide-Ultra SCSI Disk Drives. > > However the NT used to see all Discs. > > Could you please assist on how this can be solved. What version of FreeBSD are you using? What make/model is the SCSI controller in the machine? My guess is that the SCSI controller in that box isn't supported in the version of FreeBSD that you're using. I would suggest trying FreeBSD 4.0, if you aren't using that already. 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 May 9 13: 0:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from UCONNVM.UConn.Edu (uconnvm.uconn.edu [137.99.26.3]) by hub.freebsd.org (Postfix) with SMTP id 9373037C2A8 for ; Tue, 9 May 2000 12:50:40 -0700 (PDT) (envelope-from ATHOMAS@UCONNVM.UCONN.EDU) Received: by UCONNVM.UConn.Edu (IBM VM SMTP V2R4a) via spool with SMTP id 1312 ; Tue, 09 May 2000 15:50:32 EDT Received: from UConnVM.UConn.Edu (NJE origin ATHOMAS@UCONNVM) by UCONNVM.UCONN.EDU (LMail V1.2d/1.8d) with BSMTP id 4250; Tue, 9 May 2000 15:50:32 -0400 Date: Tue, 09 May 00 15:49:11 EDT From: ATHOMAS@UCONNVM.UConn.Edu Subject: Looking for information of tagged command queueing To: scsi@freebsd.org X-Mailer: MailBook 98.01.000 Message-Id: <000509.155032.EDT.ATHOMAS@UConnVM.UConn.Edu> 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 PS I would appreciate receiveing the names of articles, web pages, and books on relevant info I will ask more detailed questions afterwards Alex Thomasian, Prof. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 13:17:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 6009137C0A6 for ; Tue, 9 May 2000 13:13:50 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id OAA08705 for ; Tue, 9 May 2000 14:13:51 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <200005092013.OAA08705@caspian.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: scsi@FreeBSD.org Subject: Aic7xxx U160 support (and other CAM improvements). Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 May 2000 14:13:51 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For those of you interested in testing U160 support as well as some performance enhancements in the aic7xxx driver, check out the patches here: http://people.FreeBSD.org/~gibbs/cam_aic7xxx_u160.diffs You will also need to copy src/lib/libc/stdlib/bsearch.c to sys/libkern in order for the patches to work. Here's a run down of what is included: o U160 support for the aic7892/aic7899 chips and controllers based on them. o Embedded CDB support for cdbs up to 12 bytes in length on all controllers. In the past, all controllers other than those in the 789X series performed a separate dma for transaction information and the cdb. o Better use of chips with two DMA engines. We now use the secondary DMA channel to pull in S/G blocks in advance of the DMA engine running dry. o Full support for "Bayonet" style DMA. In addition to using the secondary DMA channel, we take advantage of the in chip S/G element FIFO so that the DMA engine does not have to wait on the sequencer engine to load the next S/G segment when one completes. This applies to all aic789X chips other than the aic7895. There are also a bunch of CAM changes in the patches. The CAM changes include some cleanup of the error recovery code as well as some enhancements to the get/set transfer settings API. So why aren't these in the tree? For one thing, the CAM API changes, once reviewed, will require all SIM drivers to undergo some changes. These patches only include support for the aic7xxx driver. It is also unclear that what I have here will be the "final" API for this CCB type. During 5.0, it is expected that the CAM API will change considerably. The intent is to push these API changes onto a "CAM branch" until they have stabilized and then have only a single integration phase for 5.0. One of my goals for CAM in 5.0 is to have a rich API that third party vendors can write to without the fear that the API will change in the near future. This will require a lot of experimentation and development work to achieve. I'll be posting another message about CAM goals in 5.0 that proposes a road map for CAM and I hope the rest of the readers of -scsi will help me refine it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 14:34:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lvcablemodem.com (hams3.lvcablemodem.com [24.234.0.77]) by hub.freebsd.org (Postfix) with ESMTP id 13DCC37BFA9; Tue, 9 May 2000 14:34:31 -0700 (PDT) (envelope-from slumos@nevada.edu) Received: from localhost ([24.234.19.246]) by lvcablemodem.com with Microsoft SMTPSVC(5.5.1877.387.38); Tue, 9 May 2000 14:32:56 -0700 From: slumos@nevada.edu To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Status of Ultra160 SCSI support? Date: Tue, 09 May 2000 14:31:45 -0700 Message-ID: <031845632210950HAMS3@lvcablemodem.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. In search for information on Ultra160 support in FreeBSD, I saw a couple references in the mail-list archives saying it was or would be supported in 4.0, but it isn't listed in the 4.0 release notes. Can anyone tell me when it is expected to be in a -RELEASE version? Thanks in advance. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 14:37: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DFF1537BF60; Tue, 9 May 2000 14:36:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA30891; Tue, 9 May 2000 14:35:23 -0700 Date: Tue, 9 May 2000 14:36:39 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: slumos@nevada.edu Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? In-Reply-To: <031845632210950HAMS3@lvcablemodem.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 There is U160 support in that the Qlogic 12160 cards are supported as of FreeBSD 4.0. On Tue, 9 May 2000 slumos@nevada.edu wrote: > > Hi. > > In search for information on Ultra160 support in FreeBSD, I saw a > couple references in the mail-list archives saying it was or would > be supported in 4.0, but it isn't listed in the 4.0 release notes. > Can anyone tell me when it is expected to be in a -RELEASE version? > > Thanks in advance. > > Steve > > > 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 May 9 15: 4:26 2000 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 ED2D637B50B; Tue, 9 May 2000 15:03:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA08676; Tue, 9 May 2000 16:03:39 -0600 (MDT) (envelope-from ken) Date: Tue, 9 May 2000 16:03:39 -0600 From: "Kenneth D. Merry" To: slumos@nevada.edu Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? Message-ID: <20000509160339.A8627@panzer.kdm.org> References: <031845632210950HAMS3@lvcablemodem.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <031845632210950HAMS3@lvcablemodem.com>; from slumos@nevada.edu on Tue, May 09, 2000 at 02:31:45PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 09, 2000 at 14:31:45 -0700, slumos@nevada.edu wrote: > > Hi. > > In search for information on Ultra160 support in FreeBSD, I saw a > couple references in the mail-list archives saying it was or would > be supported in 4.0, but it isn't listed in the 4.0 release notes. > Can anyone tell me when it is expected to be in a -RELEASE version? As Matt already noted, 4.0 shipped with support for the QLogic Ultra160 boards. Symbios C1010 Ultra160 boards are also supported in 4.0. The Adaptec Ultra160 boards (based on the 7892 and 7899) are supported in 4.0, but they only run at 80MB/sec, i.e. Ultra2 speeds, not at 160MB/sec. If you want the Adaptec chips to run at 160MB/sec, you need the patches Justin referred to in his mail to the -scsi list today. 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 May 9 15:23:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from larryboy.graphics.cornell.edu (larryboy.graphics.cornell.edu [128.84.247.48]) by hub.freebsd.org (Postfix) with ESMTP id 52E5A37BD71; Tue, 9 May 2000 15:23:24 -0700 (PDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Received: from larryboy.graphics.cornell.edu (mkc@localhost) by larryboy.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id SAA75925; Tue, 9 May 2000 18:23:18 -0400 (EDT) (envelope-from mkc@larryboy.graphics.cornell.edu) Message-Id: <200005092223.SAA75925@larryboy.graphics.cornell.edu> To: "Kenneth D. Merry" Cc: slumos@nevada.edu, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? In-Reply-To: Message from "Kenneth D. Merry" of "Tue, 09 May 2000 16:03:39 MDT." <20000509160339.A8627@panzer.kdm.org> Date: Tue, 09 May 2000 18:23:18 -0400 From: Mitch Collinsworth Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >The Adaptec Ultra160 boards (based on the 7892 and 7899) are supported in >4.0, but they only run at 80MB/sec, i.e. Ultra2 speeds, not at 160MB/sec. > >If you want the Adaptec chips to run at 160MB/sec, you need the patches >Justin referred to in his mail to the -scsi list today. I distinctly remember someone saying the same thing about 3.4-R a while back, and that 4.0-R would have the 160MB/s support. -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 15:30:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front3.grolier.fr (front3.grolier.fr [194.158.96.53]) by hub.freebsd.org (Postfix) with ESMTP id 51D2237BE3A; Tue, 9 May 2000 15:30:44 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from ppp-173-66.villette.club-internet.fr (ppp-173-66.villette.club-internet.fr [195.36.173.66]) by front3.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id AAA28572; Wed, 10 May 2000 00:30:31 +0200 (MET DST) Date: Wed, 10 May 2000 00:05:44 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Matthew Jacob Cc: slumos@nevada.edu, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? 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 Tue, 9 May 2000, Matthew Jacob wrote: > There is U160 support in that the Qlogic 12160 cards are supported as of > FreeBSD 4.0. U160 support for the Symbios C1010 controller is also available in 4.0, as you know, Matt. ;) Gerard. > On Tue, 9 May 2000 slumos@nevada.edu wrote: > > > > > Hi. > > > > In search for information on Ultra160 support in FreeBSD, I saw a > > couple references in the mail-list archives saying it was or would > > be supported in 4.0, but it isn't listed in the 4.0 release notes. > > Can anyone tell me when it is expected to be in a -RELEASE version? > > > > Thanks in advance. > > > > Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 9 16: 9:51 2000 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 9137537BA63; Tue, 9 May 2000 16:09:43 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA09158; Tue, 9 May 2000 17:09:37 -0600 (MDT) (envelope-from ken) Date: Tue, 9 May 2000 17:09:37 -0600 From: "Kenneth D. Merry" To: Mitch Collinsworth Cc: slumos@nevada.edu, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? Message-ID: <20000509170937.B9102@panzer.kdm.org> References: <200005092223.SAA75925@larryboy.graphics.cornell.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200005092223.SAA75925@larryboy.graphics.cornell.edu>; from mkc@Graphics.Cornell.EDU on Tue, May 09, 2000 at 06:23:18PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 09, 2000 at 18:23:18 -0400, Mitch Collinsworth wrote: > >The Adaptec Ultra160 boards (based on the 7892 and 7899) are supported in > >4.0, but they only run at 80MB/sec, i.e. Ultra2 speeds, not at 160MB/sec. > > > >If you want the Adaptec chips to run at 160MB/sec, you need the patches > >Justin referred to in his mail to the -scsi list today. > > I distinctly remember someone saying the same thing about 3.4-R a > while back, and that 4.0-R would have the 160MB/s support. I dunno who said what, but the reality is that 3.4 doesn't support the 7892 or the 7899, and 4.0 does support those chips, but only at 80MB/sec. If you want 160MB/sec with released code, you'll need to go with 4.0 and either Symbios or QLogic chips. 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 May 9 16:28:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4915137B5D2; Tue, 9 May 2000 16:28:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA31167; Tue, 9 May 2000 16:26:40 -0700 Date: Tue, 9 May 2000 16:27:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: slumos@nevada.edu, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Status of Ultra160 SCSI support? 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 Tue, 9 May 2000, Matthew Jacob wrote: > > > There is U160 support in that the Qlogic 12160 cards are supported as of > > FreeBSD 4.0. > > U160 support for the Symbios C1010 controller is also available in 4.0, as > you know, Matt. ;) Yeah, sorry, but because I couldn't verify it with *my* LSI Logic h/w (you know, rev 0 C1010 chips that require specific phase matching for DT cycles), I wasn't going to say..... Whereas I *do* know it works for my Qlogic 12160 cards :-) .... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 10 11:32:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.sullivan-reportlibrary.com (chrtn1UBR2-3-hfc-0252-d8d8b012.rdc1.tn.comcastatwork.com [216.216.176.18]) by hub.freebsd.org (Postfix) with ESMTP id 01D8537BA66 for ; Wed, 10 May 2000 11:32:28 -0700 (PDT) (envelope-from marketing@infotechsys.net) Received: from infotechsys.net (2K-SERVER [192.168.0.100]) by mail.sullivan-reportlibrary.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id KTQY5PJN; Wed, 10 May 2000 14:29:13 -0400 MIME-Version: 1.0 From: marketing@infotechsys.net Reply-To: marketing@infotechsys.net To: scsi@freebsd.org Subject: ITS Brochure Mime-Version: 1.0 Content-Type: text/html; charset="us-ascii" Message-Id: <20000510183228.01D8537BA66@hub.freebsd.org> Date: Wed, 10 May 2000 11:32:28 -0700 (PDT) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ITS Internet Site

P.O. Box 70671

Charleston, SC 29415-0671

843.566.1397


To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 10 12:19:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from vidar.erilab.com (vidar.erilab.com [208.224.156.104]) by hub.freebsd.org (Postfix) with ESMTP id CA8A537B749 for ; Wed, 10 May 2000 12:19:49 -0700 (PDT) (envelope-from rainer@erilab.com) Received: from erilab.com (rainer.erilab.com [192.168.174.43]) by vidar.erilab.com (8.9.3/8.9.3) with ESMTP id MAA21680; Wed, 10 May 2000 12:19:10 -0700 (PDT) Message-ID: <394118A6.7B7C2FAE@erilab.com> Date: Fri, 09 Jun 2000 12:17:42 -0400 From: Rainer Enders Reply-To: rainer@erilab.com Organization: Ericsson Radio X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Rainer Enders , freebsd-scsi@FreeBSD.ORG Subject: Re: Which RAID controllers? References: <199812012045.NAA21624@panzer.plutotech.com> Content-Type: multipart/mixed; boundary="------------94E6CB0B7EDCAB97B79564BC" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------94E6CB0B7EDCAB97B79564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, what are the current choices for RAID controllers? Are there any of the new boards supported in the 4.0 Release? I checked in the Release Notes and it doesn't seem so. It's strange that a good Server Operating System does not have good support for the newer RAID hardware. On the DPT website it says for the FreeBSD driver "Coming Soon" whatever that means. Which one would be the best choice of RAID controller for FreeBSD today? When will SmartRAID V and VI supported? Regards, Rainer. "Kenneth D. Merry" wrote: > Rainer Enders wrote... > > Which RAID Controllers work best with > > FreeBSD 2.2.7/2.2.8? > > > > Any different answer for 3.0? > > For 2.2.7/2.2.8, or 3.0, your choices are: > > - DPT, if you want an internal RAID controller > - Any external SCSI-SCSI RAID controller. > > > I would like to use either Mylex or DPT if at > > all possible. > > DPT cards are supported. The Mylex internal RAID controllers are > not supported, but their SCSI-SCSI controllers should work fine with a > supported SCSI controller. > > Ken > -- > Kenneth Merry > ken@plutotech.com --------------94E6CB0B7EDCAB97B79564BC Content-Type: text/x-vcard; charset=us-ascii; name="rainer.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Rainer Enders Content-Disposition: attachment; filename="rainer.vcf" begin:vcard n:Enders;Rainer tel;cell:+1.415.244.1937 tel;home:+1.925.979.9591 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:rainer@erilab.com fn:Rainer Enders end:vcard --------------94E6CB0B7EDCAB97B79564BC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 10 12:22:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 8BAEB37B92F for ; Wed, 10 May 2000 12:22:42 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA42874; Wed, 10 May 2000 12:22:51 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005101922.MAA42874@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: rainer@erilab.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Which RAID controllers? In-reply-to: Your message of "Fri, 09 Jun 2000 12:17:42 EDT." <394118A6.7B7C2FAE@erilab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 May 2000 12:22:51 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org http://people.freebsd.org/~msmith/RAID > what are the current choices for RAID controllers? > Are there any of the new boards supported in the 4.0 Release? > I checked in the Release Notes and it doesn't seem so. > It's strange that a good Server Operating System does not > have good support for the newer RAID hardware. > On the DPT website it says for the FreeBSD driver > "Coming Soon" whatever that means. > > Which one would be the best choice of RAID controller > for FreeBSD today? When will SmartRAID V and VI > supported? > > Regards, > Rainer. > > "Kenneth D. Merry" wrote: > > > Rainer Enders wrote... > > > Which RAID Controllers work best with > > > FreeBSD 2.2.7/2.2.8? > > > > > > Any different answer for 3.0? > > > > For 2.2.7/2.2.8, or 3.0, your choices are: > > > > - DPT, if you want an internal RAID controller > > - Any external SCSI-SCSI RAID controller. > > > > > I would like to use either Mylex or DPT if at > > > all possible. > > > > DPT cards are supported. The Mylex internal RAID controllers are > > not supported, but their SCSI-SCSI controllers should work fine with a > > supported SCSI controller. > > > > Ken > > -- > > Kenneth Merry > > ken@plutotech.com > > begin:vcard > n:Enders;Rainer > tel;cell:+1.415.244.1937 > tel;home:+1.925.979.9591 > x-mozilla-html:FALSE > adr:;;;;;; > version:2.1 > email;internet:rainer@erilab.com > fn:Rainer Enders > end:vcard > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Wed May 10 12:23: 7 2000 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 E1B3F37B9C5 for ; Wed, 10 May 2000 12:23:04 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 0FE059B1D; Wed, 10 May 2000 15:23:04 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 05807BA0F; Wed, 10 May 2000 15:23:04 -0400 (EDT) Date: Wed, 10 May 2000 15:23:03 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Rainer Enders Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Which RAID controllers? In-Reply-To: <394118A6.7B7C2FAE@erilab.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 Fri, 9 Jun 2000, Rainer Enders wrote: > Hello, > > what are the current choices for RAID controllers? > Are there any of the new boards supported in the 4.0 Release? > I checked in the Release Notes and it doesn't seem so. > It's strange that a good Server Operating System does not > have good support for the newer RAID hardware. > On the DPT website it says for the FreeBSD driver > "Coming Soon" whatever that means. > Either search the mailing lists, see LINT, or see http://people.freebsd.org/~msmith/RAID/ for more info. > Which one would be the best choice of RAID controller > for FreeBSD today? When will SmartRAID V and VI > supported? > ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - 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 May 10 14:38:44 2000 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 39F5737B996 for ; Wed, 10 May 2000 14:38:41 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA28415; Wed, 10 May 2000 15:38:33 -0600 (MDT) (envelope-from ken) Date: Wed, 10 May 2000 15:38:33 -0600 From: "Kenneth D. Merry" To: Rainer Enders Cc: Rainer Enders , freebsd-scsi@FreeBSD.ORG Subject: Re: Which RAID controllers? Message-ID: <20000510153833.A28378@panzer.kdm.org> References: <199812012045.NAA21624@panzer.plutotech.com> <394118A6.7B7C2FAE@erilab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <394118A6.7B7C2FAE@erilab.com>; from rainer@erilab.com on Fri, Jun 09, 2000 at 12:17:42PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 09, 2000 at 12:17:42 -0400, Rainer Enders wrote: > Hello, > > what are the current choices for RAID controllers? > Are there any of the new boards supported in the 4.0 Release? > I checked in the Release Notes and it doesn't seem so. > It's strange that a good Server Operating System does not > have good support for the newer RAID hardware. > On the DPT website it says for the FreeBSD driver > "Coming Soon" whatever that means. > > Which one would be the best choice of RAID controller > for FreeBSD today? When will SmartRAID V and VI > supported? The internal RAID controllers from Mylex and AMI are supported in 4.0. Not every model is supported, however. Compaq SmartArray controllers are supported as well, and Mike Smith has a beta driver for 3ware RAID controllers. See: http://people.freebsd.org/~msmith/RAID/index.html For a better synopsis of what is available. If you've got questions about the Mylex, AMI or 3ware support, mail Mike Smith . Simon Shapiro has written an I2O layer for FreeBSD that supports (I think) the SmartRAID V and maybe the VI as well. Contact him for details on that. 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 May 11 2:37:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.malawi.net (mail.malawi.net [208.148.169.7]) by hub.freebsd.org (Postfix) with ESMTP id E6E7937B521 for ; Thu, 11 May 2000 02:37:23 -0700 (PDT) (envelope-from ganizani@malawi.net) Received: from one (one.malawi.net [208.148.169.10]) by mail.malawi.net (8.10.0/8.10.0) with SMTP id e4BBabj09422; Thu, 11 May 2000 13:36:49 +0200 (CAT) Message-ID: <003101bfbb23$ddc18540$0aa994d0@one.malawi.net> From: "Ganizani Phiri" To: Cc: Subject: Can't FreeBSD4.0 Date: Thu, 11 May 2000 11:35:00 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002C_01BFBB3C.F132BF90" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_002C_01BFBB3C.F132BF90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable dear Thank you for your help. I have downloaded FreeBSD4.0 and have installed = it on our mail server. However I am still finding problems. FreeBSD can't boot. This is the = boot message. 'Loading /boot/defaults/loader.conf unable to load kernel Aborted! Can you please help me figure out what could be the cause of this. Or how do i get a boot floppy Ganizani ------=_NextPart_000_002C_01BFBB3C.F132BF90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
dear

Thank you for your help. I have downloaded FreeBSD4.0 = and have=20 installed it
on our mail server.

However I am still finding = problems.=20 FreeBSD can't boot. This is the boot
message.

'Loading=20 /boot/defaults/loader.conf
unable to load = kernel
Aborted!

Can you=20 please help me figure out what could be the cause of
this.
Or how = do i get=20 a boot floppy

Ganizani <ganizani@malawi.net>

------=_NextPart_000_002C_01BFBB3C.F132BF90-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 11 14:15: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AB22637B7DB; Thu, 11 May 2000 14:15:00 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA09045; Thu, 11 May 2000 17:14:59 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA87117; Thu, 11 May 2000 17:14:59 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 11 May 2000 17:14:59 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Aic7xxx U160 support (and other CAM improvements). In-Reply-To: <200005092013.OAA08705@caspian.plutotech.com> References: <200005092013.OAA08705@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14619.8277.992062.384988@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > For those of you interested in testing U160 support as well as > some performance enhancements in the aic7xxx driver, check out > the patches here: > > http://people.FreeBSD.org/~gibbs/cam_aic7xxx_u160.diffs > > You will also need to copy src/lib/libc/stdlib/bsearch.c to sys/libkern > in order for the patches to work. > Justin, I just tried to build a kernel with these patches. We seem to be missing aicasm_insformat.h <5:03pm>sausage/gallatin:GENERIC>make -m ../../../share/mk depend make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /usr/project/ari_scratch2/gallatin/sys5/src/sys/compile/GENERIC cc -O -pipe -I/usr/include -I. -c aicasm_gram.c ../../dev/aic7xxx/aicasm_gram.y:42: aicasm_insformat.h: No such file or directory ../../dev/aic7xxx/aicasm_gram.y: In function `format_1_instr': <...> Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 11 14:20:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id D40DD37BBCF; Thu, 11 May 2000 14:20:33 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id PAA28124; Thu, 11 May 2000 15:20:37 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <200005112120.PAA28124@caspian.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Aic7xxx U160 support (and other CAM improvements). In-Reply-To: Your message of "Thu, 11 May 2000 17:14:59 EDT." <14619.8277.992062.384988@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 May 2000 15:20:37 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Justin, > >I just tried to build a kernel with these patches. We seem to be >missing aicasm_insformat.h http://people.FreeBSD.org/~gibbs/aicasm_insformat.h -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 13 23:23:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from imap4.CS.Berkeley.EDU (imap4.CS.Berkeley.EDU [169.229.60.23]) by hub.freebsd.org (Postfix) with ESMTP id C723837BCBB for ; Sat, 13 May 2000 23:23:52 -0700 (PDT) (envelope-from stamos@cs.berkeley.edu) Received: from cs.berkeley.edu (ishmael-169-229-102.Reshall.Berkeley.EDU [169.229.102.254]) by imap4.CS.Berkeley.EDU (Netscape Messaging Server 4.15) with ESMTP id FUJDRQ00.U4B for ; Sat, 13 May 2000 23:23:50 -0700 Message-ID: <391E4679.3F59CDFB@cs.berkeley.edu> Date: Sat, 13 May 2000 23:23:54 -0700 From: Alex Stamos Organization: UC Berkeley Computer Science Department X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: T10 drafts versus ANSI standards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am currently working on a software SCSI emulator for FreeBSD. I was wondering if anybody knows if there's any signifigant differences between the T10 groups final working drafts, which are free on their web site, and the final ANSI standards, which cost upwards of $100 a pop. Thanks, Alex -- **************************************** Alex Stamos stamos@cs.berkeley.edu ISTORE Project UC Berkeley CS Department GO BEARS! **************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 13 23:41:33 2000 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 C3CB337BD3C for ; Sat, 13 May 2000 23:41:30 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA57537; Sun, 14 May 2000 00:41:12 -0600 (MDT) (envelope-from ken) Date: Sun, 14 May 2000 00:41:12 -0600 From: "Kenneth D. Merry" To: Alex Stamos Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: T10 drafts versus ANSI standards Message-ID: <20000514004112.A54445@panzer.kdm.org> References: <391E4679.3F59CDFB@cs.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <391E4679.3F59CDFB@cs.berkeley.edu>; from stamos@cs.berkeley.edu on Sat, May 13, 2000 at 11:23:54PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, May 13, 2000 at 23:23:54 -0700, Alex Stamos wrote: > I am currently working on a software SCSI emulator for FreeBSD. I > was wondering if anybody knows if there's any signifigant differences > between the T10 groups final working drafts, which are free on their web > site, and the final ANSI standards, which cost upwards of $100 a pop. I think they're pretty close, but you'd have to ask someone who has actually compared the drafts to the standards to be sure. :) FWIW, we have used the drafts for the CAM development, and I don't think we've run into any issues caused by a draft/standard difference. What sort of emulator are you working on? Is this a SCSI target emulator, i.e. something that is supposed to act like a disk or a tape drive? Or is this some other sort of emulator? A well written disk emulator (or tape emulator) could be a valuable contribution to FreeBSD. You could use a disk emulator to do things like form the basis of a FreeBSD-hosted software RAID array, or to test 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 Sat May 13 23:54: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from imap4.CS.Berkeley.EDU (imap4.CS.Berkeley.EDU [169.229.60.23]) by hub.freebsd.org (Postfix) with ESMTP id B446C37BD40 for ; Sat, 13 May 2000 23:54:07 -0700 (PDT) (envelope-from stamos@cs.berkeley.edu) Received: from cs.berkeley.edu (ishmael-169-229-102.Reshall.Berkeley.EDU [169.229.102.254]) by imap4.CS.Berkeley.EDU (Netscape Messaging Server 4.15) with ESMTP id FUJF6600.U4E for ; Sat, 13 May 2000 23:54:06 -0700 Message-ID: <391E4D91.8C9BB7CD@cs.berkeley.edu> Date: Sat, 13 May 2000 23:54:10 -0700 From: Alex Stamos Organization: UC Berkeley Computer Science Department X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Re: T10 drafts versus ANSI standards References: <391E4679.3F59CDFB@cs.berkeley.edu> <20000514004112.A54445@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 > FWIW, we have used the drafts for the CAM development, and I don't think > we've run into any issues caused by a draft/standard difference. > > What sort of emulator are you working on? Is this a SCSI target emulator, > i.e. something that is supposed to act like a disk or a tape drive? Or is > this some other sort of emulator? A SCSI-3 target mode disk emulator. Our group is aiming to build an extremely reliable 80-node cluster. Unfortunately, its difficult to test the fault-tolerance of our SCSI adapters or drivers when the only things you can do to a scsi drive to inject faults is to unplug it or shake it :) The group already owns a commercial product that runs under NT, but the process of interjecting faults crashes the NT system that pretending to be the drive! I hope to fix up some of the target mode code in the Adaptec 71xxx driver, and then make a user mode SCSI parser with either a command line or GUI (if I have time) interface that allows me to inject repeatable faults. My intention is to open the code and invite other people to contribute, but I'll have to cross that bridge when I get to it (all the IP belongs to UC Berkeley, not the lowly undergrad that writes it). Justin Gibbs has already been very helpful. If anybody else has suggestions, please PLEASE let me know. I can use all the help I can get. Thanks, guys. -Alex -- **************************************** Alex Stamos stamos@cs.berkeley.edu ISTORE Project UC Berkeley CS Department GO BEARS! **************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message