From owner-freebsd-scsi Sun Aug 23 11:56:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12815 for freebsd-scsi-outgoing; Sun, 23 Aug 1998 11:56:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from forest.fscinternet.com (aurora.fscinternet.com [165.154.230.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12809; Sun, 23 Aug 1998 11:56:14 -0700 (PDT) (envelope-from rreiner@forest.fscinternet.com) Received: from jupiter (jupiter.fscinternet.com [10.1.1.103]) by forest.fscinternet.com (8.8.5/8.8.5) with SMTP id OAA11540; Sun, 23 Aug 1998 14:55:32 -0400 (EDT) Message-Id: <199808231855.OAA11540@forest.fscinternet.com> From: "Richard Reiner" Organization: FSC Internet To: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Date: Sun, 23 Aug 1998 14:58:19 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: SCSI tape crashes on 2.1.6 Reply-to: rreiner@fscinternet.com X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org P90 using a 1542CF driving an Archive DDS-1 DAT and 90m tapes. We're running FreeBSD 2.1.6 on this box (yes, it's time for an upgrade, but unless someone can tell me otherwise that won't solve this problem). Problem: We can write backups to tape without error. Reading backups back from tape results in a large variety of errors ranging from bad reads to system crashes. Termination has been double-and-triple-and-quadruple-checked to be correct. Have also tried a different SCSI host adapter -- BT946C -- with same results. Has our DAT drive just gone south? Or is this some bug in the scsi or st drivers in our old version of FreeBSD? BTW, this problem came to light when we switched from GNU tar to BRU (from www.estinc.com), thanks to BRU's superior error detection and tape verification features. EXCELLENT backup software -- buy it if you value your data! >From dmesg: 100 nSEC ok, using 150 nSEC aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "CONNER CFP2105S 2.14GB 2B4B" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 2048MB (4194304 512 byte sectors) (aha0:2:0): "ARCHIVE Python 28388-XXX 5.28" type 1 removable SCSI 2 st0(aha0:2:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled (aha0:4:0): "TOSHIBA CD-ROM XM-5301TA 1535" type 5 removable SCSI 2 cd0(aha0:4:0): CD-ROM cd present.[325264 x 2048 byte records] Thanks, Richard -- . . . . . . . . . . . . . . . . . . . . . . . . . . . Richard Reiner, Ph.D. . rreiner@fscinternet.com ~~~~~~~~~~~~~~~~~~~~~ . http://www.fscinternet.com FSC Internet Corp. . +1 416 921-4280 . . . . . . . . . . . . . . . . . . . . . . . . . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 00:05:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11271 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 00:05:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hermes.hrz.uni-bielefeld.de (hermes.hrz.uni-bielefeld.de [129.70.4.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11262; Tue, 25 Aug 1998 00:05:09 -0700 (PDT) (envelope-from lkoeller@post.uni-bielefeld.de) Received: from mitch.hrz.uni-bielefeld.de (9134@mitch.hrz.uni-bielefeld.de [129.70.4.17]) by hermes.hrz.uni-bielefeld.de (8.8.6/8.8.6) with ESMTP id JAA28204; Tue, 25 Aug 1998 09:04:56 +0200 (METDST) Received: from localhost by mitch.hrz.uni-bielefeld.de with SMTP (8.8.6/16.2) id HAA14327; Tue, 25 Aug 1998 07:03:59 GMT Message-Id: <199808250703.HAA14327@mitch.hrz.uni-bielefeld.de> X-Mailer: exmh version 2.0.2 2/24/98 From: Lars =?iso-8859-1?Q?K=F6ller?= To: freebsd-scsi@FreeBSD.ORG, "Justin T. Gibbs" , "Kenneth D. Merry" Subject: Parse sense data with camcontrol into shell variable! X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=[/(4+0a$~ Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01044 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 02:39:36 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01031 for ; Tue, 25 Aug 1998 02:39:34 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA21407 for ; Tue, 25 Aug 1998 02:38:46 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id CAA01303; Tue, 25 Aug 1998 02:38:43 -0700 (PDT) Date: Tue, 25 Aug 1998 02:38:43 -0700 (PDT) Message-Id: <199808250938.CAA01303@silvia.hip.berkeley.edu> To: scsi@FreeBSD.ORG Subject: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, One of our machines started hanging (or crashing) occasionally. This is the message that was printed out to the serial console just before the disk array (ccd of 13 disks) locked up. === (da8:ahc0:0:8:0): WRITE(10). CDB: 2a 0 0 cc a7 9f 0 0 30 0 (da8:ahc0:0:8:0): ABORTED COMMAND asc:47,0 (da8:ahc0:0:8:0): SCSI parity error (da1:ahc0:0:1:0): parity error during Data-In phase. === I could still log in to the machine, but any process (bash) that did anything with the array will lock up. Also, this is what was on the console before the machine hung before. (It was a hard hang, needed a reset.) === (da2:ahc0:0:2:0): WRITE(10). CDB: 2a 0 0 82 74 ef 0 0 40 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:47,0 (da2:ahc0:0:2:0): SCSI parity error (da3:ahc0:0:3:0): parity error during Data-In phase. (da3:ahc0:0:3:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 SEQADDR == 0xb (da3:ahc0:0:3:0): Queueing a BDR SCB (da3:ahc0:0:3:0): Bus Device Reset Message Sent Bus Device Reset Completed. (da3:ahc0:0:3:0): no longer in timeout ahc0: Bus Device Reset delivered. 1 SCBs aborted === It does seem to come back up after a reboot/power cycle and work fine for a while (a few days to a week) though. So, two questions. I assume the SCSI parity error means bus integrity problems (enclosure went bad or something)? Also, if it's going to come back after a reboot, can it be done without actual rebooting? (Like sending a bus reset....under no cases have we actually power-cycled the disk enclosures.) Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 02:49:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01879 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 02:49:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01874 for ; Tue, 25 Aug 1998 02:49:03 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca10-63.ix.netcom.com [205.186.214.63]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id CAA21417 for ; Tue, 25 Aug 1998 02:48:15 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id CAA01323; Tue, 25 Aug 1998 02:48:13 -0700 (PDT) Date: Tue, 25 Aug 1998 02:48:13 -0700 (PDT) Message-Id: <199808250948.CAA01323@silvia.hip.berkeley.edu> To: scsi@FreeBSD.ORG In-reply-to: <199808250938.CAA01303@silvia.hip.berkeley.edu> (asami@cs.berkeley.edu) Subject: Re: parity errors From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Hi, Oops, forgot to mention I'm using CAM on 3.0-current from January. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 10:10:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27561 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 10:10:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27552; Tue, 25 Aug 1998 10:10:42 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA15177; Tue, 25 Aug 1998 11:09:39 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808251709.LAA15177@panzer.plutotech.com> Subject: Re: Parse sense data with camcontrol into shell variable! In-Reply-To: <199808250703.HAA14327@mitch.hrz.uni-bielefeld.de> from =?ISO-8859-1?Q?Lars_K=F6ller?= at "Aug 25, 98 09:03:59 am" To: Lars.Koeller@post.uni-bielefeld.de (Lars =?iso-8859-1?Q?K=F6ller?=) Date: Tue, 25 Aug 1998 11:09:39 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG, ken@plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Lars Köller wrote... > -------- > > Hallo experts! > > I just rewrite a ADIC DAT AutoLoader script from scsi to chio! The > problem is to get the sense data (19 bytes) from the changer. The > chio command is not able to solve this problem. > > However, I need only byte number 19 from the sense data, cause it > contains data about an open doors of the changer etc. > > How can I parse the data with camcontrol into a shell variable. > Request sense data command is "03 ....", so it should look like > > camcontrol -n ch -c "03 0 0 0 13 0" -O ....... Hmm, try something like this: camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 64 "s18 b8" Or perhaps: camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 64 "s18 i1" The "s" argument tells it to skip that many bytes. The 'b' argument tells it to print out that many bits. The 'i' argument tells it to print the data as an n-byte integer. (where 1 <= n <= 4) A few hints/notes about command parsing in camcontrol: - -I is equivalent to -i in scsi(8) - -O is equivalent to -o in scsi(8) - unlike scsi(8), you can't specify arguments to the CDB. i.e. you can't do stuff like: camcontrol -n da -u 0 -c "v 00 00 00 00 00" 0 This is because I didn't figure out exactly how I wanted to do the argument parsing when I first wrote the buffer parsing code, and I haven't had time to work on it since. It isn't a very big deal, though...it's generally easy enough to just fill out the CDB. Arguments are supported for -I and -O, however. - camcontrol doesn't yet support reading data from stdin (for -O) or writing data to stdout (for -I) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 10:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29674 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 10:26:37 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29667; Tue, 25 Aug 1998 10:26:34 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA15288; Tue, 25 Aug 1998 11:25:42 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199808251725.LAA15288@panzer.plutotech.com> Subject: Re: Parse sense data with camcontrol into shell variable! In-Reply-To: <199808251709.LAA15177@panzer.plutotech.com> from "Kenneth D. Merry" at "Aug 25, 98 11:09:39 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Tue, 25 Aug 1998 11:25:42 -0600 (MDT) Cc: Lars.Koeller@post.uni-bielefeld.de, freebsd-scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote... > Hmm, try something like this: > > camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 64 "s18 b8" > > Or perhaps: > > camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 64 "s18 i1" Sorry to reply to myself, but those should probably be: camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 0x64 "s18 b8" and camcontrol -n ch -u 0 -c "03 00 00 00 64 00" -I 0x64 "s18 i1" The length inside the CDB is in hex, so the length specified for the -I argument should match it. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 11:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11409 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 11:39:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nlanr.net (oceana.sdsc.edu [132.249.40.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11398 for ; Tue, 25 Aug 1998 11:39:19 -0700 (PDT) (envelope-from bigj@nlanr.net) Received: from localhost (bigj@localhost) by nlanr.net (8.8.6/8.8.6) with SMTP id LAA07808 for ; Tue, 25 Aug 1998 11:38:26 -0700 (PDT) Date: Tue, 25 Aug 1998 11:38:26 -0700 (PDT) From: Jambi cc: freebsd-scsi@FreeBSD.ORG Subject: Fiber Channel. In-Reply-To: <199808250703.HAA14327@mitch.hrz.uni-bielefeld.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, We are thinking about building a little data crunching farm which will be a whole bunch of FreeBSD machines. We were offered a fiber channel controller as our current problem is in IO (having to parse serially huge network dumps...what a pain). I was looking around the FreeBSD FAQ etc and could find no reference to a supported Fiber Channel controllers. Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? Is CAM supporting it? 10x Jambi _______________________________________________ Jambi Ganbar | (619) 8220938 | jambi@nlanr.net San Diego SuperComputer Center ________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 12:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17162 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 12:17:49 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17157 for ; Tue, 25 Aug 1998 12:17:47 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id MAA30105; Tue, 25 Aug 1998 12:16:38 -0700 Date: Tue, 25 Aug 1998 12:16:38 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Jambi cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fiber Channel. 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 Qlogic Fibre Channel card (2100) is mostly supported- it's the same driver as the SCSI driver. It's fabric support is minimal (uh, not there yet) right now, but a plain loop or a PLDA seems to work as long as nothing complicated in terms of PLOGI parameters seems to be expected. I don't know the PM2554UWF, although if someone got me one and specs for it, I'd likely do a driver for it. I'm also planning to do the Adaptec F9{4,5}0 sooner or later. On Tue, 25 Aug 1998, Jambi wrote: > Hey all, > We are thinking about building a little data crunching farm which will > be a whole bunch of FreeBSD machines. We were offered a fiber channel > controller as our current problem is in IO (having to parse serially huge > network dumps...what a pain). I was looking around the FreeBSD FAQ etc > and could find no reference to a supported Fiber Channel controllers. > Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? Is > CAM supporting it? > > 10x > Jambi > _______________________________________________ > Jambi Ganbar | (619) 8220938 | jambi@nlanr.net > San Diego SuperComputer Center > ________________________________________________ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 13:51:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03497 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 13:51:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d2.dialup.hilink.com.au [203.2.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03465 for ; Tue, 25 Aug 1998 13:50:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA02594; Tue, 25 Aug 1998 13:48:17 GMT (envelope-from mike@dingo.cdrom.com) Message-Id: <199808251348.NAA02594@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jambi cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fiber Channel. In-reply-to: Your message of "Tue, 25 Aug 1998 11:38:26 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Aug 1998 13:48:16 +0000 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hey all, > We are thinking about building a little data crunching farm which will > be a whole bunch of FreeBSD machines. We were offered a fiber channel > controller as our current problem is in IO (having to parse serially huge > network dumps...what a pain). I was looking around the FreeBSD FAQ etc > and could find no reference to a supported Fiber Channel controllers. > Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? Is > CAM supporting it? It should behave like a "normal" DPT, so yes, we should support it. We also support Fibrechannel controllers based on the Qlogic chips. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Tue Aug 25 15:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21441 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 15:31:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA21428 for ; Tue, 25 Aug 1998 15:31:04 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA26750 (5.67b/IDA-1.5); Wed, 26 Aug 1998 00:18:59 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA01698; Tue, 25 Aug 1998 23:10:28 +0200 (CEST) From: Wilko Bulte Message-Id: <199808252110.XAA01698@yedi.iaf.nl> Subject: Re: Fiber Channel. In-Reply-To: from Matthew Jacob at "Aug 25, 98 12:16:38 pm" To: mjacob@feral.com Date: Tue, 25 Aug 1998 23:10:28 +0200 (CEST) Cc: bigj@nlanr.net, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org People might also be interested in looking at the Emulex LP6000 and LP7000 cards. Maybe (*big* maybe) I'll have a chance to check one out. W/ As Matthew Jacob wrote... > The Qlogic Fibre Channel card (2100) is mostly supported- it's the > same driver as the SCSI driver. It's fabric support is minimal > (uh, not there yet) right now, but a plain loop or a PLDA seems to work as > long as nothing complicated in terms of PLOGI parameters seems to be > expected. > > I don't know the PM2554UWF, although if someone got me one and specs > for it, I'd likely do a driver for it. > > I'm also planning to do the Adaptec F9{4,5}0 sooner or later. > > On Tue, 25 Aug 1998, Jambi wrote: > > > Hey all, > > We are thinking about building a little data crunching farm which will > > be a whole bunch of FreeBSD machines. We were offered a fiber channel > > controller as our current problem is in IO (having to parse serially huge > > network dumps...what a pain). I was looking around the FreeBSD FAQ etc > > and could find no reference to a supported Fiber Channel controllers. > > Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? Is > > CAM supporting it? Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 16:28:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00289 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 16:28:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00283 for ; Tue, 25 Aug 1998 16:28:22 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id QAA30585; Tue, 25 Aug 1998 16:27:28 -0700 Date: Tue, 25 Aug 1998 16:27:28 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Wilko Bulte cc: bigj@nlanr.net, freebsd-scsi@FreeBSD.ORG Subject: Re: Fiber Channel. In-Reply-To: <199808252110.XAA01698@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 On Tue, 25 Aug 1998, Wilko Bulte wrote: > > People might also be interested in looking at the Emulex LP6000 and > LP7000 cards. Maybe (*big* maybe) I'll have a chance to check one out. Yes- the Emulex cards look good- more from an FC/IP point of view from what I've heard, and also JAYCOR. And, still to be worth doing, SOCAL SBus cards for the sparc port (:-)). The big issue with all of this will be fabric and multipathing device naming support. This kind of stuff is basically my charter at NASA/Ames for a chunk of the next year. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 25 16:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00666 for freebsd-scsi-outgoing; Tue, 25 Aug 1998 16:30:34 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA00644 for ; Tue, 25 Aug 1998 16:30:32 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 21580 invoked by uid 3759); 25 Aug 1998 23:29:38 -0000 Date: Tue, 25 Aug 1998 19:29:37 -0400 (EDT) From: "B. Richardson" To: Stefan Esser cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ncr:2: ERROR (0:18) In-Reply-To: <19980815000822.A1587@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Replaced the cable, replaced the MB, and got an active terminator. The "ncr0:2: ERROR" message is gone but every few days I get these Aug 20 18:21:38 rabtter /kernel: ncr0: timeout ccb=f1026000 (skip) Aug 20 18:21:38 rabtter /kernel: ncr0: timeout ccb=f1026800 (skip) Aug 20 18:21:46 rabtter /kernel: ncr0: timeout ccb=f1026400 (skip) and the filesystems freeze. Any hints, tips, suggestions? - Barrett Richardson rabtter@orion.aye.net On Sat, 15 Aug 1998, Stefan Esser wrote: > On 1998-08-13 21:33 -0400, "B. Richardson" wrote: > > > > I am jinxed. I fought the "Timed out while idle" with and adaptec 3940 > > for a month and finally ditched it a day before Justin posted the > > sequencer file and got a Diamond Fireport 40. Played with > > termination/cables for weeks with a 2.2 6/29 snapshot. Reinstalled > > 2.2.5 (had a CD handy) with the Diamond Fireport 40, ran some > > bonnie test for a few hours, and put my cacheing server live today. > > After about 8 hours this happens (chunks of dmesg output below). > > Lovely error message is after Drives/controllers. > > > ------- Lovely error message ------------ > > > > ncr0:2: ERROR (0:18) (1-21-302) (10/9d) @ (script 6cc:19000000). > > SIST = 0x18 => Gross Error + Reselected by Another Device > > The "Gross Error" condition is what caused the transfer to > fail. Seems there is some electrical problem, or the Viking > violates the SCSI protocol. The conditions that set the > Gross Error bit in the SCSI Interrupt Status Register are: > > 1) Data Underflow (more data requested by target than available) > 2) Data Overflow (more data sent by target than expected) > 3) Offset Underflow ([target mode only, does not apply]) > 4) Offset Overflow (target exceeded max. sync. offset) > 5) Phase Change (with outstanding synchronous offset) > 6) Residual data (data left over in sync. FIFO) > > All these conditions are most probably caused by a lost REQ > or ACK. In order to exclude case 4) you could try patching > the NCR driver to negotiate a lower "offset". The bus phase > seems to have been DATA IN, which corresponds to the NCR > command "MOVE TABLE" with DATA IN bus phase (0x19000000). > > Everything I see indicates, that there is handshake problem > on the SCSI bus. > > Regards, STefan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 03:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09576 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 03:48:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA09570 for ; Wed, 26 Aug 1998 03:48:12 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA24750 (5.67b/IDA-1.5); Wed, 26 Aug 1998 11:34:19 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id LAA07224; Wed, 26 Aug 1998 11:24:25 +0200 (CEST) From: Wilko Bulte Message-Id: <199808260924.LAA07224@yedi.iaf.nl> Subject: Re: Fiber Channel. In-Reply-To: from Matthew Jacob at "Aug 25, 98 04:27:28 pm" To: mjacob@feral.com Date: Wed, 26 Aug 1998 11:24:25 +0200 (CEST) Cc: bigj@nlanr.net, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote... > > On Tue, 25 Aug 1998, Wilko Bulte wrote: > > > > People might also be interested in looking at the Emulex LP6000 and > > LP7000 cards. Maybe (*big* maybe) I'll have a chance to check one out. > > Yes- the Emulex cards look good- more from an FC/IP point of view > from what I've heard, and also JAYCOR. And, still to be worth > doing, SOCAL SBus cards for the sparc port (:-)). Digital/Compaq also uses them (the LP6000) to drive FCAL RAID arrays. The LP7000 has a considerable performance advantage and is supposed to be compatible on the driver level. > The big issue with all of this will be fabric and multipathing > device naming support. This kind of stuff is basically my charter > at NASA/Ames for a chunk of the next year. Ughh. Good luck. This is mainly vapourware at the moment. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 06:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01633 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 06:45:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from acc0.visti.net (acc0.visti.net [195.64.225.233]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01610 for ; Wed, 26 Aug 1998 06:45:17 -0700 (PDT) (envelope-from amb@visti.net) Received: from office.visti.net (office.visti.net [195.64.225.183]) by acc0.visti.net (8.8.8/8.8.8) with ESMTP id QAA14622 for ; Wed, 26 Aug 1998 16:44:19 +0300 (EEST) Received: from pinta.visti.net (pinta.visti.net [195.64.225.241]) by office.visti.net (8.6.12/8.ElVisti) with SMTP id QAA14935 for ; Wed, 26 Aug 1998 16:42:16 +0300 Message-ID: <35E41133.446B9B3D@visti.net> Date: Wed, 26 Aug 1998 13:44:19 +0000 From: Andrei Biryukov Organization: Elvisti X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 2.2-970618-RELEN0 i386) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: GDT SCSI Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does FreeBSD support GDT SCSI RAID controller ? http://www.icp-vortex.com/prod/pci/u2_e.html -- âÉÒÀËÏ× áÎÄÒÅÊ IC ElVisti E-mail amb@visti.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 06:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02873 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 06:54:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA02868 for ; Wed, 26 Aug 1998 06:54:31 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 17958 invoked by uid 1000); 26 Aug 1998 14:55:41 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 26 Aug 1998 10:55:41 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Matthew Jacob Subject: Re: Fiber Channel. Cc: freebsd-scsi@FreeBSD.ORG, Jambi Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob, On 25-Aug-98 you wrote: > > The Qlogic Fibre Channel card (2100) is mostly supported- it's the > same driver as the SCSI driver. It's fabric support is minimal > (uh, not there yet) right now, but a plain loop or a PLDA seems to work > as > long as nothing complicated in terms of PLOGI parameters seems to be > expected. > > I don't know the PM2554UWF, although if someone got me one and specs > for it, I'd likely do a driver for it. I am already working on it. It is an i2o based controller, and that raises several issues; FreeBSD declared decision not to do anything in i20 is one of the issues. I2o licensing is another. The driver will be ready in a couple of months. > > I'm also planning to do the Adaptec F9{4,5}0 sooner or later. > > On Tue, 25 Aug 1998, Jambi wrote: > > > Hey all, > > We are thinking about building a little data crunching farm which > > will > > be a whole bunch of FreeBSD machines. We were offered a fiber channel > > controller as our current problem is in IO (having to parse serially > > huge > > network dumps...what a pain). I was looking around the FreeBSD FAQ etc > > and could find no reference to a supported Fiber Channel controllers. > > Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? > > Is > > CAM supporting it? > > > > 10x > > Jambi > > _______________________________________________ > > Jambi Ganbar | (619) 8220938 | jambi@nlanr.net > > San Diego SuperComputer Center > > ________________________________________________ > > > > > > 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 Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 06:55:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03115 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 06:55:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA03086 for ; Wed, 26 Aug 1998 06:55:14 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 17968 invoked by uid 1000); 26 Aug 1998 14:56:43 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808251348.NAA02594@dingo.cdrom.com> Date: Wed, 26 Aug 1998 10:56:43 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: Fiber Channel. Cc: freebsd-scsi@FreeBSD.ORG, Jambi Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith, On 25-Aug-98 you wrote: > > Hey all, > > We are thinking about building a little data crunching farm which > > will > > be a whole bunch of FreeBSD machines. We were offered a fiber channel > > controller as our current problem is in IO (having to parse serially > > huge > > network dumps...what a pain). I was looking around the FreeBSD FAQ etc > > and could find no reference to a supported Fiber Channel controllers. > > Question: Does the DPT PM2554UWF have support in the FreeBSD kernel? > > Is > > CAM supporting it? > > It should behave like a "normal" DPT, so yes, we should support it. Like I said, i20... > > We also support Fibrechannel controllers based on the Qlogic chips. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 08:04:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15061 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 08:04:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15048 for ; Wed, 26 Aug 1998 08:04:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id IAA31997; Wed, 26 Aug 1998 08:04:01 -0700 Date: Wed, 26 Aug 1998 08:04:00 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Wilko Bulte cc: bigj@nlanr.net, freebsd-scsi@FreeBSD.ORG Subject: Re: Fiber Channel. In-Reply-To: <199808260924.LAA07224@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 On Wed, 26 Aug 1998, Wilko Bulte wrote: > As Matthew Jacob wrote... > > > > On Tue, 25 Aug 1998, Wilko Bulte wrote: > > > > > > People might also be interested in looking at the Emulex LP6000 and > > > LP7000 cards. Maybe (*big* maybe) I'll have a chance to check one out. > > > > Yes- the Emulex cards look good- more from an FC/IP point of view > > from what I've heard, and also JAYCOR. And, still to be worth > > doing, SOCAL SBus cards for the sparc port (:-)). > > Digital/Compaq also uses them (the LP6000) to drive FCAL RAID arrays. > The LP7000 has a considerable performance advantage and is supposed > to be compatible on the driver level. > > > The big issue with all of this will be fabric and multipathing > > device naming support. This kind of stuff is basically my charter > > at NASA/Ames for a chunk of the next year. > > Ughh. Good luck. This is mainly vapourware at the moment. > Yes, and no. The actual hardware support is coming along and even the f/w support for fabric logins are around. It just becomes a bit of a pissing match in the OS arena on how to do this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 16:18:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14325 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 16:18:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise-atm.cs.unm.edu [198.83.90.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA14318 for ; Wed, 26 Aug 1998 16:18:39 -0700 (PDT) (envelope-from cfaehl@cs.unm.edu) Received: from avarice.cs.unm.edu [198.83.92.131] by enterprise.cs.unm.edu with esmtp (Exim 1.80 #2) id 0zBop3-0003OA-00; Wed, 26 Aug 1998 17:17:49 -0600 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: CAM-19980716 most recent? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Aug 1998 17:17:38 -0600 From: "Chris D. Faehl" Message-Id: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It doesn't appear as if the above CAM-SNAP works with -current as of this morning (no, on my machine, it hasn't ever - I'm just getting up to speed on -current [which does buildworld without CAM-SNAP diffs applied]). Is there a CAM-SNAP that will? Do most people tracking CAM only track -current when a new CAM-SNAP is released? ------------------------------------------------------------------------------- Chris Faehl | Email: cfaehl@cs.unm.edu The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 Albuquerque, NM 87131 USA | FAX: 505/277-6927 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 26 19:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15184 for freebsd-scsi-outgoing; Wed, 26 Aug 1998 19:30:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (nat0118.mpoweredpc.net [142.177.188.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15174 for ; Wed, 26 Aug 1998 19:30:15 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.8.8) with SMTP id XAA27942; Wed, 26 Aug 1998 23:29:20 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 26 Aug 1998 23:29:20 -0300 (ADT) From: The Hermit Hacker To: "Chris D. Faehl" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM-19980716 most recent? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26 Aug 1998, Chris D. Faehl wrote: > > It doesn't appear as if the above CAM-SNAP works with -current as of > this morning (no, on my machine, it hasn't ever - I'm just getting up > to speed on -current [which does buildworld without CAM-SNAP diffs applied]). > Is there a CAM-SNAP that will? Do most people tracking CAM only track > -current when a new CAM-SNAP is released? I recently backed out the CAM stuff to play with an AVA-1505 controller, but while I was using CAM on my home machine, what I did was sync my sources to the day/time of the CAM-snapshot, apply the patch, and then *carefully* do a 'cvs update' on the source tree. Other then the occasional conflict, that appeared to work pretty good... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 28 17:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17293 for freebsd-scsi-outgoing; Fri, 28 Aug 1998 17:46:53 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17288 for ; Fri, 28 Aug 1998 17:46:50 -0700 (PDT) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id RAA19265; Fri, 28 Aug 1998 17:45:58 -0700 (PDT) Message-ID: <19980828174558.A6421@Alameda.net> Date: Fri, 28 Aug 1998 17:45:58 -0700 From: Ulf Zimmermann To: scsi@FreeBSD.ORG Subject: CAM problems. Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. I have an Intel DK440LX motherboard with an Adaptec AIC-7895 onboard. After going to 980716 CAM I had some problems, but they were solved. Now I am trying to add a new disk to the system and and it gives me trouble about it. Old config was: Channel A = empty Channel B = ID 0 9GB narrow drive, ID 4 CD-Rom, ID 6 CD-W I now added a disk on channel A and the dmesg output is: ahc0: rev 0x03 int a irq 17 on pci0.9.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: rev 0x03 int b irq 17 on pci0.9.1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs ahc1:A:6: refuses synchronous negotiation. Using asynchronous transfers changing root device to wd1s1a cd0 at ahc1 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [328472 x 2048 byte records] da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) cd1: fatal error, failed to attach to device (cd1:ahc1:0:6:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc1:0:6:0): error code 83 da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) I got the disk somehow fdisk, but now fdisk reports this: Playtoy root /root # fdisk da0 fdisk: can't get disk parameters on /dev/rda0; supplying dummy ones ******* Working on device /dev/rda0 ******* parameters extracted from in-core disklabel are: cylinders=1 heads=1 sectors/track=1 (1 blks/cyl) parameters to be used for BIOS calculations are: cylinders=1 heads=1 sectors/track=1 (1 blks/cyl) And it never returns. I have to press CTRL-C Disklabel does return the correct values: Playtoy root /root # disklabel da0 # /dev/rda0c: type: SCSI disk: sd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 526 sectors/unit: 8466192 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 7417616 1048576 4.2BSD 0 0 0 # (Cyl. 65*- 526*) b: 1048576 0 swap # (Cyl. 0 - 65*) c: 8466192 0 unused 0 0 # (Cyl. 0 - 526*) I just made a newfs and it seems to work. fsck /dev/da0s1a seems to work too. But a mount: Playtoy root /root # mount /dev/da0s1a /disk2 mount: /dev/da0s1a on /disk2: incorrect super block And here I am now clueless. Any ideas ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 28 19:09:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27375 for freebsd-scsi-outgoing; Fri, 28 Aug 1998 19:09:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA27362 for ; Fri, 28 Aug 1998 19:09:49 -0700 (PDT) (envelope-from brian@hyperreal.org) Received: (qmail 14747 invoked by uid 24); 29 Aug 1998 02:08:56 -0000 Message-ID: <19980829020856.14746.qmail@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 28 Aug 1998 19:04:01 -0700 To: freebsd-scsi@FreeBSD.ORG From: Brian Behlendorf Subject: medium error Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (please include my address in responses, I'm not on -scsi) I had a disk go bad on me while installing a new one - unfortunately it had a few things on it that are worth trying to salvage the disk for (items that backups didn't save). At this point all I'm getting when I try to talk to it is "Medium format error - device not configured" errors to the console, although the SCSI card can identify it properly, even get the manufacturer & model #. All tools, from disklabel to fdisk, fail to do anything, causing the above error message. Am I outta luck? Is it beyond the OS at this point? Are there any shops in the Bay Area that will re-seat the platters into a new drive housing for a reasonable fee? This was a Seagate 15230N, by the way. Thanks! Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- "Common sense is the collection of prejudices | brian@apache.org acquired by the age of eighteen." - Einstein | brian@hyperreal.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 28 22:14:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11548 for freebsd-scsi-outgoing; Fri, 28 Aug 1998 22:14:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from word.smith.net.au (castles244.castles.com [208.214.165.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11522 for ; Fri, 28 Aug 1998 22:14:11 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id WAA00589; Fri, 28 Aug 1998 22:11:09 GMT (envelope-from mike@word.smith.net.au) Message-Id: <199808282211.WAA00589@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Behlendorf cc: freebsd-scsi@FreeBSD.ORG Subject: Re: medium error In-reply-to: Your message of "Fri, 28 Aug 1998 19:04:01 MST." <19980829020856.14746.qmail@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Aug 1998 22:11:08 +0000 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > (please include my address in responses, I'm not on -scsi) > > I had a disk go bad on me while installing a new one - unfortunately it had > a few things on it that are worth trying to salvage the disk for (items > that backups didn't save). At this point all I'm getting when I try to > talk to it is "Medium format error - device not configured" errors to the > console, although the SCSI card can identify it properly, even get the > manufacturer & model #. These parameters are usually in nonvolatile memory, not on the disk, although there is often a second firmware component loaded off the disk. > All tools, from disklabel to fdisk, fail to do > anything, causing the above error message. Am I outta luck? Is it beyond > the OS at this point? It looks like the disk is damaged in a fashion that's making it impossible to obtain slice and/or label information. Recovery at this point is problematic, but may not be impossible, depending on how much time and effort you are willing to put into the process, and how lucky you are. To start with, try writing a simple program which just opens the bare device (eg. /dev/sdX). If the open completes OK, then you should be able to improve the program to build an image of the entire disk in a file on another disk. You will have to read the device one block at a time, and note whether you succeed or fail. It's possible that the disk may go offline after a failure, so you may need to further improve the program such that you can reboot and take up where you left off. If you are unable to open the bare device, then you should check with the scsi(8) command as to whether you can read a single block from the drive. This will involve some familiarity with SCSI commands. If this works, then you should build a program as described above, but use raw SCSI commands rather than device I/O to talk to the drive. The chances of this sort of program working are only slightly better than the first. If you are able to recover most of the disk, you will then need to reconstruct the missing blocks as required to recover your data. Needless to say, you should make a backup of the image file before you start. Start by reestablishing the MBR (if the disk had one), and then the partition table(s) in the slices. If you can't remember what the table(s) looked like, search the image file for the filesystem magic numbers to find the beginning of your partition(s). This can be complicated if the top of a filesystem has been damaged; you will have to locate an alternate superblock, work out from that where the base of the filesystem was, reconstruct and then use fsck -b. > Are there any shops in the Bay Area that will > re-seat the platters into a new drive housing for a reasonable fee? Without knowing the FRU out of the vendor-specific data from the SCSI error codes, and having the FRU list for the disk in question, it's difficult to know whether this would be worth the effort. There are a number of such organisations; check your copy of MicroTimes as I'm fairly sure that several of them advertise there regularly. > This was a Seagate 15230N, by the way. Hmm, that's fairly odd. These (Hawk 4) are normally pretty solid; I presume you *were* keeping it cool? 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Aug 29 05:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23072 for freebsd-scsi-outgoing; Sat, 29 Aug 1998 05:46:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zeus.starwon.com.au (zeus.starwon.com.au [203.15.243.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23066 for ; Sat, 29 Aug 1998 05:46:07 -0700 (PDT) (envelope-from paul@fastlane.net.au) Received: from penfold.fastlane.net.au (penfold.fastlane.net.au [203.15.242.186]) by zeus.starwon.com.au (8.9.0/8.9.0) with SMTP id UAA11096 for ; Sat, 29 Aug 1998 20:48:44 +0800 (WST) Message-Id: <3.0.5.32.19980829203901.007d64a0@zeus.starwon.com.au> X-Sender: paulpop@zeus.starwon.com.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 29 Aug 1998 20:39:01 +0800 To: scsi@FreeBSD.ORG From: Paul Reece Subject: well. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Guys. You've probably answered this a million times before... When can we expect support for AdvanSYS SCSI adaptors? (in my case for the UltraWide PCI one) Anytime soon? Regards, Paul. -- Paul Reece | Perth, Western Australia paul@fastlane.net.au | http://www.fastlane.net.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 29 09:43:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11913 for freebsd-scsi-outgoing; Sat, 29 Aug 1998 09:43:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11908 for ; Sat, 29 Aug 1998 09:43:36 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA20115; Sat, 29 Aug 1998 10:36:31 -0600 (MDT) Date: Sat, 29 Aug 1998 10:36:31 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808291636.KAA20115@narnia.plutotech.com> To: Paul Reece cc: scsi@FreeBSD.ORG Subject: Re: well. Newsgroups: pluto.freebsd.scsi In-Reply-To: <3.0.5.32.19980829203901.007d64a0@zeus.starwon.com.au> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <3.0.5.32.19980829203901.007d64a0@zeus.starwon.com.au> you wrote: > > Hi Guys. > > You've probably answered this a million times before... > > When can we expect support for AdvanSYS SCSI adaptors? (in my case for the > UltraWide PCI one) The UltraWide cards won't happen for a bit longer. I need to conver the DPT driver to CAM first. I already have a card and sufficient documentation to modify the existing CAM AdvanSys driver for UW support, but as this is not on the critical path for 3.0 CAM integration, other things have to come first. > Anytime soon? I'd say it's a least a month away. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message