From owner-freebsd-scsi Sun Mar 5 7:44:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 3D0F237B564 for ; Sun, 5 Mar 2000 07:44:28 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 12RdCl-000LHV-00 for freebsd-scsi@freebsd.org; Sun, 05 Mar 2000 07:44:27 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: write failures Message-Id: Date: Sun, 05 Mar 2000 07:44:27 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ASUS P2B-DS 4.0-CURRENT-0002270030 ahc0: port 0xd000-0xd0ff mem 0xdf000000-0xdf000fff irq 14 at device 6.0 on pci0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) ccd striping in use ccd3f 32 0 /dev/da0e /dev/da1f ccd4g 32 0 /dev/da0f /dev/da1g ccd5h 32 0 /dev/da0g /dev/da1h Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0a 31743 28041 1163 96% / /dev/da1e 31743 46 29158 0% /root mfs:27 15847 573 14007 4% /tmp /dev/ccd3c 254031 53427 180282 23% /var /dev/ccd4c 254031 14955 218754 6% /var/spool /dev/ccd5c 7534860 4305742 2626330 62% /usr procfs 4 4 0 100% /proc running fine for a loooong time suddenly, when using as samba backup for a w98 laptoy, i get the following: Mar 4 21:37:41 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 48744, size: 4096 Mar 4 21:52:03 rip /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 86 c3 20 0 0 10 0 Mar 4 21:52:31 rip /kernel: (da0:ahc0:0:0:0): HARDWARE FAILURE info:86c32a asc:3,0 Mar 4 21:52:34 rip /kernel: (da0:ahc0:0:0:0): Peripheral device write fault field replaceable unit: 10 sks:80,18 Mar 4 21:52:36 rip /kernel: ccd5: error 5 on component 0 block 7717664 (ccd block 15435280) Mar 4 21:52:45 rip /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 86 c3 20 0 0 10 0 Mar 4 21:52:45 rip /kernel: (da0:ahc0:0:0:0): HARDWARE FAILURE info:86c322 asc:3,0 Mar 4 21:52:45 rip /kernel: (da0:ahc0:0:0:0): Peripheral device write fault field replaceable unit: 10 sks:80,18 Mar 4 21:52:45 rip /kernel: ccd5: error 5 on component 0 block 7717664 (ccd block 15435280) Mar 4 23:30:38 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 5120, size: 4096 Mar 4 23:32:23 rip /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 82 32 60 0 0 10 0 Mar 4 23:32:24 rip /kernel: (da0:ahc0:0:0:0): HARDWARE FAILURE info:82326a asc:3,0 Mar 4 23:32:24 rip /kernel: (da0:ahc0:0:0:0): Peripheral device write fault field replaceable unit: 10 sks:80,18 Mar 4 23:32:24 rip /kernel: ccd5: error 5 on component 0 block 7418464 (ccd block 14836880) Mar 5 05:23:50 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 33640, size: 4096 Mar 5 06:01:13 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 12032, size: 4096 Mar 5 06:29:15 rip /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 77 f1 10 0 0 20 0 Mar 5 06:29:17 rip /kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:77f113 asc:3,0 Mar 5 06:29:17 rip /kernel: (da0:ahc0:0:0:0): Peripheral device write fault field replaceable unit: 10 sks:80,18 Mar 5 06:29:17 rip /kernel: ccd5: error 5 on component 0 block 6746384 (ccd block 13492672) Mar 5 07:27:49 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 23512, size: 4096 Mar 5 07:28:27 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 15360, size: 4096 Mar 5 07:28:38 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 107480, size: 8192 Mar 5 07:29:21 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 22360, size: 8192 Mar 5 07:30:10 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 18376, size: 4096 Mar 5 07:30:11 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 80608, size: 12288 Mar 5 07:30:11 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 33640, size: 4096 Mar 5 07:30:11 rip /kernel: swap_pager: indefinite wait buffer: device: #da/1, blkno: 80608, size: 12288 randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 5 11:27:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id 7E57E37BAB7; Sun, 5 Mar 2000 11:27:42 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id LAA53977; Sun, 5 Mar 2000 11:26:58 -0800 (PST) Message-ID: <20000305112658.59344@hydrogen.funkthat.com> Date: Sun, 5 Mar 2000 11:26:58 -0800 From: John-Mark Gurney To: Lauri Laupmaa Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: plist/glist query & proposal Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug White forwarded this message to me.... I actually have done this but I have not cleaned the code up for committing to the tree... I have been running this code for over a half year now... if people want, I can comitte this as is, but I'm using old daily routines on my box, not the newer ones... bak=/var/backups echo "" echo "" echo "checking disks for defects:" for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do if [ -f ${bak}/da${i}.glist ]; then mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak fi echo -n "da${i}: " camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist if [ -f ${bak}/da${i}.glist.bak ]; then if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist fi fi done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 5 13:47:29 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 0448C37BB26 for ; Sun, 5 Mar 2000 13:47:27 -0800 (PST) (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 NAA05898; Sun, 5 Mar 2000 13:47:14 -0800 Date: Sun, 5 Mar 2000 13:47:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Randy Bush Cc: freebsd-scsi@FreeBSD.org Subject: Re: write failures 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 > Mar 4 21:52:31 rip /kernel: (da0:ahc0:0:0:0): HARDWARE FAILURE info:86c32a asc:3,0 > Mar 4 21:52:34 rip /kernel: (da0:ahc0:0:0:0): Peripheral device write fault field replaceable unit: 10 sks:80,18 err, ummm, do you suppose this message might be telling you something? :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 5 13:49:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7590F37BB8C; Sun, 5 Mar 2000 13:49:27 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id QAA87475; Sun, 5 Mar 2000 16:49:16 -0500 (EST) Date: Sun, 5 Mar 2000 16:49:16 -0500 (EST) From: "Matthew N. Dodd" To: John-Mark Gurney Cc: Lauri Laupmaa , scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: plist/glist query & proposal In-Reply-To: <20000305112658.59344@hydrogen.funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 5 Mar 2000, John-Mark Gurney wrote: > Doug White forwarded this message to me.... I actually have done this > but I have not cleaned the code up for committing to the tree... > > I have been running this code for over a half year now... > > if people want, I can comitte this as is, but I'm using old daily > routines on my box, not the newer ones... I like it, though you may want to have an /etc/glist.conf and let the user add stuff with a script that tests to make sure a drive supports the format. A script to test and populate this file wouldn't be difficult. # # /etc/glist.conf # # Drive name Format (block, bfi, phys) da0 phys da1 block ... > bak=/var/backups > echo "" > echo "" > echo "checking disks for defects:" > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do > if [ -f ${bak}/da${i}.glist ]; then > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > fi > echo -n "da${i}: " > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > if [ -f ${bak}/da${i}.glist.bak ]; then > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > fi > fi > done > > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 5 14:15:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (adsl-63-195-54-213.dsl.snfc21.pacbell.net [63.195.54.213]) by hub.freebsd.org (Postfix) with ESMTP id CBE7637BB2D; Sun, 5 Mar 2000 14:15:41 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id OAA56560; Sun, 5 Mar 2000 14:15:20 -0800 (PST) Message-ID: <20000305141520.52809@hydrogen.funkthat.com> Date: Sun, 5 Mar 2000 14:15:20 -0800 From: John-Mark Gurney To: "Matthew N. Dodd" Cc: Lauri Laupmaa , scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: plist/glist query & proposal References: <20000305112658.59344@hydrogen.funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Matthew N. Dodd on Sun, Mar 05, 2000 at 04:49:16PM -0500 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org make sure to keep me on the cc list, I'm not on -current or -scsi Matthew N. Dodd scribbled this message on Mar 5: > On Sun, 5 Mar 2000, John-Mark Gurney wrote: > > Doug White forwarded this message to me.... I actually have done this > > but I have not cleaned the code up for committing to the tree... > > > > I have been running this code for over a half year now... > > > > if people want, I can comitte this as is, but I'm using old daily > > routines on my box, not the newer ones... > > I like it, though you may want to have an /etc/glist.conf and let the > user add stuff with a script that tests to make sure a drive supports the > format. A script to test and populate this file wouldn't be > difficult. yeh, I originally was using block for a while, and ONE of my drives didn't support it, then I switched to phys, and haven't had a problem.. and I have quite a range of drives: hydrogen,ttyq3,~,502$grep 'Direct Access' /var/run/dmesg.boot da3: Fixed Direct Access SCSI-CCS device da0: Fixed Direct Access SCSI-2 device da5: Fixed Direct Access SCSI-CCS device da6: Fixed Direct Access SCSI-CCS device da2: Fixed Direct Access SCSI-2 device da1: Fixed Direct Access SCSI-2 device da4: Fixed Direct Access SCSI-2 device which is a selection of scsi-1 (scsi-ccs), fast scsi, and ultra scsi drives... I'm sure that just using phys will keep all drives usable.. and if the user wants a different format, they can manually run camcontrol... bad disk blocks SHOULDN'T appear that often... :) > # > # /etc/glist.conf > # > # Drive name Format (block, bfi, phys) > da0 phys > da1 block > ... something like: `awk '$1 ~ /(da|sd)'"${i}"'/ { type = $2 } END { if (type == "" ) echo "phys"; else echo type; }'` should do perfectly fine... :) > > bak=/var/backups > > echo "" > > echo "" > > echo "checking disks for defects:" > > for i in `camcontrol devlist | awk '/(da|sd)/ { if (match($0, "(da|sd)[[:digit:]]+") != 0) { diskname = substr($0, RSTART, RLENGTH); match(diskname, "[[:digit:]]+"); print substr(diskname, RSTART, RLENGTH) } }' | sort -u`; do > > if [ -f ${bak}/da${i}.glist ]; then > > mv ${bak}/da${i}.glist ${bak}/da${i}.glist.bak > > fi > > echo -n "da${i}: " > > camcontrol defects -u $i -f phys -G 2>&1 > ${bak}/da${i}.glist > > if [ -f ${bak}/da${i}.glist.bak ]; then > > if ! cmp -s ${bak}/da${i}.glist ${bak}/da${i}.glist.bak; then > > diff ${bak}/da${i}.glist.bak ${bak}/da${i}.glist > > fi > > fi > > done -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 5 18:31: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from darius.concentric.net (darius.concentric.net [207.155.198.79]) by hub.freebsd.org (Postfix) with ESMTP id 8954837B794; Sun, 5 Mar 2000 18:30:59 -0800 (PST) (envelope-from aronchick@archegenesis.com) Received: from mcfeely.concentric.net (mcfeely.concentric.net [207.155.198.83]) by darius.concentric.net (8.9.1a/(98/12/15 5.12)) id VAA07264; Sun, 5 Mar 2000 21:30:57 -0500 (EST) [1-800-745-2747 The Concentric Network] Received: from aronchick (w148.z208036085.nyc-ny.dsl.cnc.net [208.36.85.148]) by mcfeely.concentric.net (8.9.1a) id VAA24376; Sun, 5 Mar 2000 21:30:56 -0500 (EST) Date: Sun, 05 Mar 2000 21:30:55 -0500 From: David Aronchick Reply-To: David Aronchick To: freebsd-scsi@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG Subject: Vinum vs Adaptec AIC 7890? Message-ID: <3104082854.952291855@aronchick> X-Mailer: Mulberry/2.0.0b11 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi-- I've had the following problems... we're currently running with 3x18 GB 10k Segate drives and an Asus p2b-ds with onboard scsi card. The drives are divided into 3 partitions /usr /var / and a RAID 5 of 26 GB. I was able to recover by just doing vinum start on the stale drive, but it brought the system down, and i need to make sure this doesn't happen again. Does anyone have any suggestions? Is this a CAM or vinum problem? or should I look to hardware. Here's the standard list. What problems are you having? Using lftp, I was in the midst of ftping a 50 MB or so file to the raid directly. After about 5% was done, the entire box froze. As it is remote, I don't know if the drives were accessing, but all open ssh sessions just stopped, i could ping and nmap the box, but when I tried to initiate an ssh, they would just open, and sit there. I've previously been able to copy a couple of hundred MB back and forth, with seemingly no problems. That was a few days ago. Which version of FreeBSD are you running? > uname -r 3.4-STABLE Have you made any changes to the system sources, including Vinum? No, everything is unchanged. Kernel stuff: # vinum list Configuration summary Drives: 3 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 3 (16 configured) D d0 State: up Device /dev/da0s2e Avail: 311/15311 MB (2%) D d1 State: up Device /dev/da1s2e Avail: 311/15311 MB (2%) D d2 State: up Device /dev/da2s2e Avail: 311/15311 MB (2%) V raid5 State: up Plexes: 1 Size: 29 GB P raid5.p0 R5 State: degraded Subdisks: 3 Size: 29 GB S raid5.p0.s0 State: up PO: 0 B Size: 14 GB S raid5.p0.s1 State: stale PO: 512 kB Size: 14 GB S raid5.p0.s2 State: up PO: 1024 kB Size: 14 GB # tail -100 /var/log/messages [...] Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): READ(10). CDB: 28 0 0 41 82 4e 0 0 80 0 Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): MEDIUM ERROR info:41825b asc:11,0 Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): Unrecovered read error field replaceable unit: e4 sks:80,101 Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal read I/O error Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is crashed by force Mar 5 13:25:18 db /kernel: vinum: raid5.p0 is degraded Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal write I/O error Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is stale by force Mar 5 16:52:08 db /kernel: Copyright (c) 1992-1999 FreeBSD Inc. [ the machine was manually rebooted 3 hours later ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 0: 8:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mojave.worldwide.lemis.com (dialup98.sydney.net.au [202.61.208.38]) by hub.freebsd.org (Postfix) with ESMTP id CFA6837BC65; Mon, 6 Mar 2000 00:08:41 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id SAA00373; Mon, 6 Mar 2000 18:45:53 +1100 (EST) (envelope-from grog) Date: Mon, 6 Mar 2000 18:45:53 +1100 From: Greg Lehey To: David Aronchick Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Vinum vs Adaptec AIC 7890? Message-ID: <20000306184553.A332@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <3104082854.952291855@aronchick> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3104082854.952291855@aronchick>; from aronchick@archegenesis.com on Sun, Mar 05, 2000 at 09:30:55PM -0500 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, 5 March 2000 at 21:30:55 -0500, David Aronchick wrote: > Hi-- > > I've had the following problems... > we're currently running with 3x18 GB 10k Segate drives and an Asus p2b-ds > with > onboard scsi card. The drives are divided into 3 partitions /usr /var / > and a RAID 5 of 26 GB. > > I was able to recover by just doing vinum start on the stale drive, but it > brought the system down, and i need to make sure this doesn't happen again. > Does anyone have any suggestions? Is this a CAM or vinum problem? or should > I look to hardware. Here's the standard list. Hmm. There are a couple of things missing here, like the dump. The log files show that there's something wrong with /dev/da1 (unrecovered data error; you should check whether you have ARRE and AWRE set), but that shouldn't cause the system to hang up. I'd strongly doubt that the problem has anything to do with the host adapter. I don't know of anything in Vinum which would cause these problems either, so we'd really need to know more details. Sorry I can't give you any more ideas, but there's not much to go on. > What problems are you having? Using lftp, I was in the midst of > ftping a 50 MB or so file to the raid directly. After about 5% was > done, the entire box froze. As it is remote, I don't know if the > drives were accessing, but all open ssh sessions just stopped, i > could ping and nmap the box, but when I tried to initiate an ssh, > they would just open, and sit there. I've previously been able to > copy a couple of hundred MB back and forth, with seemingly no > problems. That was a few days ago. > > Which version of FreeBSD are you running? > > 3.4-STABLE > > Have you made any changes to the system sources, including Vinum? > No, everything is unchanged. > > Kernel stuff: > # vinum list > Configuration summary > > Drives: 3 (4 configured) > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 3 (16 configured) > > D d0 State: up Device /dev/da0s2e Avail: 311/15311 MB (2%) > D d1 State: up Device /dev/da1s2e Avail: 311/15311 MB (2%) > D d2 State: up Device /dev/da2s2e Avail: 311/15311 MB (2%) > > V raid5 State: up Plexes: 1 Size: 29 GB > > P raid5.p0 R5 State: degraded Subdisks: 3 Size: 29 GB > > S raid5.p0.s0 State: up PO: 0 B Size: 14 GB > S raid5.p0.s1 State: stale PO: 512 kB Size: 14 GB > S raid5.p0.s2 State: up PO: 1024 kB Size: 14 GB > > # tail -100 /var/log/messages > > [...] > Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): READ(10). CDB: 28 0 0 41 82 > 4e 0 0 80 0 > Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): MEDIUM ERROR info:41825b > asc:11,0 > Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): Unrecovered read error field > replaceable unit: e4 sks:80,101 > Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal read I/O error > Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is crashed by force > Mar 5 13:25:18 db /kernel: vinum: raid5.p0 is degraded > Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal write I/O error > Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is stale by force > Mar 5 16:52:08 db /kernel: Copyright (c) 1992-1999 FreeBSD Inc. > [ the machine was manually rebooted 3 hours later ] Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 8: 7: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 7289337BBAD for ; Mon, 6 Mar 2000 08:06:35 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id QAA65870 for ; Mon, 6 Mar 2000 16:07:07 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id PAA00384 for ; Mon, 6 Mar 2000 15:47:21 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 6 Mar 2000 15:47:21 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: first INQUIRY goes round in circles (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The very first command issued by XPT, INQUIRY, goes round in circles if a drive chooses to not reset a Unit Attention (UA) error. It retries the INQUIRY command indefinitely (I have no idea why, but my gut feeling is that somewhere a new INQUIRY command is issued to get some sensible info from the drive, which then ends up in a loop) The UFI (SCSI derivative) USB device (Y-E Data Flashbuster-U floppy drive) I have here is broken as it INQUIRY - REQUEST SENSE - INQUIRY returns the same sense code (sense key = 0x06, asc = 0x29, ascq = 0x00) again at the second INQUIRY command, because the INQUIRY does not clear the UA state. As this is the very first command tried, it is impossible to use a device specific quirk. I suggest the following patch. It might have the following problems: - Test Unit Ready not supported by some devices - Devices reporting more than 4 UA states (4 is the number of retries in scsi_inquiry) Let me know. Nick =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v retrieving revision 1.14 diff -u -r1.14 scsi_all.c --- scsi/scsi_all.c 2000/02/20 04:42:43 1.14 +++ scsi/scsi_all.c 2000/03/06 12:11:29 @@ -1045,7 +1045,7 @@ "Not ready to ready change, medium may have changed") }, /* DT WR OM */{SST(0x28, 0x01, SS_DEF, "Import or export element accessed") }, -/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_NEDEF|ENXIO, +/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, "Power on, reset, or bus device reset occurred") }, /* DTLPWRSOMCAE */{SST(0x29, 0x01, SS_DEF, "Power on occurred") }, -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 8:17:53 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 C922B37BDFB for ; Mon, 6 Mar 2000 08:17:49 -0800 (PST) (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 IAA08566; Mon, 6 Mar 2000 08:17:40 -0800 Date: Mon, 6 Mar 2000 08:17:40 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 Test Unit Ready is mandatory, and that SCSI Floppy is sure busted, but I'm very nervous about this change. If people agree that it should be adopted, let's really wait until after 4.0 is cut, okay? > > The very first command issued by XPT, INQUIRY, goes round in circles if > a drive chooses to not reset a Unit Attention (UA) error. It retries the > INQUIRY command indefinitely (I have no idea why, but my gut feeling is > that somewhere a new INQUIRY command is issued to get some sensible > info from the drive, which then ends up in a loop) > > > The UFI (SCSI derivative) USB device (Y-E Data Flashbuster-U floppy > drive) I have here is broken as it INQUIRY - REQUEST SENSE - INQUIRY > returns the same sense code (sense key = 0x06, asc = 0x29, ascq = 0x00) > again at the second INQUIRY command, because the INQUIRY does not clear > the UA state. > > As this is the very first command tried, it is impossible to use a > device specific quirk. > > I suggest the following patch. It might have the following problems: > > - Test Unit Ready not supported by some devices > - Devices reporting more than 4 UA states (4 is the number of retries > in scsi_inquiry) > > Let me know. > > Nick > > > > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > retrieving revision 1.14 > diff -u -r1.14 scsi_all.c > --- scsi/scsi_all.c 2000/02/20 04:42:43 1.14 > +++ scsi/scsi_all.c 2000/03/06 12:11:29 > @@ -1045,7 +1045,7 @@ > "Not ready to ready change, medium may have changed") }, > /* DT WR OM */{SST(0x28, 0x01, SS_DEF, > "Import or export element accessed") }, > -/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_NEDEF|ENXIO, > +/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, > "Power on, reset, or bus device reset occurred") }, > /* DTLPWRSOMCAE */{SST(0x29, 0x01, SS_DEF, > "Power on occurred") }, > > -- > n_hibma@webweaving.org > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 9:37: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id D03CB37BE24 for ; Mon, 6 Mar 2000 09:36:24 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id RAA68367; Mon, 6 Mar 2000 17:37:11 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id RAA00540; Mon, 6 Mar 2000 17:33:27 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 6 Mar 2000 17:33:27 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Matthew Jacob Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 > Test Unit Ready is mandatory, and that SCSI Floppy is sure busted, but I'm > very nervous about this change. If people agree that it should be adopted, > let's really wait until after 4.0 is cut, okay? That was my intention. The driver for that drive is not going to be in the tree before that. In any case, the fact that the code goes round in circles instead of failing for some reason should be solved, no matter what. > > The very first command issued by XPT, INQUIRY, goes round in circles if > > a drive chooses to not reset a Unit Attention (UA) error. It retries the > > INQUIRY command indefinitely (I have no idea why, but my gut feeling is > > that somewhere a new INQUIRY command is issued to get some sensible > > info from the drive, which then ends up in a loop) > > > > > > The UFI (SCSI derivative) USB device (Y-E Data Flashbuster-U floppy > > drive) I have here is broken as it INQUIRY - REQUEST SENSE - INQUIRY > > returns the same sense code (sense key = 0x06, asc = 0x29, ascq = 0x00) > > again at the second INQUIRY command, because the INQUIRY does not clear > > the UA state. > > > > As this is the very first command tried, it is impossible to use a > > device specific quirk. > > > > I suggest the following patch. It might have the following problems: > > > > - Test Unit Ready not supported by some devices > > - Devices reporting more than 4 UA states (4 is the number of retries > > in scsi_inquiry) > > > > Let me know. > > > > Nick > > > > > > > > =================================================================== > > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > > retrieving revision 1.14 > > diff -u -r1.14 scsi_all.c > > --- scsi/scsi_all.c 2000/02/20 04:42:43 1.14 > > +++ scsi/scsi_all.c 2000/03/06 12:11:29 > > @@ -1045,7 +1045,7 @@ > > "Not ready to ready change, medium may have changed") }, > > /* DT WR OM */{SST(0x28, 0x01, SS_DEF, > > "Import or export element accessed") }, > > -/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_NEDEF|ENXIO, > > +/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, > > "Power on, reset, or bus device reset occurred") }, > > /* DTLPWRSOMCAE */{SST(0x29, 0x01, SS_DEF, > > "Power on occurred") }, > > > > -- > > n_hibma@webweaving.org > > n_hibma@freebsd.org USB project > > http://www.etla.net/~n_hibma/ > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 9:38:43 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 1C3C537BE4D for ; Mon, 6 Mar 2000 09:38:41 -0800 (PST) (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 JAA08906; Mon, 6 Mar 2000 09:38:32 -0800 Date: Mon, 6 Mar 2000 09:38:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 > > Test Unit Ready is mandatory, and that SCSI Floppy is sure busted, but I'm > > very nervous about this change. If people agree that it should be adopted, > > let's really wait until after 4.0 is cut, okay? > > That was my intention. The driver for that drive is not going to be in > the tree before that. > > In any case, the fact that the code goes round in circles instead of > failing for some reason should be solved, no matter what. Umm, yes indeed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 9:41:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from darius.concentric.net (darius.concentric.net [207.155.198.79]) by hub.freebsd.org (Postfix) with ESMTP id 5241037BE13; Mon, 6 Mar 2000 09:41:05 -0800 (PST) (envelope-from aronchick@archegenesis.com) Received: from mcfeely.concentric.net (mcfeely.concentric.net [207.155.198.83]) by darius.concentric.net (8.9.1a/(98/12/15 5.12)) id MAA29057; Mon, 6 Mar 2000 12:41:04 -0500 (EST) [1-800-745-2747 The Concentric Network] Received: from aronchick (w148.z208036085.nyc-ny.dsl.cnc.net [208.36.85.148]) by mcfeely.concentric.net (8.9.1a) id MAA09184; Mon, 6 Mar 2000 12:41:03 -0500 (EST) Date: Mon, 06 Mar 2000 12:40:56 -0500 From: David Aronchick Reply-To: David Aronchick To: Greg Lehey Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Vinum vs Adaptec AIC 7890? Message-ID: <3158684381.952346456@aronchick> In-Reply-To: <20000306184553.A332@mojave.worldwide.lemis.com> X-Mailer: Mulberry/2.0.0b11 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi again-- I wasn't sure what you meant by ARRE or AWRE in this case either, and I couldn't find them in the vinum docs. I don't think the kernel panicked, or if it did, it couldn't write any logs. I think the controller just freaked out or something. The worst part is the lack of availability of the machine when this happens, anything you could provide that would help me fix this would be very helpful. --On Monday, March 06, 2000 18:45 +1100 Greg Lehey wrote: > On Sunday, 5 March 2000 at 21:30:55 -0500, David Aronchick wrote: >> Hi-- >> >> I've had the following problems... >> we're currently running with 3x18 GB 10k Segate drives and an Asus p2b-ds >> >> with onboard scsi card. The drives are divided into 3 partitions /usr >> /var / and a RAID 5 of 26 GB. >> >> I was able to recover by just doing vinum start on the stale drive, but >> it brought the system down, and i need to make sure this doesn't happen >> again. Does anyone have any suggestions? Is this a CAM or vinum problem? >> or should I look to hardware. Here's the standard list. > > Hmm. There are a couple of things missing here, like the dump. The > log files show that there's something wrong with /dev/da1 (unrecovered > data error; you should check whether you have ARRE and AWRE set), but > that shouldn't cause the system to hang up. > > I'd strongly doubt that the problem has anything to do with the host > adapter. I don't know of anything in Vinum which would cause these > problems either, so we'd really need to know more details. Sorry I > can't give you any more ideas, but there's not much to go on. > >> What problems are you having? Using lftp, I was in the midst of >> ftping a 50 MB or so file to the raid directly. After about 5% was >> done, the entire box froze. As it is remote, I don't know if the >> drives were accessing, but all open ssh sessions just stopped, i >> could ping and nmap the box, but when I tried to initiate an ssh, >> they would just open, and sit there. I've previously been able to >> copy a couple of hundred MB back and forth, with seemingly no >> problems. That was a few days ago. >> >> Which version of FreeBSD are you running? >> >> 3.4-STABLE >> >> Have you made any changes to the system sources, including Vinum? >> No, everything is unchanged. >> >> Kernel stuff: >> # vinum list >> Configuration summary >> >> Drives: 3 (4 configured) >> Volumes: 1 (4 configured) >> Plexes: 1 (8 configured) >> Subdisks: 3 (16 configured) >> >> D d0 State: up Device /dev/da0s2e Avail: >> 311/15311 MB (2%) D d1 State: up Device >> /dev/da1s2e Avail: 311/15311 MB (2%) D d2 State: >> up Device /dev/da2s2e Avail: 311/15311 MB (2%) >> >> V raid5 State: up Plexes: 1 Size: 29 >> GB >> >> P raid5.p0 R5 State: degraded Subdisks: 3 Size: 29 >> GB >> >> S raid5.p0.s0 State: up PO: 0 B Size: 14 >> GB S raid5.p0.s1 State: stale PO: 512 kB Size: >> 14 GB S raid5.p0.s2 State: up PO: 1024 kB Size: >> 14 GB >> >> # tail -100 /var/log/messages >> >> [...] >> Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): READ(10). CDB: 28 0 0 41 82 >> 4e 0 0 80 0 >> Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): MEDIUM ERROR info:41825b >> asc:11,0 >> Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): Unrecovered read error >> field replaceable unit: e4 sks:80,101 >> Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal read I/O error >> Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is crashed by force >> Mar 5 13:25:18 db /kernel: vinum: raid5.p0 is degraded >> Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal write I/O error >> Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is stale by force >> Mar 5 16:52:08 db /kernel: Copyright (c) 1992-1999 FreeBSD Inc. >> [ the machine was manually rebooted 3 hours later ] > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 13:24:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 38F2C37BF4A for ; Mon, 6 Mar 2000 13:24:46 -0800 (PST) (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 NAA00633; Mon, 6 Mar 2000 13:25:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003062125.NAA00633@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: Nick Hibma , FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) In-reply-to: Your message of "Mon, 06 Mar 2000 08:17:40 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Mar 2000 13:25:45 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This sounds an awful lot like what's happening with this stupid Spectra changer, actually. 8( > Test Unit Ready is mandatory, and that SCSI Floppy is sure busted, but I'm > very nervous about this change. If people agree that it should be adopted, > let's really wait until after 4.0 is cut, okay? > > > > > > The very first command issued by XPT, INQUIRY, goes round in circles if > > a drive chooses to not reset a Unit Attention (UA) error. It retries the > > INQUIRY command indefinitely (I have no idea why, but my gut feeling is > > that somewhere a new INQUIRY command is issued to get some sensible > > info from the drive, which then ends up in a loop) > > > > > > The UFI (SCSI derivative) USB device (Y-E Data Flashbuster-U floppy > > drive) I have here is broken as it INQUIRY - REQUEST SENSE - INQUIRY > > returns the same sense code (sense key = 0x06, asc = 0x29, ascq = 0x00) > > again at the second INQUIRY command, because the INQUIRY does not clear > > the UA state. > > > > As this is the very first command tried, it is impossible to use a > > device specific quirk. > > > > I suggest the following patch. It might have the following problems: > > > > - Test Unit Ready not supported by some devices > > - Devices reporting more than 4 UA states (4 is the number of retries > > in scsi_inquiry) > > > > Let me know. > > > > Nick > > > > > > > > =================================================================== > > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > > retrieving revision 1.14 > > diff -u -r1.14 scsi_all.c > > --- scsi/scsi_all.c 2000/02/20 04:42:43 1.14 > > +++ scsi/scsi_all.c 2000/03/06 12:11:29 > > @@ -1045,7 +1045,7 @@ > > "Not ready to ready change, medium may have changed") }, > > /* DT WR OM */{SST(0x28, 0x01, SS_DEF, > > "Import or export element accessed") }, > > -/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_NEDEF|ENXIO, > > +/* DTLPWRSOMCAE */{SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, > > "Power on, reset, or bus device reset occurred") }, > > /* DTLPWRSOMCAE */{SST(0x29, 0x01, SS_DEF, > > "Power on occurred") }, > > > > -- > > n_hibma@webweaving.org > > n_hibma@freebsd.org USB project > > http://www.etla.net/~n_hibma/ > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 13:35: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 9A11137B833; Mon, 6 Mar 2000 13:35:56 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA78344; Mon, 6 Mar 2000 14:35:51 -0700 (MST) (envelope-from ken) Date: Mon, 6 Mar 2000 14:35:51 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: mjacob@feral.com, Nick Hibma , FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) Message-ID: <20000306143551.A78310@panzer.kdm.org> References: <200003062125.NAA00633@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003062125.NAA00633@mass.cdrom.com>; from msmith@FreeBSD.ORG on Mon, Mar 06, 2000 at 01:25:45PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 06, 2000 at 13:25:45 -0800, Mike Smith wrote: > > This sounds an awful lot like what's happening with this stupid Spectra > changer, actually. 8( It is very similar, except that in his case the autosense didn't fail. (Thus the reason things go around in circles for him.) It's amazing how these broken devices just seem to pop up in spurts. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 17:11:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4223737C004; Mon, 6 Mar 2000 17:10:53 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id BAA71961; Tue, 7 Mar 2000 01:11:47 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id XAA00952; Mon, 6 Mar 2000 23:44:21 GMT (envelope-from n_hibma@calcaphon.com) Date: Mon, 6 Mar 2000 23:44:20 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: Mike Smith , mjacob@feral.com, FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) In-Reply-To: <20000306143551.A78310@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 > > This sounds an awful lot like what's happening with this stupid Spectra > > changer, actually. 8( > > It is very similar, except that in his case the autosense didn't fail. > (Thus the reason things go around in circles for him.) Well, the same routine decides that a restart is needed, so it's not quite as dissimilar as you are suggesting. > It's amazing how these broken devices just seem to pop up in spurts. Just like drunk Englishmen :-) Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 17:44:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 7512D37BD3C; Mon, 6 Mar 2000 17:44:22 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id BAA72101; Tue, 7 Mar 2000 01:45:17 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id BAA00406; Tue, 7 Mar 2000 01:42:02 GMT (envelope-from n_hibma@calcaphon.com) Date: Tue, 7 Mar 2000 01:42:02 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: Mike Smith , mjacob@feral.com, FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) In-Reply-To: <20000306143551.A78310@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 After having another look at what CAM does, the following strikes me as odd. In the case of SF_RETRY_UA being set, the command is retried _without_ decrementing the retry_count. Can anyone enlighten me as to why that is being done this way? It's the cause of the infinite retry of the initial INQUIRY command. (This does not solve the problem of UA not being reset for my drive, but that needs a quirk anyway, instead of modifying the asc_text quirk table) "/sys/cam/scsi/scsi_all.c" line 2230 of 2933 --76%-- col 11-25 case SSD_KEY_UNIT_ATTENTION: /* * This should also be filtered out by * peripheral drivers since each has a different * concept of what it means to invalidate the * media. */ if ((sense_flags & SF_RETRY_UA) != 0) { /* don't decrement retry count */ error = ERESTART; print_sense = FALSE; } else { /* decrement the number of retries */ retry = ccb->ccb_h.retry_count > 0; if (retry) { ccb->ccb_h.retry_count--; error = ERESTART; print_sense = FALSE; } else { On Mon, 6 Mar 2000, Kenneth D. Merry wrote: > On Mon, Mar 06, 2000 at 13:25:45 -0800, Mike Smith wrote: > > > > This sounds an awful lot like what's happening with this stupid Spectra > > changer, actually. 8( > > It is very similar, except that in his case the autosense didn't fail. > (Thus the reason things go around in circles for him.) > > It's amazing how these broken devices just seem to pop up in spurts. > > Ken > -- > Kenneth Merry > ken@kdm.org > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 17:57:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 15A8037BE4C; Mon, 6 Mar 2000 17:57:47 -0800 (PST) (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 RAA03274; Mon, 6 Mar 2000 17:58:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003070158.RAA03274@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Sat, 04 Mar 2000 16:10:54 MST." <20000304161054.A61108@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Mar 2000 17:58:21 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Oooh, I think I know what may be going on here. I suspect you're hitting > the following case in cam_periph_error(): > > } else { > /* decrement the number of retries */ > retry = ccb->ccb_h.retry_count > 0; > if (retry) > ccb->ccb_h.retry_count--; > /* > * If it was aborted with no > * clue as to the reason, just > * retry it again. > */ > error = ERESTART; > } > > You hit that when there is a SCSI error, but autosense failed, and there > are still retries left. Sorry; doesn't look like it. Some simple printf tracing suggests that it's actually the CAM_SCSI_STATUS_ERROR/CAM_STATUS_BUSY case that's getting called. That'd also explain the 1s delay between commands. Not sure yet why it's not "just working" after the unit comes ready - I'm guessing that's because we don't send two TUR's in sequence. Shouldn't we spin using TUR if the unit's not ready, until it does become ready? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 19:32:29 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 5FEF437BCF0; Mon, 6 Mar 2000 19:32:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA80344; Mon, 6 Mar 2000 20:32:18 -0700 (MST) (envelope-from ken) Date: Mon, 6 Mar 2000 20:32:18 -0700 From: "Kenneth D. Merry" To: Nick Hibma Cc: Mike Smith , mjacob@feral.com, FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) Message-ID: <20000306203217.A80256@panzer.kdm.org> References: <20000306143551.A78310@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from n_hibma@calcaphon.com on Tue, Mar 07, 2000 at 01:42:02AM +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 07, 2000 at 01:42:02 +0000, Nick Hibma wrote: > After having another look at what CAM does, the following strikes me as > odd. In the case of SF_RETRY_UA being set, the command is retried > _without_ decrementing the retry_count. Can anyone enlighten me as to > why that is being done this way? > > It's the cause of the infinite retry of the initial INQUIRY command. A unit attenion is not supposed to be returned in response to an inquiry. But your drive is returning a unit attention error. Here's the relevant section from the SCSI-2 spec: ======================================================================== The INQUIRY command shall return CHECK CONDITION status only when the target cannot return the requested INQUIRY data. NOTE 64 The INQUIRY data should be returned even though the peripheral device may not be ready for other commands. If an INQUIRY command is received from an initiator with a pending unit attention condition (i.e. before the target reports CHECK CONDITION status), the target shall perform the INQUIRY command and shall not clear the unit attention condition (see 7.9). ======================================================================== So there are two components: - the target should *only* return an error if it cannot return the inquiry data. - any unit attention condition should not be cleared by an inquiry [*] But any other command should generate the check condition which would then clear the unit attention state. So in most cases, a unit attention will be cleared after the first command, so the "infinite" number of retries only ends up being 1. You're running into this problem because you've got a broken driver that reports an error in response to an inquiry. [*] Unit attention handling is actually a little more complicated than I've described, due to contingent allegiance conditions. Don't ask me to explain that, since I don't have a good understanding of it. :) It's explained in the SCSI specs. > (This does not solve the problem of UA not being reset for my drive, > but that needs a quirk anyway, instead of modifying the asc_text quirk > table) You can't have a quirk entry for a device that doesn't have inquiry data yet, since quirk entries are matched against inquiry data. The only way to quirk it would be to have a system specific bus/target/lun quirked. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 19:43: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 7478737BDA7; Mon, 6 Mar 2000 19:43:19 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA80418; Mon, 6 Mar 2000 20:43:18 -0700 (MST) (envelope-from ken) Date: Mon, 6 Mar 2000 20:43:18 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000306204318.B80256@panzer.kdm.org> References: <20000304161054.A61108@panzer.kdm.org> <200003070158.RAA03274@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003070158.RAA03274@mass.cdrom.com>; from msmith@FreeBSD.ORG on Mon, Mar 06, 2000 at 05:58:21PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 06, 2000 at 17:58:21 -0800, Mike Smith wrote: > > Oooh, I think I know what may be going on here. I suspect you're hitting > > the following case in cam_periph_error(): > > > > } else { > > /* decrement the number of retries */ > > retry = ccb->ccb_h.retry_count > 0; > > if (retry) > > ccb->ccb_h.retry_count--; > > /* > > * If it was aborted with no > > * clue as to the reason, just > > * retry it again. > > */ > > error = ERESTART; > > } > > > > You hit that when there is a SCSI error, but autosense failed, and there > > are still retries left. > > Sorry; doesn't look like it. Some simple printf tracing suggests that > it's actually the CAM_SCSI_STATUS_ERROR/CAM_STATUS_BUSY case that's > getting called. That'd also explain the 1s delay between commands. Oooooh. Well that's not nearly as broken as I thought. In fact, it's probably acceptable behavior. > Not sure yet why it's not "just working" after the unit comes ready - I'm > guessing that's because we don't send two TUR's in sequence. > > Shouldn't we spin using TUR if the unit's not ready, until it does become > ready? We don't currently have the ability to fire off error recovery commands in response to the SCSI status byte. So there's not an easy way to do that right now. Hopefully Justin has addressed that in his error recovery rewrite. I think the best thing for you to do at the moment is what you did originally -- make the SCSI_DELAY long enough for the changer to become ready. I know it's painful, but you can probably tweak it to within 10 seconds or so of what you need. A TUR handler would give you two things that that wouldn't do -- it would let the drive probe succeed as soon as the changer is ready, and it would allow the rest of the system to boot while the changer sits there waiting to become ready. Sorry we don't have an immediate solution, but hopefully we can get things right with Justin's revamp of the error recovery code. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 6 23:14:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from server1.huntsvilleal.com (www.huntsvilleal.com [207.13.224.7]) by hub.freebsd.org (Postfix) with ESMTP id DB60837BC99; Mon, 6 Mar 2000 23:14:53 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from barricuda.bsd.nws.net (kris.huntsvilleal.com [207.13.224.46]) by server1.huntsvilleal.com (8.9.3/8.9.3) with ESMTP id BAA15432; Tue, 7 Mar 2000 01:56:09 -0500 Received: from localhost (localhost [127.0.0.1]) by barricuda.bsd.nws.net (8.9.3/8.9.3) with ESMTP id BAA37977; Tue, 7 Mar 2000 01:14:46 -0600 (CST) (envelope-from kris@hiwaay.net) Date: Tue, 7 Mar 2000 01:14:46 -0600 (CST) From: Kris Kirby To: David Aronchick Cc: Greg Lehey , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Vinum vs Adaptec AIC 7890? In-Reply-To: <3158684381.952346456@aronchick> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I wasn't sure what you meant by ARRE or AWRE in this case either, and I > couldn't find them in the vinum docs. I don't think the kernel panicked, or > if it did, it couldn't write any logs. I think the controller just freaked > out or something. The worst part is the lack of availability of the > machine when this happens, anything you could provide that would help me > fix this would be very helpful. You mean to say you have built a machine with no serial ports? Go grab another box and attach the two via a null modem to each other. The monitoring box should use COM2 idealy, but it's no big deal. The PC to be monitored should be connected on COM1. Set the monitor to 9600 bps and whatever port you picked. You can use kermit to log to a file and then watch or screen to interact with the downed PC, assuming it drops to debug. Boot the kernel -P and disconnect the keyboard. All /dev/console activity appears out the serial port. Do test this config before using it though. You don't want important data spilling out the port without something to catch it. --- Kris Kirby, KE4AHR | TGIFreeBSD... 'Nuff said. | ------------------------------------------------------- "God gave them the ability to reproduce... ... Science gave us the hope they won't." -KBK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 3: 7:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id B1D4D37BB4D; Tue, 7 Mar 2000 03:07:06 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id LAA04856; Tue, 7 Mar 2000 11:05:28 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id KAA01073; Tue, 7 Mar 2000 10:53:12 GMT (envelope-from n_hibma@calcaphon.com) Date: Tue, 7 Mar 2000 10:53:12 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: Mike Smith , mjacob@feral.com, FreeBSD SCSI Mailing List , BLACKSON Jim Subject: Re: first INQUIRY goes round in circles (fwd) In-Reply-To: <20000306203217.A80256@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 What I don't understand is why the drive does not clear the Unit Attention after REQUEST SENSE has been sent. The solution to all this Jim pointed out was to not request sense after INQUIRY. This I can live with as it is a valid solution. If INQUIRY fails, the data stage of the USB transfer will fail and you have another indicator that things went wrong. Thanks for the help. Nick > > After having another look at what CAM does, the following strikes me as > > odd. In the case of SF_RETRY_UA being set, the command is retried > > _without_ decrementing the retry_count. Can anyone enlighten me as to > > why that is being done this way? > > > > It's the cause of the infinite retry of the initial INQUIRY command. > > A unit attenion is not supposed to be returned in response to an inquiry. > But your drive is returning a unit attention error. Here's the relevant > section from the SCSI-2 spec: > > ======================================================================== > The INQUIRY command shall return CHECK CONDITION status only when the > target cannot return the requested INQUIRY data. > > NOTE 64 The INQUIRY data should be returned even though the peripheral > device may not be ready for other commands. > > If an INQUIRY command is received from an initiator with a pending unit > attention condition (i.e. before the target reports CHECK CONDITION > status), the target shall perform the INQUIRY command and shall not > clear the unit attention condition (see 7.9). > ======================================================================== > > So there are two components: > > - the target should *only* return an error if it cannot return the > inquiry data. > > - any unit attention condition should not be cleared by an inquiry [*] > > But any other command should generate the check condition which would then > clear the unit attention state. > > So in most cases, a unit attention will be cleared after the first command, > so the "infinite" number of retries only ends up being 1. > > You're running into this problem because you've got a broken driver that > reports an error in response to an inquiry. > > [*] Unit attention handling is actually a little more complicated than I've > described, due to contingent allegiance conditions. Don't ask me to > explain that, since I don't have a good understanding of it. :) It's > explained in the SCSI specs. -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 6: 9:17 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 6062437BBFE for ; Tue, 7 Mar 2000 06:09:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id GAA12192; Tue, 7 Mar 2000 06:09:09 -0800 Date: Tue, 7 Mar 2000 06:09:09 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 > What I don't understand is why the drive does not clear the Unit > Attention after REQUEST SENSE has been sent. Uh, f/w bug? > > The solution to all this Jim pointed out was to not request sense after > INQUIRY. This I can live with as it is a valid solution. If INQUIRY > fails, the data stage of the USB transfer will fail and you have another > indicator that things went wrong. Note that might be a case in which it's possible for an unadorned INQUIRY* to generate a CHECK CONDITION- that's when there's a parity error on the IDENTIFY message at the start of the command or a parity error sending the CDB. I haven't done this level of SCSI for 10 years and don't have the spec in front of me, but IIRC it's up to the target as to how it decides it wants to cope with received bytes with parity errors so the mechanisms that cope with parity errors while the command is active may not be used and a CHECK CONDITION with the ASC/ASCQ may be latched up. -matt *The second INQUIRY that FreeBSD's xpt_probe always sends that asks for the VPD info will generally always get a CHECK CONDITION for devices that don't support VDP info, so blindly saying "don't request sense after an INQUIRY" is a Bad Thing To Do (tm) as it will leave the latched up Illegal Bit in CDB for the next command to have to cope with- which will be the poor old Test Unit Ready. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 6:50:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 041D237BE53 for ; Tue, 7 Mar 2000 06:49:07 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id OAA09667; Tue, 7 Mar 2000 14:49:50 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id OAA01427; Tue, 7 Mar 2000 14:46:42 GMT (envelope-from n_hibma@calcaphon.com) Date: Tue, 7 Mar 2000 14:46:42 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Matthew Jacob Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The solution to all this Jim pointed out was to not request sense after > > INQUIRY. This I can live with as it is a valid solution. If INQUIRY > > fails, the data stage of the USB transfer will fail and you have another > > indicator that things went wrong. > > Note that might be a case in which it's possible for an unadorned INQUIRY* to > generate a CHECK CONDITION- that's when there's a parity error on the IDENTIFY > message at the start of the command or a parity error sending the CDB. I > haven't done this level of SCSI for 10 years and don't have the spec in front > of me, but IIRC it's up to the target as to how it decides it wants to cope > with received bytes with parity errors so the mechanisms that cope with parity > errors while the command is active may not be used and a CHECK CONDITION with > the ASC/ASCQ may be latched up. Transport problems (so-called wire errors) are handled in the USB part and are signalled differently. They are reported as CAM_REQ_CMP_ERR. > *The second INQUIRY that FreeBSD's xpt_probe always sends that asks for the > VPD info will generally always get a CHECK CONDITION for devices that don't > support VDP info, so blindly saying "don't request sense after an INQUIRY" is > a Bad Thing To Do (tm) as it will leave the latched up Illegal Bit in CDB for > the next command to have to cope with- which will be the poor old Test Unit > Ready. In that case the command or data transport will fail. This means that SENSE will be requested. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 6:59:36 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 E740237BC09 for ; Tue, 7 Mar 2000 06:59:33 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id GAA12297; Tue, 7 Mar 2000 06:59:28 -0800 Date: Tue, 7 Mar 2000 06:59:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 > Transport problems (so-called wire errors) are handled in the USB part > and are signalled differently. They are reported as CAM_REQ_CMP_ERR. Uh, the USB adapter can't tell when the *target* has gotten a prity error. > > > *The second INQUIRY that FreeBSD's xpt_probe always sends that asks for the > > VPD info will generally always get a CHECK CONDITION for devices that don't > > support VDP info, so blindly saying "don't request sense after an INQUIRY" is > > a Bad Thing To Do (tm) as it will leave the latched up Illegal Bit in CDB for > > the next command to have to cope with- which will be the poor old Test Unit > > Ready. > > In that case the command or data transport will fail. This means that > SENSE will be requested. > Uh, okay. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 10: 8:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 3153737BCAD for ; Tue, 7 Mar 2000 10:08:22 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id SAA19777; Tue, 7 Mar 2000 18:04:24 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id RAA03392; Tue, 7 Mar 2000 17:40:03 GMT (envelope-from n_hibma@calcaphon.com) Date: Tue, 7 Mar 2000 17:40:03 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Matthew Jacob Cc: FreeBSD SCSI Mailing List Subject: Re: first INQUIRY goes round in circles (fwd) 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 > > Transport problems (so-called wire errors) are handled in the USB part > > and are signalled differently. They are reported as CAM_REQ_CMP_ERR. > > Uh, the USB adapter can't tell when the *target* has gotten a prity error. It is assumed that the host controller and the target are one. This is not always the case however in which case your remark is quite valid. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 14:39: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 6E72437B50D for ; Tue, 7 Mar 2000 14:37:28 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id QAA93944 for scsi@freebsd.org; Tue, 7 Mar 2000 16:37:21 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200003072237.QAA93944@celery.dragondata.com> Subject: DLT problems To: scsi@freebsd.org Date: Tue, 7 Mar 2000 16:37:06 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When doing a backup to my DLT occasionally, I get the following: (sa0:ahc0:0:2:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa (sa0:ahc0:0:2:0): Queuing a BDR SCB (sa0:ahc0:0:2:0): Bus Device Reset Message Sent (sa0:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:2. 1 SCBs aborted (sa0:ahc0:0:2:0): LOAD UNLOAD. CDB: 1b 0 0 0 1 0 (sa0:ahc0:0:2:0): UNIT ATTENTION asc:28,0 (sa0:ahc0:0:2:0): Not ready to ready change, medium may have changed Am I hitting the end of the tape, or something else? Here's my config: ahc0: rev 0x01 int a irq 9 on pci0.9.0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs ahc1: rev 0x01 int a irq 10 on pci0.10.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da3 at ahc1 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da4 at ahc1 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da6 at ahc1 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da6: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da5 at ahc1 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 18: 5:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id AD59837B930 for ; Tue, 7 Mar 2000 18:05:43 -0800 (PST) (envelope-from pulsifer@mediaone.net) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls06.mediaone.net (8.8.7/8.8.7) with SMTP id VAA04869 for ; Tue, 7 Mar 2000 21:05:41 -0500 (EST) From: "Allen Pulsifer" To: Subject: FC-AL adapter Date: Tue, 7 Mar 2000 21:05:41 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone direct me to a FC-AL controller that works well with FreeBSD-current? Thanks, Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 20:28:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gordius.gordian.com (gordius.gordian.com [192.73.220.81]) by hub.freebsd.org (Postfix) with ESMTP id 3D62937B5FD for ; Tue, 7 Mar 2000 20:28:39 -0800 (PST) (envelope-from steve@gordian.com) X-bait: aablmeh@gordian.com,mmblmeh@gordian.com,zzblmeh@gordian.com Received: from delphi.gordian.com (delphi.gordian.com [192.73.220.125]) by gordius.gordian.com (8.9.3/8.9.3) with ESMTP id UAA28680 for ; Tue, 7 Mar 2000 20:28:38 -0800 (PST) Received: from gordian.com (asclepius [192.73.220.254]) by delphi.gordian.com (8.9.3/8.6.9) with ESMTP id UAA07070 for ; Tue, 7 Mar 2000 20:28:36 -0800 (PST) Message-ID: <38C5D6F4.4A4A6970@gordian.com> Date: Tue, 07 Mar 2000 20:28:36 -0800 From: Steve Khoo Organization: Gordian; Santa Ana Heights, CA X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: DPT SmartRAID IV PM3334UW firmware RAID 0+1? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is the DPT SmartRAID IV PM3334UW capable of doing RAID 0+1 without software striping? I checked the archive and found some reference to forcing firmware RAID 0 via "dptmgr /fw0". But, it's not clear if that'll allow RAID 0+1. I'm running 2.2.8-STABLE as of Sept. 7th 1999. I created a RAID 1 array consisting of 4 x 36G drives via "dptmgr /fw0" method. However, I'm seeing two drives from the OS. Firmware version on the controller is 07M0. I'd appreciate any advise. Thanks! SEK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 21:14:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 0017037B5D4 for ; Tue, 7 Mar 2000 21:14:30 -0800 (PST) (envelope-from gemohler@tgn.net) Received: from tgn.net ([63.196.210.178]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FR300DDN7OUN6@mta4.snfc21.pbi.net> for freebsd-scsi@FreeBSD.ORG; Tue, 7 Mar 2000 21:11:21 -0800 (PST) Date: Tue, 07 Mar 2000 21:11:08 -0800 From: Geoff Mohler Subject: Re: FC-AL adapter To: Allen Pulsifer Cc: freebsd-scsi@FreeBSD.ORG Reply-To: gemohler@tgn.net Message-id: <38C5E0EC.80D4EDD9@tgn.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (Win98; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en,pdf References: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I use the Qlogic ISP2100 just peachy in my 3.x boxes. I work at Network Appliance, and its really kinda neat to see 8 shelves full of 7 36G drives on that adapter working on the BSD box. Makes one hell'uva CCD array, formats in under a minute. Allen Pulsifer wrote: > Can anyone direct me to a FC-AL controller that works well with > FreeBSD-current? > > Thanks, > > Allen > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 21:20:25 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 CBDC637B5AA for ; Tue, 7 Mar 2000 21:20:22 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA89234; Tue, 7 Mar 2000 22:20:03 -0700 (MST) (envelope-from ken) Date: Tue, 7 Mar 2000 22:20:03 -0700 From: "Kenneth D. Merry" To: Geoff Mohler Cc: Allen Pulsifer , freebsd-scsi@FreeBSD.ORG Subject: Re: FC-AL adapter Message-ID: <20000307222003.A89199@panzer.kdm.org> References: <38C5E0EC.80D4EDD9@tgn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38C5E0EC.80D4EDD9@tgn.net>; from gemohler@tgn.net on Tue, Mar 07, 2000 at 09:11:08PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 07, 2000 at 21:11:08 -0800, Geoff Mohler wrote: > I use the Qlogic ISP2100 just peachy in my 3.x boxes. > > I work at Network Appliance, and its really kinda neat to see 8 shelves > full of 7 36G drives on that adapter working on the BSD box. > > Makes one hell'uva CCD array, formats in under a minute. Have you actually formatted all 56 drives as one filesystem? IIRC, there's a 1TB limit on filesystem sizes. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 21:24:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 2665F37B5B1 for ; Tue, 7 Mar 2000 21:24:40 -0800 (PST) (envelope-from gemohler@tgn.net) Received: from tgn.net ([63.196.210.178]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FR3002N889VXB@mta4.snfc21.pbi.net> for freebsd-scsi@FreeBSD.ORG; Tue, 7 Mar 2000 21:22:44 -0800 (PST) Date: Tue, 07 Mar 2000 21:23:45 -0800 From: Geoff Mohler Subject: Re: FC-AL adapter To: "Kenneth D. Merry" Cc: Allen Pulsifer , freebsd-scsi@FreeBSD.ORG Reply-To: gemohler@tgn.net Message-id: <38C5E3E1.B376117A@tgn.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (Win98; I) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en,pdf References: <38C5E0EC.80D4EDD9@tgn.net> <20000307222003.A89199@panzer.kdm.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had 8 shelves, but I dont recall how many total drives of 9, 18, and 36G I had available. At least 4 full shelves of 36s, and whatever else was layin around in the lab at the time. I dont even recall how long I spend creating devices for all the drives either. It got to be more of a PITA than anything else..but was still fun. And stable. "Kenneth D. Merry" wrote: > On Tue, Mar 07, 2000 at 21:11:08 -0800, Geoff Mohler wrote: > > I use the Qlogic ISP2100 just peachy in my 3.x boxes. > > > > I work at Network Appliance, and its really kinda neat to see 8 shelves > > full of 7 36G drives on that adapter working on the BSD box. > > > > Makes one hell'uva CCD array, formats in under a minute. > > Have you actually formatted all 56 drives as one filesystem? > > IIRC, there's a 1TB limit on filesystem sizes. > > Ken > -- > Kenneth Merry > ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 22:49:21 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 1265637B5B1 for ; Tue, 7 Mar 2000 22:49:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA14911; Tue, 7 Mar 2000 22:49:02 -0800 Date: Tue, 7 Mar 2000 22:49:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kevin Day Cc: scsi@FreeBSD.ORG Subject: Re: DLT problems In-Reply-To: <200003072237.QAA93944@celery.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's funny you should mention that- I've seen this too (although on a different host adatper) with a DLT4000- and it does appear to be related to getting near end of tape, but there's nothing programmatically to be done. I have not figured out what is actually going on f/w wise- I have a very downrev Sun OEM DLT4000. Are you in fixed block or in variable block mode? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 7 23:53:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 85D5137B588 for ; Tue, 7 Mar 2000 23:53:17 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA94833; Wed, 8 Mar 2000 01:52:59 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200003080752.BAA94833@celery.dragondata.com> Subject: Re: DLT problems To: mjacob@feral.com Date: Wed, 8 Mar 2000 01:52:59 -0600 (CST) Cc: toasty@dragondata.com (Kevin Day), scsi@FreeBSD.ORG In-Reply-To: from "Matthew Jacob" at Mar 07, 2000 10:49:01 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > It's funny you should mention that- I've seen this too (although on a > different host adatper) with a DLT4000- and it does appear to be related to > getting near end of tape, but there's nothing programmatically to be done. > > I have not figured out what is actually going on f/w wise- I have a very > downrev Sun OEM DLT4000. > > Are you in fixed block or in variable block mode? > > -matt Fixed block, I believe. When I get back there, I'll double check. I looked for a firmware upgrade for this, but www.compaq.com seems to have no DEC related materials any more. If there's anything you want me to try, I'm willing. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 7: 2:26 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 26F6337B570 for ; Wed, 8 Mar 2000 07:02:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id HAA16129; Wed, 8 Mar 2000 07:02:01 -0800 Date: Wed, 8 Mar 2000 07:01:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Kevin Day Cc: scsi@FreeBSD.ORG Subject: Re: DLT problems In-Reply-To: <200003080752.BAA94833@celery.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > It's funny you should mention that- I've seen this too (although on a > > different host adatper) with a DLT4000- and it does appear to be related to > > getting near end of tape, but there's nothing programmatically to be done. > > > > I have not figured out what is actually going on f/w wise- I have a very > > downrev Sun OEM DLT4000. > > > > Are you in fixed block or in variable block mode? > > > > -matt > > Fixed block, I believe. When I get back there, I'll double check. > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > no DEC related materials any more. DEC sold it's DLT technology to Quantum years ago. See http://www.dltape.com. > If there's anything you want me to try, I'm willing. :) I'm not real sure. Other than 'check f/w'. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 7:49:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 35F6937C0BD for ; Wed, 8 Mar 2000 07:49:08 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id QAA07533 for ; Wed, 8 Mar 2000 16:49:03 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id QAA12780 for ; Wed, 8 Mar 2000 16:49:02 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id QAA23255 for ; Wed, 8 Mar 2000 16:49:02 +0100 (CET) Date: Wed, 8 Mar 2000 16:49:00 +0100 From: Andre Albsmeier To: Matthew Jacob Cc: Kevin Day , scsi@FreeBSD.ORG Subject: Re: DLT problems Message-ID: <20000308164900.A89535@internal> References: <200003080752.BAA94833@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Wed, Mar 08, 2000 at 07:01:59AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 08-Mar-2000 at 07:01:59 -0800, Matthew Jacob wrote: > > > > > > > It's funny you should mention that- I've seen this too (although on a > > > different host adatper) with a DLT4000- and it does appear to be related to > > > getting near end of tape, but there's nothing programmatically to be done. > > > > > > I have not figured out what is actually going on f/w wise- I have a very > > > downrev Sun OEM DLT4000. > > > > > > Are you in fixed block or in variable block mode? > > > > > > -matt > > > > Fixed block, I believe. When I get back there, I'll double check. > > > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > > no DEC related materials any more. > > DEC sold it's DLT technology to Quantum years ago. > See http://www.dltape.com. > > > If there's anything you want me to try, I'm willing. :) I am using this one (OK, it is a Quantum DLT4700): sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) ch0 at ahc0 bus 0 target 4 lun 1 ch0: Removable Changer SCSI-2 device ch0: 10.000MB/s transfers (10.000MHz, offset 15) ch0: 7 slots, 1 drive, 1 picker, 0 portals The firmware for the DLT4xxx can be found at: ftp://ftp.quantum.com/Tape_Firmware/DLT4000/ Don't know if it is DEC compatible... -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 11: 2:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 25F9537B636 for ; Wed, 8 Mar 2000 11:02:08 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA15270; Wed, 8 Mar 2000 19:51:17 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA01011; Wed, 8 Mar 2000 19:44:33 +0100 (CET) (envelope-from wilko) Date: Wed, 8 Mar 2000 19:44:33 +0100 From: Wilko Bulte To: Kevin Day Cc: mjacob@feral.com, scsi@FreeBSD.ORG Subject: Re: DLT problems Message-ID: <20000308194433.C927@yedi.iaf.nl> References: <200003080752.BAA94833@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003080752.BAA94833@celery.dragondata.com>; from toasty@dragondata.com on Wed, Mar 08, 2000 at 01:52:59AM -0600 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 08, 2000 at 01:52:59AM -0600, Kevin Day wrote: > > > > > > It's funny you should mention that- I've seen this too (although on a > > different host adatper) with a DLT4000- and it does appear to be related to > > getting near end of tape, but there's nothing programmatically to be done. > > > > I have not figured out what is actually going on f/w wise- I have a very > > downrev Sun OEM DLT4000. > > > > Are you in fixed block or in variable block mode? > > > > -matt > > Fixed block, I believe. When I get back there, I'll double check. > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > no DEC related materials any more. Firmware upgrades were always done via DEC Fieldservice. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 11: 4:34 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 859E937C09F for ; Wed, 8 Mar 2000 11:04:32 -0800 (PST) (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 LAA17125; Wed, 8 Mar 2000 11:03:56 -0800 Date: Wed, 8 Mar 2000 11:04:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: Kevin Day , scsi@FreeBSD.ORG Subject: Re: DLT problems In-Reply-To: <20000308194433.C927@yedi.iaf.nl> 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 > > > > Fixed block, I believe. When I get back there, I'll double check. > > > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > > no DEC related materials any more. > > Firmware upgrades were always done via DEC Fieldservice. Ah, not always after Quantum bought AVAstore. Check the ftp site- they've some windoze tools for upgrading f/w. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 11:11:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id CA8FF37B6B5 for ; Wed, 8 Mar 2000 11:11:15 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id NAA95952; Wed, 8 Mar 2000 13:11:02 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200003081911.NAA95952@celery.dragondata.com> Subject: Re: DLT problems To: mjacob@feral.com Date: Wed, 8 Mar 2000 13:11:02 -0600 (CST) Cc: wilko@yedi.iaf.nl (Wilko Bulte), toasty@dragondata.com (Kevin Day), scsi@FreeBSD.ORG In-Reply-To: from "Matthew Jacob" at Mar 08, 2000 11:04:01 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > > > Fixed block, I believe. When I get back there, I'll double check. > > > > > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > > > no DEC related materials any more. > > > > Firmware upgrades were always done via DEC Fieldservice. > > Ah, not always after Quantum bought AVAstore. Check the ftp site- they've some > windoze tools for upgrading f/w. > > > Yeah, I found firmware on ftp.quantum.com.... www.dltape.com has a tip that if you dd the upgrade onto a tape, then power off/on the drive, it'll read the firmware off of the tape and reflash itself... I'm not sure if I'm brave enough to try this, though. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 14:55:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0A74337B52B for ; Wed, 8 Mar 2000 14:55:08 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA27320; Wed, 8 Mar 2000 23:43:44 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA09616; Wed, 8 Mar 2000 23:17:38 +0100 (CET) (envelope-from wilko) Date: Wed, 8 Mar 2000 23:17:38 +0100 From: Wilko Bulte To: Matthew Jacob Cc: Kevin Day , scsi@FreeBSD.ORG Subject: Re: DLT problems Message-ID: <20000308231738.A3366@yedi.iaf.nl> References: <20000308194433.C927@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjacob@feral.com on Wed, Mar 08, 2000 at 11:04:01AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 08, 2000 at 11:04:01AM -0800, Matthew Jacob wrote: > > > > > > Fixed block, I believe. When I get back there, I'll double check. > > > > > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > > > no DEC related materials any more. > > > > Firmware upgrades were always done via DEC Fieldservice. > > Ah, not always after Quantum bought AVAstore. Check the ftp site- they've some > windoze tools for upgrading f/w. I'm talking DEC branded drives in the days before Quantum bought the DEC storage device outfit. You won't find DEC firmware (stuff that will announce itself as DEC TZ8x ) on the Quantum web site. And it was not on the 'old' DEC website either -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 8 14:55:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 7DE8537B66F for ; Wed, 8 Mar 2000 14:55:26 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA27324; Wed, 8 Mar 2000 23:43:46 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA09627; Wed, 8 Mar 2000 23:18:43 +0100 (CET) (envelope-from wilko) Date: Wed, 8 Mar 2000 23:18:43 +0100 From: Wilko Bulte To: Kevin Day Cc: mjacob@feral.com, scsi@FreeBSD.ORG Subject: Re: DLT problems Message-ID: <20000308231843.B3366@yedi.iaf.nl> References: <200003081911.NAA95952@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003081911.NAA95952@celery.dragondata.com>; from toasty@dragondata.com on Wed, Mar 08, 2000 at 01:11:02PM -0600 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 08, 2000 at 01:11:02PM -0600, Kevin Day wrote: > > > > > > > > > > Fixed block, I believe. When I get back there, I'll double check. > > > > > > > > I looked for a firmware upgrade for this, but www.compaq.com seems to have > > > > no DEC related materials any more. > > > > > > Firmware upgrades were always done via DEC Fieldservice. > > > > Ah, not always after Quantum bought AVAstore. Check the ftp site- they've some > > windoze tools for upgrading f/w. > > > > > > > > Yeah, I found firmware on ftp.quantum.com.... www.dltape.com has a tip that > if you dd the upgrade onto a tape, then power off/on the drive, it'll read > the firmware off of the tape and reflash itself... I'm not sure if I'm brave > enough to try this, though. :) That is known as a FUP tape. Works well in my experience. Quantum also had/has (have not checked recently) the DLTtools program. DOS/ASPI based. W/ -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 9 1: 6:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from clefw.ra.rockwell.com (clefw.ra.rockwell.com [192.159.76.15]) by hub.freebsd.org (Postfix) with ESMTP id E46A637B752 for ; Thu, 9 Mar 2000 01:06:10 -0800 (PST) (envelope-from mkes@ra.rockwell.com) Received: from raclesmtp01.cle.ra.rockwell.com (raclesmtp01.cle.ra.rockwell.com [130.151.192.220]) by clefw.ra.rockwell.com (8.9.3/8.9.3) with ESMTP id EAA22278 for ; Thu, 9 Mar 2000 04:06:05 -0500 (EST) From: mkes@ra.rockwell.com Subject: Adaptec AIC 7892 not detected in 3.x To: freebsd-scsi@freebsd.org Date: Thu, 9 Mar 2000 10:04:06 +0100 Message-ID: X-MIMETrack: Serialize by Router on RACleSMTP01/Cleveland/RA/Rockwell(Release 5.0.2b (Intl)|16 December 1999) at 03/09/2000 03:55:56 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have new HP Kayak XU800 with onboard Adaptec AIC 7892 (that's what BIOS says) which should be supported (ahc0) in FreeBSD. If I try to install 3.4 from the CDROM the controller is not detected. The SCSI controller itself seems to be OK (running Win NT without problems). I tried to experiment a little bit with other releases with following results: 2.2.6: Probing devices on PCI bus 3: pci 3:0:0 Intel Corporation, device=0x1161, class system, subclass=0x00 [no driver assigned] pci 3:9: vendor=0x9005, device=0x008f, class=storage(scsi), int a irq 10 [no driver assigned] 3.1 and 3.4 (both the same): Probing devices on PCI bus 3: ... and nothing else 4.0 snapshot March 8 2000: PCI 3: on pcib3 PCI 3: (vendor=0x8086, dev=0x1161) at 0.0 ahc0: port 0xb800 - 0xb8ff mem 0xfd8ff000 - 0xfd8fffff irq 10 at device 9.0 om pci 3 So the 2.2.6 at least says it the card was found, 3.x doesn't detect the card (and doesn't say anything) and 4.0 detects the controller correctly. The 3.4 has the AIC 7892 on the compatibility list - I would be happy to use it on that machine. On the other hand it is not so critical for me so I can wait for 4.0 or 3.5 ( if this version will fix it), but if you someone could give me a tip what to do to make it work that would be great :-) Mira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 9 6:52:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 4A52537B51E for ; Thu, 9 Mar 2000 06:52:29 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id HAA89449; Thu, 9 Mar 2000 07:38:54 -0700 (MST) Date: Thu, 9 Mar 2000 07:38:54 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200003091438.HAA89449@narnia.plutotech.com> To: mkes@ra.rockwell.com Cc: scsi@FreeBSD.org Subject: Re: Adaptec AIC 7892 not detected in 3.x X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > I have new HP Kayak XU800 with onboard Adaptec AIC 7892 (that's what BIOS > says) which should be supported (ahc0) in FreeBSD. > If I try to install 3.4 from the CDROM the controller is not detected. > The SCSI controller itself seems to be OK (running Win NT without > problems). U160 support has not been ported back to the -stable branch yet. This is why your controller is not probed by the 3.4 release. > The 3.4 has the AIC 7892 on the compatibility list - I would be happy to > use it on that machine. If the supported hardware list for 3.4 includes the 7892, it is in error. I seem to recall updating the hardware list to add in the 7892/7899 in the -current version of that file, so I'm surprised that the -stable version makes any mention of those controllers at all. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message