From owner-freebsd-scsi Mon May 29 17:23:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29]) by hub.freebsd.org (Postfix) with ESMTP id 0CDF037BD05 for ; Mon, 29 May 2000 17:23:24 -0700 (PDT) (envelope-from lee@lcremeans.erols.com) Received: (from lee@localhost) by lcremeans.erols.com (8.9.3/8.9.3) id UAA00437 for freebsd-scsi@freebsd.org; Mon, 29 May 2000 20:23:21 -0400 (EDT) (envelope-from lee) Date: Mon, 29 May 2000 20:23:20 -0400 From: Lee Cremeans To: freebsd-scsi@freebsd.org Subject: Symbios dual ultra-wide woes Message-ID: <20000529202320.A403@lcremeans.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just got a Symbios SYM22801 (53C876-based) card handed to me last week, and I decided to put it in my machine to replace a less-capable Adaptec AVA-2904. I've run into an interesting problem. I'm not sure if it's cabling-related or not, but the cables do seem to make a difference. Here's how my setup works: ID 5 ID 6 +-----------------+ +-----------------+ | UMAX scanner |----narrow SCSI---| Archive DDS-1 | | (Astra 1220S) | | | +-----------------+---terminator +-----------------+ | | CS Electronics 68-pin VHDCI<->50-pin Amphenol cable -->| | +----------------------+ | (ext 68-pin) | | SYM22801 channel B | | | | (int 50-pin) | +----------------------+ | | ID 4 +----------------------+ | TEAC CD-R55S | | (terminated) | +----------------------+ Now, here's the interesting part. - When I have *only* the external cable connected, the channel works without errors. - When I have *only* the CD-R55 connected, it also works fine. - If I have the external stuff on channel A, and the internal stuff on channel B (or vice versa), that works. - However, when I have both connected to channel B, I get this mess: sym1:4: ERROR (0:48) (2-21-0) (f/35) @ (scriptb 2e8:11000020). sym1: script cmd = 88080000 sym1: regdump: da 10 80 35 47 0f 04 0a 01 02 00 21 80 01 09 00 00 52 dc 01 08 ff ff ff. (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. over and over again, until I reboot the machine. I've not yet tried the old ncr driver on it. I've tried setting the channel switches to INT50 ON and HIGH TERM ON, but to no avail. I could put the CD-R on channel A for now, but when I get a SCSI disk to go there, I want to reserve channel A for it and other-high speed stuff, and channel B for the slow things. Any idea what's going on here? -lee -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremeans@erols.com | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 30 7:18:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from web1905.mail.yahoo.com (web1905.mail.yahoo.com [128.11.23.54]) by hub.freebsd.org (Postfix) with SMTP id 7778237B6DF for ; Tue, 30 May 2000 07:18:09 -0700 (PDT) (envelope-from p_k_nandan@yahoo.com) Received: (qmail 28109 invoked by uid 60001); 30 May 2000 14:18:04 -0000 Message-ID: <20000530141804.28108.qmail@web1905.mail.yahoo.com> Received: from [203.197.179.17] by web1905.mail.yahoo.com; Tue, 30 May 2000 07:18:04 PDT Date: Tue, 30 May 2000 07:18:04 -0700 (PDT) From: "NandaKumar P.K." Subject: Debugging the HBA driver (SCSI-CAM) To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am in the process of debugging my HBA driver for our Fibre Channel RAID adapter. It has registered with the CAM layer and i can communicate to the disks connected. I did disklabel,newfs and mounted the disk and copied some files. It works fine till i copy small no. of files, but when i copy a large no. of files system just stops responding. In between while copying the files it gives the "input/output error". Any ideas how to proceed with my debugging ? Will it help debugging with CAM layer printf's ? We tried once but none of the printfs were coming ? Regards, Nandan Regards, Nandan __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 30 11:55:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lsi.lsil.com (lsi.lsil.com [147.145.40.2]) by hub.freebsd.org (Postfix) with ESMTP id 0408637B505 for ; Tue, 30 May 2000 11:55:39 -0700 (PDT) (envelope-from pdelaney@lsil.com) Received: from mhbs.lsil.com ([147.145.31.100]) by lsi.lsil.com (8.9.3+Sun/8.9.1) with ESMTP id LAA10218 for ; Tue, 30 May 2000 11:55:31 -0700 (PDT) Received: from inca.co.lsil.com by mhbs.lsil.com with ESMTP; Tue, 30 May 2000 11:55:21 -0700 Received: from exw-kansas.ks.symbios.com (exw-kansas.ks.lsil.com [153.79.8.7]) by inca.co.lsil.com (8.9.3/8.9.3) with ESMTP id MAA19443; Tue, 30 May 2000 12:55:12 -0600 (MDT) Received: by exw-kansas.ks.lsil.com with Internet Mail Service (5.5.2650.21) id ; Tue, 30 May 2000 13:54:36 -0500 Message-Id: From: "Delaney, Pam" To: "'Lee Cremeans'" , freebsd-scsi@FreeBSD.ORG Subject: RE: Symbios dual ultra-wide woes Date: Tue, 30 May 2000 13:54:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFCA68.7FFA5EEC" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BFCA68.7FFA5EEC Content-Type: text/plain; charset="iso-8859-1" Lee - The 22801 specifically prohibits using the configuration you show. You can use all narrow or all wide, but cannot mix wide and narrow (in general). If the 22801 is at the end of the bus, termination at the board is enabled. If the 22801 is in the middle of the bus, the board will terminate the upper 9 lines if the cable is narrow, otherwise no termination is used. You have a wide cable and a narrow cable, the board hardware defaults to the wide bus case and provides no termination at all. Thus the upper 9 lines are floating. Options: 1) Use different channels (the board will autoterminate each channel). 2) Get a cable that terminates the upper 8 bits. I checked the web and CS electronics does manufacture a cable (T68D I think) that is a 68->50 with termination at both ends. You will need something like: term ---68->50 cable---term Cables that terminate only one end will not work, because the signal being applied to the 22801 has to look like it is coming from a narrow bus. -pamela > -----Original Message----- > From: Lee Cremeans [mailto:lcremeans@erols.com] > Sent: Monday, May 29, 2000 7:23 PM > To: freebsd-scsi@FreeBSD.ORG > Subject: Symbios dual ultra-wide woes > > > I just got a Symbios SYM22801 (53C876-based) card handed to > me last week, > and I decided to put it in my machine to replace a > less-capable Adaptec > AVA-2904. I've run into an interesting problem. I'm not sure if it's > cabling-related or not, but the cables do seem to make a difference. > > Here's how my setup works: > > ID 5 ID 6 > +-----------------+ +-----------------+ > | UMAX scanner |----narrow SCSI---| Archive DDS-1 | > | (Astra 1220S) | | | > +-----------------+---terminator +-----------------+ > | > | > CS Electronics 68-pin VHDCI<->50-pin Amphenol cable -->| > | > +----------------------+ > | (ext 68-pin) | > | SYM22801 channel B | > | | > | (int 50-pin) | > +----------------------+ > | > | ID 4 > +----------------------+ > | TEAC CD-R55S | > | (terminated) | > +----------------------+ > > Now, here's the interesting part. > > - When I have *only* the external cable connected, the > channel works without > errors. > > - When I have *only* the CD-R55 connected, it also works fine. > > - If I have the external stuff on channel A, and the internal stuff on > channel B (or vice versa), that works. > > - However, when I have both connected to channel B, I get this mess: > > sym1:4: ERROR (0:48) (2-21-0) (f/35) @ (scriptb 2e8:11000020). > sym1: script cmd = 88080000 > sym1: regdump: da 10 80 35 47 0f 04 0a 01 02 00 21 80 01 09 > 00 00 52 dc 01 > 08 ff ff ff. > (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. > > over and over again, until I reboot the machine. I've not yet > tried the old > ncr driver on it. I've tried setting the channel switches to > INT50 ON and > HIGH TERM ON, but to no avail. > > I could put the CD-R on channel A for now, but when I get a > SCSI disk to > go there, I want to reserve channel A for it and other-high > speed stuff, and > channel B for the slow things. Any idea what's going on here? > > -lee > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on > WTnet) | > | lcremeans@erols.com | http://wakky.dyndns.org/~lee | > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > ------_=_NextPart_001_01BFCA68.7FFA5EEC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Symbios dual ultra-wide woes

Lee -

The 22801 specifically prohibits using the = configuration
you show.  You can use all narrow or all wide, = but
cannot mix wide and narrow (in general).

If the 22801 is at the end of the bus, = termination
at the board is enabled.  If the 22801 is in = the middle
of the bus, the board will terminate the upper 9 = lines if
the cable is narrow, otherwise no termination is = used.
You have a wide cable and a narrow cable, the = board
hardware defaults to the wide bus case and provides = no
termination at all.  Thus the upper 9 lines are = floating.

Options:
1) Use different channels (the board will = autoterminate
    each channel).
2) Get a cable that terminates the upper 8 = bits.  I checked
    the web and CS electronics does = manufacture a cable (T68D
    I think) that is a 68->50 with = termination at both ends.
    You will need something = like:
         = term ---68->50 cable---term
    Cables that terminate only one = end will not work, because
    the signal being applied to the = 22801 has to look like it
    is coming from a narrow = bus.
  
        -pamela

> -----Original Message-----
> From: Lee Cremeans [mailto:lcremeans@erols.com]
> Sent: Monday, May 29, 2000 7:23 PM
> To: freebsd-scsi@FreeBSD.ORG
> Subject: Symbios dual ultra-wide woes
>
>
> I just got a Symbios SYM22801 (53C876-based) = card handed to
> me last week,
> and I decided to put it in my machine to = replace a
> less-capable Adaptec
> AVA-2904. I've run into an interesting problem. = I'm not sure if it's
> cabling-related or not, but the cables do seem = to make a difference.
>
> Here's how my setup works:
>    
>       ID = 5            = ;            = ;           ID = 6
> = +-----------------+         = ;         = +-----------------+
> |  UMAX  scanner  |----narrow = SCSI---|  Archive DDS-1  |
> |  (Astra 1220S)  = |           =      = |            = ;     |
> = +-----------------+---terminator     = +-----------------+
>       =         =         =         =         =         =        |
>       =         =         =         =         =         =        |
> CS Electronics 68-pin VHDCI<->50-pin = Amphenol cable -->|
>       =         =         =         =         =         =        |
>       =         =         =              = +----------------------+
>       =         =         =              = |     (ext 68-pin)     |
>       =         =         =             = |  SYM22801 channel B  |  
>       =         =         =              = |            = ;          |
>       =         =         =              = |     (int 50-pin)     |
>       =         =         =              = +----------------------+  
>       =         =         =         =         =         |
>       =         =         =         =         =         |  ID 4
>       =         =         =              = +----------------------+
>       =         =         =              = |    TEAC CD-R55S      |
>       =         =         =              = |    (terminated)      |
>       =         =         =              = +----------------------+
>
> Now, here's the interesting part.
>
> - When I have *only* the external cable = connected, the
> channel works without
> errors.
>
> - When I have *only* the CD-R55 connected, it = also works fine.
>
> - If I have the external stuff on channel A, = and the internal stuff on
> channel B (or vice versa), that works.
>
> - However, when I have both connected to = channel B, I get this mess:
>
> sym1:4: ERROR (0:48) (2-21-0) (f/35) @ (scriptb = 2e8:11000020).
> sym1: script cmd =3D 88080000
> sym1: regdump: da 10 80 35 47 0f 04 0a 01 02 00 = 21 80 01 09
> 00 00 52 dc 01
> 08 ff ff ff.
> (noperiph:sym1:0:-1:-1): SCSI BUS reset = detected.
>
> over and over again, until I reboot the = machine. I've not yet
> tried the old
> ncr driver on it. I've tried setting the = channel switches to
> INT50 ON and
> HIGH TERM ON, but to no avail.
>
> I could put the CD-R on channel A for now, but = when I get a
> SCSI disk to
> go there, I want to reserve channel A for it = and other-high
> speed stuff, and
> channel B for the slow things. Any idea what's = going on here?
>
> -lee
>
> --
> = +--------------------------------------------------------------------+
> |      Lee Cremeans -- = Manassas, VA, USA  (WakkyMouse on
> WTnet)      |  =
> = |         lcremeans@erols.com | = http://wakky.dyndns.org/~lee   &nbs= p;     |
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-scsi" in = the body of the message
>

------_=_NextPart_001_01BFCA68.7FFA5EEC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 30 12: 4:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52]) by hub.freebsd.org (Postfix) with ESMTP id 6287137BDFF for ; Tue, 30 May 2000 12:04:15 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from ppp-171-234.villette.club-internet.fr (ppp-171-234.villette.club-internet.fr [195.36.171.234]) by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA12178; Tue, 30 May 2000 21:04:06 +0200 (MET DST) Date: Tue, 30 May 2000 20:40:34 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Lee Cremeans Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Symbios dual ultra-wide woes In-Reply-To: <20000529202320.A403@lcremeans.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 29 May 2000, Lee Cremeans wrote: > I just got a Symbios SYM22801 (53C876-based) card handed to me last week, > and I decided to put it in my machine to replace a less-capable Adaptec > AVA-2904. I've run into an interesting problem. I'm not sure if it's > cabling-related or not, but the cables do seem to make a difference. >=20 > Here's how my setup works: > =20 > ID 5 ID 6 > +-----------------+ +-----------------+ > | UMAX scanner |----narrow SCSI---| Archive DDS-1 | > | (Astra 1220S) | =09 | | > +-----------------+---terminator +-----------------+ > =09=09=09=09=09=09 | > =09=09=09=09=09=09 | > CS Electronics 68-pin VHDCI<->50-pin Amphenol cable -->| > =09=09=09=09=09=09 | > =09=09=09=09 +----------------------+ > =09=09=09=09 | (ext 68-pin) | > =09=09=09 | SYM22801 channel B |=09 > =09=09=09=09 | | > =09=09=09=09 | (int 50-pin) | > =09=09=09=09 +----------------------+=09 > =09=09=09=09=09=09| > =09=09=09=09=09=09| ID 4 > =09=09=09=09 +----------------------+ > =09=09=09=09 | TEAC CD-R55S=09 | > =09=09=09=09 |=09 (terminated)=09 | > =09=09=09=09 +----------------------+ > Now, here's the interesting part.=20 >=20 > - When I have *only* the external cable connected, the channel works with= out > errors. >=20 > - When I have *only* the CD-R55 connected, it also works fine.=20 >=20 > - If I have the external stuff on channel A, and the internal stuff on > channel B (or vice versa), that works. >=20 > - However, when I have both connected to channel B, I get this mess:=20 >=20 > sym1:4: ERROR (0:48) (2-21-0) (f/35) @ (scriptb 2e8:11000020). ^ This '8' means `SCSI GROSS ERROR' When such error happens, it is likely the SCSI BUS that is not good enough or has flaws. > sym1: script cmd =3D 88080000 > sym1: regdump: da 10 80 35 47 0f 04 0a 01 02 00 21 80 01 09 00 00 52 dc 0= 1 > 08 ff ff ff. > (noperiph:sym1:0:-1:-1): SCSI BUS reset detected. >=20 > over and over again, until I reboot the machine. I've not yet tried the o= ld > ncr driver on it. In my opinion, miracle will not occur with the `ncr', but this should be tried anyway. > I've tried setting the channel switches to INT50 ON and > HIGH TERM ON, but to no avail. HIGH TERM ON / LOW TERM OFF looks correct. I donnot have the doc of this controller, but if it is possible to also force the other terminator part to OFF, this could not be bad. I don't know what INT50 ON means. > I could put the CD-R on channel A for now, but when I get a SCSI disk to > go there, I want to reserve channel A for it and other-high speed stuff, = and > channel B for the slow things. Any idea what's going on here?=20 I would suspect the following causes in that order: - The auto-termination stuff of the controller being confused by the external 68-50 converter. - The scanner making some shit on the BUS. - A not good enough or just bad cable chunk or terminator. - A flaw or unexpected feature of the 68-50 converter. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 16:39:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 0086137C022 for ; Wed, 31 May 2000 16:39:42 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id TAA00403 for ; Wed, 31 May 2000 19:39:38 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 31 May 2000 19:42:28 -0400 To: freebsd-scsi@freebsd.org From: John Subject: Dying connection? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I ran into some really odd (to me, that is) problems. Via Samba I was trying to move items from my windows PC to my FreeBSD (4.0-Stable) box. During these transfers I will occasionally get the following error which (as far as I've figured out) requires a complete power-down to correct. Any thoughts? Thanks, John The error is: May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out while idle, SEQADDR == 0xa May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset Message Sent May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out in Message-out phase, SEQADDR == 0x157 May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, status = 34b May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack I've also got the scsi info from dmesg: ahc0: port 0x6000-0x60ff mem 0xf1200000-0xf1200fff irq 11 at device 17.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 7) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da1 at ahc0 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) Mounting root from ufs:/dev/sd0s1a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 16:51:57 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 3281937B759 for ; Wed, 31 May 2000 16:51:53 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA86314; Wed, 31 May 2000 17:51:40 -0600 (MDT) (envelope-from ken) Date: Wed, 31 May 2000 17:51:39 -0600 From: "Kenneth D. Merry" To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000531175139.A86282@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu>; from papalia@udel.edu on Wed, May 31, 2000 at 07:42:28PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 19:42:28 -0400, John wrote: > Hi all, > > I ran into some really odd (to me, that is) problems. Via Samba I was > trying to move items from my windows PC to my FreeBSD (4.0-Stable) > box. During these transfers I will occasionally get the following error > which (as far as I've figured out) requires a complete power-down to > correct. Any thoughts? > > Thanks, > John > > > The error is: > > May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out > while idle, SEQADDR == 0xa > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset Message Sent > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out in > Message-out phase, SEQADDR == 0x157 > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, > status = 34b > May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs > aborted > May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack The drive is going "out to lunch" and not coming back for a full minute. We hit it with a bus device reset to wake it up, and then it appears we sent a bus reset after we got another timeout in the message out phase. Perhaps something had a stuck signal on the bus. > da1 at ahc0 bus 0 target 8 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) If I had to guess, I'd say it is a firmware problem with the drive, but it's hard to say for sure. You might also want to check your cabling and termination. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 16:56:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 3B02737B759 for ; Wed, 31 May 2000 16:56:13 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id TAA00490; Wed, 31 May 2000 19:56:02 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 31 May 2000 19:58:51 -0400 To: "Kenneth D. Merry" From: John Subject: Re: Dying connection? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000531175139.A86282@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hi all, > > > > I ran into some really odd (to me, that is) problems. Via Samba I was > > trying to move items from my windows PC to my FreeBSD (4.0-Stable) > > box. During these transfers I will occasionally get the following error > > which (as far as I've figured out) requires a complete power-down to > > correct. Any thoughts? > > > > Thanks, > > John > > > > > > The error is: > > > > May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out > > while idle, SEQADDR == 0xa > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset > Message Sent > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out in > > Message-out phase, SEQADDR == 0x157 > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, > > status = 34b > > May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs > > aborted > > May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack > >The drive is going "out to lunch" and not coming back for a full minute. > >We hit it with a bus device reset to wake it up, and then it appears we >sent a bus reset after we got another timeout in the message out phase. > >Perhaps something had a stuck signal on the bus. Is it possible to kick-start or "burp" the bus when that happens, other than resetting the box? > > da1 at ahc0 bus 0 target 8 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > > da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) > >If I had to guess, I'd say it is a firmware problem with the drive, but >it's hard to say for sure. You might also want to check your cabling and >termination. I'll check the cables and terminations just as soon as my backup finishes. I'm not sure if it would be either though since this drive configuration has been running fine for almost 6 months. Thanks again, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 17: 1:42 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 C78AF37B759 for ; Wed, 31 May 2000 17:01:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA86488; Wed, 31 May 2000 18:01:35 -0600 (MDT) (envelope-from ken) Date: Wed, 31 May 2000 18:01:35 -0600 From: "Kenneth D. Merry" To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000531180135.A86440@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <20000531175139.A86282@panzer.kdm.org> <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu>; from papalia@udel.edu on Wed, May 31, 2000 at 07:58:51PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 19:58:51 -0400, John wrote: > > > May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out > > > while idle, SEQADDR == 0xa > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset > > Message Sent > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out in > > > Message-out phase, SEQADDR == 0x157 > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, > > > status = 34b > > > May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs > > > aborted > > > May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack > > > >The drive is going "out to lunch" and not coming back for a full minute. > > > >We hit it with a bus device reset to wake it up, and then it appears we > >sent a bus reset after we got another timeout in the message out phase. > > > >Perhaps something had a stuck signal on the bus. > > Is it possible to kick-start or "burp" the bus when that happens, other > than resetting the box? I don't think there is a way to get a device back from an invalidated pack, short of pulling it off the bus, rescanning, putting it back on, and rescanning again. With an invalidated pack, a fatal error has occured with the device in question, and we've given up on trying to revive it. Rebooting the machine should have the same effect as powering it off or resetting it. > > > da1 at ahc0 bus 0 target 8 lun 0 > > > da1: Fixed Direct Access SCSI-2 device > > > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > > > da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) > > > >If I had to guess, I'd say it is a firmware problem with the drive, but > >it's hard to say for sure. You might also want to check your cabling and > >termination. > > I'll check the cables and terminations just as soon as my backup > finishes. I'm not sure if it would be either though since this drive > configuration has been running fine for almost 6 months. The drive may be going bad. It would be interesting to see if the problem goes away if you take the Micropolis out of the system. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 17:40: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id DCD9F37B7A5 for ; Wed, 31 May 2000 17:40:05 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id UAA00647; Wed, 31 May 2000 20:40:02 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000531204111.00ad0660@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 31 May 2000 20:42:50 -0400 To: "Kenneth D. Merry" From: John Subject: Re: Dying connection? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000531180135.A86440@panzer.kdm.org> References: <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <20000531175139.A86282@panzer.kdm.org> <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > May 31 18:46:08 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed out > > > > while idle, SEQADDR == 0xa > > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Queuing a BDR SCB > > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): Bus Device Reset > > > Message Sent > > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): SCB 0x30 - timed > out in > > > > Message-out phase, SEQADDR == 0x157 > > > > May 31 18:46:20 merlin /kernel: (da1:ahc0:0:8:0): no longer in timeout, > > > > status = 34b > > > > May 31 18:46:20 merlin /kernel: ahc0: Issued Channel A Bus Reset. 1 > SCBs > > > > aborted > > > > May 31 18:46:22 merlin /kernel: (da1:ahc0:0:8:0): Invalidating pack > > > > > >The drive is going "out to lunch" and not coming back for a full minute. > > > > > >We hit it with a bus device reset to wake it up, and then it appears we > > >sent a bus reset after we got another timeout in the message out phase. > > > > > >Perhaps something had a stuck signal on the bus. > > > > Is it possible to kick-start or "burp" the bus when that happens, other > > than resetting the box? > >I don't think there is a way to get a device back from an invalidated pack, >short of pulling it off the bus, rescanning, putting it back on, and >rescanning again. > >With an invalidated pack, a fatal error has occured with the device in >question, and we've given up on trying to revive it. > >Rebooting the machine should have the same effect as powering it off or >resetting it. > > > > > da1 at ahc0 bus 0 target 8 lun 0 > > > > da1: Fixed Direct Access SCSI-2 device > > > > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > > > > da1: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) > > > > > >If I had to guess, I'd say it is a firmware problem with the drive, but > > >it's hard to say for sure. You might also want to check your cabling and > > >termination. > > > > I'll check the cables and terminations just as soon as my backup > > finishes. I'm not sure if it would be either though since this drive > > configuration has been running fine for almost 6 months. > >The drive may be going bad. It would be interesting to see if the problem >goes away if you take the Micropolis out of the system. Now, THAT is not exactly an easy thing to do.... all my home directories are on the 9.1G micropolis, and that includes all my saves from my windows box - which includes all my school work, email, and research.... so, unfortunately I can't test that idea easily :) --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 17:46:23 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 1F10437B935 for ; Wed, 31 May 2000 17:46:19 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA86764; Wed, 31 May 2000 18:46:16 -0600 (MDT) (envelope-from ken) Date: Wed, 31 May 2000 18:46:16 -0600 From: "Kenneth D. Merry" To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000531184615.A86744@panzer.kdm.org> References: <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <20000531175139.A86282@panzer.kdm.org> <4.3.1.2.20000531195721.00ad3b50@mail.udel.edu> <20000531180135.A86440@panzer.kdm.org> <4.3.1.2.20000531204111.00ad0660@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000531204111.00ad0660@mail.udel.edu>; from papalia@udel.edu on Wed, May 31, 2000 at 08:42:50PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 20:42:50 -0400, John wrote: > > > > I'll check the cables and terminations just as soon as my backup > > > finishes. I'm not sure if it would be either though since this drive > > > configuration has been running fine for almost 6 months. > > > >The drive may be going bad. It would be interesting to see if the problem > >goes away if you take the Micropolis out of the system. > > Now, THAT is not exactly an easy thing to do.... all my home directories > are on the 9.1G micropolis, and that includes all my saves from my windows > box - which includes all my school work, email, and research.... so, > unfortunately I can't test that idea easily :) Well, it's a good thing you've got a backup. :) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 19:58:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 3C7B737BA2C; Wed, 31 May 2000 19:58:22 -0700 (PDT) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id MAA87297; Thu, 1 Jun 2000 12:58:19 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma087284; Thu, 1 Jun 00 12:58:18 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id MAA05515; Thu, 1 Jun 2000 12:58:18 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Thu, 1 Jun 2000 12:58:18 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: QLogic 2200 to IBM ESS (Shark) via SAN Data Gateway. 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 Is anyone using a QLogic 2200 FC card that can help me with a problem. I'm trying to get a 4.0-STABLE box qith a QLogic 2200 card talking to an IBM ESS 2105-E20 (Shark) via an IBM SAN Data Gateway. The card is seeing the two LUNS as delivered by the ESS through the Gateway but they are not being properly configured by the isp driver. Here is some dmesg output; isp0: port 0xfc00-0xfcff mem 0xfeb00000-0xfeb00fff irq 5 at device 1.0 on pci3 isp0: Firmware State Config Wait -> Ready isp0: Target 0 (Loop 0x0) Port ID 0xef role Target arrived Port WWN 0x20010060451604e5 Node WWN 0x10000060451604e5 pass2 at isp0 bus 0 target 0 lun 0 pass2: Fixed Storage Arrray SCSI-3 device pass2: 100.000MB/s transfers, Tagged Queueing Enabled pass3 at isp0 bus 0 target 0 lun 1 pass3: Fixed Storage Arrray SCSI-3 device pass3: 100.000MB/s transfers, Tagged Queueing Enabled pass4 at isp0 bus 0 target 0 lun 2 pass4: Fixed Storage Arrray SCSI-3 device pass4: 100.000MB/s transfers, Tagged Queueing Enabled pass5 at isp0 bus 0 target 0 lun 3 pass5: Fixed Storage Arrray SCSI-3 device pass5: 100.000MB/s transfers, Tagged Queueing Enabled pass6 at isp0 bus 0 target 0 lun 4 pass6: Fixed Storage Arrray SCSI-3 device pass6: 100.000MB/s transfers, Tagged Queueing Enabled pass7 at isp0 bus 0 target 0 lun 5 pass7: Fixed Storage Arrray SCSI-3 device pass7: 100.000MB/s transfers, Tagged Queueing Enabled pass8 at isp0 bus 0 target 0 lun 6 pass8: Fixed Storage Arrray SCSI-3 device pass8: 100.000MB/s transfers, Tagged Queueing Enabled pass9 at isp0 bus 0 target 0 lun 7 pass9: Fixed Storage Arrray SCSI-3 device pass9: 100.000MB/s transfers, Tagged Queueing Enabled There is an 8Gb LUN at 1, and a 20Gb LUN at 2. LUN 0 is the Gateway itself. There is nothing at LUN 3->7. I had to enable the bios on the QLogic card to get this far. Without the bios enabled the card just timed out in the probe. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 20:23: 5 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 7AE5A37BA2E; Wed, 31 May 2000 20:22:58 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA87582; Wed, 31 May 2000 21:22:29 -0600 (MDT) (envelope-from ken) Date: Wed, 31 May 2000 21:22:29 -0600 From: "Kenneth D. Merry" To: Carl Makin Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: QLogic 2200 to IBM ESS (Shark) via SAN Data Gateway. Message-ID: <20000531212228.A87365@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from carl@xena.IPAustralia.gov.au on Thu, Jun 01, 2000 at 12:58:18PM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 01, 2000 at 12:58:18 +1000, Carl Makin wrote: > > Is anyone using a QLogic 2200 FC card that can help me with a problem. > > I'm trying to get a 4.0-STABLE box qith a QLogic 2200 card talking to an > IBM ESS 2105-E20 (Shark) via an IBM SAN Data Gateway. > > The card is seeing the two LUNS as delivered by the ESS through the > Gateway but they are not being properly configured by the isp driver. Here > is some dmesg output; > > isp0: port 0xfc00-0xfcff mem > 0xfeb00000-0xfeb00fff irq 5 at device 1.0 on pci3 > > isp0: Firmware State Config Wait -> Ready > isp0: Target 0 (Loop 0x0) Port ID 0xef role Target arrived > Port WWN 0x20010060451604e5 > Node WWN 0x10000060451604e5 > > pass2 at isp0 bus 0 target 0 lun 0 > pass2: Fixed Storage Arrray SCSI-3 device > pass2: 100.000MB/s transfers, Tagged Queueing Enabled > pass3 at isp0 bus 0 target 0 lun 1 > pass3: Fixed Storage Arrray SCSI-3 device > pass3: 100.000MB/s transfers, Tagged Queueing Enabled > pass4 at isp0 bus 0 target 0 lun 2 > pass4: Fixed Storage Arrray SCSI-3 device > pass4: 100.000MB/s transfers, Tagged Queueing Enabled [ ... ] > There is an 8Gb LUN at 1, and a 20Gb LUN at 2. LUN 0 is the Gateway > itself. There is nothing at LUN 3->7. > > I had to enable the bios on the QLogic card to get this far. Without the > bios enabled the card just timed out in the probe. You probably won't get much help on the QLogic side of things until Matt Jacob gets back from vacation. But, you may be able to play with things a bit in the mean time. If those devices use the typical direct access command set, you can probably use the attached patch to make the da(4) driver attach to the luns on the array. Then you can try to disklabel it, newfs, etc. The patch is against -current, hopefully it'll apply okay to -stable. Ken -- Kenneth Merry ken@kdm.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_da.c.array.20000531" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c#9 - /a/ken/perforce3/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c ==== *** /tmp/tmp.87433.0 Wed May 31 21:15:39 2000 --- /a/ken/perforce3/FreeBSD-ken/src/sys/cam/scsi/scsi_da.c Wed May 31 21:15:22 2000 *************** *** 847,853 **** cgd = (struct ccb_getdev *)arg; if (SID_TYPE(&cgd->inq_data) != T_DIRECT ! && SID_TYPE(&cgd->inq_data) != T_OPTICAL) break; /* --- 847,854 ---- cgd = (struct ccb_getdev *)arg; if (SID_TYPE(&cgd->inq_data) != T_DIRECT ! && SID_TYPE(&cgd->inq_data) != T_OPTICAL ! && SID_TYPE(&cgd->inq_data) != T_STORARRAY) break; /* --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 21: 6:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id 58A7937BC90; Wed, 31 May 2000 21:06:23 -0700 (PDT) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id OAA91491; Thu, 1 Jun 2000 14:05:44 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma091484; Thu, 1 Jun 00 14:05:29 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id OAA17676; Thu, 1 Jun 2000 14:05:28 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Thu, 1 Jun 2000 14:05:27 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: QLogic 2200 to IBM ESS (Shark) via SAN Data Gateway. In-Reply-To: <20000531212228.A87365@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Ken, On Wed, 31 May 2000, Kenneth D. Merry wrote: > On Thu, Jun 01, 2000 at 12:58:18 +1000, Carl Makin wrote: > > Is anyone using a QLogic 2200 FC card that can help me with a problem. > You probably won't get much help on the QLogic side of things until Matt > Jacob gets back from vacation. I compiled the 2200 firmware into the driver in the kernel and applied your patch (and enabled SMP as this is a SMP box) and it's now recognising the disks fine. It throws an error on LUN 0 which is the Gateway box, not a disk LUN but now maps the 2 disk LUNS fine. > The patch is against -current, hopefully it'll apply okay to -stable. Applied fine with an offset of -10. :) FYI, bash-2.04# ./rawio -a -I ESS-FC -v 1 /dev/da1c Test ID K/sec /sec %User %Sys %Total RR ESS-FC 8396.3 522 0.2 4.3 4.4 16384 SR ESS-FC 21633.9 1320 0.4 9.7 10.1 16384 RW ESS-FC 5498.9 340 0.2 2.6 2.8 16384 SW ESS-FC 18207.9 1111 0.3 8.3 8.6 16384 I'm happy enough with that! Many thanks! Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 21:38:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 2CAFF37BF8A for ; Wed, 31 May 2000 21:38:20 -0700 (PDT) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id XAA07399; Wed, 31 May 2000 23:42:47 -0500 Message-ID: <3935DAA5.7859492B@raccoon.com> Date: Wed, 31 May 2000 22:38:13 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wow! I was going to post this same thing tonight... I got the same type of error message today on one of my machines. I run 4.0-RELEASE, Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any problems with the drive over the past 10 days since I installed it. I recieved the error, while I was hitting the drive hard doing a 1GM ftp and processing a 400M http log file using urchin. I was wondering it if might be a firmware problem on the 2940 or the drive revolving around tag queueing. ahc0: port 0xec00-0xecff mem 0xfebef000-0xfebeffff i rq 11 at device 18.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBsda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 31 22:38: 2 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 E7EB237B93A for ; Wed, 31 May 2000 22:37:59 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA88574; Wed, 31 May 2000 23:37:54 -0600 (MDT) (envelope-from ken) Date: Wed, 31 May 2000 23:37:54 -0600 From: "Kenneth D. Merry" To: John Lengeling Cc: John , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000531233754.A88537@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3935DAA5.7859492B@raccoon.com>; from johnl@raccoon.com on Wed, May 31, 2000 at 10:38:13PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 31, 2000 at 22:38:13 -0500, John Lengeling wrote: > > Wow! I was going to post this same thing tonight... I got the same type > of error message today on one of my machines. I run 4.0-RELEASE, > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > problems with the drive over the past 10 days since I installed it. > > I recieved the error, while I was hitting the drive hard doing a 1GM ftp > and processing a 400M http log file using urchin. I was wondering it if > might be a firmware problem on the 2940 or the drive revolving around > tag queueing. I kinda doubt it's a tagged queueing problem with your drives, I think both of those Seagates are known good. As for the controller, we don't use Adaptec's firmware, and no one else has reported Adaptec driver problems. You'll have to post the error messages you got. While they may look similar, there are many different types of timeout messages, and we'll only be able to speculate on what the problem is if you post the errors. 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 Jun 1 10:31:20 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 409C437B5E8 for ; Thu, 1 Jun 2000 10:31:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA30817; Thu, 1 Jun 2000 10:27:08 -0700 Date: Thu, 1 Jun 2000 10:30:06 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Carl Makin Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2200, IBM SAN Data Gateway/Enterprise Storage Server. 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 just back from vacation....sorry for the delay.. Yeah, the deal here is that 2200 card onboard f/w has the SCCLUN code enabled. But there's no way to tell a priori that it is. Unfortunately, SCCLUN enabling puts the lun at a different spot in a request queue entry. I'm very curious as to any issues you might run into with the Shark. Please let me know how it's going. -matt On Mon, 29 May 2000, Carl Makin wrote: > > Hi Matthew, > I'm trying to hook up a FreeBSD 4.0-RELEASE box with a QLogic 2200 card to > an IBM Shark (ESS E20) storage server via an IBM SAN Data Gateway. > > If I disable the bios on the card I get an error about initialising the > loop. If I enable the bios I get the following; > > isp0: port 0xfc00-0xfcff mem > 0xfeb00000-0xfeb00fff irq 5 at device 1.0 on pci3 > . > . > isp0: Loop UP > Waiting 15 seconds for SCSI devices to settle > isp0: Firmware State Config Wait -> Ready > isp0: Target 0 (Loop 0x0) Port ID 0xef role Target arrived > Port WWN 0x20010060451604e5 > Node WWN 0x10000060451604e5 > . > . > pass2 at isp0 bus 0 target 0 lun 0 > pass2: Fixed Storage Arrray SCSI-3 device > pass2: 100.000MB/s transfers, Tagged Queueing Enabled > pass3 at isp0 bus 0 target 0 lun 1 > pass3: Fixed Storage Arrray SCSI-3 device > pass3: 100.000MB/s transfers, Tagged Queueing Enabled > pass4 at isp0 bus 0 target 0 lun 2 > pass4: Fixed Storage Arrray SCSI-3 device > pass4: 100.000MB/s transfers, Tagged Queueing Enabled > pass5 at isp0 bus 0 target 0 lun 3 > pass5: Fixed Storage Arrray SCSI-3 device > pass5: 100.000MB/s transfers, Tagged Queueing Enabled > pass6 at isp0 bus 0 target 0 lun 4 > pass6: Fixed Storage Arrray SCSI-3 device > pass6: 100.000MB/s transfers, Tagged Queueing Enabled > pass7 at isp0 bus 0 target 0 lun 5 > pass7: Fixed Storage Arrray SCSI-3 device > pass7: 100.000MB/s transfers, Tagged Queueing Enabled > pass8 at isp0 bus 0 target 0 lun 6 > pass8: Fixed Storage Arrray SCSI-3 device > pass8: 100.000MB/s transfers, Tagged Queueing Enabled > pass9 at isp0 bus 0 target 0 lun 7 > pass9: Fixed Storage Arrray SCSI-3 device > pass9: 100.000MB/s transfers, Tagged Queueing Enabled > no devsw (majdev=0 bootdev=0xa0300000) > Mounting root from ufs:/dev/amrd0s2a > > (Note the 3 r's on Arrray! :) > > There should be two disk devices on LUN's 0 and 1 at target 0. > > If I use -Q and enter the cards firmware then it sees the two LUNS > correctly. > > Do you have any ideas on what could be happening? > > > Thanks, > > Carl. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 1 17:52:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id AA86C37B541 for ; Thu, 1 Jun 2000 17:52:10 -0700 (PDT) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id KAA21605; Fri, 2 Jun 2000 10:51:58 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma021592; Fri, 2 Jun 00 10:51:34 +1000 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.3) with ESMTP id KAA71297; Fri, 2 Jun 2000 10:51:34 +1000 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Fri, 2 Jun 2000 10:51:34 +1000 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: Matthew Jacob Cc: freebsd-scsi@freebsd.org Subject: Re: QLogic 2200, IBM SAN Data Gateway/Enterprise Storage Server. 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 Hi Matthew, On Thu, 1 Jun 2000, Matthew Jacob wrote: > just back from vacation....sorry for the delay.. No problems. Ken Merry replied with some info that helped. > Yeah, the deal here is that 2200 card onboard f/w has the SCCLUN code enabled. > But there's no way to tell a priori that it is. Unfortunately, SCCLUN enabling > puts the lun at a different spot in a request queue entry. Ok. I was using a generic kernel that doesn't have the f/w compiled in by default. I rebuilt the kernel with the 2200 f/w compiled in and included Ken's patch and the machine now recognises the drives. It also thinks the first LUN is a disk but gets an error trying to access it. The other two LUNS which really are disks now work fine. I get the following from rawio bash-2.04# ./rawio -a -I ESS-FC -v 1 /dev/da1c Test ID K/sec /sec %User %Sys %Total RR ESS-FC 8396.3 522 0.2 4.3 4.4 16384 SR ESS-FC 21633.9 1320 0.4 9.7 10.1 16384 RW ESS-FC 5498.9 340 0.2 2.6 2.8 16384 SW ESS-FC 18207.9 1111 0.3 8.3 8.6 16384 > I'm very curious as to any issues you might run into with the Shark. Please > let me know how it's going. Well the Shark doesn't natively support FC yet so we're using a "SAN Data Gateway" to map SCSI LUNS to FC LUNS. Native FC support for the Shark is expected soon so I'd expect better performance when it does. Thanks Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 1 20: 7:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 8DFD737B67B for ; Thu, 1 Jun 2000 20:07:34 -0700 (PDT) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id WAA04917; Thu, 1 Jun 2000 22:12:02 -0500 Message-ID: <393724F1.B90D3283@raccoon.com> Date: Thu, 01 Jun 2000 22:07:30 -0500 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: John , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@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 "Kenneth D. Merry" wrote: > > On Wed, May 31, 2000 at 22:38:13 -0500, John Lengeling wrote: > > > > Wow! I was going to post this same thing tonight... I got the same type > > of error message today on one of my machines. I run 4.0-RELEASE, > > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > > problems with the drive over the past 10 days since I installed it. > > > > I recieved the error, while I was hitting the drive hard doing a 1GM ftp > > and processing a 400M http log file using urchin. I was wondering it if > > might be a firmware problem on the 2940 or the drive revolving around > > tag queueing. > > I kinda doubt it's a tagged queueing problem with your drives, I think both > of those Seagates are known good. > > As for the controller, we don't use Adaptec's firmware, and no one else has > reported Adaptec driver problems. > > You'll have to post the error messages you got. While they may look > similar, there are many different types of timeout messages, and we'll only > be able to speculate on what the problem is if you post the errors. I wrote down the following error message: SCB 0x25 - timed out while idle, SEQADDR - 0xc Queueing a BDR SCB Bus Device Reset Message Sent no longer in timout, status = 34b Bus Device Reset on A:0 18 SCBs aborted Invalidating Pack johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 1 20:22:58 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 7154E37B70B for ; Thu, 1 Jun 2000 20:22:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA96929; Thu, 1 Jun 2000 21:22:49 -0600 (MDT) (envelope-from ken) Date: Thu, 1 Jun 2000 21:22:49 -0600 From: "Kenneth D. Merry" To: John Lengeling Cc: John , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000601212248.A96817@panzer.kdm.org> References: <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393724F1.B90D3283@raccoon.com>; from johnl@raccoon.com on Thu, Jun 01, 2000 at 10:07:30PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 01, 2000 at 22:07:30 -0500, John Lengeling wrote: > "Kenneth D. Merry" wrote: > > On Wed, May 31, 2000 at 22:38:13 -0500, John Lengeling wrote: > > > > > > Wow! I was going to post this same thing tonight... I got the same type > > > of error message today on one of my machines. I run 4.0-RELEASE, > > > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > > > problems with the drive over the past 10 days since I installed it. > > > > > > I recieved the error, while I was hitting the drive hard doing a 1GM ftp > > > and processing a 400M http log file using urchin. I was wondering it if > > > might be a firmware problem on the 2940 or the drive revolving around > > > tag queueing. > > > > I kinda doubt it's a tagged queueing problem with your drives, I think both > > of those Seagates are known good. > > > > As for the controller, we don't use Adaptec's firmware, and no one else has > > reported Adaptec driver problems. > > > > You'll have to post the error messages you got. While they may look > > similar, there are many different types of timeout messages, and we'll only > > be able to speculate on what the problem is if you post the errors. > > I wrote down the following error message: > > SCB 0x25 - timed out while idle, SEQADDR - 0xc > Queueing a BDR SCB > Bus Device Reset Message Sent > no longer in timout, status = 34b > Bus Device Reset on A:0 18 SCBs aborted > Invalidating Pack Then the messages are somewhat similar. It could be drive firmware, or perhaps cabling and termination. I haven't seen bad drive firmware on a Barracuda, so you might want to check your cabling and termination first. (I even have the same model 4G Barracuda, with slightly newer firmware.) Look for bent pins, crimped cables, cables that are too long, go too close to a power supply, etc. It could also be that the drive is going bad. You might want to check and see how many defects are in the grown defect list. (camcontrol defects will do it, see the camcontrol(8) manual for details.) So, there are any number of things that could be wrong. Sorry I can't give you a better answer. About all you can do is check the things you can, and make sure you have a backup in case the drive is going bad. 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 Jun 1 22:31:43 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 9A98C37B75D for ; Thu, 1 Jun 2000 22:31:37 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id BAA07473; Fri, 2 Jun 2000 01:32:10 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 02 Jun 2000 01:30:21 -0400 To: "Kenneth D. Merry" , John Lengeling From: John Subject: Re: Dying connection? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000601212248.A96817@panzer.kdm.org> References: <393724F1.B90D3283@raccoon.com> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Wow! I was going to post this same thing tonight... I got the same > type > > > > of error message today on one of my machines. I run 4.0-RELEASE, > > > > Adaptec 2940 v1.11 firmware, and a Seagate ST34371N. I haven't had any > > > > problems with the drive over the past 10 days since I installed it. > > > > > > > > I recieved the error, while I was hitting the drive hard doing a > 1GM ftp > > > > and processing a 400M http log file using urchin. I was wondering > it if > > > > might be a firmware problem on the 2940 or the drive revolving around > > > > tag queueing. > > > > > > I kinda doubt it's a tagged queueing problem with your drives, I > think both > > > of those Seagates are known good. > > > > > > As for the controller, we don't use Adaptec's firmware, and no one > else has > > > reported Adaptec driver problems. > > > > > > You'll have to post the error messages you got. While they may look > > > similar, there are many different types of timeout messages, and > we'll only > > > be able to speculate on what the problem is if you post the errors. > > > > I wrote down the following error message: > > > > SCB 0x25 - timed out while idle, SEQADDR - 0xc > > Queueing a BDR SCB > > Bus Device Reset Message Sent > > no longer in timout, status = 34b > > Bus Device Reset on A:0 18 SCBs aborted > > Invalidating Pack > >Then the messages are somewhat similar. > >It could be drive firmware, or perhaps cabling and termination. I haven't >seen bad drive firmware on a Barracuda, so you might want to check your >cabling and termination first. (I even have the same model 4G Barracuda, >with slightly newer firmware.) > >Look for bent pins, crimped cables, cables that are too long, go too close >to a power supply, etc. > >It could also be that the drive is going bad. You might want to check and >see how many defects are in the grown defect list. (camcontrol defects >will do it, see the camcontrol(8) manual for details.) Well, this kinda brings up another question that I had posted to freebsd-questions a few weeks back.... I found info describing *what* CAM is and is supposed to do (http://people.freebsd.org/~gibbs), but is there a read-me or a txt file or *anything* someplace to describe how to set it up and configure it correctly. Just point me in the right direction :) Thanks again, John P. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 1 22:36: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 25D3037B88F for ; Thu, 1 Jun 2000 22:35:51 -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 WAA01381; Thu, 1 Jun 2000 22:38:30 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006020538.WAA01381@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Cc: "Kenneth D. Merry" , John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? In-reply-to: Your message of "Fri, 02 Jun 2000 01:30:21 EDT." <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jun 2000 22:38:30 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Well, this kinda brings up another question that I had posted to > freebsd-questions a few weeks back.... I found info describing *what* CAM > is and is supposed to do (http://people.freebsd.org/~gibbs), but is there a > read-me or a txt file or *anything* someplace to describe how to set it up > and configure it correctly. Just point me in the right direction :) There's nothing to "set up" or "configure"; there are no user-maintainable parts inside. You have hardware issues; bitching about CAM is entirely irrelevant. -- \\ 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 Thu Jun 1 22:36: 3 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 5E95B37BC44 for ; Thu, 1 Jun 2000 22:35:55 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA97944; Thu, 1 Jun 2000 23:35:49 -0600 (MDT) (envelope-from ken) Date: Thu, 1 Jun 2000 23:35:49 -0600 From: "Kenneth D. Merry" To: John Cc: John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000601233549.A97833@panzer.kdm.org> References: <393724F1.B90D3283@raccoon.com> <4.3.1.2.20000531193727.00ac2af0@mail.udel.edu> <3935DAA5.7859492B@raccoon.com> <20000531233754.A88537@panzer.kdm.org> <393724F1.B90D3283@raccoon.com> <20000601212248.A96817@panzer.kdm.org> <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu>; from papalia@udel.edu on Fri, Jun 02, 2000 at 01:30:21AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 02, 2000 at 01:30:21 -0400, John wrote: > > >Then the messages are somewhat similar. > > > >It could be drive firmware, or perhaps cabling and termination. I haven't > >seen bad drive firmware on a Barracuda, so you might want to check your > >cabling and termination first. (I even have the same model 4G Barracuda, > >with slightly newer firmware.) > > > >Look for bent pins, crimped cables, cables that are too long, go too close > >to a power supply, etc. > > > >It could also be that the drive is going bad. You might want to check and > >see how many defects are in the grown defect list. (camcontrol defects > >will do it, see the camcontrol(8) manual for details.) > > Well, this kinda brings up another question that I had posted to > freebsd-questions a few weeks back.... I found info describing *what* CAM > is and is supposed to do (http://people.freebsd.org/~gibbs), but is there a > read-me or a txt file or *anything* someplace to describe how to set it up > and configure it correctly. Just point me in the right direction :) CAM is just the SCSI layer. There's not much to configure or setup. Most of what there is to know about configuring it can be found in LINT and GENERIC, and in the scsi(4) man page. (As well as in the man pages for the various peripheral drivers -- da(4), sa(4), cd(4), pass(4), etc.) 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 Jun 1 22:46: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id D1FAD37B63C; Thu, 1 Jun 2000 22:46:03 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.1.168.192.IN-ADDR.ARPA [192.168.1.2] (may be forged)) by wondermutt.net (8.9.3/8.9.3) with ESMTP id BAA07547; Fri, 2 Jun 2000 01:46:49 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 02 Jun 2000 01:44:56 -0400 To: Mike Smith From: John Subject: Re: Dying connection? Cc: "Kenneth D. Merry" , John Lengeling , freebsd-scsi@FreeBSD.ORG In-Reply-To: <200006020538.WAA01381@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Well, this kinda brings up another question that I had posted to > > freebsd-questions a few weeks back.... I found info describing *what* CAM > > is and is supposed to do (http://people.freebsd.org/~gibbs), but is > there a > > read-me or a txt file or *anything* someplace to describe how to set it up > > and configure it correctly. Just point me in the right direction :) > >There's nothing to "set up" or "configure"; there are no >user-maintainable parts inside. You have hardware issues; bitching about >CAM is entirely irrelevant. This was NOT a bitch. It was a request for help and info. I currently do NOT have cam enabled, so it would be wrong for me to "bitch" about it. I simply don't want to go willy-nilly adding kernel options without making sure that I'm doing it correctly. Also, it was suggested to use a cam feature to check out the hardware, and that is what I'm trying to do. Forgive me if attempting to understand what I'm doing is a crime. --John P To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 1 22:50:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 86DE837B53B for ; Thu, 1 Jun 2000 22:50:23 -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 WAA01439; Thu, 1 Jun 2000 22:53:20 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200006020553.WAA01439@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? In-reply-to: Your message of "Fri, 02 Jun 2000 01:44:56 EDT." <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jun 2000 22:53:20 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Well, this kinda brings up another question that I had posted to > > > freebsd-questions a few weeks back.... I found info describing *what* CAM > > > is and is supposed to do (http://people.freebsd.org/~gibbs), but is > > there a > > > read-me or a txt file or *anything* someplace to describe how to set it up > > > and configure it correctly. Just point me in the right direction :) > > > >There's nothing to "set up" or "configure"; there are no > >user-maintainable parts inside. You have hardware issues; bitching about > >CAM is entirely irrelevant. > > This was NOT a bitch. It was a request for help and info. I currently do > NOT have cam enabled, so it would be wrong for me to "bitch" about it. I > simply don't want to go willy-nilly adding kernel options without making > sure that I'm doing it correctly. Er, if you are using a SCSI device under 3.x or later you are using CAM. > Also, it was suggested to use a cam feature to check out the hardware, and > that is what I'm trying to do. Forgive me if attempting to understand what > I'm doing is a crime. I'm simply giving you the information you're looking for. Chill out, pal. 8) -- \\ 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 Thu Jun 1 22:50:34 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 1C76937BADE; Thu, 1 Jun 2000 22:50:29 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA98138; Thu, 1 Jun 2000 23:50:26 -0600 (MDT) (envelope-from ken) Date: Thu, 1 Jun 2000 23:50:26 -0600 From: "Kenneth D. Merry" To: John Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000601235026.A98092@panzer.kdm.org> References: <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000602013902.00ae1330@mail.udel.edu>; from papalia@udel.edu on Fri, Jun 02, 2000 at 01:44:56AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 02, 2000 at 01:44:56 -0400, John wrote: > > > > Well, this kinda brings up another question that I had posted to > > > freebsd-questions a few weeks back.... I found info describing *what* CAM > > > is and is supposed to do (http://people.freebsd.org/~gibbs), but is > > there a > > > read-me or a txt file or *anything* someplace to describe how to set it up > > > and configure it correctly. Just point me in the right direction :) > > > >There's nothing to "set up" or "configure"; there are no > >user-maintainable parts inside. You have hardware issues; bitching about > >CAM is entirely irrelevant. > > This was NOT a bitch. It was a request for help and info. I currently do > NOT have cam enabled, so it would be wrong for me to "bitch" about it. I > simply don't want to go willy-nilly adding kernel options without making > sure that I'm doing it correctly. Ahh, but you do have CAM enabled. If you've got the scbus device in your config file, you've got CAM. So you probably don't need to add anything to your kernel config file, unless you don't have the pass(4) driver configured. (You can't get the defects list off the drive with camcontrol(8) without it.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 2 21:31:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id A526637BA3D; Fri, 2 Jun 2000 21:31:32 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id AAA04323; Sat, 3 Jun 2000 00:31:39 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 03 Jun 2000 00:34:08 -0400 To: "Kenneth D. Merry" From: John Subject: Re: Dying connection? Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000601235026.A98092@panzer.kdm.org> References: <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Well, this kinda brings up another question that I had posted to > > > > freebsd-questions a few weeks back.... I found info describing > *what* CAM > > > > is and is supposed to do (http://people.freebsd.org/~gibbs), but is > > > there a > > > > read-me or a txt file or *anything* someplace to describe how to > set it up > > > > and configure it correctly. Just point me in the right direction :) > > > > > >There's nothing to "set up" or "configure"; there are no > > >user-maintainable parts inside. You have hardware issues; bitching about > > >CAM is entirely irrelevant. > > > > This was NOT a bitch. It was a request for help and info. I currently do > > NOT have cam enabled, so it would be wrong for me to "bitch" about it. I > > simply don't want to go willy-nilly adding kernel options without making > > sure that I'm doing it correctly. > >Ahh, but you do have CAM enabled. If you've got the scbus device in your >config file, you've got CAM. I must have been out the day that this clue was handed out :) >So you probably don't need to add anything to your kernel config file, >unless you don't have the pass(4) driver configured. (You can't get the >defects list off the drive with camcontrol(8) without it.) So, to address curiosity, I recompiled with the pass device in the kernel. Now, using "camcontrol defects -f phys -P", I get the following nice long list. Does it mean anything in the end run? Also, from within the Adaptec SCSI bios, if I run their "media check", all turns up ok. Thanks again, John Errors: 182:3:66 183:3:197 183:3:198 183:3:199 183:3:200 184:3:123 200:3:85 201:3:12 202:3:142 331:4:8 332:4:138 333:4:65 403:3:1 404:3:131 404:3:132 404:3:133 404:3:134 405:3:58 511:3:104 512:3:31 512:3:32 513:3:161 768:0:97 769:0:24 770:0:154 1810:3:114 1811:3:43 1812:3:168 1813:3:12 1813:3:13 1813:3:14 1813:3:15 1814:3:137 1815:3:67 1815:3:68 1815:3:69 1815:3:70 1816:3:192 1817:3:121 1818:3:51 2170:3:8 2171:3:133 2172:3:63 2173:3:102 2174:3:32 2175:3:156 3967:4:118 3968:4:54 3969:4:168 4039:4:130 4039:4:131 4039:4:132 4039:4:133 4039:4:134 4039:4:135 4039:4:136 4039:4:137 4040:4:68 4040:4:69 4040:4:70 4040:4:71 4040:4:72 4040:4:73 4040:4:74 4040:4:75 4041:4:6 4041:4:7 4041:4:8 4041:4:9 4041:4:10 4041:4:11 4041:4:12 4041:4:13 4064:0:45 4065:0:155 4065:0:156 4066:0:93 4613:5:9 4614:5:110 4615:5:3 5819:0:20 5820:0:108 5820:0:109 5820:0:110 5821:0:58 5825:7:55 5826:7:5 5827:7:93 6178:1:60 6179:1:127 6180:1:80 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 2 21:35:11 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 6270737B9F0; Fri, 2 Jun 2000 21:35:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA07395; Fri, 2 Jun 2000 22:34:58 -0600 (MDT) (envelope-from ken) Date: Fri, 2 Jun 2000 22:34:57 -0600 From: "Kenneth D. Merry" To: John Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000602223457.A7354@panzer.kdm.org> References: <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu>; from papalia@udel.edu on Sat, Jun 03, 2000 at 12:34:08AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jun 03, 2000 at 00:34:08 -0400, John wrote: > >So you probably don't need to add anything to your kernel config file, > >unless you don't have the pass(4) driver configured. (You can't get the > >defects list off the drive with camcontrol(8) without it.) > > So, to address curiosity, I recompiled with the pass device in the > kernel. Now, using "camcontrol defects -f phys -P", I get the following > nice long list. Does it mean anything in the end run? Also, from within > the Adaptec SCSI bios, if I run their "media check", all turns up ok. The -P argument to the defects subcommand gives you the permanent defect list, which is created at the factory. It is a list of blocks that were bad when the disk was manufactured. Your list is fairly short. If you use the -G argument, you get the grown defect list, which is the list if defects that have popped up since the drive left the factory. If you use both -P and -G, you'll get both lists at the same time. 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 Jun 2 21:38:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id 12B9037B9F0; Fri, 2 Jun 2000 21:38:23 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id AAA04346; Sat, 3 Jun 2000 00:38:38 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 03 Jun 2000 00:41:08 -0400 To: "Kenneth D. Merry" From: John Subject: Re: Dying connection? Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000602223457.A7354@panzer.kdm.org> References: <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >So you probably don't need to add anything to your kernel config file, > > >unless you don't have the pass(4) driver configured. (You can't get the > > >defects list off the drive with camcontrol(8) without it.) > > > > So, to address curiosity, I recompiled with the pass device in the > > kernel. Now, using "camcontrol defects -f phys -P", I get the following > > nice long list. Does it mean anything in the end run? Also, from within > > the Adaptec SCSI bios, if I run their "media check", all turns up ok. > >The -P argument to the defects subcommand gives you the permanent defect >list, which is created at the factory. It is a list of blocks that were >bad when the disk was manufactured. Your list is fairly short. > >If you use the -G argument, you get the grown defect list, which is the >list if defects that have popped up since the drive left the factory. If >you use both -P and -G, you'll get both lists at the same time. Ah..... ok. My mistake. Retrying, I get: merlin# camcontrol defects -f phys -G Got 0 defects. So now, is that a good thing, or a bad thing? And does that ultimately take into account all errors encountered since the drive left the factory, but before I configure the "pass" device? Thanks again for your patience!!! --John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 2 21:44:12 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 59F9C37B9A1; Fri, 2 Jun 2000 21:44:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA07562; Fri, 2 Jun 2000 22:44:05 -0600 (MDT) (envelope-from ken) Date: Fri, 2 Jun 2000 22:44:04 -0600 From: "Kenneth D. Merry" To: John Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000602224404.A7506@panzer.kdm.org> References: <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <20000602223457.A7354@panzer.kdm.org> <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000603004007.00ae3100@mail.udel.edu>; from papalia@udel.edu on Sat, Jun 03, 2000 at 12:41:08AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jun 03, 2000 at 00:41:08 -0400, John wrote: > > > >So you probably don't need to add anything to your kernel config file, > > > >unless you don't have the pass(4) driver configured. (You can't get the > > > >defects list off the drive with camcontrol(8) without it.) > > > > > > So, to address curiosity, I recompiled with the pass device in the > > > kernel. Now, using "camcontrol defects -f phys -P", I get the following > > > nice long list. Does it mean anything in the end run? Also, from within > > > the Adaptec SCSI bios, if I run their "media check", all turns up ok. > > > >The -P argument to the defects subcommand gives you the permanent defect > >list, which is created at the factory. It is a list of blocks that were > >bad when the disk was manufactured. Your list is fairly short. > > > >If you use the -G argument, you get the grown defect list, which is the > >list if defects that have popped up since the drive left the factory. If > >you use both -P and -G, you'll get both lists at the same time. > > Ah..... ok. My mistake. Retrying, I get: > > merlin# camcontrol defects -f phys -G > Got 0 defects. > > So now, is that a good thing, or a bad thing? It's good, probably. You might have defects, but the drive may not have remapped them. > And does that ultimately take > into account all errors encountered since the drive left the factory, but > before I configure the "pass" device? It includes all remapped blocks since the drive left the factory. The pass device doesn't affect it. You'll probably want to make sure you've got read and write reallocation turned on for the drive. To check it: {panzer:/usr/home/ken:1:0} camcontrol modepage da1 -m 1 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 [ ... ] Those two parameters should be set to 1. They tell the drive to automatically remap a bad block to a spare sector when it finds the block on either a read or a write. As a practical matter, I think it's probably easier for the drive to remap on a write, since it already has the "good" data that is supposed to go into that particular block. On a read, it's trying to get the data, and therefore may not be able to remap the block since it can't get good data for the block. (If it can detect that the block is starting to go bad, from ECC information or something similar, it may be able to salvage it on a read.) If read and write reallocation aren't enabled, you'll probably want to enable them, using the following command: camcontrol modepage da1 -m 1 -P 3 -e (obviously, use daN, where daN is the drive in question) Change the above two bits from 0 to 1. 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 Jun 2 22:12:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id C407237B98E; Fri, 2 Jun 2000 22:12:22 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id BAA04486; Sat, 3 Jun 2000 01:12:36 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sat, 03 Jun 2000 01:15:04 -0400 To: "Kenneth D. Merry" From: John Subject: Re: Dying connection? Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG In-Reply-To: <20000602224404.A7506@panzer.kdm.org> References: <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <20000602223457.A7354@panzer.kdm.org> <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > >So you probably don't need to add anything to your kernel config file, > > > > >unless you don't have the pass(4) driver configured. (You can't > get the > > > > >defects list off the drive with camcontrol(8) without it.) > > > > > > > > So, to address curiosity, I recompiled with the pass device in the > > > > kernel. Now, using "camcontrol defects -f phys -P", I get the > following > > > > nice long list. Does it mean anything in the end run? Also, from > within > > > > the Adaptec SCSI bios, if I run their "media check", all turns up ok. > > > > > >The -P argument to the defects subcommand gives you the permanent defect > > >list, which is created at the factory. It is a list of blocks that were > > >bad when the disk was manufactured. Your list is fairly short. > > > > > >If you use the -G argument, you get the grown defect list, which is the > > >list if defects that have popped up since the drive left the factory. If > > >you use both -P and -G, you'll get both lists at the same time. > > > > Ah..... ok. My mistake. Retrying, I get: > > > > merlin# camcontrol defects -f phys -G > > Got 0 defects. > > > > So now, is that a good thing, or a bad thing? > >It's good, probably. You might have defects, but the drive may not have >remapped them. > > > And does that ultimately take > > into account all errors encountered since the drive left the factory, but > > before I configure the "pass" device? > >It includes all remapped blocks since the drive left the factory. The pass >device doesn't affect it. > >You'll probably want to make sure you've got read and write reallocation >turned on for the drive. To check it: > >{panzer:/usr/home/ken:1:0} camcontrol modepage da1 -m 1 >AWRE (Auto Write Reallocation Enbld): 1 >ARRE (Auto Read Reallocation Enbld): 1 >[ ... ] > >Those two parameters should be set to 1. They tell the drive to >automatically remap a bad block to a spare sector when it finds the block >on either a read or a write. Ahhhhhhhh. Very interesting. Crash courses in learning tend to teach a lot. I'm curious though about the variable EER (Enable Early Recovery). From a cursory interpretation of the variable name, it would make sense to be set on. From a realism stance though, should it be? (Mine is currently 0). So now, with all this information at hand, does this still point to possible hard drive going back in terms of the original SCSI Bus error which I was receiving? Even if it doesn't, i can definitely say the experience has taught a lot :) Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 2 22:26:42 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 2557D37BAC0; Fri, 2 Jun 2000 22:26:40 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA08068; Fri, 2 Jun 2000 23:26:37 -0600 (MDT) (envelope-from ken) Date: Fri, 2 Jun 2000 23:26:37 -0600 From: "Kenneth D. Merry" To: John Cc: Mike Smith , John Lengeling , freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <20000602232637.B7954@panzer.kdm.org> References: <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <20000602223457.A7354@panzer.kdm.org> <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> <20000602224404.A7506@panzer.kdm.org> <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu>; from papalia@udel.edu on Sat, Jun 03, 2000 at 01:15:04AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jun 03, 2000 at 01:15:04 -0400, John wrote: > > > And does that ultimately take > > > into account all errors encountered since the drive left the factory, but > > > before I configure the "pass" device? > > > >It includes all remapped blocks since the drive left the factory. The pass > >device doesn't affect it. > > > >You'll probably want to make sure you've got read and write reallocation > >turned on for the drive. To check it: > > > >{panzer:/usr/home/ken:1:0} camcontrol modepage da1 -m 1 > >AWRE (Auto Write Reallocation Enbld): 1 > >ARRE (Auto Read Reallocation Enbld): 1 > >[ ... ] > > > >Those two parameters should be set to 1. They tell the drive to > >automatically remap a bad block to a spare sector when it finds the block > >on either a read or a write. > > Ahhhhhhhh. Very interesting. Crash courses in learning tend to teach a > lot. I'm curious though about the variable EER (Enable Early > Recovery). From a cursory interpretation of the variable name, it would > make sense to be set on. From a realism stance though, should it be? (Mine > is currently 0). I don't know what it does, I'd suggest looking at the SCSI draft specs at www.t10.org, specifically at the block command specifications. > So now, with all this information at hand, does this still point to > possible hard drive going back in terms of the original SCSI Bus error > which I was receiving? Even if it doesn't, i can definitely say the > experience has taught a lot :) It could be, although I would still say you need to check your cabling and termination, just in case. And make sure you have a backup. Then if your drive goes out, you haven't lost much. (That's a good policy whether or not you think your drive is having trouble.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message