From owner-freebsd-scsi Mon Mar 27 5:25:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from free.transecon.ru (free.transecon.ru [194.67.127.6]) by hub.freebsd.org (Postfix) with ESMTP id D4EE337BAF9 for ; Mon, 27 Mar 2000 05:25:18 -0800 (PST) (envelope-from CoreDumped@CoreDumped.null.ru) Received: from localhost (core@localhost) by free.transecon.ru (8.9.3/8.9.3) with ESMTP id RAA58244 for ; Mon, 27 Mar 2000 17:24:46 +0400 (MSD) (envelope-from CoreDumped@CoreDumped.null.ru) Date: Mon, 27 Mar 2000 17:24:45 +0400 (MSD) From: Eugeny Kuzakov X-Sender: core@free.transecon.ru Reply-To: CoreDumped@CoreDumped.null.ru To: scsi@freebsd.org Subject: 3.4R*onboard aic aic7870 on acer altos 7000v Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi*& I am tryed to install 3.4R on this machine. fbsd can not find aic7870. Can anyony help me? 10tx. Eugeny. p.s. I can't install more new version of freebsd because cronyx cards (cx) supported only on 3.x fbsd versions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 27 6:26: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 4AF8A37BB38 for ; Mon, 27 Mar 2000 06:25:58 -0800 (PST) (envelope-from kibbet@kibby.au.knfpub.com) Received: (from kibbet@localhost) by kibby.au.knfpub.com (8.9.3/8.9.3) id XAA07019; Mon, 27 Mar 2000 23:52:33 +0930 (CST) (envelope-from kibbet) 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: Mon, 27 Mar 2000 23:52:32 +0930 (CST) From: kibbet To: Eugeny Kuzakov Subject: RE: 3.4R*onboard aic aic7870 on acer altos 7000v Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, From my 4.0-STABLE LINT file (v 1.749.2.4) it appears cx devices are supported, though, I don't have one therefore I haven't compiled support for it; # cx: Cronyx/Sigma multiport sync/async (with Cisco or PPP framing) Also looks like AIC7xxx devices are supported (from my 3.2 and 4.0 LINT file); device ahc # AHA2940 and onboard AIC7xxx devices So, recompile your kernel with the above device line, and things should be happy. (You may need "device pci" as well) Don't forget: LINT is our friend. :) Kent Ibbetson KNF Publishing kibbet@knfpub.com On 27-Mar-00 Eugeny Kuzakov wrote: > > hi*& > > I am tryed to install 3.4R on this machine. > fbsd can not find aic7870. > Can anyony help me? > 10tx. > Eugeny. > > p.s. I can't install more new version of freebsd because cronyx cards > (cx) supported only on 3.x fbsd versions. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 27 13:49:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from alumni.cs.wisc.edu (alumni.cs.wisc.edu [128.105.12.18]) by hub.freebsd.org (Postfix) with ESMTP id A430037B6F7 for ; Mon, 27 Mar 2000 13:49:37 -0800 (PST) (envelope-from mjhans@alumni.cs.wisc.edu) Received: (from mjhans@localhost) by alumni.cs.wisc.edu (8.9.2/8.9.2) id PAA14773 for freebsd-scsi@freebsd.org; Mon, 27 Mar 2000 15:49:33 -0600 (CST) Date: Mon, 27 Mar 2000 15:49:33 -0600 (CST) From: Matthew Hanselman Message-Id: <200003272149.PAA14773@alumni.cs.wisc.edu> To: freebsd-scsi@freebsd.org Subject: Terrible SCSI performance with 4.0 -- please help Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running 4.0-RELEASE on a K6-2 with an Adaptec 29160 and some IBM DMVS18M drives (nice 10k disks), and am getting absolutely terrible performance. My setup has a Quantum IDE drive in it as well, and I get about 2X better read/write performance on the IDE drive than the SCSI (the SCSI should be a bit faster than the IDE...) I've tried swapping in an Adaptec 2940 to no avail, so it's not the 29160 specifically; I've tried moving the disks to another (Linux) box and the drives work perfectly fine, so it's not the drives/cables. I don't know what else to try, even what other info to send out as diagnostics. Apologies if this is not the right list; I'm running out of ideas, please point me to the right list if nothing else. Thanks a lot. - Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 27 14:24:27 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 9368837B5F0 for ; Mon, 27 Mar 2000 14:24:23 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA07150; Mon, 27 Mar 2000 15:23:50 -0700 (MST) (envelope-from ken) Date: Mon, 27 Mar 2000 15:23:50 -0700 From: "Kenneth D. Merry" To: Matthew Hanselman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Terrible SCSI performance with 4.0 -- please help Message-ID: <20000327152350.A7100@panzer.kdm.org> References: <200003272149.PAA14773@alumni.cs.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003272149.PAA14773@alumni.cs.wisc.edu>; from mjhans@cs.wisc.edu on Mon, Mar 27, 2000 at 03:49:33PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 27, 2000 at 15:49:33 -0600, Matthew Hanselman wrote: > I'm running 4.0-RELEASE on a K6-2 with an Adaptec 29160 and some IBM > DMVS18M drives (nice 10k disks), and am getting absolutely terrible > performance. My setup has a Quantum IDE drive in it as well, and I get > about 2X better read/write performance on the IDE drive than the SCSI > (the SCSI should be a bit faster than the IDE...) > > I've tried swapping in an Adaptec 2940 to no avail, so it's not the 29160 > specifically; I've tried moving the disks to another (Linux) box and the > drives work perfectly fine, so it's not the drives/cables. I don't know > what else to try, even what other info to send out as diagnostics. > > Apologies if this is not the right list; I'm running out of ideas, please > point me to the right list if nothing else. Thanks a lot. Well, it'll take a little more information to try to track down the problem. How about dmesg output, and benchmark numbers from bonnie and iozone. Also, is write caching enabled or disabled on those drives? You can find out with camcontrol, like this: camcontrol modepage da0 -m 8 will print out mode page 8 for da0. While you're doing the benchmarks, run top(1) to see if you're CPU bound. Also, are you getting any error messages? 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 27 16: 2: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from alumni.cs.wisc.edu (alumni.cs.wisc.edu [128.105.12.18]) by hub.freebsd.org (Postfix) with ESMTP id 9C89037B9ED for ; Mon, 27 Mar 2000 16:02:02 -0800 (PST) (envelope-from mjhans@alumni.cs.wisc.edu) Received: from localhost (mjhans@localhost) by alumni.cs.wisc.edu (8.9.2/8.9.2) with SMTP id SAA15508; Mon, 27 Mar 2000 18:01:58 -0600 (CST) Date: Mon, 27 Mar 2000 18:01:56 -0600 (CST) From: Matthew Hanselman To: ken@kdm.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Terrible SCSI performance with 4.0 -- please help 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 Before I get into the my message, thanks for the help! Here's my info: No errors, at least in /var/log/messages. Just the expected (?) diag re: the controllers/disks upon boot, which mimics that of dmesg: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) (Same for da1, 2, and 3) Here's the IDE disk, FYI: ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 As for caching, I don't know how to make out all of these options, but here's your requested info from camcontrol: IC: 0 ABPF: 0 CAP: 0 DISC: 0 SIZE: 0 WCE: 0 MF: 0 RCD: 0 Demand Retention Priority: 1 Write Retention Priority: 1 Disable Pre-fetch Transfer Length: 65535 Minimum Pre-fetch: 0 Maximum Pre-fetch: 65535 Maximum Pre-fetch Ceiling: 65535 Getting into benchmarking: Funny thing is bonnie makes it look as though the drives are similar. Here was my original benchmark that confirms disk times: copying a tar file of size 26M to a directory and untarring it into the same directory, doing so a couple of times to take caching into account. Here's the output time from that: For the IDE disk: % time tar xf apache.tar 0.071u 1.559s 0:05.62 28.8% 318+308k 2+1996io 0pf+0w For the SCSI disk: % time tar xf apache.tar 0.095u 1.396s 0:10.11 14.6% 313+303k 2+2166io 0pf+0w Here's bonnie output for the IDE disk: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 60 13247 97.2 18640 51.0 23199 75.2 16173 99.9 95878 100.0 11389.4 97.4 This seems to be taking about about 50% user and about 40% system time For the SCSI disk: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 60 12845 96.6 27812 73.4 30856 93.6 15726 99.6 96393 98.8 11477.9 99.8 This seems to be taking about 60% user and about 30% system time... Finally, iozone for the IDE disk: random random KB reclen write rewrite read reread read write 60000 4 14156 17189 61853 72246 52582 831 bkwd record stride read rewrite read fwrite frewrite fread freread 50540 120910 62517 14640 17569 49850 60480 And for the SCSI disk (Note the write being 95% bigger, etc): random random KB reclen write rewrite read reread read write 60000 4 27227 28223 86392 65592 67151 1213 bkwd record stride read rewrite read fwrite frewrite fread freread 88551 115087 67553 21548 18198 51120 75003 top said the CPU was mostly idle (around 80-90% idle) during these... Any ideas? - Matt > Well, it'll take a little more information to try to track down the > problem. > > How about dmesg output, and benchmark numbers from bonnie and iozone. > > Also, is write caching enabled or disabled on those drives? You can find > out with camcontrol, like this: > > camcontrol modepage da0 -m 8 > > will print out mode page 8 for da0. > > While you're doing the benchmarks, run top(1) to see if you're CPU bound. > > Also, are you getting any error messages? > > 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 27 16: 7: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (pyramid.cdrom.com [204.216.28.136]) by hub.freebsd.org (Postfix) with ESMTP id 3310337B720 for ; Mon, 27 Mar 2000 16:06:59 -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 QAA87098; Mon, 27 Mar 2000 16:10:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003280010.QAA87098@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Hanselman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Terrible SCSI performance with 4.0 -- please help In-reply-to: Your message of "Mon, 27 Mar 2000 18:01:56 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Mar 2000 16:10:09 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org None of this suggests 'terrible SCSI performance' so far, just the usual misconceptions about benchmarks, etc. -- \\ 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 27 16:15: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 78FC537B87D for ; Mon, 27 Mar 2000 16:15:19 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA08095; Mon, 27 Mar 2000 17:15:15 -0700 (MST) (envelope-from ken) Date: Mon, 27 Mar 2000 17:15:15 -0700 From: "Kenneth D. Merry" To: Matthew Hanselman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Terrible SCSI performance with 4.0 -- please help Message-ID: <20000327171515.A8046@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mjhans@cs.wisc.edu on Mon, Mar 27, 2000 at 06:01:56PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 27, 2000 at 18:01:56 -0600, Matthew Hanselman wrote: > Before I get into the my message, thanks for the help! > > Here's my info: > > No errors, at least in /var/log/messages. Just the expected (?) diag re: > the controllers/disks upon boot, which mimics that of dmesg: > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > > (Same for da1, 2, and 3) > > Here's the IDE disk, FYI: > ad0: 6149MB [13328/15/63] at ata0-master using UDMA33 > > > As for caching, I don't know how to make out all of these options, but > here's your requested info from camcontrol: > > IC: 0 > ABPF: 0 > CAP: 0 > DISC: 0 > SIZE: 0 > WCE: 0 WCE == 0 means write caching is disabled. > Getting into benchmarking: Funny thing is bonnie makes it look as though > the drives are similar. Here was my original benchmark that confirms disk > times: copying a tar file of size 26M to a directory and untarring it into > the same directory, doing so a couple of times to take caching into > account. Here's the output time from that: > > For the IDE disk: > % time tar xf apache.tar > 0.071u 1.559s 0:05.62 28.8% 318+308k 2+1996io 0pf+0w > > For the SCSI disk: > % time tar xf apache.tar > 0.095u 1.396s 0:10.11 14.6% 313+303k 2+2166io 0pf+0w Write caching could be affecting your results somewhat in comparison to the IDE drive. You can try enabling write caching for your SCSI disk, like this: camcontrol modepage da0 -m 8 -P 3 -e Then change the 'WCE' bit from 0 to 1. > Here's bonnie output for the IDE disk: > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 60 13247 97.2 18640 51.0 23199 75.2 16173 99.9 95878 100.0 11389.4 97.4 > > This seems to be taking about about 50% user and about 40% system time > > For the SCSI disk: > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 60 12845 96.6 27812 73.4 30856 93.6 15726 99.6 96393 98.8 11477.9 99.8 > > This seems to be taking about 60% user and about 30% system time... Your SCSI disk looks like it is significantly faster than the IDE disk for sequential writes -- 28MB/sec block writes versus 18.6MB/sec. > Finally, iozone for the IDE disk: > random random > KB reclen write rewrite read reread read write > 60000 4 14156 17189 61853 72246 52582 831 > > bkwd record stride > read rewrite read fwrite frewrite fread freread > 50540 120910 62517 14640 17569 49850 60480 > > > And for the SCSI disk (Note the write being 95% bigger, etc): > random random > KB reclen write rewrite read reread read write > 60000 4 27227 28223 86392 65592 67151 1213 > > bkwd record stride > read rewrite read fwrite frewrite fread freread > 88551 115087 67553 21548 18198 51120 75003 > > top said the CPU was mostly idle (around 80-90% idle) during these... > > Any ideas? I'm not sure you really have a problem here. It looks like your SCSI disks are faster than your generally faster than your IDE disk. It makes sense that you'd use more CPU with the SCSI disks, since you're doing more I/O to them than the IDE disk. 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 27 16:27:50 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 87D9937B720 for ; Mon, 27 Mar 2000 16:27:46 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA08200; Mon, 27 Mar 2000 17:27:43 -0700 (MST) (envelope-from ken) Date: Mon, 27 Mar 2000 17:27:42 -0700 From: "Kenneth D. Merry" To: Matthew Hanselman Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Terrible SCSI performance with 4.0 -- please help Message-ID: <20000327172742.A8034@panzer.kdm.org> References: <20000327171515.A8046@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000327171515.A8046@panzer.kdm.org>; from ken@kdm.org on Mon, Mar 27, 2000 at 05:15:15PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 27, 2000 at 17:15:15 -0700, Kenneth D. Merry wrote: > On Mon, Mar 27, 2000 at 18:01:56 -0600, Matthew Hanselman wrote: > > Any ideas? > > I'm not sure you really have a problem here. It looks like your SCSI disks > are faster than your generally faster than your IDE disk. *sigh* That should read: "It looks like your SCSI disks are generally faster than your IDE disk." 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 27 17:49:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from free.transecon.ru (free.transecon.ru [194.67.127.6]) by hub.freebsd.org (Postfix) with ESMTP id 94E2337B7F4 for ; Mon, 27 Mar 2000 17:49:09 -0800 (PST) (envelope-from CoreDumped@CoreDumped.null.ru) Received: from localhost (core@localhost) by free.transecon.ru (8.9.3/8.9.3) with ESMTP id FAA62175; Tue, 28 Mar 2000 05:48:03 +0400 (MSD) (envelope-from CoreDumped@CoreDumped.null.ru) Date: Tue, 28 Mar 2000 05:48:03 +0400 (MSD) From: Eugeny Kuzakov X-Sender: core@free.transecon.ru Reply-To: CoreDumped@CoreDumped.null.ru To: kibbet Cc: scsi@FreeBSD.ORG Subject: RE: 3.4R*onboard aic aic7870 on acer altos 7000v In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Mar 2000, kibbet wrote: > >From my 4.0-STABLE LINT file (v 1.749.2.4) it appears cx devices > are supported, though, I don't have one therefore I haven't > compiled support for it; > > # cx: Cronyx/Sigma multiport sync/async (with Cisco or PPP framing) Yes. Some driver present in distribution. Butthis driver does not works in reality. Vendors driver supports =<3.4R. cx driver in 4R supported by fbsd developers only for success compile kernel :( > Also looks like AIC7xxx devices are supported (from my 3.2 and 4.0 LINT file); > > device ahc # AHA2940 and onboard AIC7xxx devices > So, recompile your kernel with the above device line, and things should > be happy. (You may need "device pci" as well) ahc by default compiled into kernel.GENERIC, that placed on installation diskettes. I know that it should works. But I haven' success. I am not so understand. > > Don't forget: LINT is our friend. :) yes,yes...:) There is main problem of linuxoids -- they has not LINT. :) Eugeny. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 27 20:43:43 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ultra.ultra.net.au (ultra.ultra.net.au [203.20.237.5]) by hub.freebsd.org (Postfix) with ESMTP id 6BB1A37B99A; Mon, 27 Mar 2000 20:43:37 -0800 (PST) (envelope-from avatar@ultra.ultra.net.au) Received: from localhost (avatar@localhost) by ultra.ultra.net.au (8.9.3/8.9.3) with SMTP id OAA25062; Tue, 28 Mar 2000 14:43:25 +1000 (EST) Date: Tue, 28 Mar 2000 14:43:25 +1000 (EST) From: Karl Hanmore To: freebsd-questions@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: DPT Raid controllers... 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 Good Day, Please excuse my ignorance (and cross posting). I have just installed a DPT SmartRaid IV card, and am very happy that FreeBSD finds and uses it with no problems. To simulate drive failure, I have unplugged one of the drives (with the system powered down) and then powered the system up. The raid controllor knows something is amis, and beeps continually during boot. However, I was disapointed not to see any form of error/warning message in the logs. Is there a way to get some feedback? Unfortuantly, the box is being installed remotely, and thus, I cannot hear its wails for help in the event of drive failure... Any and all help would be greatly appreciated. As I am not subscribed to this list at present, could you please mail me and CC the list. Kind Regards, Karl Hanmore Ultranet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 27 20:50:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from iohost.com (io001.iohost.com [209.189.124.99]) by hub.freebsd.org (Postfix) with ESMTP id 6378337BB06; Mon, 27 Mar 2000 20:50:39 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from ntserver (w146.z206111055.lax-ca.dsl.cnc.net [206.111.55.146]) by iohost.com (8.9.3/8.9.3) with SMTP id UAA24603; Mon, 27 Mar 2000 20:50:19 -0800 Message-Id: <3.0.5.32.20000327204938.041b0100@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 27 Mar 2000 20:49:38 -0800 To: Karl Hanmore , freebsd-questions@FreeBSD.ORG From: "Randy A. Katz" Subject: Re: DPT Raid controllers... Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've used the later versions on Linux and there is a diagnostic executable which I run every 5 minutes from a script which sends email to my cell phone if the condition changes. Perhaps DPT has something like that on the FreeBSD side or you can cat /proc something to get the status...I would call them and escalate, the first 2-3 techs won't have a clue what you're talking about... Take care, Randy Katz At 02:43 PM 3/28/00 +1000, Karl Hanmore wrote: >Good Day, >Please excuse my ignorance (and cross posting). > >I have just installed a DPT SmartRaid IV card, and am very happy that >FreeBSD finds and uses it with no problems. > >To simulate drive failure, I have unplugged one of the drives (with the >system powered down) and then powered the system up. The raid controllor >knows something is amis, and beeps continually during boot. However, I >was disapointed not to see any form of error/warning message in the logs. >Is there a way to get some feedback? Unfortuantly, the box is being >installed remotely, and thus, I cannot hear its wails for help in the >event of drive failure... > >Any and all help would be greatly appreciated. As I am not subscribed to >this list at present, could you please mail me and CC the list. > >Kind Regards, >Karl Hanmore >Ultranet > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" 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 28 12:19:23 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 37CC237BB34 for ; Tue, 28 Mar 2000 12:19:14 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id VAA74225 for ; Tue, 28 Mar 2000 21:23:56 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Tue, 28 Mar 2000 21:16:38 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: Bus rescan (second try) 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 fragment below is intended to rescan the bus on connection of a device. The problem is that cam_periph_find always returns NULL, because a SIM does not seem to have a periph. An option would be to make xpt_periph available in cam_periph.h. Or someone telling me how to do the rescan on connection of a drive. I think I've tried everything imaginable. Nick /* Create a path and lookup the peripheral for the SIM */ if (xpt_create_path(&path, NULL, cam_sim_path(umass_sim), UMASS_SCSIID_HOST, 0) != CAM_REQ_CMP) return; periph = cam_periph_find(path, DEVNAME); if (periph == NULL) { DPRINTF(UDMASS_SCSI, ("%s:%d:%d:%d: no periph\n", USBDEVNAME(sc->sc_dev), cam_sim_path(umass_sim), device_get_unit(sc->sc_dev), 0)); xpt_free_path(path); return; } xpt_free_path(path); /* Lookup the path again, but now include the periph in the path*/ if (xpt_create_path(&path, periph, cam_sim_path(umass_sim), UMASS_SCSIID_HOST, 0) != CAM_REQ_CMP) return; xpt_setup_ccb(&ccb->ccb_h, path, 5/*priority (low)*/); ccb->ccb_h.func_code = XPT_SCAN_BUS; ccb->ccb_h.cbfcnp = umass_cam_rescan_callback; ccb->crcn.flags = CAM_FLAG_NONE; xpt_action(ccb); -- 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 Wed Mar 29 1:56:32 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 0BBA737BC3C for ; Wed, 29 Mar 2000 01:56:26 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.calcaphon.com (henny.calcaphon.com [10.0.0.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id LAA53999 for ; Wed, 29 Mar 2000 11:01:16 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Wed, 29 Mar 2000 10:53:52 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: Re: Bus rescan (second try) 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 Ken, Justin, Sorry for the rerun. After checking the archives again, I don't expect anyone to have a better answer this time round, so I'll just propose a patch. It makes xpt_periph a kernel global variable. Let me know whether this is acceptable, and if not, how else to get a pointer to the peripheral for the bus to be scanned. xpt_done (and subroutines after that, require periph to be set in the path). Nick Index: cam_periph.h =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_periph.h,v retrieving revision 1.7 diff -u -r1.7 cam_periph.h --- cam_periph.h 2000/03/15 21:55:46 1.7 +++ cam_periph.h 2000/03/29 09:48:11 @@ -35,6 +35,8 @@ #ifdef _KERNEL +struct cam_periph *xpt_periph; + extern struct linker_set periphdriver_set; typedef void (periph_init_t)(void); /* Index: cam_xpt.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.81 diff -u -r1.81 cam_xpt.c --- cam_xpt.c 2000/03/15 21:55:46 1.81 +++ cam_xpt.c 2000/03/29 09:46:22 @@ -528,7 +528,7 @@ */ static u_int xpt_ccb_count; /* Current count of allocated ccbs */ -static struct cam_periph *xpt_periph; +struct cam_periph *xpt_periph; static periph_init_t xpt_periph_init; On Tue, 28 Mar 2000, Nick Hibma wrote: > > The fragment below is intended to rescan the bus on connection of a > device. The problem is that cam_periph_find always returns NULL, because > a SIM does not seem to have a periph. > > An option would be to make xpt_periph available in cam_periph.h. Or > someone telling me how to do the rescan on connection of a drive. > > I think I've tried everything imaginable. > > Nick > > > /* Create a path and lookup the peripheral for the SIM */ > if (xpt_create_path(&path, NULL, cam_sim_path(umass_sim), > UMASS_SCSIID_HOST, 0) > != CAM_REQ_CMP) > return; > periph = cam_periph_find(path, DEVNAME); > if (periph == NULL) { > DPRINTF(UDMASS_SCSI, ("%s:%d:%d:%d: no periph\n", > USBDEVNAME(sc->sc_dev), cam_sim_path(umass_sim), > device_get_unit(sc->sc_dev), 0)); > xpt_free_path(path); > return; > } > xpt_free_path(path); > > /* Lookup the path again, but now include the periph in the path*/ > if (xpt_create_path(&path, periph, cam_sim_path(umass_sim), > UMASS_SCSIID_HOST, 0) > != CAM_REQ_CMP) > return; > > xpt_setup_ccb(&ccb->ccb_h, path, 5/*priority (low)*/); > ccb->ccb_h.func_code = XPT_SCAN_BUS; > ccb->ccb_h.cbfcnp = umass_cam_rescan_callback; > ccb->crcn.flags = CAM_FLAG_NONE; > xpt_action(ccb); > > > -- > 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 Wed Mar 29 6:33:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 40FE637C1A6; Wed, 29 Mar 2000 06:32:55 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA17667; Wed, 29 Mar 2000 09:32:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA26479; Wed, 29 Mar 2000 09:32:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 29 Mar 2000 09:32:24 -0500 (EST) To: picapau@minmei.iqm.unicamp.br Cc: alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: SCSI disk problems on AS1000 In-Reply-To: <20000329111836.A10213@minmei.iqm.unicamp.br> References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14562.4832.203053.753476@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Severo writes: > > My apologies for such an obscure sentence =) > > What I meant by that was that I had to use the command "exerc" > on the srm monitor prior to the boot procedure to sort of > "warm up" the disks. > > Without this "warm up exercise" for a few seconds the disks are detected but > their size is not assessed (this failure is what I meant by > "taken to be offline"). Hmm.. Older DEC disks tend to not spin up when they're powered on. I'd assumed that the FreeBSD CAM system would take care of spinning up such disks. Can a SCSI guru out there confirm this? Bear in mind that he's using the ncr driver, so some bets are off... Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 29 8:44: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 BB69337C0D1; Wed, 29 Mar 2000 08:44:16 -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 IAA11160; Wed, 29 Mar 2000 08:43:48 -0800 Date: Wed, 29 Mar 2000 08:44:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: SCSI disk problems on AS1000 In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > I'd assumed that the FreeBSD CAM system would take care of spinning up > such disks. Can a SCSI guru out there confirm this? Bear in mind > that he's using the ncr driver, so some bets are off... > The cam_periph_error code does issue a START UNIT command, but only if scsi_error_action returns an error_action for this, which is then contingent upon what kind of error the disk returns. Frankly, this whole area of CAM is a bit too labyrynthine to state unequivocally that a START UNIT would be sent here. Sigh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 29 9:49:22 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail1.csun.edu (mail1.csun.edu [130.166.1.23]) by hub.freebsd.org (Postfix) with ESMTP id 1805737B8CE for ; Wed, 29 Mar 2000 09:49:02 -0800 (PST) (envelope-from albert.kinderman@csun.edu) Received: from csun.edu (s097n054.csun.edu [130.166.97.54]) by mail1.csun.edu (2.0.3/SMS 2.0.3) with ESMTP id JAA46348; Wed, 29 Mar 2000 09:43:24 -0800 Message-ID: <38E2420A.7A2CA84@csun.edu> Date: Wed, 29 Mar 2000 09:48:58 -0800 From: Albert Kinderman X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: All SCSI Install: No Disks Found! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to install 3.4 on a Dell PowerEdge 4400 which has three scsi controllers: an Adaptec AIC-7899 and an AIC-7880 on board and a 2940U2W. Right now, the cdrom is on the 7880 and the two hard drives are on the 7899. Using either the floppies or the 3.4 cdrom to begin the install, the install kernel boots, but when I choose the install type (novice, quick, or custom), the install fails with the message that no hard drives are found. In looking at the messages that flash by and those to be found by Alt-F2, I can see that the PCI bus is probed and the Intel ethernet card is found (fxp0), but there are no adaptec controllers found (ahc0 or ahc1). Is there something special to be done for an all scsi install? My previous experience is with ide drives. Thanks, Al (posted previously on freebsd-questions with no response) -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Albert Kinderman California State University, Northridge albert.kinderman@csun.edu Department of Management Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 29 10: 5:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E5B2637C110; Wed, 29 Mar 2000 10:05:13 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA91931; Wed, 29 Mar 2000 11:04:39 -0700 (MST) (envelope-from ken) Date: Wed, 29 Mar 2000 11:04:38 -0700 From: "Kenneth D. Merry" To: Matthew Jacob Cc: Andrew Gallatin , picapau@minmei.iqm.unicamp.br, alpha@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329110438.A91800@panzer.kdm.org> References: <14562.4832.203053.753476@grasshopper.cs.duke.edu> 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 29, 2000 at 08:44:04AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 08:44:04 -0800, Matthew Jacob wrote: > > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > > I'd assumed that the FreeBSD CAM system would take care of spinning up > > such disks. Can a SCSI guru out there confirm this? Bear in mind > > that he's using the ncr driver, so some bets are off... > > > > The cam_periph_error code does issue a START UNIT command, but only if > scsi_error_action returns an error_action for this, which is then contingent > upon what kind of error the disk returns. Frankly, this whole area of CAM is a > bit too labyrynthine to state unequivocally that a START UNIT would be sent > here. Sigh. Yes, it is one of the most complicated pieces of the CAM code. Error recovery in general is complicated. That code is being rewritten, though. In any case, yes, you will get a start unit if the error is 0x04,0x02, or "Logical unit not ready, initializing cmd. required". You will also get a start unit if you have a Quantum Fireball ST and it returns 0x04,0x0b. Since the boot disk in the machine in question must be spinning in order for any OS to boot, you should be able to get dmesg output from the machine, and we can see what sort of error the disks are returning. If you just want to kludge around it, you can do things like: camcontrol start da1 in /etc/rc before the disks are mounted. If these disks are returning a non-standard sense code, we can probably quirk them so they'll get started. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 29 10:33:52 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 599FD37BC92 for ; Wed, 29 Mar 2000 10:32:40 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA92189; Wed, 29 Mar 2000 11:32:31 -0700 (MST) (envelope-from ken) Date: Wed, 29 Mar 2000 11:32:31 -0700 From: "Kenneth D. Merry" To: Albert Kinderman Cc: scsi@FreeBSD.ORG Subject: Re: All SCSI Install: No Disks Found! Message-ID: <20000329113231.A92169@panzer.kdm.org> References: <38E2420A.7A2CA84@csun.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38E2420A.7A2CA84@csun.edu>; from albert.kinderman@csun.edu on Wed, Mar 29, 2000 at 09:48:58AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 29, 2000 at 09:48:58 -0800, Albert Kinderman wrote: > I am trying to install 3.4 on a Dell PowerEdge 4400 which has three scsi > controllers: an Adaptec AIC-7899 and an AIC-7880 on board and a > 2940U2W. Right now, the cdrom is on the 7880 and the two hard drives > are on the 7899. > > Using either the floppies or the 3.4 cdrom to begin the install, the > install kernel boots, but when I choose the install type (novice, quick, > or custom), the install fails with the message that no hard drives are > found. > > In looking at the messages that flash by and those to be found by > Alt-F2, I can see that the PCI bus is probed and the Intel ethernet card > is found (fxp0), but there are no adaptec controllers found (ahc0 or > ahc1). > > Is there something special to be done for an all scsi install? My > previous experience is with ide drives. The 7899 isn't supported in 3.4, but it is supported in FreeBSD 4.0. So you need to install 4.0. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 29 12:45:56 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 8428D37C187; Wed, 29 Mar 2000 12:45:31 -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 WAA18951; Wed, 29 Mar 2000 22:29:42 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02201; Wed, 29 Mar 2000 20:52:37 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 20:52:37 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@freebsd.org, scsi@freebsd.org Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329205237.E2044@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> <14562.4832.203053.753476@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 29, 2000 at 09:32:24AM -0500 X-OS: 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 29, 2000 at 09:32:24AM -0500, Andrew Gallatin wrote: > > Andre Severo writes: > > > > My apologies for such an obscure sentence =) > > > > What I meant by that was that I had to use the command "exerc" > > on the srm monitor prior to the boot procedure to sort of > > "warm up" the disks. > > > > Without this "warm up exercise" for a few seconds the disks are detected but > > their size is not assessed (this failure is what I meant by > > "taken to be offline"). > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. These are the older RZxx disks. The 'multivendor variant' of the same drives (SWX*-*) are set for staggered spinup (spin up delay based on SCSI target ID). 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 Wed Mar 29 12:46: 0 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 0CBD237C110; Wed, 29 Mar 2000 12:45:41 -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 WAA18950; Wed, 29 Mar 2000 22:29:41 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02190; Wed, 29 Mar 2000 20:51:08 +0200 (CEST) (envelope-from wilko) Date: Wed, 29 Mar 2000 20:51:08 +0200 From: Wilko Bulte To: Andrew Gallatin Cc: picapau@minmei.iqm.unicamp.br, alpha@freebsd.org, scsi@freebsd.org Subject: Re: SCSI disk problems on AS1000 Message-ID: <20000329205108.D2044@yedi.iaf.nl> Reply-To: wilko@freebsd.org References: <20000325181342.A88910@minmei.iqm.unicamp.br> <14557.27001.718759.711008@grasshopper.cs.duke.edu> <20000329092158.A96147@minmei.iqm.unicamp.br> <14562.2571.201291.426577@grasshopper.cs.duke.edu> <20000329111836.A10213@minmei.iqm.unicamp.br> <14562.4832.203053.753476@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14562.4832.203053.753476@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Mar 29, 2000 at 09:32:24AM -0500 X-OS: 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 29, 2000 at 09:32:24AM -0500, Andrew Gallatin wrote: > > Andre Severo writes: > > > > My apologies for such an obscure sentence =) > > > > What I meant by that was that I had to use the command "exerc" > > on the srm monitor prior to the boot procedure to sort of > > "warm up" the disks. > > > > Without this "warm up exercise" for a few seconds the disks are detected but > > their size is not assessed (this failure is what I meant by > > "taken to be offline"). > > > Hmm.. Older DEC disks tend to not spin up when they're powered on. > I'd assumed that the FreeBSD CAM system would take care of spinning up > such disks. Can a SCSI guru out there confirm this? Bear in mind Yes it does. But a SHOW DEVICES on SRM also does it if I remember correctly. I had no troubles when I tested one of the 4.0-RC on our 1000A. I no longer have a 1000 available. This was using DEC RZxx disks. -- 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 Fri Mar 31 7:54:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mailgate.vver.kiae.ru (mailgate.vver.kiae.ru [144.206.175.2]) by hub.freebsd.org (Postfix) with ESMTP id ADFCD37B909 for ; Fri, 31 Mar 2000 07:53:29 -0800 (PST) (envelope-from pavel@vver.kiae.ru) Received: from ns.vver.kiae.ru ([144.206.175.1] helo=vver.kiae.ru) by mailgate.vver.kiae.ru with esmtp (Exim 1.90 #1) for scsi@freebsd.org id 12b3pZ-0000uy-00; Fri, 31 Mar 2000 19:59:30 +0400 Message-ID: <38E4CB16.1B46EE13@vver.kiae.ru> Date: Fri, 31 Mar 2000 19:58:15 +0400 From: "Pavel A. Novikov" Organization: RRC "Kurchatov Institute" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: HP's SureStore 2600fx Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have problems with connection of Hewlett-Packard Sure Store Optical 2600fx removable scsi device to the system. It refuses to be probed in direct access mode as sd device (Illegal request). In optical memory mode it is correctly probed by the kernel as od0 device and I also can write a disk label on it (seems so). But cannot create the filesystem (Invalid argument). Strange also that sysinstall cannot probe it correctly (od0: oops not queued) and exits. The system is FreeBSD 2.2.6. Possibly upgrade is needed? Or it has problems with 1024 bytes/sector? Pavel Novikov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 31 8:55:15 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 91E5237B9CA for ; Fri, 31 Mar 2000 08:55:12 -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 LAA09958; Fri, 31 Mar 2000 11:55:05 -0500 (EST) Date: Fri, 31 Mar 2000 11:55:05 -0500 (EST) From: "Matthew N. Dodd" To: "Pavel A. Novikov" Cc: scsi@FreeBSD.ORG Subject: Re: HP's SureStore 2600fx In-Reply-To: <38E4CB16.1B46EE13@vver.kiae.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 31 Mar 2000, Pavel A. Novikov wrote: > I have problems with connection of Hewlett-Packard Sure Store Optical > 2600fx removable scsi device to the system. It refuses to be probed in > direct access mode as sd device (Illegal request). In optical memory > mode it is correctly probed by the kernel as od0 device and I also can > write a disk label on it (seems so). But cannot create the filesystem > (Invalid argument). Strange also that sysinstall cannot probe it > correctly (od0: oops not queued) and exits. The system is FreeBSD > 2.2.6. Possibly upgrade is needed? Or it has problems with 1024 > bytes/sector? You really want to upgrade to 4.0 at the very least. I've got a pile of Sony SMO-C501s, a model 10 and a model 40fx HP changer that work just fine. -- | 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