From owner-freebsd-scsi Sun Dec 10 11:13:43 2000 From owner-freebsd-scsi@FreeBSD.ORG Sun Dec 10 11:13:41 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.arsconcero.com (elvis2.intrepid.net [209.190.164.164]) by hub.freebsd.org (Postfix) with SMTP id F14BA37B401 for ; Sun, 10 Dec 2000 11:13:40 -0800 (PST) Received: (qmail 581 invoked by uid 1000); 10 Dec 2000 19:13:35 -0000 Date: Sun, 10 Dec 2000 14:13:34 -0500 From: Mark Conway Wirt To: freebsd-scsi@freebsd.org Subject: Problems with Adadptec 7880 Message-ID: <20001210141334.A443@ArsConcero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: mark@mail.arsconcero.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had an IBM PC Server 325 providing some networking services. It worked well, but eventually died. It sat inert for a while, but I recently purchased another one. "Great," I though -- I'll just take the disks and the memory and put them into the new server, and everything should work. Unfortunately, the new machine will not boot. Everything looks good until it waits for the "SCSI devices to settle." At that point, the machine never comes back (It has to be cold booted). It's the same machine that worked perviously, with an AIC 7880 card (firware V1.25). I've verbosely booted it, but I'm not sure if that gives me any information. After the line about waiting for devices to settle, I get the message (noperiph:ahc0:0:-1:-1) SCSI bus reset delivered. 0 SCBs aborted. then nothing. If additional information would help, I can see if I can kludge a serial cable together to capture the boot sequence. I'm running 4.0-STABLE on the box, but I've tried to boot with the 4.2-RELEASE floppies, and I've observed the same behavior. Any insights would be appreciated! --Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 10:46:11 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 10:46:09 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id E0E5137B400 for ; Mon, 11 Dec 2000 10:46:08 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id D594BDC74; Mon, 11 Dec 2000 13:44:32 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id CAE57D93D for ; Mon, 11 Dec 2000 13:44:32 -0500 (EST) Date: Mon, 11 Dec 2000 13:44:32 -0500 (EST) From: David Miller To: freebsd-scsi@freebsd.org Subject: LUN 1 on 3.2-R? 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 Hi All:) I'm stumped. I have a 3.2R system with an attached external SCSI-SCSI RAID controller. I had a nice 10 drive array last year with 36 GB drives, and this year I'm adding on another nice array. I have this in my config file: # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) # device da0 # Direct Access (disks) disk da0 at scbus0 target 2 unit 0 disk da1 at scbus0 target 2 unit 1 device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI) But in dmesg I get: Waiting 5 seconds for SCSI devices to settle pass1 at ahc0 bus 0 target 2 lun 1 pass1: Fixed Processor SCSI-2 device pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 2 pass2: Fixed Processor SCSI-2 device pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 279097MB (571591680 512 byte sectors: 255H 63S/T 35579C) changing root device to wd0s1a camcontrol devlist: su-2.03# camcontrol devlist at scbus0 target 2 lun 0 (pass0,da0) at scbus0 target 2 lun 1 (pass1) at scbus0 target 2 lun 2 (pass2) The associated da* and pass* devices seem to exist. What am I missing? Thanks in advance, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 10:48:58 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 10:48:55 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 807F637B400 for ; Mon, 11 Dec 2000 10:48:54 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA12530; Mon, 11 Dec 2000 10:48:48 -0800 Date: Mon, 11 Dec 2000 10:48:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: David Miller Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? 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 The pass2 devices is SES (try 4.X or later for this). The pass1 device is also reporting itself as a PROCESSOR type device- not a direct access. Again, try 4.X. 3.2 is pretty damned old. > Hi All:) > > I'm stumped. I have a 3.2R system with an attached external SCSI-SCSI > RAID controller. I had a nice 10 drive array last year with 36 GB drives, > and this year I'm adding on another nice array. > > I have this in my config file: > > # SCSI peripherals > # Only one of each of these is needed, they are dynamically allocated. > controller scbus0 # SCSI bus (required) > # device da0 # Direct Access (disks) > disk da0 at scbus0 target 2 unit 0 > disk da1 at scbus0 target 2 unit 1 > device sa0 # Sequential Access (tape etc) > device cd0 # CD > device pass0 # Passthrough device (direct SCSI) > > > But in dmesg I get: > > Waiting 5 seconds for SCSI devices to settle > pass1 at ahc0 bus 0 target 2 lun 1 > pass1: Fixed Processor SCSI-2 device > pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged > Queueing Enabled > pass2 at ahc0 bus 0 target 2 lun 2 > pass2: Fixed Processor SCSI-2 device > pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) > da0 at ahc0 bus 0 target 2 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing > Enabled > da0: 279097MB (571591680 512 byte sectors: 255H 63S/T 35579C) > changing root device to wd0s1a > > > camcontrol devlist: > > su-2.03# camcontrol devlist > at scbus0 target 2 lun 0 (pass0,da0) > at scbus0 target 2 lun 1 (pass1) > at scbus0 target 2 lun 2 (pass2) > > > The associated da* and pass* devices seem to exist. > > What am I missing? > > Thanks in advance, > > --- David > > > > 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 Dec 11 11: 0:54 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:00:48 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 6568337B6A0 for ; Mon, 11 Dec 2000 11:00:26 -0800 (PST) Received: from shell-1.enteract.com (presence@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA35916; Mon, 11 Dec 2000 13:00:19 -0600 (CST) (envelope-from presence@churchofinformationwarfare.org) Date: Mon, 11 Dec 2000 13:00:18 -0600 (CST) From: Reverend K Kanno X-Sender: presence@shell-1.enteract.com To: David Miller Cc: freebsd-scsi@freebsd.org Subject: Re: LUN 1 on 3.2-R? 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 Mon, 11 Dec 2000, David Miller wrote: What SCSI HA are you using? It seems lots of HAs dont' properly support LUNs. For instance, I have yet to see an onboard Adaptec Dell SCSI HA that works with an Infortrend or Chapparal controller. > Hi All:) > > I'm stumped. I have a 3.2R system with an attached external SCSI-SCSI > RAID controller. I had a nice 10 drive array last year with 36 GB drives, > and this year I'm adding on another nice array. > > I have this in my config file: > > # SCSI peripherals > # Only one of each of these is needed, they are dynamically allocated. > controller scbus0 # SCSI bus (required) > # device da0 # Direct Access (disks) > disk da0 at scbus0 target 2 unit 0 > disk da1 at scbus0 target 2 unit 1 > device sa0 # Sequential Access (tape etc) > device cd0 # CD > device pass0 # Passthrough device (direct SCSI) > > > But in dmesg I get: > > Waiting 5 seconds for SCSI devices to settle > pass1 at ahc0 bus 0 target 2 lun 1 > pass1: Fixed Processor SCSI-2 device > pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged > Queueing Enabled > pass2 at ahc0 bus 0 target 2 lun 2 > pass2: Fixed Processor SCSI-2 device > pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) > da0 at ahc0 bus 0 target 2 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing > Enabled > da0: 279097MB (571591680 512 byte sectors: 255H 63S/T 35579C) > changing root device to wd0s1a > > > camcontrol devlist: > > su-2.03# camcontrol devlist > at scbus0 target 2 lun 0 (pass0,da0) > at scbus0 target 2 lun 1 (pass1) > at scbus0 target 2 lun 2 (pass2) > > > The associated da* and pass* devices seem to exist. > > What am I missing? > > Thanks in advance, > > --- David > > > > 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 Dec 11 11:14: 5 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:14:02 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 687A037B400 for ; Mon, 11 Dec 2000 11:14:02 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id 4AA28DC74; Mon, 11 Dec 2000 14:12:36 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 3DA08D93D; Mon, 11 Dec 2000 14:12:36 -0500 (EST) Date: Mon, 11 Dec 2000 14:12:36 -0500 (EST) From: David Miller To: Reverend K Kanno Cc: freebsd-scsi@freebsd.org Subject: Re: LUN 1 on 3.2-R? 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 Mon, 11 Dec 2000, Reverend K Kanno wrote: > On Mon, 11 Dec 2000, David Miller wrote: > > What SCSI HA are you using? It seems lots of HAs dont' properly support LUNs. Adaptec 2940. --- David > For instance, I have yet to see an onboard Adaptec Dell SCSI HA that works > with an Infortrend or Chapparal controller. > > > Hi All:) > > > > I'm stumped. I have a 3.2R system with an attached external SCSI-SCSI > > RAID controller. I had a nice 10 drive array last year with 36 GB drives, > > and this year I'm adding on another nice array. > > > > I have this in my config file: > > > > # SCSI peripherals > > # Only one of each of these is needed, they are dynamically allocated. > > controller scbus0 # SCSI bus (required) > > # device da0 # Direct Access (disks) > > disk da0 at scbus0 target 2 unit 0 > > disk da1 at scbus0 target 2 unit 1 > > device sa0 # Sequential Access (tape etc) > > device cd0 # CD > > device pass0 # Passthrough device (direct SCSI) > > > > > > But in dmesg I get: > > > > Waiting 5 seconds for SCSI devices to settle > > pass1 at ahc0 bus 0 target 2 lun 1 > > pass1: Fixed Processor SCSI-2 device > > pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged > > Queueing Enabled > > pass2 at ahc0 bus 0 target 2 lun 2 > > pass2: Fixed Processor SCSI-2 device > > pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) > > da0 at ahc0 bus 0 target 2 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing > > Enabled > > da0: 279097MB (571591680 512 byte sectors: 255H 63S/T 35579C) > > changing root device to wd0s1a > > > > > > camcontrol devlist: > > > > su-2.03# camcontrol devlist > > at scbus0 target 2 lun 0 (pass0,da0) > > at scbus0 target 2 lun 1 (pass1) > > at scbus0 target 2 lun 2 (pass2) > > > > > > The associated da* and pass* devices seem to exist. > > > > What am I missing? > > > > Thanks in advance, > > > > --- David > > > > > > > > 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 Mon Dec 11 11:19: 5 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:19:04 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 79DAB37B402 for ; Mon, 11 Dec 2000 11:19:03 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBJIes01804; Mon, 11 Dec 2000 12:18:41 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012111918.eBBJIes01804@aslan.scsiguy.com> To: Reverend K Kanno Cc: David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 13:00:18 CST." Date: Mon, 11 Dec 2000 12:18:40 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Mon, 11 Dec 2000, David Miller wrote: > >What SCSI HA are you using? It seems lots of HAs dont' properly support LUNs. >For instance, I have yet to see an onboard Adaptec Dell SCSI HA that works >with an Infortrend or Chapparal controller. The aic7xxx driver has supported luns for several years now. It is also known to work with Chapparal controllers. If you can be more specific about your issues, we might be able to help. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:35: 4 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:35:02 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5450137B400 for ; Mon, 11 Dec 2000 11:35:02 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA12739; Mon, 11 Dec 2000 11:34:59 -0800 Date: Mon, 11 Dec 2000 11:34:52 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Reverend K Kanno , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012111918.eBBJIes01804@aslan.scsiguy.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 Look at the INQUIRY data for the pass devices- they're Processor type for lun 1 && lun 2. > >On Mon, 11 Dec 2000, David Miller wrote: > > > >What SCSI HA are you using? It seems lots of HAs dont' properly support LUNs. > >For instance, I have yet to see an onboard Adaptec Dell SCSI HA that works > >with an Infortrend or Chapparal controller. > > The aic7xxx driver has supported luns for several years now. It is > also known to work with Chapparal controllers. If you can be more > specific about your issues, we might be able to help. > > -- > Justin > > > 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 Dec 11 11:42:48 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:42:47 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 3673C37B400 for ; Mon, 11 Dec 2000 11:42:46 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBJges02409; Mon, 11 Dec 2000 12:42:40 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012111942.eBBJges02409@aslan.scsiguy.com> To: mjacob@feral.com Cc: Reverend K Kanno , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 11:34:52 PST." Date: Mon, 11 Dec 2000 12:42:39 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >Look at the INQUIRY data for the pass devices- they're Processor type for lun >1 && lun 2. The lack of a peripheral driver doesn't have anything to do with whether luns are supported or not. It also doesn't preclude the system from talking to the array as a disk. David seemed to imply that the Chapparal arrays didn't work *at all*. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:48:54 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:48:52 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5808D37B400 for ; Mon, 11 Dec 2000 11:48:52 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA12793; Mon, 11 Dec 2000 11:48:46 -0800 Date: Mon, 11 Dec 2000 11:48:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Reverend K Kanno , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012111942.eBBJges02409@aslan.scsiguy.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 Mon, 11 Dec 2000, Justin T. Gibbs wrote: > > > > > >Look at the INQUIRY data for the pass devices- they're Processor type for lun > >1 && lun 2. > > The lack of a peripheral driver doesn't have anything to do with > whether luns are supported or not. It also doesn't preclude the > system from talking to the array as a disk. David seemed to > imply that the Chapparal arrays didn't work *at all*. Uh, if they report themselves as Processor type, they won't attach as disk: > Waiting 5 seconds for SCSI devices to settle > pass1 at ahc0 bus 0 target 2 lun 1 > pass1: Fixed Processor SCSI-2 device > pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged > Queueing Enabled > pass2 at ahc0 bus 0 target 2 lun 2 > pass2: Fixed Processor SCSI-2 device > pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) > da0 at ahc0 bus 0 target 2 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing > Enabled > da0: 279097MB (571591680 512 byte sectors: 255H 63S/T 35579C) > changing root device to wd0s1a Target 2, lun 0, DIRECT ACCESS Target 2, lun 1, lun 2, Processor Type (no pt driver config'd) -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:50:55 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:50:54 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 6B39537B404 for ; Mon, 11 Dec 2000 11:50:53 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBJols02740; Mon, 11 Dec 2000 12:50:48 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012111950.eBBJols02740@aslan.scsiguy.com> To: mjacob@feral.com Cc: Reverend K Kanno , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 11:48:39 PST." Date: Mon, 11 Dec 2000 12:50:47 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> The lack of a peripheral driver doesn't have anything to do with >> whether luns are supported or not. It also doesn't preclude the >> system from talking to the array as a disk. David seemed to >> imply that the Chapparal arrays didn't work *at all*. > >Uh, if they report themselves as Processor type, they won't attach as disk: Only the control port on these devices is processor type. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:52: 1 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:52:00 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 9681F37B400 for ; Mon, 11 Dec 2000 11:51:59 -0800 (PST) Received: from shell-1.enteract.com (presence@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA70208; Mon, 11 Dec 2000 13:51:50 -0600 (CST) (envelope-from presence@churchofinformationwarfare.org) Date: Mon, 11 Dec 2000 13:51:49 -0600 (CST) From: Reverend K Kanno X-Sender: presence@shell-1.enteract.com To: Matthew Jacob Cc: "Justin T. Gibbs" , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? 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 > > The aic7xxx driver has supported luns for several years now. It is > > also known to work with Chapparal controllers. If you can be more > > specific about your issues, we might be able to help. The driver itself may have, but not all aic7xxx based cards do. I suggest to anybody who has weird problems with any device that uses LUNs and not just ID to get an off the shelf adaptec 29160 card with a 2.57 or later BIOS and try with that. Not all mylex/buslogic, Symbios/LSI Logic, Adaptec or OEMed Adaptec cards work properly. KEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:54:18 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:54:16 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 9F96D37B400 for ; Mon, 11 Dec 2000 11:54:15 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBJs9s03186; Mon, 11 Dec 2000 12:54:10 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012111954.eBBJs9s03186@aslan.scsiguy.com> To: Reverend K Kanno Cc: Matthew Jacob , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 13:51:49 CST." Date: Mon, 11 Dec 2000 12:54:09 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> > The aic7xxx driver has supported luns for several years now. It is >> > also known to work with Chapparal controllers. If you can be more >> > specific about your issues, we might be able to help. > >The driver itself may have, but not all aic7xxx based cards do. I suggest to >anybody who has weird problems with any device that uses LUNs and not just ID >to get an off the shelf adaptec 29160 card with a 2.57 or later BIOS and try >with that. Not all mylex/buslogic, Symbios/LSI Logic, Adaptec or OEMed Adaptec >cards work properly. > >KEN The only difference between talking to lun 0 and talking to a lun other than 0 is software. FreeBSD will probe higher luns on any chip shpported by the aic7xxx driver. In other words, unless there is a physical defect that prevents the chip from talking to targets in general, multi-lun support is available regardless of whether the chip is on the motherboard or on a PCI card. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 11:59:23 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 11:59:21 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 1D33737B400 for ; Mon, 11 Dec 2000 11:59:21 -0800 (PST) Received: from shell-1.enteract.com (presence@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id NAA74404; Mon, 11 Dec 2000 13:59:13 -0600 (CST) (envelope-from presence@churchofinformationwarfare.org) Date: Mon, 11 Dec 2000 13:59:13 -0600 (CST) From: Reverend K Kanno X-Sender: presence@shell-1.enteract.com To: "Justin T. Gibbs" Cc: Matthew Jacob , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012111954.eBBJs9s03186@aslan.scsiguy.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 > The only difference between talking to lun 0 and talking to a lun other > than 0 is software. FreeBSD will probe higher luns on any chip shpported > by the aic7xxx driver. In other words, unless there is a physical defect > that prevents the chip from talking to targets in general, multi-lun > support is available regardless of whether the chip is on the motherboard > or on a PCI card. False. There are many BAD SCSI BIOSes out there. I challenge you to get a Chapparal or Infortrend SCSI-SCSI raid controller with at least two raid volumes to work with the integrated aic7899 HAs that come on dell 64xx servers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 12: 0:26 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 12:00:24 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (unknown [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id E79FF37B400 for ; Mon, 11 Dec 2000 12:00:23 -0800 (PST) Received: by search.sparks.net (Postfix, from userid 100) id 09CB8DC74; Mon, 11 Dec 2000 14:57:37 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id E5DEDD93D; Mon, 11 Dec 2000 14:57:37 -0500 (EST) Date: Mon, 11 Dec 2000 14:57:37 -0500 (EST) From: David Miller To: "Justin T. Gibbs" Cc: mjacob@feral.com, Reverend K Kanno , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012111950.eBBJols02740@aslan.scsiguy.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 Mon, 11 Dec 2000, Justin T. Gibbs wrote: > >> The lack of a peripheral driver doesn't have anything to do with > >> whether luns are supported or not. It also doesn't preclude the > >> system from talking to the array as a disk. David seemed to > >> imply that the Chapparal arrays didn't work *at all*. Actually that was Reverend K Kanno. > > > >Uh, if they report themselves as Processor type, they won't attach as disk: > > Only the control port on these devices is processor type. That makes sense, except that I have a da0 and a pass1 and pass2: pass1 at ahc0 bus 0 target 2 lun 1 pass1: Fixed Processor SCSI-2 device pass1: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 2 pass2: Fixed Processor SCSI-2 device pass2: 80.000MB/s transfers (40.000MHz, offset 127, 16bit) Why that second array would come up as a processor type is quite the mystery. --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 12:16:23 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 12:16:22 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 22B5837B400 for ; Mon, 11 Dec 2000 12:16:21 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBKGCs04057; Mon, 11 Dec 2000 13:16:12 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012112016.eBBKGCs04057@aslan.scsiguy.com> To: Reverend K Kanno Cc: Matthew Jacob , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 13:59:13 CST." Date: Mon, 11 Dec 2000 13:16:12 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >False. There are many BAD SCSI BIOSes out there. > >I challenge you to get a Chapparal or Infortrend SCSI-SCSI raid controller >with at least two raid volumes to work with the integrated aic7899 HAs that >come on dell 64xx servers. Perhaps. The aic7899 on my Dell Precision 420 does not seem to have this issue, but I don't have access to a Dell 64xx to test against. In this entire thread, my assumption was that you were complaining about FreeBSD being unable to talk to these devices. There are, as I've said before, no known issues in this regard. If you have a particular machine where the BIOS is not functioning correctly, I can forward your report to the appropriate people within Adaptec so that the problem can be addressed. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 12:17:12 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 12:17:11 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 49B3337B402 for ; Mon, 11 Dec 2000 12:17:10 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eBBKGts04088; Mon, 11 Dec 2000 13:16:55 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200012112016.eBBKGts04088@aslan.scsiguy.com> To: David Miller Cc: mjacob@feral.com, Reverend K Kanno , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: Your message of "Mon, 11 Dec 2000 14:57:37 EST." Date: Mon, 11 Dec 2000 13:16:55 -0700 From: "Justin T. Gibbs" Sender: gibbs@aslan.scsiguy.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Why that second array would come up as a processor type is quite the >mystery. You'll have to bring that up with the vendor of the array. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 12:33:45 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 12:33:43 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 2DBDD37B400 for ; Mon, 11 Dec 2000 12:33:43 -0800 (PST) Received: from shell-1.enteract.com (presence@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id OAA95695; Mon, 11 Dec 2000 14:33:37 -0600 (CST) (envelope-from presence@churchofinformationwarfare.org) Date: Mon, 11 Dec 2000 14:33:26 -0600 (CST) From: Reverend K Kanno X-Sender: presence@shell-1.enteract.com To: "Justin T. Gibbs" Cc: Matthew Jacob , David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: LUN 1 on 3.2-R? In-Reply-To: <200012112016.eBBKGCs04057@aslan.scsiguy.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 Mon, 11 Dec 2000, Justin T. Gibbs wrote: > > > >False. There are many BAD SCSI BIOSes out there. > > > >I challenge you to get a Chapparal or Infortrend SCSI-SCSI raid controller > >with at least two raid volumes to work with the integrated aic7899 HAs that > >come on dell 64xx servers. > > Perhaps. The aic7899 on my Dell Precision 420 does not seem to have > this issue, but I don't have access to a Dell 64xx to test against. > In this entire thread, my assumption was that you were complaining > about FreeBSD being unable to talk to these devices. There are, as > I've said before, no known issues in this regard. If you have > a particular machine where the BIOS is not functioning correctly, > I can forward your report to the appropriate people within Adaptec > so that the problem can be addressed. I never intended to make it sound as if FreeBSD was it fault, as it is not. I incorrectly assumed at first that any respected brand of SCSI controller is properly implemented and that a similar problem I had a while back was with my settings. This was simply not true at all. An bad BIOS will make LUN based devices act weird or just not work at all, yet behave properly for everything else. As a note, Dell does acknowledge any problems with their controller firmware and has no updates planned. ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== The Exploding Fruit Challenge! Rev. K. Kanno www.energybeam.com blowup-fruit@energybeam.com ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 17:33:18 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 17:33:16 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from cortez.sitemajic.net (unknown [208.153.40.60]) by hub.freebsd.org (Postfix) with ESMTP id 5392937B400 for ; Mon, 11 Dec 2000 17:33:16 -0800 (PST) Received: (from apache@localhost) by cortez.sitemajic.net (8.11.1/8.11.1) id eBC1dwi77749; Mon, 11 Dec 2000 20:39:58 -0500 (EST) To: freebsd-scsi@freebsd.org Subject: kernel/ scsi + disk error messages Message-ID: <976585198.3a3581eeebfef@www.sitemajic.net> Date: Mon, 11 Dec 2000 20:39:58 -0500 (EST) From: Chris Jesseman Cc: chris@sitemajic.net MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 204.38.56.35 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Where can I find more about these error messages (they are happening more frequently now)? /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 2 21 67 e9 0 0 2 0 /kernel: (da0:ahc0:0:0:0): Deferred Error: ABORTED COMMAND info:2215abf asc:8,1 /kernel: (da0:ahc0:0:0:0): Logical unit communication time-out field replaceable unit: 1 I asked questions@ & stable@ and searched web for similar strings- no luck. Any suggestions are very much appreciated! Please copy my address chris@sitemajic.net as I am not subscribed to scsi@ Thank you, Chris Jesseman --more--> 4.1 -STABLE system from dmesg (at boot) ahc0: port 0xe800-0xe8ff mem 0xffaff000- 0xffafffff irq 10 at device 20.0 on pci0 ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs ------ Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) Mounting root from ufs:/dev/da0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 19:46:51 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 19:46:49 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from truffaut.projex.hu (truffaut.projex.hu [195.70.35.49]) by hub.freebsd.org (Postfix) with ESMTP id 8606737B400 for ; Mon, 11 Dec 2000 19:46:48 -0800 (PST) Received: from steer (helo=localhost) by truffaut.projex.hu with local-esmtp (Exim 3.13 #2) id 145gP8-0007Zv-00 for freebsd-scsi@freebsd.org; Tue, 12 Dec 2000 04:47:02 +0100 Date: Tue, 12 Dec 2000 04:47:02 +0100 (CET) From: VENESZ Roland To: freebsd-scsi@freebsd.org Subject: Failure prediction threshold exceeded Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: VENESZ Roland Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi list, I've been searching the list archives for an answer to my question, found similar stuff, but not exactly this one. So. I installed FreeBSD on a box these days, having these (brand new) SCSI disks: da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34715MB (71096640 512 byte sectors: 255H 63S/T 4425C) (da1 is exactly the same) AWRE and ARRE is 1 for both disks. The controller is an Adaptec 29160 Ultra160 SCSI adapter. These error messages keep on coming: (da0:ahc0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:0:0): RECOVERED ERROR asc:5d,0 (da0:ahc0:0:0:0): Failure prediction threshold exceeded (da1:ahc0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:ahc0:0:1:0): RECOVERED ERROR asc:5d,0 (da1:ahc0:0:1:0): Failure prediction threshold exceeded and (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 4 3c d9 3f 0 0 1 0 (da0:ahc0:0:0:0): RECOVERED ERROR asc:5d,0 (da0:ahc0:0:0:0): Failure prediction threshold exceeded (da1:ahc0:0:1:0): WRITE(10). CDB: 2a 0 4 3c d9 3f 0 0 1 0 (da1:ahc0:0:1:0): RECOVERED ERROR asc:5d,0 (da1:ahc0:0:1:0): Failure prediction threshold exceeded I get them when trying to access the drives after some 10 minutes of inactivity. They never come when the disk is active, or was active in the last ~10 minutes. (btw APM is disabled. Totally.) They come in pair for target 0 and 1 since I use vinum RAID-1 :) Had them before as well, but not in pairs. Some messages were produced under OpenBSD as well, i can supply them if needed. Any help is highly appreciated, thanks in advance. bye, Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 21:21:31 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 21:21:30 2000 Return-Path: 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 CBA8937B400 for ; Mon, 11 Dec 2000 21:21:28 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 145hCF-00071q-00 for freebsd-scsi@freebsd.org; Mon, 11 Dec 2000 20:37:47 -0800 Date: Mon, 11 Dec 2000 20:37:45 -0800 (PST) From: Tom Samplonius To: freebsd-scsi@freebsd.org Subject: All this talk of LUNs... 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 As far as LUNs go, how many LUNs are probed by default? Can it be changed? I'm about to start using a storage server that can present up to 64 LUNs to the host, and the documentation goes into a lot of detail of various OS limitations on how many LUNs can be supported. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 21:28:36 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 21:28:35 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EC0D337B400 for ; Mon, 11 Dec 2000 21:28:34 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA14654; Mon, 11 Dec 2000 21:28:29 -0800 Date: Mon, 11 Dec 2000 21:28:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Tom Samplonius Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: All this talk of LUNs... 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 We will be implementing the use of REPORT LUNS rsn. Otherwise, it's up to each SIM (HBA) to tell CAM how far to go. On Mon, 11 Dec 2000, Tom Samplonius wrote: > > As far as LUNs go, how many LUNs are probed by default? Can it be > changed? > > I'm about to start using a storage server that can present up to 64 LUNs > to the host, and the documentation goes into a lot of detail of various OS > limitations on how many LUNs can be supported. > > Tom > > > > 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 Dec 11 22: 3:28 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 22:03:27 2000 Return-Path: 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 8F73C37B400 for ; Mon, 11 Dec 2000 22:03:25 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 145hqm-00074Z-00; Mon, 11 Dec 2000 21:19:40 -0800 Date: Mon, 11 Dec 2000 21:19:38 -0800 (PST) From: Tom Samplonius To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: All this talk of LUNs... 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 Mon, 11 Dec 2000, Matthew Jacob wrote: > We will be implementing the use of REPORT LUNS rsn. > Otherwise, it's up to each SIM (HBA) to tell CAM how far to go. Well, I've taken a look at the ahc and sym manpages. No mention of how LUNs get probed. I took at look at LINT, and there is a SYM_SETUP_MAX_LUN option for the sym driver. I don't know what ahc does. Also, I've noticed that the ahc manpage (on a 4.2-STABLE system) says that U160 controllers are not supported yet, but that features seems to have been added now. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 11 23:16: 3 2000 From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 11 23:16:01 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id E77BC37B400 for ; Mon, 11 Dec 2000 23:16:00 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 145jfH-0006i2-00; Tue, 12 Dec 2000 07:15:55 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eBC7FhH04990; Tue, 12 Dec 2000 08:15:43 +0100 (CET) (envelope-from wkb) Date: Tue, 12 Dec 2000 08:15:43 +0100 From: Wilko Bulte To: VENESZ Roland Cc: freebsd-scsi@freebsd.org Subject: Re: Failure prediction threshold exceeded Message-ID: <20001212081543.C4706@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from steer@projex.hu on Tue, Dec 12, 2000 at 04:47:02AM +0100 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Dec 12, 2000 at 04:47:02AM +0100, VENESZ Roland wrote: > da0: 34715MB (71096640 512 byte sectors: 255H 63S/T 4425C) > (da1 is exactly the same) > > AWRE and ARRE is 1 for both disks. > The controller is an Adaptec 29160 Ultra160 SCSI adapter. > > These error messages keep on coming: > > (da0:ahc0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:0:0): RECOVERED ERROR asc:5d,0 > (da0:ahc0:0:0:0): Failure prediction threshold exceeded > (da1:ahc0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:ahc0:0:1:0): RECOVERED ERROR asc:5d,0 > (da1:ahc0:0:1:0): Failure prediction threshold exceeded IIRC these disks have predictive failure detection in their hardware. They might just be dying on you. Wild guess: is the cooling sufficient? -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 12 19:52:46 2000 From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 12 19:52:44 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 2766F37B400; Tue, 12 Dec 2000 19:52:44 -0800 (PST) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA03927; Tue, 12 Dec 2000 22:52:35 -0500 (EST) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA04652; Tue, 12 Dec 2000 22:53:55 -0500 (EST) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA04648; Tue, 12 Dec 2000 22:53:55 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Tue, 12 Dec 2000 22:53:55 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: 4.2 panic with AHA-2940 ... fixed 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 It seems the problem had something to do with my using so many kld's... I am now only using the linux kld, and everything works fine now. :-) Thanks for the help though. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 12 20:18: 8 2000 From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 12 20:18:06 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-64.dsl.snfc21.pacbell.net [63.202.176.64]) by hub.freebsd.org (Postfix) with ESMTP id BD31937B402; Tue, 12 Dec 2000 20:18:05 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBD4Rp306536; Tue, 12 Dec 2000 20:27:53 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012130427.eBD4Rp306536@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: 4.2 panic with AHA-2940 ... fixed In-reply-to: Your message of "Tue, 12 Dec 2000 22:53:55 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Dec 2000 20:27:51 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It seems the problem had something to do with my using so many kld's... I > am now only using the linux kld, and everything works fine now. :-) Thanks > for the help though. You probably just had one out of date KLD. There aren't any real issues with "too many" KLDs (I occasionally test by loading all of them). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 12 22: 2:34 2000 From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 12 22:02:31 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 4F47237B400; Tue, 12 Dec 2000 22:02:31 -0800 (PST) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA13161; Wed, 13 Dec 2000 01:02:30 -0500 (EST) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA12654; Wed, 13 Dec 2000 01:02:29 -0500 (EST) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA12649; Wed, 13 Dec 2000 01:02:29 -0500 (EST) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Wed, 13 Dec 2000 01:02:29 -0500 (EST) From: Kenneth Wayne Culver To: Mike Smith Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: 4.2 panic with AHA-2940 ... fixed In-Reply-To: <200012130427.eBD4Rp306536@mass.osd.bsdi.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 > You probably just had one out of date KLD. There aren't any real > issues with "too many" KLDs (I occasionally test by loading all of > them). I recompile all my kld's every time I rebuild a kernel to make sure they're up to date... I'm running -STABLE so it automatically rebuilds them every time (I'm sure about this... because in order to keep from building them now I use -DNO_MODULES because I'm not using them anymore) There must be a problem in there some where... I have no idea where though... although every time I got the crash it happened in the same exact place in the code... I traced it using kgdb on my crash dumps Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 14 5:16:24 2000 From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 14 05:16:23 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from bayer2.bayer-ag.de (bayer2.bayer-ag.de [194.120.191.2]) by hub.freebsd.org (Postfix) with SMTP id 2833237B400 for ; Thu, 14 Dec 2000 05:16:22 -0800 (PST) Received: from BYE473.BAYER-AG.DE (bye473.bayer-ag.com) by bayer2.bayer-ag.de with SMTP id OAA29245 (SMTP Gateway 4.2 for ); Thu, 14 Dec 2000 14:15:12 +0100 Received: by BYE473.BAYER-AG.DE (Soft-Switch LMS 3.2) with snapi via MT0044 id 0006800037112728; Thu, 14 Dec 2000 14:16:16 +0100 From: andreas.klemm.ak@bayer-ag.de To: " - *freebsd-scsi@freebsd.org" Subject: are printers with SCSI interface supported on FreeBSD ? Message-Id: <0006800037112728000002L082*@MHS> Date: Thu, 14 Dec 2000 14:16:16 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! A friend of my wifes collegue has access to SCSI printer. He wanted to drive this under Linux. Didn%t find infos concerning this on google.com. Do we perhaps support SCSI printer and which devices to use then ? pt ? prozessor target ? Andreas /// To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 14 16:27:33 2000 From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 14 16:27:25 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from paranoid.gws.org (adsl-216-101-234-121.dsl.snfc21.pacbell.net [216.101.234.121]) by hub.freebsd.org (Postfix) with SMTP id 5C5EE37B402 for ; Thu, 14 Dec 2000 16:27:23 -0800 (PST) Received: (qmail 26051 invoked by uid 1000); 15 Dec 2000 00:32:40 -0000 Date: Thu, 14 Dec 2000 16:32:40 -0800 From: noah To: freebsd-scsi@freebsd.org Cc: Micah Anderson Subject: Re: update Message-ID: <20001214163240.C25983@indymedia.org> References: <20001212233150.F11687@riseup.net> <20001213072136.B25257@indymedia.org> <20001214092814.K11687@riseup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001214092814.K11687@riseup.net>; from micah@indymedia.org on Thu, Dec 14, 2000 at 09:28:14AM -0800 Sender: noah@paranoid.gws.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm working on trying to install FreeBSD 4.2 on a dual p3 700 with an Adaptec 3200S raid card. From what I can tell everyone that has tried this card has had good luck. When we install FreeBSD (booting off cd) it recognizes the card and installs on it perfectly, but when it loads the OS off the raid it does something to damage the hardware raid, requiring us to rebuild the RAID in the 3200S' bios. We're pretty sure that this isn't a hardware problem. I've included a verbose copy of the boot up. Thanks for any help. > Where the raid dies is after the line, "asr0: major=154" - > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 > jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC > Calibrating clock(s) ... TSC clock: 697068092 Hz, i8254 clock: 1193349 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz > CLK_USE_TSC_CALIBRATION not specified - using old calibration method > CPU: Pentium III/Pentium III Xeon/Celeron (696.97-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > Features=0x383fbff > real memory = 536805376 (524224K bytes) > Physical memory chunk(s): > 0x00001000 - 0x0009efff, 647168 bytes (158 pages) > 0x0044f000 - 0x1ffe7fff, 532254720 bytes (129945 pages) > avail memory = 518422528 (506272K bytes) > bios32: Found BIOS32 Service Directory header at 0xc00f6c30 > bios32: Entry = 0xfd7e3 (c00fd7e3) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0x430 > pnpbios: Found PnP BIOS data at 0xc00f6c60 > pnpbios: Entry = f0000:a8cb Rev = 1.0 > Other BIOS signatures found: > ACPI: 000f6ad0 > Preloaded elf kernel "kernel" at 0xc0436000. > Pentium Pro MTRR support enabled > md0: Malloc disk > Creating DISK md0 > Math emulator present > pci_open(1): mode 1 addr port (0x0cf8) is 0x80022108 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > pcib-: pcib0 exists, using next available unit number > npx0: on motherboard > npx0: INT 16 interface > pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > pcib0: on motherboard > found-> vendor=0x8086, dev=0x71a0, revid=0x00 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base f8000000, size 26 > found-> vendor=0x8086, dev=0x71a1, revid=0x00 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=3 secondarybus=1 > found-> vendor=0x9005, dev=0x005f, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base 00002000, size 8 > map[14]: type 1, range 64, base f4100000, size 12 > found-> vendor=0x9005, dev=0x005f, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base 00002400, size 8 > map[14]: type 1, range 64, base f4101000, size 12 > found-> vendor=0x8086, dev=0x1229, revid=0x08 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[10]: type 1, range 32, base f4102000, size 12 > map[14]: type 1, range 32, base 00002800, size 6 > map[18]: type 1, range 32, base f4000000, size 20 > found-> vendor=0x8086, dev=0x7110, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[20]: type 1, range 32, base 00002860, size 4 > found-> vendor=0x8086, dev=0x7112, revid=0x01 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=10 > map[20]: type 1, range 32, base 00002840, size 5 > found-> vendor=0x8086, dev=0x7113, revid=0x02 > class=06-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[90]: type 1, range 32, base 00001040, size 4 > found-> vendor=0x1013, dev=0x00bc, revid=0x23 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[10]: type 1, range 32, base f6000000, size 25 > map[14]: type 1, range 32, base f4103000, size 12 > pci0: on pcib0 > pcib2: at device 1.0 on pci0 > found-> vendor=0x1011, dev=0x0023, revid=0x06 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=3 secondarybus=2 > pci1: on pcib2 > pcib3: at device 15.0 on pci1 > found-> vendor=0x1044, dev=0xa500, revid=0x02 > class=06-04-00, hdrtype=0x01, mfdev=1 > subordinatebus=3 secondarybus=3 > found-> vendor=0x1044, dev=0xa501, revid=0x02 > class=0e-00-01, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 > intpin=a, irq=5 > map[10]: type 1, range 32, base fc000000, size 25 > pci2: on pcib3 > pcib4: at device 4.0 on pci2 > pci3: on pcib4 > asr0: mem 0xfc000000-0xfdffffff irq 5 at device 4.1 on pci2 > asr0: major=154 > asr0: ADAPTEC 3200S FW Rev. 320P, 2 channel, 256 CCBs, Protocol I2O > ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0 > ahc0: Reading SEEPROM...done. > ahc0: Manual LVD Termination > ahc0: BIOS eeprom is present > ahc0: Secondary High byte termination Enabled > ahc0: Secondary Low byte termination Enabled > ahc0: Primary Low Byte termination Enabled > ahc0: Primary High Byte termination Enabled > ahc0: Downloading Sequencer Program... 412 instructions downloaded > aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 > ahc1: Reading SEEPROM...done. > ahc1: Manual LVD Termination > ahc1: BIOS eeprom is present > ahc1: Secondary High byte termination Enabled > ahc1: Secondary Low byte termination Enabled > ahc1: Primary Low Byte termination Enabled > ahc1: Primary High Byte termination Enabled > ahc1: Downloading Sequencer Program... 412 instructions downloaded > aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs > using shared irq11. > fxp0: port 0x2800-0x283f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0 > fxp0: Ethernet address 00:d0:b7:a9:34:0c > bpf: fxp0 attached > isab0: at device 18.0 on pci0 > isa0: on isab0 > atapci0: port 0x2860-0x286f at device 18.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x2860 > ata0: mask=03 status0=00 status1=00 > ata0: mask=03 ostat0=00 ostat2=00 > ata0-master: ATAPI probe a=00 b=00 > ata0-slave: ATAPI probe a=00 b=00 > ata0: mask=03 status0=00 status1=00 > ata0: devices=00 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x2868 > ata1: mask=03 status0=00 status1=00 > ata1: mask=03 ostat0=00 ostat2=00 > ata1-master: ATAPI probe a=00 b=00 > ata1-slave: ATAPI probe a=00 b=00 > ata1: mask=03 status0=00 status1=00 > ata1: devices=00 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0x2840-0x285f irq 10 at device 18.2 on pci0 > using shared irq10. > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > chip1: port 0x1040-0x104f at device 18.3 on pci0 > pci0: (vendor=0x1013, dev=0x00bc) at 20.0 > pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) > pci-: pci1 exists, using next available unit number > pcib1: on motherboard > pci4: on pcib1 > ata-: ata0 exists, using next available unit number > ata-: ata1 exists, using next available unit number > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ata2 failed to probe at port 0x1f0 irq 14 on isa0 > ata3 failed to probe at port 0x170 irq 15 on isa0 > adv0 failed to probe at port 0x330 on isa0 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x330 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x334 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x230 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x234 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x130 > bt0: Failed Status Reg Test - ff > bt_isa_probe: Probe failed at 0x134 > bt0 failed to probe at port 0x134-0x137 on isa0 > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0: status reg test failed ff > aha0 failed to probe at port 0x134-0x137 on isa0 > aic0 failed to probe at port 0x140-0x15f on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > atkbd: the current kbd controller command byte 0047 > atkbd: keyboard ID 0x41ab (2) > kbdc: RESET_KBD return code:00fa > kbdc: RESET_KBD status:00aa > kbd0 at atkbd0 > kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 > psm0: current command byte:0047 > kbdc: TEST_AUX_PORT status:0000 > kbdc: RESET_AUX return code:00fe > kbdc: RESET_AUX return code:00fe > kbdc: RESET_AUX return code:00fe > kbdc: DIAGNOSE status:0055 > kbdc: TEST_KBD_PORT status:0000 > psm0: failed to reset the aux device. > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > fb0: vga0, vga, type:VGA (5), flags:0x7007f > fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 > fb0: init mode:24, bios mode:3, current mode:24 > fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k > VGA parameters upon power-up > 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > VGA parameters in BIOS for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > EGA/VGA parameters to be used for mode 24 > 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 > bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 > b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) > pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 > pcic1: not probed (disabled) > sio0: irq maps: 0x41 0x51 0x41 0x41 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: irq maps: 0x41 0x41 0x41 0x41 > sio1: probe failed test(s): 0 1 2 4 6 7 9 > sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 > sio2: not probed (disabled) > sio3: not probed (disabled) > ppc0: parallel port found at 0x378 > ppc0: using extended I/O port range > ppc0: ECP SPP SPP > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > plip0: on ppbus0 > bpf: lp0 attached > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ed0 failed to probe at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 > fe0 failed to probe at port 0x300-0x31f on isa0 > ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 > lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 > cs0 failed to probe at port 0x300 on isa0 > sn0 failed to probe at port 0x300 irq 10 on isa0 > isa_probe_children: probing PnP devices > BIOS Geometries: > 0:03fffe3f 0..1023=1024 cylinders, 0..254=255 heads, 1..63=63 sectors > 0 accounted for > Device configuration finished. > bpf: faith0 attached > bpf: gif0 attached > bpf: gif1 attached > bpf: gif2 attached > bpf: gif3 attached > bpf: lo0 attached > bpf: ppp0 attached > new masks: bio 68c440, tty 630092, net 670492 > bpf: sl0 attached > Waiting 15 seconds for SCSI devices to settle > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > Creating DISK da0 > Creating DISK da1 > pass0 at asr0 bus 0 target 1 lun 0 > pass0: Fixed Direct Access SCSI-2 device > pass0: Serial Number + > pass0: Tagged Queueing Enabled > pass1 at asr0 bus 0 target 3 lun 0 > pass1: Fixed Direct Access SCSI-3 device > pass1: Serial Number 4DY1M466 > pass1: Tagged Queueing Enabled > da0 at asr0 bus 0 target 1 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: Serial Number + > da0: Tagged Queueing Enabled > da0: 17496MB (35831808 512 byte sectors: 255H 63S/T 2230C) > da1 at asr0 bus 0 target 3 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: Serial Number 4DY1M466 > da1: Tagged Queueing Enabled > da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > Mounting root from ufs:/dev/da0s1a > da0s1: type 0xa5, start 63, end = 35824949, size 35824887 : OK > start_init: trying /sbin/init -- noah .. email for pgp/gpg key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 15 8:42: 4 2000 From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 15 08:42:03 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 68F1337B400 for ; Fri, 15 Dec 2000 08:42:02 -0800 (PST) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id QAA85169 for scsi@freebsd.org; Fri, 15 Dec 2000 16:50:17 GMT (envelope-from geoffb) Date: Fri, 15 Dec 2000 16:50:17 +0000 From: Geoff Buckingham To: scsi@freebsd.org Subject: de-tuning scsi subsystem? Message-ID: <20001215165017.B79626@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone suggest a way to de-tune the scsi subsystem such that it does not load, and therfore break the aac driver? (This would allow us to install a machine with that RAID, and keep it running until the driver becomes stable under load) -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 15 8:47: 7 2000 From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 15 08:47:05 2000 Return-Path: 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 D8E2337B400 for ; Fri, 15 Dec 2000 08:47:04 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA49555; Fri, 15 Dec 2000 09:46:54 -0700 (MST) (envelope-from ken) Date: Fri, 15 Dec 2000 09:46:54 -0700 From: "Kenneth D. Merry" To: Geoff Buckingham Cc: scsi@FreeBSD.ORG Subject: Re: de-tuning scsi subsystem? Message-ID: <20001215094654.A49516@panzer.kdm.org> References: <20001215165017.B79626@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001215165017.B79626@chuggalug.clues.com>; from geoffb@chuggalug.clues.com on Fri, Dec 15, 2000 at 04:50:17PM +0000 Sender: ken@panzer.kdm.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Dec 15, 2000 at 16:50:17 +0000, Geoff Buckingham wrote: > > Can anyone suggest a way to de-tune the scsi subsystem such that it does not > load, and therfore break the aac driver? (This would allow us to install a > machine with that RAID, and keep it running until the driver becomes stable > under load) I don't think the aac driver runs through CAM, so de-tuning the SCSI subsytem won't do the trick. There might be a way to tweak the driver, but I don't know how you'd do 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 Fri Dec 15 14:19:41 2000 From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 15 14:19:39 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-28.dsl.snfc21.pacbell.net [63.202.177.28]) by hub.freebsd.org (Postfix) with ESMTP id 8B1E337B400 for ; Fri, 15 Dec 2000 14:19:39 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBFMTfo05053; Fri, 15 Dec 2000 14:29:42 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012152229.eBFMTfo05053@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geoff Buckingham Cc: scsi@freebsd.org Subject: Re: de-tuning scsi subsystem? In-reply-to: Your message of "Fri, 15 Dec 2000 16:50:17 GMT." <20001215165017.B79626@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Dec 2000 14:29:41 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Can anyone suggest a way to de-tune the scsi subsystem such that it does not > load, and therfore break the aac driver? (This would allow us to install a > machine with that RAID, and keep it running until the driver becomes stable > under load) aac doesn't use the scsi subsystem. I believe that Scott has tried rate-limiting I/O as well, without success. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 15 23:32:28 2000 From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 15 23:32:27 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (dhcp242.osd.bsdi.com [204.216.28.242]) by hub.freebsd.org (Postfix) with ESMTP id C332E37B400 for ; Fri, 15 Dec 2000 23:32:26 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBG7gEO01321; Fri, 15 Dec 2000 23:42:14 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012160742.eBG7gEO01321@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: noah Cc: freebsd-scsi@freebsd.org, Micah Anderson Subject: Re: update In-reply-to: Your message of "Thu, 14 Dec 2000 16:32:40 PST." <20001214163240.C25983@indymedia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Dec 2000 23:42:14 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, I'm working on trying to install FreeBSD 4.2 on a dual p3 700 with > an Adaptec 3200S raid card. From what I can tell everyone that has tried > this card has had good luck. When we install FreeBSD (booting off cd) it > recognizes the card and installs on it perfectly, but when it loads the OS > off the raid it does something to damage the hardware raid, requiring us > to rebuild the RAID in the 3200S' bios. We're pretty sure that this isn't > a hardware problem. You haven't actually included anything that suggests that there's a problem occurring, so it's somewhat difficult to guess what's going on. However, I don't lend much credibility to the suggestion that "FreeBSD does something to damage the hadware raid" - things just don't happen like that. I would be inclined to suspect that you probably have a suspect disk, or cabling/enclosure problems, but without more details it's hard to be sure. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 16 7: 8:23 2000 From owner-freebsd-scsi@FreeBSD.ORG Sat Dec 16 07:08:21 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from paranoid.gws.org (adsl-216-101-234-121.dsl.snfc21.pacbell.net [216.101.234.121]) by hub.freebsd.org (Postfix) with SMTP id 6283837B402 for ; Sat, 16 Dec 2000 07:08:21 -0800 (PST) Received: (qmail 27128 invoked by uid 1000); 16 Dec 2000 15:13:51 -0000 Date: Sat, 16 Dec 2000 07:13:51 -0800 From: noah To: Mike Smith Cc: freebsd-scsi@freebsd.org, micah@indymedia.org Subject: Re: update Message-ID: <20001216071351.A27119@indymedia.org> References: <20001214163240.C25983@indymedia.org> <200012160742.eBG7gEO01321@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012160742.eBG7gEO01321@mass.osd.bsdi.com>; from msmith@freebsd.org on Fri, Dec 15, 2000 at 11:42:14PM -0800 Sender: noah@paranoid.gws.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At "asr0: major=154" the raid card begins a high pitched beep indicating that two of the drives have failed and that a rebuild of the raid is required, but we've tested all of the drives and replaced the raid card with a new one, and still get the same problem. The reason I'm asking about possible software issues is that other OS's have worked on this raid setup. Thanks. On 12/15, Mike Smith wrote: > > > Hi, I'm working on trying to install FreeBSD 4.2 on a dual p3 700 with > > an Adaptec 3200S raid card. From what I can tell everyone that has tried > > this card has had good luck. When we install FreeBSD (booting off cd) it > > recognizes the card and installs on it perfectly, but when it loads the OS > > off the raid it does something to damage the hardware raid, requiring us > > to rebuild the RAID in the 3200S' bios. We're pretty sure that this isn't > > a hardware problem. > > You haven't actually included anything that suggests that there's a > problem occurring, so it's somewhat difficult to guess what's going on. > > However, I don't lend much credibility to the suggestion that "FreeBSD > does something to damage the hadware raid" - things just don't happen > like that. > > I would be inclined to suspect that you probably have a suspect disk, or > cabling/enclosure problems, but without more details it's hard to be sure. > > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > -- noah .. email for pgp/gpg key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 16 10: 1: 5 2000 From owner-freebsd-scsi@FreeBSD.ORG Sat Dec 16 10:01:03 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from shrubbery.satx.bikeworld.net (shrubbery.satx.bikeworld.net [209.142.99.220]) by hub.freebsd.org (Postfix) with ESMTP id AC04B37B400 for ; Sat, 16 Dec 2000 10:01:03 -0800 (PST) Received: from roscoe ([10.0.0.2] helo=roscoe.ah.bikeworld.net ident=mailserv) by shrubbery.satx.bikeworld.net with esmtp (Exim 3.16 #1) id 147LdR-000OG0-00; Sat, 16 Dec 2000 12:00:41 -0600 Received: from roscoe.ah.bikeworld.net ([10.0.0.2] ident=root) by roscoe.ah.bikeworld.net with esmtp (Exim 3.16 #1) id 147LdQ-0009du-00; Sat, 16 Dec 2000 12:00:40 -0600 Date: Sat, 16 Dec 2000 12:00:40 -0600 (CST) From: Chris Snell X-Sender: chris@roscoe.ah.bikeworld.net To: noah Cc: freebsd-scsi@freebsd.org Subject: Re: update In-Reply-To: <20001216071351.A27119@indymedia.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 On Sat, 16 Dec 2000, noah wrote: > At "asr0: major=154" the raid card begins a high pitched beep > indicating that two of the drives have failed and that a rebuild of > the raid is required, but we've tested all of the drives and replaced > the raid card with a new one, and still get the same problem. The > reason I'm asking about possible software issues is that other OS's > have worked on this raid setup. We're using a 3200S in a Dell PowerEdge 4400 server, where it is plugged into a 2x4 hot-swappable backplane. When I installed it, I created a RAID using the BIOS tools and then installed FreeBSD 4.1.1-STABLE without a hitch. It's been running like a champ for about 6 weeks now. Check your disks, backplane, SCSI cables, connections, etc. very carefully. Try using fresh SCSI cables--factory defects can be invisible. Chris -- "Responsibility is a heavy responsibility, man." - Cheech Marin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 16 16:28:20 2000 From owner-freebsd-scsi@FreeBSD.ORG Sat Dec 16 16:28:18 2000 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-28.dsl.snfc21.pacbell.net [63.202.177.28]) by hub.freebsd.org (Postfix) with ESMTP id E111437B400 for ; Sat, 16 Dec 2000 16:28:17 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eBH0caQ02010; Sat, 16 Dec 2000 16:38:37 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200012170038.eBH0caQ02010@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: noah Cc: freebsd-scsi@freebsd.org, micah@indymedia.org, mark.salyzyn@adaptec.com Subject: Re: update In-reply-to: Your message of "Sat, 16 Dec 2000 07:13:51 PST." <20001216071351.A27119@indymedia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Dec 2000 16:38:36 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (please wrap your paragraphs so that it's possible to reply to your messages in a sane fashion, thanks 8) > At "asr0: major=154" the raid card begins a high pitched beep indicating > that two of the drives have failed and that a rebuild of the raid is > required, but we've tested all of the drives and replaced the raid card > with a new one, and still get the same problem. The reason I'm asking > about possible software issues is that other OS's have worked on this raid > setup. I've copied Mark at Adaptec, who is the author and principle maintainer of the 'asr' driver, since he's going to have the best idea of what's actually going on here. Without saying which OS' you've used, it's tough to know whether they simply aren't enabling the card alarm though. Have you tried running the Adaptec management software to check the status of the card? > Thanks. > > On 12/15, Mike Smith wrote: > > > > > Hi, I'm working on trying to install FreeBSD 4.2 on a dual p3 700 with > > > an Adaptec 3200S raid card. From what I can tell everyone that has tried > > > this card has had good luck. When we install FreeBSD (booting off cd) it > > > recognizes the card and installs on it perfectly, but when it loads the OS > > > off the raid it does something to damage the hardware raid, requiring us > > > to rebuild the RAID in the 3200S' bios. We're pretty sure that this isn't > > > a hardware problem. > > > > You haven't actually included anything that suggests that there's a > > problem occurring, so it's somewhat difficult to guess what's going on. > > > > However, I don't lend much credibility to the suggestion that "FreeBSD > > does something to damage the hadware raid" - things just don't happen > > like that. > > > > I would be inclined to suspect that you probably have a suspect disk, or > > cabling/enclosure problems, but without more details it's hard to be sure. > > > > > > -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > > > > > -- > noah .. email for pgp/gpg key > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message