From owner-freebsd-scsi Sun Jan 21 8:24:35 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 46AE437B400 for ; Sun, 21 Jan 2001 08:24:15 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14KNGI-000Ntv-00; Sun, 21 Jan 2001 19:22:39 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14KNI3-00033U-00; Sun, 21 Jan 2001 19:24:27 +0300 Date: Sun, 21 Jan 2001 19:24:27 +0300 From: Odhiambo Washington To: Matthew Jacob Cc: freebsd-scsi@freebsd.org Subject: Re: CANNOT ACCESS T20 TAPE Message-ID: <20010121192427.K589@poeza.iconnect.co.ke> References: <20010119210817.B14078@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from "Matthew Jacob" on Sat, Jan 20, 2001 at 03:25:47PM -0800 X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Matthew Jacob [20010121 02:26]: writing on the subject 'Re: CANNOT ACCESS T20 TAPE' Matthew> Matthew> I have a T20 with 3.00 f/w which works just peacy in -current. Matthew> Matthew> I know you said things worked fine under 3.4 and now don't work when you Matthew> upgraded to 4.2- but I have to say that this seems very unlikely somehow. It Matthew> seems like your tape drive has died. Please retry 3.4 and see what's up with Matthew> that and let me know. Is it easy for a tape drive to die? I still hope it is some other issue because I did a full backup 2 days before the upgrade and we've not had any power failures or something that I can suspect. Okay the only problem here now is that it is a SCSI tape and I do not have another readily available system with a SCSI adapter to attach it to for a test. Well, whatever it is lemme think hard about it. I'll take one of the last options I always resort to when i have something like this. You know the Powell doctrine? (Yes, that Powell - General Colin Powell) - "Think hard before you act, act decisively when you do, and finish quickly" . Okay the last part might be a bit out of range but the first 2 definately are called for at this moment. I also hope that someone somewhere could have an idea or so. Or do you suppose I can try -CURRENT?? ;-) ..hmmm.. I am not at par with those running -CURRENT and this is a server that is relied upon by hundreds of clients - so I am just tied for now. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Once you start to romanticize something, it's usually over. -Prof. John von der Heide To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 21 11:20:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9708637B401 for ; Sun, 21 Jan 2001 11:20:28 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA03102; Sun, 21 Jan 2001 11:20:16 -0800 Date: Sun, 21 Jan 2001 11:20:17 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Odhiambo Washington Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CANNOT ACCESS T20 TAPE In-Reply-To: <20010121192427.K589@poeza.iconnect.co.ke> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 21 Jan 2001, Odhiambo Washington wrote: > * Matthew Jacob [20010121 02:26]: writing on the subject 'Re: CANNOT ACCESS T20 TAPE' > Matthew> > Matthew> I have a T20 with 3.00 f/w which works just peacy in -current. > Matthew> > Matthew> I know you said things worked fine under 3.4 and now don't work when you > Matthew> upgraded to 4.2- but I have to say that this seems very unlikely somehow. It > Matthew> seems like your tape drive has died. Please retry 3.4 and see what's up with > Matthew> that and let me know. > > Is it easy for a tape drive to die? I still hope it is some other issue > because I did a full backup 2 days before the upgrade and we've not had > any power failures or something that I can suspect. Okay the only problem > here now is that it is a SCSI tape and I do not have another readily > available system with a SCSI adapter to attach it to for a test. It wouldn't be the adapter. > Well, whatever it is lemme think hard about it. I'll take one of the last > options I always resort to when i have something like this. You know the > Powell doctrine? (Yes, that Powell - General Colin Powell) - "Think hard > before you act, act decisively when you do, and finish quickly" . Okay the > last part might be a bit out of range but the first 2 definately are > called for at this moment. Okay. > > I also hope that someone somewhere could have an idea or so. Or do you > suppose I can try -CURRENT?? ;-) ..hmmm.. I am not at par with those > running -CURRENT and this is a server that is relied upon by hundreds of > clients - so I am just tied for now. > I wish I had something better to tell you. One things you *might* try is this change: Change, in scsi_sa.c:samount: /* * *Very* first off, make sure we're loaded to BOT. */ scsi_load_unload(&ccb->csio, 2, sadone, MSG_SIMPLE_Q_TAG, FALSE, FALSE, FALSE, 1, SSD_FULL_SIZE, REWIND_TIMEOUT); error = cam_periph_runccb(ccb, saerror, 0, SF_NO_PRINT, &softc->device_stats); QFRLS(ccb); /* * In case this doesn't work, do a REWIND instead */ if (error) { scsi_rewind(&ccb->csio, 2, sadone, MSG_SIMPLE_Q_TAG, FALSE, SSD_FULL_SIZE, REWIND_TIMEOUT); error = cam_periph_runccb(ccb, saerror, 0, SF_NO_PRINT, &softc->device_stats); QFRLS(ccb); } if (error) { xpt_release_ccb(ccb); goto exit; } to /* * *Very* first off, make sure we're loaded to BOT. */ scsi_rewind(&ccb->csio, 2, sadone, MSG_SIMPLE_Q_TAG, FALSE, SSD_FULL_SIZE, REWIND_TIMEOUT); error = cam_periph_runccb(ccb, saerror, 0, SF_NO_PRINT, &softc->device_stats); QFRLS(ccb); if (error) { xpt_release_ccb(ccb); goto exit; } It's *just* possible that this tape drive is stupid as to not only fail the LOAD/UNLOAD but then get sent into the weeds and fail to do the rewind. The reason the LOAD/UNLOAD is used first is to catch the case of tape inserted but not spun up and loaded to BOT (rewind would fail on those drives). But this is something of an edge case. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jan 21 21:32:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from balzac.cybercable.fr (balzac.cybercable.fr [212.198.0.198]) by hub.freebsd.org (Postfix) with SMTP id 859AF37B400 for ; Sun, 21 Jan 2001 21:31:53 -0800 (PST) Received: (qmail 2112472 invoked from network); 22 Jan 2001 05:31:51 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by balzac.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 22 Jan 2001 05:31:51 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id f0M5Vnw87400; Mon, 22 Jan 2001 06:31:49 +0100 (CET) (envelope-from clefevre@citeweb.net) To: "Kenneth D. Merry" Cc: Cyrille Lefevre , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI suspend/resume References: <20010112211218.A32720@panzer.kdm.org> <20010117104437.B17373@panzer.kdm.org> <20010117223602.A22556@panzer.kdm.org> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C In-Reply-To: "Kenneth D. Merry"'s message of "Wed, 17 Jan 2001 22:36:02 -0700" From: Cyrille Lefevre Reply-To: clefevre@noos.fr Mail-Copies-To: never Date: 22 Jan 2001 06:31:46 +0100 Message-ID: Lines: 70 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > On Wed, Jan 17, 2001 at 23:54:17 +0100, Cyrille Lefevre wrote: > > "Kenneth D. Merry" writes: [snip] > > don't understand why this works for you and not for me ? > > I'll ask some friends about that... until now, I was always thinking > > this was a "normal" comportment. > > Nope, that's not normal. The drive should spin up automatically. I'm not > sure why yours doesn't. > [snip] > > why this makes more difficult to debug problems ? > > have you some preferences about kernel settings ? > > Well, the sense strings provide a text description of the numeric error > codes (ASC and ASCQ). That saves me from having to look up the error code > in the table if I don't have it memorized. I saw that after I send you my previous message. in fact, I misunderstood the meaning of those variables. > > do you want a copy of my kernel config file ? any other things ? > > Nah, that's okay. The only thing I'm curious about is what sort of drive > this is. Can you send dmesg output for your SCSI disk? single-ended 2GB HP drives :) ... sym0: <875> port 0xfc00-0xfcff mem 0xffbea000-0xffbeafff,0xffbebc00-0xffbebcff irq 9 at device 14.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking ... Waiting 5 seconds for SCSI devices to settle (probe2:sym0:0:2:0): phase change 6-7 6@07e4398c resid=4. sa0 at sym0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled da0: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) da2 at sym0 bus 0 target 5 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled da2: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) da3 at sym0 bus 0 target 6 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled da3: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) da1 at sym0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) Mounting root from ufs:/dev/da0s1a cd1 at sym0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: cd present [282540 x 2048 byte records] cd0 at sym0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present I know, my PLEXTOR CDROM seems to be dead :( Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 22 5:54:31 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from synology.com (dns1.synology.com [202.173.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 56E1837B400 for ; Mon, 22 Jan 2001 05:54:11 -0800 (PST) Received: from synology.com (IDENT:nobody@localhost [127.0.0.1]) by synology.com (8.9.3/8.9.3) with SMTP id VAA12927; Mon, 22 Jan 2001 21:54:42 +0800 Date: Mon, 22 Jan 2001 21:54:42 +0800 Message-Id: <200101221354.VAA12927@synology.com> To: iain@research.canon.com.au;, gibbs@scsiguy.com;, cheen@synology.com;; Subject: RE: More target mode observations From: X-Mailer: TWIG Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Following up to myself with a bit more info, > >I played around a little bit more, and discovered that yes, we do have >some atio's waiting, and if we get a bus reset one of these gets sent >back. > >I also discovered that ahc_intr() never gets called during the rescan of >the bus whilst in target mode. To me at least this would suggest that >the controller is never being selected, or failing that the controller >is never telling the device driver that it has been selected. > >Unfortunately we do not have any hardware here for examining SCSI >busses, otherwise I could find out whether the controller was responding >to the select with BSY (well, we have the logic analyser, but nothing to >plug it in with). > >The other thing is that I only get bus reset intermittantly, which >worries me. By this I mean that I can do a camcontrol reset on one >machine, and the other machine doesn't always pick it up (I don't get >he "Somebody reset bus %d" message). > Hi: I am experiencing exactly what you described in your mail. And I am also looking for the answers. I have two AHA-2940U2W card on two different machine respectively. I named them brain-test and idb-test respectively. They are connected by an external scsi cable. The chip on the scsi card is aic-7890 (it should work well according to Justin.) And the FreeBSD version is 4.1-20000812-STABLE. Unfortunately, when I triggered the target mode operation on the idb-test machine and rescanned the bus from the brain-test machine, it found nothing. On the one way, the brain-test did select the target mode controller, but it got no response and returned with time out message. On the other way, the target controller didn't capture any select request. It looks like that chip on idb-test is not properly triggered. I mean it doesn't know it should act as a target mode controller. But the interesting thins is it can catch the channel reset signal. I had also tested the aic-7899, and put in on the idb-test machine. But it still didn't work. I'm including a copy of the /var/log/messages with diagnostic output. I wish it helps for verifying the situations. If anyone has any ideas or suggestions, I would like to hear from you Derren L. derrenl@synology.com Here is the /var/log/messages output: # # the log on brain-test machine # brain-test /kernel: ahc1: port 0x1c00-0x1cff mem 0xfb400000-0xfb400fff irq 10 at device 14.0 on pci1 brain-test /kernel: ahc1: Reading SEEPROM...done. brain-test /kernel: ahc1: BIOS eeprom is present brain-test /kernel: ahc1: Secondary High byte termination Enabled brain-test /kernel: ahc1: Secondary Low byte termination Enabled brain-test /kernel: ahc1: Primary Low Byte termination Enabled brain-test /kernel: ahc1: Primary High Byte termination Enabled brain-test /kernel: ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs brain-test /kernel: ahc1: hardware scb 64 bytes; kernel scb 32 bytes; ahc_dma 8 bytes brain-test /kernel: ahc1: Downloading Sequencer Program... 403 instructions downloaded # Enable the debug information brain-test /kernel: (xpt0:xpt0:0:-1:-1): debugging flags now 7 # Reset the bus. And the idb-test did get the reset request. brain-test /kernel: (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. # Rescan the target mode controller # It got a select time out status brain-test /kernel: (probe0:ahc1:0:9:0): probestart brain-test /kernel: (probe0:ahc1:0:9:0): xpt_action brain-test /kernel: (probe0:ahc1:0:9:0): ahc_action brain-test /kernel: (probe0:ahc1:0:9:0): start scb(0xc0a41000) brain-test /kernel: ahc_handle_scsiint: SELTO brain-test /kernel: (probe0:ahc1:0:9:0): ahc_done - scb 0 brain-test /kernel: (probe0:ahc1:0:9:0): xpt_done brain-test /kernel: (probe0:ahc1:0:9:0): camisr(probe0:ahc1:0:9:0): probedone # # the log on idb-test machine # idb-test /kernel: ahc1: port 0x1c00-0x1cff mem 0xfb400000-0xfb idb-test /kernel: ahc1: Reading SEEPROM...done. idb-test /kernel: ahc1: BIOS eeprom is present idb-test /kernel: ahc1: Secondary High byte termination Enabled idb-test /kernel: ahc1: Secondary Low byte termination Enabled idb-test /kernel: ahc1: Primary Low Byte termination Enabled idb-test /kernel: ahc1: Primary High Byte termination Enabled idb-test /kernel: ahc1: aic7890/91 Wide Channel A, SCSI Id=9, 16/255 SCBs idb-test /kernel: ahc1: hardware scb 64 bytes; kernel scb 32 bytes; ahc_dma 8 bytes idb-test /kernel: ahc1: Downloading Sequencer Program... 392 instructions downloaded # Enable the debug information idb-test /kernel: (xpt0:xpt0:0:-1:-1): debugging flags now 7 # The target mode was enabled here idb-test /kernel: (targ0:ahc1:0:9:0): Lun now enabled for target mode # idb-test can capture the channel reset signal idb-test /kernel: ahc1: Someone reset channel A idb-test /kernel: (targ0:ahc1:0:9:0): camisrSaw event 4e:0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 22 7:47:30 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id CECD637B699 for ; Mon, 22 Jan 2001 07:47:13 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id D6D4B177EA3 for ; Mon, 22 Jan 2001 09:47:13 -0600 (CST) Message-ID: <004001c0848a$974f8c20$931576d8@inethouston.net> From: "David W. Chapman Jr." To: Subject: VXA Tape drives Date: Mon, 22 Jan 2001 09:47:14 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is nothing important, just wanted to let the users of VXA tape drives know that if they wanted to update their firmware, I just fould out that Ecrix can send your a "firmware tape" that you just stick in the tape drive and it updates the firmware if you are having troubles using the vxatool for dos like I was. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 22 15:24:22 2001 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 8D7ED37B6B8 for ; Mon, 22 Jan 2001 15:24:02 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA82664; Mon, 22 Jan 2001 16:23:54 -0700 (MST) (envelope-from ken) Date: Mon, 22 Jan 2001 16:23:54 -0700 From: "Kenneth D. Merry" To: clefevre@noos.fr Cc: Cyrille Lefevre , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI suspend/resume Message-ID: <20010122162354.B82472@panzer.kdm.org> References: <20010112211218.A32720@panzer.kdm.org> <20010117104437.B17373@panzer.kdm.org> <20010117223602.A22556@panzer.kdm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from clefevre@citeweb.net on Mon, Jan 22, 2001 at 06:31:46AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 22, 2001 at 06:31:46 +0100, Cyrille Lefevre wrote: > "Kenneth D. Merry" writes: > > On Wed, Jan 17, 2001 at 23:54:17 +0100, Cyrille Lefevre wrote: > > > do you want a copy of my kernel config file ? any other things ? > > > > Nah, that's okay. The only thing I'm curious about is what sort of drive > > this is. Can you send dmesg output for your SCSI disk? > > single-ended 2GB HP drives :) > > ... > sym0: <875> port 0xfc00-0xfcff mem 0xffbea000-0xffbeafff,0xffbebc00-0xffbebcff irq 9 at device 14.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking > ... > Waiting 5 seconds for SCSI devices to settle > (probe2:sym0:0:2:0): phase change 6-7 6@07e4398c resid=4. > sa0 at sym0 bus 0 target 3 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 8) > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled > da0: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) > da2 at sym0 bus 0 target 5 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled > da2: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) > da3 at sym0 bus 0 target 6 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 10.000MB/s transfers (10.000MHz, offset 16), Tagged Queueing Enabled > da3: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) > da1 at sym0 bus 0 target 4 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da1: 2048MB (4194685 512 byte sectors: 255H 63S/T 261C) These drives look normal enough, I don't know of any problems offhand with them. So I don't really know why your drives aren't spinning up. Here are some things to try: - boot with -v (boot -v) and see if you get any additional diagnostic information when you spin down a drive and then try to do I/O. - try the attached patch, and see if you get any diagnostic printouts. Also, make sure you compile your kernel without excluding the sense and CDB strings, so the error messages make more sense. > Mounting root from ufs:/dev/da0s1a > cd1 at sym0 bus 0 target 2 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 3.300MB/s transfers > cd1: cd present [282540 x 2048 byte records] > cd0 at sym0 bus 0 target 1 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > I know, my PLEXTOR CDROM seems to be dead :( That's normal. It's just telling you there is no CD in the drive. Ken -- Kenneth Merry ken@kdm.org --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="cam_periph.c.start_diag.20010122" ==== //depot/FreeBSD-ken/src/sys/cam/cam_periph.c#9 - /c/ken/perforce/FreeBSD-ken/src/sys/cam/cam_periph.c ==== *** /tmp/tmp.82637.0 Mon Jan 22 16:21:35 2001 --- /c/ken/perforce/FreeBSD-ken/src/sys/cam/cam_periph.c Mon Jan 22 16:21:20 2001 *************** *** 1292,1297 **** --- 1292,1300 ---- else le = FALSE; + xpt_print_path(periph->path); + printf("attempting START UNIT\n"); + /* * Attempt to start the drive up. * --6c2NcOVqGQ03X4Wi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 22 19:48:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from demai05.mw.mediaone.net (demai05.mw.mediaone.net [24.131.1.56]) by hub.freebsd.org (Postfix) with ESMTP id 5113F37B400 for ; Mon, 22 Jan 2001 19:48:02 -0800 (PST) Received: from ian.batcave.com (nic-131-c233-239.mw.mediaone.net [24.131.233.239]) by demai05.mw.mediaone.net (8.8.7/8.8.7) with SMTP id WAA07846 for ; Mon, 22 Jan 2001 22:48:01 -0500 (EST) From: Ian Cartwright Reply-To: icartwright@mediaone.net To: freebsd-scsi@freebsd.org Subject: SCSI Speed Question Date: Mon, 22 Jan 2001 22:48:01 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01012222480104.00373@ian.batcave.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a question about the speed of my SCSI devices, especially under FreeBSD. I currently have an Adaptec 2940U/w Fast/Wide controller with two Compaq Fast/Wide hard disks, and Toshiba SCSI II cdrom and an HP SCSI II DAT Drive. My question is, is this the optimum configuration to support the highest transfer rate for my hard disks? Does the SCSI bus run at the speed of the slowest device on the bus or can I run it in asynchronous mode? If I can run in async mode, how do I tell FreeBSD to do it? I guess that's more than one question... ;-) In case it helps, here's the info camcontrol gave me: >camcontrol inquiry 0:0 pass0: Fixed Direct Access SCSI-2 device pass0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >camcontrol inquiry 0:1 pass1: Fixed Direct Access SCSI-2 device pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled >camcontrol inquiry 0:2 pass2: Removable CD-ROM SCSI-2 device pass2: 10.000MB/s transfers (10.000MHz, offset 8) >camcontrol inquiry 0:6 pass3: Removable Sequential Access SCSI-2 device pass3: 10.000MB/s transfers (10.000MHz, offset 15) Cheers Ian Cartwright BTW: I am not subscribed to the FreeBSD SCSI mailing list so please send responses directly to me... Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 22 20:10:58 2001 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 C8CF637B400 for ; Mon, 22 Jan 2001 20:10:40 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA84927; Mon, 22 Jan 2001 21:10:37 -0700 (MST) (envelope-from ken) Date: Mon, 22 Jan 2001 21:10:37 -0700 From: "Kenneth D. Merry" To: Ian Cartwright Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Speed Question Message-ID: <20010122211037.A84856@panzer.kdm.org> References: <01012222480104.00373@ian.batcave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <01012222480104.00373@ian.batcave.com>; from icartwright@mediaone.net on Mon, Jan 22, 2001 at 10:48:01PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 22, 2001 at 22:48:01 -0500, Ian Cartwright wrote: > I have a question about the speed of my SCSI devices, especially under > FreeBSD. I currently have an Adaptec 2940U/w Fast/Wide controller with two > Compaq Fast/Wide hard disks, and Toshiba SCSI II cdrom and an HP SCSI II DAT > Drive. My question is, is this the optimum configuration to support the > highest transfer rate for my hard disks? Does the SCSI bus run at the speed > of the slowest device on the bus or can I run it in asynchronous mode? If I > can run in async mode, how do I tell FreeBSD to do it? Yes, you are running at the fastest speeds possible for your hardware. In your case, no, the SCSI bus doesn't run at the speed of the slowest device on the bus. (*) If you run in async mode, that will slow things down significantly. I think you can make your devices negotiate async like this: camcontrol negotiate da0 -v -R 0 -a (*) With LVD busses (i.e. this doesn't apply in your case), the entire LVD bus segment will be restricted to single-ended speeds (20MHz maximum) if there is one device on that bus segment that can't do LVD. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 12:40: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.osd.bsdi.com (unknown [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 93E8237B404 for ; Tue, 23 Jan 2001 12:39:48 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0NKdix58438 for ; Tue, 23 Jan 2001 12:39:44 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f0NKdJd27822 for scsi@FreeBSD.org; Tue, 23 Jan 2001 12:39:19 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 23 Jan 2001 12:39:19 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: scsi@FreeBSD.org Subject: Warning fixes in cam Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey gang, I've been fixing various warnings in the kernel and have a simple patch for cam at http://www.FreeBSD.org/~jhb/public_html/patches/cam.patch. It makes cam_sim.sim_name a const char * instead of a char * and wraps a debugging variable in in a function in an appropriate #ifdef. Is it ok for me to commit? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jan 23 13:51:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B54837B69C; Tue, 23 Jan 2001 13:51:17 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA12766; Tue, 23 Jan 2001 13:51:17 -0800 Date: Tue, 23 Jan 2001 13:51:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam 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 Hou about a URL that works? > Hey gang, > > I've been fixing various warnings in the kernel and have a simple patch > for cam at http://www.FreeBSD.org/~jhb/public_html/patches/cam.patch. > It makes cam_sim.sim_name a const char * instead of a char * and wraps > a debugging variable in in a function in an appropriate #ifdef. Is it > ok for me to commit? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 13:56:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.osd.bsdi.com (unknown [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A8D0137B6A3 for ; Tue, 23 Jan 2001 13:56:05 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0NLu0x63979; Tue, 23 Jan 2001 13:56:00 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f0NLta628790; Tue, 23 Jan 2001 13:55:36 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 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: Tue, 23 Jan 2001 13:55:35 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: Re: Warning fixes in cam Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Jan-01 Matthew Jacob wrote: > > Hou about a URL that works? That would be the one without the 'public_html/' part. :-P http://www.FreeBSD.org/~jhb/patches/cam.patch. >> Hey gang, >> >> I've been fixing various warnings in the kernel and have a simple >> patch >> for cam at >> http://www.FreeBSD.org/~jhb/public_html/patches/cam.patch. >> It makes cam_sim.sim_name a const char * instead of a char * and >> wraps >> a debugging variable in in a function in an appropriate #ifdef. Is >> it >> ok for me to commit? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jan 23 14:23:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1188C37B400; Tue, 23 Jan 2001 14:23:09 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA13000; Tue, 23 Jan 2001 14:23:08 -0800 Date: Tue, 23 Jan 2001 14:23:07 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam 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 That doesn't work either. > > On 23-Jan-01 Matthew Jacob wrote: > > > > Hou about a URL that works? > > That would be the one without the 'public_html/' part. :-P > > http://www.FreeBSD.org/~jhb/patches/cam.patch. > > >> Hey gang, > >> > >> I've been fixing various warnings in the kernel and have a simple > >> patch > >> for cam at > >> http://www.FreeBSD.org/~jhb/public_html/patches/cam.patch. > >> It makes cam_sim.sim_name a const char * instead of a char * and > >> wraps > >> a debugging variable in in a function in an appropriate #ifdef. Is > >> it > >> ok for me to commit? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 14:28:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 9FFA937B400; Tue, 23 Jan 2001 14:28:10 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 6F16B177EA3; Tue, 23 Jan 2001 16:28:14 -0600 (CST) Message-ID: <01cb01c0858b$c4160660$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , "John Baldwin" Cc: References: Subject: Re: Warning fixes in cam Date: Tue, 23 Jan 2001 16:28:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org it seems to work for me..... ----- Original Message ----- From: "Matthew Jacob" To: "John Baldwin" Cc: Sent: Tuesday, January 23, 2001 4:23 PM Subject: Re: Warning fixes in cam > > That doesn't work either. > > > > > > On 23-Jan-01 Matthew Jacob wrote: > > > > > > Hou about a URL that works? > > > > That would be the one without the 'public_html/' part. :-P > > > > http://www.FreeBSD.org/~jhb/patches/cam.patch. > > > > >> Hey gang, > > >> > > >> I've been fixing various warnings in the kernel and have a simple > > >> patch > > >> for cam at > > >> http://www.FreeBSD.org/~jhb/public_html/patches/cam.patch. > > >> It makes cam_sim.sim_name a const char * instead of a char * and > > >> wraps > > >> a debugging variable in in a function in an appropriate #ifdef. Is > > >> it > > >> ok for me to commit? > > > > > > > > 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 Jan 23 14:32:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.osd.bsdi.com (unknown [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 6919A37B401 for ; Tue, 23 Jan 2001 14:32:34 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0NMWTx65531; Tue, 23 Jan 2001 14:32:29 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f0NMW5E29273; Tue, 23 Jan 2001 14:32:05 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 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: Tue, 23 Jan 2001 14:32:05 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: Re: Warning fixes in cam Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Jan-01 Matthew Jacob wrote: > > That doesn't work either. > > >> >> On 23-Jan-01 Matthew Jacob wrote: >> > >> > Hou about a URL that works? >> >> That would be the one without the 'public_html/' part. :-P >> >> http://www.FreeBSD.org/~jhb/patches/cam.patch. You're probably picking up the period at the end. Silly punctuation rules. :) http://www.FreeBSD.org/~jhb/patches/cam.patch -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jan 23 14:35:25 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2E58037B401; Tue, 23 Jan 2001 14:35:07 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA13068; Tue, 23 Jan 2001 14:35:07 -0800 Date: Tue, 23 Jan 2001 14:35:06 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam 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 Oops, yes. > > On 23-Jan-01 Matthew Jacob wrote: > > > > That doesn't work either. > > > > > >> > >> On 23-Jan-01 Matthew Jacob wrote: > >> > > >> > Hou about a URL that works? > >> > >> That would be the one without the 'public_html/' part. :-P > >> > >> http://www.FreeBSD.org/~jhb/patches/cam.patch. > > You're probably picking up the period at the end. Silly punctuation > rules. :) > > http://www.FreeBSD.org/~jhb/patches/cam.patch > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 14:36:34 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3B0B537B400; Tue, 23 Jan 2001 14:36:17 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA13076; Tue, 23 Jan 2001 14:36:17 -0800 Date: Tue, 23 Jan 2001 14:36:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam 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 They look okay to me, but why again exactly are you doing them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 14:40:22 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.osd.bsdi.com (unknown [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id C6D4137B404 for ; Tue, 23 Jan 2001 14:40:04 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0NMdxx65809; Tue, 23 Jan 2001 14:39:59 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f0NMdZH29376; Tue, 23 Jan 2001 14:39:35 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 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: Tue, 23 Jan 2001 14:39:35 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Matthew Jacob Subject: Re: Warning fixes in cam Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 23-Jan-01 Matthew Jacob wrote: > > They look okay to me, but why again exactly are you doing them? make scsi_low.o cc -c -O -pipe -mcpu=i686 -march=i686 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../cam/scsi/scsi_low.c ../../cam/scsi/scsi_low.c: In function `scsi_low_attach': ../../cam/scsi/scsi_low.c:545: warning: passing arg 3 of `cam_sim_alloc' discards qualifiers from pointer target type ../../cam/scsi/scsi_low.c: In function `scsi_low_synch': ../../cam/scsi/scsi_low.c:2086: warning: unused variable `speed' Just warning police. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jan 23 14:42:20 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B03237B698; Tue, 23 Jan 2001 14:42:02 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA13127; Tue, 23 Jan 2001 14:42:02 -0800 Date: Tue, 23 Jan 2001 14:42:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam 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 Well, Justin or Ken will know better than I... > > On 23-Jan-01 Matthew Jacob wrote: > > > > They look okay to me, but why again exactly are you doing them? > > make scsi_low.o > cc -c -O -pipe -mcpu=i686 -march=i686 -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi > -nostdinc -I- -I. -I../.. -I../../dev -I../../../include > -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include > opt_global.h -elf -mpreferred-stack-boundary=2 > ../../cam/scsi/scsi_low.c > ../../cam/scsi/scsi_low.c: In function `scsi_low_attach': > ../../cam/scsi/scsi_low.c:545: warning: passing arg 3 of > `cam_sim_alloc' discards qualifiers from pointer target type > ../../cam/scsi/scsi_low.c: In function `scsi_low_synch': > ../../cam/scsi/scsi_low.c:2086: warning: unused variable `speed' > > Just warning police. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 14:46:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 8A6A837B6A1; Tue, 23 Jan 2001 14:45:56 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0NMjbs91521; Tue, 23 Jan 2001 15:45:38 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101232245.f0NMjbs91521@aslan.scsiguy.com> To: mjacob@feral.com Cc: John Baldwin , scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam In-Reply-To: Your message of "Tue, 23 Jan 2001 14:42:01 PST." Date: Tue, 23 Jan 2001 15:45:37 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Well, Justin or Ken will know better than I... > I have yet to review the "SCSI low" code. Any changes that affect those files should probably pass through their respective authors. The changes to make sim_name const are fine with me. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 17:40:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id 1C0F537B6BD; Tue, 23 Jan 2001 17:40:08 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id KAA28316; Wed, 24 Jan 2001 10:39:35 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id KAA17301; Wed, 24 Jan 2001 10:39:35 +0900 (JST) To: gibbs@scsiguy.com Cc: mjacob@feral.com, jhb@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Warning fixes in cam In-Reply-To: <200101232245.f0NMjbs91521@aslan.scsiguy.com> References: <200101232245.f0NMjbs91521@aslan.scsiguy.com> X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010124103934B.non@ever.sanda.gr.jp> Date: Wed, 24 Jan 2001 10:39:34 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 8 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: "Justin T. Gibbs" Date: Tue, 23 Jan 2001 15:45:37 -0700 > I have yet to review the "SCSI low" code. Any changes that affect > those files should probably pass through their respective authors. This change for scsi_low.c seems OK. Please commit it. // Noriaki Mitsunaga // non@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 23 20: 1: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 4E92837B69B for ; Tue, 23 Jan 2001 20:00:48 -0800 (PST) Received: (qmail 30605312 invoked from network); 24 Jan 2001 04:00:46 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 24 Jan 2001 04:00:46 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id f0O40iT09954; Wed, 24 Jan 2001 05:00:44 +0100 (CET) (envelope-from root) From: Cyrille Lefevre Message-Id: <200101240400.f0O40iT09954@gits.dyndns.org> Subject: Re: SCSI suspend/resume In-Reply-To: <20010122162354.B82472@panzer.kdm.org> "from Kenneth D. Merry at Jan 22, 2001 04:23:54 pm" To: "Kenneth D. Merry" Date: Wed, 24 Jan 2001 05:00:43 +0100 (CET) Cc: clefevre@noos.fr, freebsd-scsi@FreeBSD.ORG Reply-To: clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C X-Mailer: ELM [version 2.4ME+ PL87 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > On Mon, Jan 22, 2001 at 06:31:46 +0100, Cyrille Lefevre wrote: > > "Kenneth D. Merry" writes: > > > On Wed, Jan 17, 2001 at 23:54:17 +0100, Cyrille Lefevre wrote: > > > > do you want a copy of my kernel config file ? any other things ? > > > > > > Nah, that's okay. The only thing I'm curious about is what sort of drive > > > this is. Can you send dmesg output for your SCSI disk? > > > > single-ended 2GB HP drives :) > [snip] > > These drives look normal enough, I don't know of any problems offhand with > them. So I don't really know why your drives aren't spinning up. > > Here are some things to try: > > - boot with -v (boot -v) and see if you get any additional diagnostic > information when you spin down a drive and then try to do I/O. there is something incredible, today. it seems to work! I don't understand anything. maybe a code change since december and now? I can't repeat the problem w/ the old kernel, I lost it. If it appears again, I'll tell you. also, I've tried a SCAM drive which is recognized by the BIOS but not by FreeBSD. the drive is a SUN UltraPack where I turn the dip-switch to one of the "holes" between 7 and 0! the problem is that I don't find any doc. on this box and I don't really know how to configure it to have full access to high SCSI targets. that's why I've tried the "hole" front to the 0. next time, I try the one front to the 7, who knows? maybe one is better than the other... > - try the attached patch, and see if you get any diagnostic printouts. yes, I did both : (da1:sym0:0:4:0): Attempting START UNIT da1s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK (da1:sym0:0:4:0): Attempting START UNIT resumed from suspended mode (slept 00:00:04) > Also, make sure you compile your kernel without excluding the sense and CDB > strings, so the error messages make more sense. already done since the last post :) > > I know, my PLEXTOR CDROM seems to be dead :( > > That's normal. It's just telling you there is no CD in the drive. even with a CD in the drive, it can't read CD anymore... the red light is flashing. and a mount /cdrom failed on device not ready. so, it's really dead :)) maybe one day I'll check the cables. diagnostic messages are as follow : (da1:sym0:0:4:0): Attempting START UNIT (cd0:sym0:0:1:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (cd0:sym0:0:1:0): NOT READY asc:57,0 Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 24 18:21:23 2001 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 358DE37B402 for ; Wed, 24 Jan 2001 18:21:05 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA04417; Wed, 24 Jan 2001 19:20:02 -0700 (MST) (envelope-from ken) Date: Wed, 24 Jan 2001 19:20:02 -0700 From: "Kenneth D. Merry" To: clefevre@citeweb.net Cc: clefevre@noos.fr, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI suspend/resume Message-ID: <20010124192001.A4335@panzer.kdm.org> References: <20010122162354.B82472@panzer.kdm.org> <200101240400.f0O40iT09954@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101240400.f0O40iT09954@gits.dyndns.org>; from root@gits.dyndns.org on Wed, Jan 24, 2001 at 05:00:43AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jan 24, 2001 at 05:00:43 +0100, Cyrille Lefevre wrote: > Kenneth D. Merry wrote: > > On Mon, Jan 22, 2001 at 06:31:46 +0100, Cyrille Lefevre wrote: > > > "Kenneth D. Merry" writes: > > > > On Wed, Jan 17, 2001 at 23:54:17 +0100, Cyrille Lefevre wrote: > > > > > do you want a copy of my kernel config file ? any other things ? > > > > > > > > Nah, that's okay. The only thing I'm curious about is what sort of drive > > > > this is. Can you send dmesg output for your SCSI disk? > > > > > > single-ended 2GB HP drives :) > > > [snip] > > > > These drives look normal enough, I don't know of any problems offhand with > > them. So I don't really know why your drives aren't spinning up. > > > > Here are some things to try: > > > > - boot with -v (boot -v) and see if you get any additional diagnostic > > information when you spin down a drive and then try to do I/O. > > there is something incredible, today. it seems to work! > I don't understand anything. maybe a code change since december > and now? I can't repeat the problem w/ the old kernel, I lost it. > If it appears again, I'll tell you. Wow, that's odd. Nothing significant has changed in CAM in the past month or two, so I don't know why it would start working again. > also, I've tried a SCAM drive which is recognized by the BIOS but > not by FreeBSD. the drive is a SUN UltraPack where I turn the > dip-switch to one of the "holes" between 7 and 0! the problem is > that I don't find any doc. on this box and I don't really know how > to configure it to have full access to high SCSI targets. that's > why I've tried the "hole" front to the 0. next time, I try the one > front to the 7, who knows? maybe one is better than the other... I'm not sure what'll happen if you use a drive in SCAM mode with FreeBSD... If you can figure out a way to configure it to have a normal, fixed SCSI ID, that would probably be better. > > - try the attached patch, and see if you get any diagnostic printouts. > > yes, I did both : > > (da1:sym0:0:4:0): Attempting START UNIT > da1s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK > (da1:sym0:0:4:0): Attempting START UNIT > resumed from suspended mode (slept 00:00:04) Okay, so the start unit certainly is being sent. But since things work correctly now, it would figure that they're being sent. :) > > > I know, my PLEXTOR CDROM seems to be dead :( > > > > That's normal. It's just telling you there is no CD in the drive. > > even with a CD in the drive, it can't read CD anymore... the red light > is flashing. and a mount /cdrom failed on device not ready. so, it's > really dead :)) maybe one day I'll check the cables. > > diagnostic messages are as follow : > > (da1:sym0:0:4:0): Attempting START UNIT > (cd0:sym0:0:1:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:sym0:0:1:0): NOT READY asc:57,0 You neglected to cut-n-paste the meaning of 0x57,0x00: "Unable to recover table-of-contents" I would suggest trying a couple more CDs before declaring it dead. Also, see if it can play an audio CD. 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 Jan 24 18:43:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 21A4237B6A1 for ; Wed, 24 Jan 2001 18:43:39 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0P2hAs05296; Wed, 24 Jan 2001 19:43:12 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101250243.f0P2hAs05296@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Derren L." Cc: "Iain Templeton" , "cheen" , freebsd-scsi@FreeBSD.ORG Subject: Re: More target mode observations In-Reply-To: Your message of "Sun, 21 Jan 2001 14:45:41 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jan 2001 19:43:10 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>Following up to myself with a bit more info, I've been tied up with things, but I'll try to look into this tomorrow. Target mode has worked, but I must have broken something recently. I'm sure it won't take me long to figure out what. >>The other thing is that I only get bus reset intermittantly, which >>worries me. By this I mean that I can do a camcontrol reset on one >>machine, and the other machine doesn't always pick it up (I don't get >>he "Somebody reset bus %d" message). This is actually a feature. The bus reset interrupt is disabled when a reset is first detected. It is only re-enabled once a reset will again effect state. That is, the interrupt will be re-enabled just before the first "select-out" as an initiator, and just after a "select-in" as a target. This prevents poorly implemented devices (usually initiators) from causing interrupt storms should they hold the reset line for long periods of time (several ms usually). If your system is doing real-time processing, having your interrupt handler called all the time to service no-op bus resets makes it difficult to meet your real-time constraints. 8-) -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 24 22:30:42 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from world.tonkinresolutions.com (233-123.adsl6.netlojix.net [207.71.233.123]) by hub.freebsd.org (Postfix) with ESMTP id 721F537B402; Wed, 24 Jan 2001 22:30:23 -0800 (PST) Received: from dingo.rlnt.net ([192.168.0.16]) by world.tonkinresolutions.com (8.9.3/8.9.3) with ESMTP id WAA03941; Wed, 24 Jan 2001 22:30:12 -0800 (PST) (envelope-from publicn@rlnt.net) Message-Id: <5.0.2.1.0.20010124222817.00a66ec0@rlnt.net> X-Sender: nick@rlnt.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 24 Jan 2001 22:30:50 -0800 To: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org From: Nick Tonkin Subject: FreeBSD will not boot (after installing!) on HP NetServer SCSI disk Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Can anyone verify Niekie's kind response to my enquiry as to FreeBSD not booting on an HP NetServer E 50? >I had a similar problem, till I replaced the 4.3Gb SCSI disk with a normal >seagate >disk. The drive geometry seems to be the problem. > >HP Drive: > >bytes/sector: 512 >sectors/track: 2 >tracks/cylinder: 91 >sectors/cylinder: 182 >cylinders: 45771 >sectors/unit: 8330502 > >Seagate Drive: >bytes/sector: 512 >sectors/track: 32 >tracks/cylinder: 64 >sectors/cylinder: 2048 >cylinders: 499 >sectors/unit: 1023968 > >I treid for days to get it working on the HP drive...no luck. The HP >works fine, >as long as you don't try to put your root/boot filesystems on it. > >Niekie Myburgh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 25 18: 5:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp1.mail.yahoo.com (smtp1.mail.yahoo.com [128.11.69.60]) by hub.freebsd.org (Postfix) with SMTP id 40D2637B404 for ; Thu, 25 Jan 2001 18:05:19 -0800 (PST) Received: from nat-220-161.nat.dot.ca.gov (HELO geocities.com) (149.136.220.161) by smtp.mail.vip.suc.yahoo.com with SMTP; 26 Jan 2001 02:05:18 -0000 X-Apparently-From: Message-ID: <3A70E26F.C88FC295@geocities.com> Date: Thu, 25 Jan 2001 18:35:27 -0800 From: greg simonoff Reply-To: gsimonoff@geocities.com X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.org Subject: scsi Zip disk Content-Type: multipart/mixed; boundary="------------68A403AD55FD7EA22724E1D4" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------68A403AD55FD7EA22724E1D4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Got a 100Meg IOMEGA SCSI Zip drive and I want to attach it to my FreeBSD system. My SCSI card has an external scsi III connector ( 68pin ) and the zip drive has what looks like a DB25 connector - are there adaptors available to connec the 25pin cable to the 68pin scsi card??? GREG --------------68A403AD55FD7EA22724E1D4 Content-Type: text/x-vcard; charset=us-ascii; name="gsimonoff.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for greg simonoff Content-Disposition: attachment; filename="gsimonoff.vcf" begin:vcard n:Simonoff;Gregory tel;work:(510) 286-4659 x-mozilla-html:FALSE org:Calif State Dept of Transportation;Software Development version:2.1 email;internet:gsimonoff@geocities.com title:PE / Electrical Engineer (CA license) adr;quoted-printable:;;111 Grand Avenue =0D=0A;Oakland ;CA;94623; note;quoted-printable:Java, HTML, C++, C=0D=0AUNIX, OS9=0D=0A fn:Gregory Simonoff end:vcard --------------68A403AD55FD7EA22724E1D4-- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 25 19: 3:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (SHW1-154.accesscable.net [24.71.144.154]) by hub.freebsd.org (Postfix) with ESMTP id 70E6137B401; Thu, 25 Jan 2001 19:03:04 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.2/8.11.1) with ESMTP id f0Q314K30200; Thu, 25 Jan 2001 23:01:04 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 25 Jan 2001 23:01:04 -0400 (AST) From: The Hermit Hacker To: Cc: Subject: Read error on booting system ... 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 Morning all ... I have a 4.x system running on an old ALR server ... EISA bus, etc ... the drives are brand new QUANTUM Atlas V's ... the controller is an Adaptec controller per 3 drives (6 drives total) ... This evening, I got a call from the office that, when booting the machine, it gives a 'Read error', so I went in and tried a few things I could think of ... Finished off with putting in a boot floppy, getting to the 'boot:' prompt and trying to boot from there, and nadda ... lsdev shows the hard drives, and file systems, with the kernel file system being disk1s1a: ... how should I try and boot from there? 'boot disk1s1a:/kernel'? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy 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 Thu Jan 25 19:28:35 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id EFAFF37B6A1 for ; Thu, 25 Jan 2001 19:28:18 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id C2899177E3F; Thu, 25 Jan 2001 21:28:24 -0600 (CST) Message-ID: <017901c08748$08359be0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , References: <3A70E26F.C88FC295@geocities.com> Subject: Re: scsi Zip disk Date: Thu, 25 Jan 2001 21:28:20 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I believe there is an adapter, but I'd wait for someone who knows a little more about scsi to answer that. ----- Original Message ----- From: "greg simonoff" To: Sent: Thursday, January 25, 2001 8:35 PM Subject: scsi Zip disk > Hi, > Got a 100Meg IOMEGA SCSI Zip drive > and I want to attach it to my FreeBSD system. > My SCSI card has an external scsi III > connector ( 68pin ) and the zip drive has > what looks like a DB25 connector - are > there adaptors available to connec the > 25pin cable to the 68pin scsi card??? > > > GREG > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 26 22:30:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from clifford.inch.com (clifford.inch.com [216.223.192.27]) by hub.freebsd.org (Postfix) with ESMTP id 4250337B401; Fri, 26 Jan 2001 22:30:09 -0800 (PST) Received: (from omar@localhost) by clifford.inch.com (8.9.3/8.8.5) id BAA22091; Sat, 27 Jan 2001 01:35:45 -0500 Message-ID: <20010127013545.A21945@clifford.inch.com> Date: Sat, 27 Jan 2001 01:35:45 -0500 From: Omar Thameen To: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org Subject: Mylex AcceleRAID 150 problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings: I have a Mylex AcceleRAID 150 running in a 4.2-RELEASE server and I've run into a couple problems and need some advice. First, the simple one. The 150 came with 4M of memory, and I'm trying to purchase a 16M SIMM from crucial.com (or wherever) to avoid the exorbitant Mylex prices for additional memory. As best as I could determine, the memory is EDO Parity RAM, 36 pin, 60 ns, SIMM. I bought exactly that from Crucial in 16M size (# CT4M36E2M6), but the server will not display or do anything when powered up, even rendering the power toggle functionless. Is there some spec that I'm missing? Second, about 3 out of 5 times, the system fails to boot. It gets to the "press enter to boot [kernel]..." phase, then shows me the slash ( / ), then hangs, again rendering the power toggle functionless, but not the reset switch. I've checked the motherboard and mobo BIOS, and swapped out the RAM, eliminating those as problems. Admittedly, I am running the Mylex Firmware/BIOS that came with the card: Firmware version 4.06-0-29 BIOS 4.10-41 Feb 2, 1999 but I am *highly* reluctant to try and upgrade, as a very competent colleague of mine had not one, but 2 of the same cards get hosed after trying the upgrade and speaking with Mylex tech support. The only other thing I can think that might be relevant to troubleshooting is that both motherboards that I've used have on-board SCSI (and a SCSI CDROM is plugged in and works). Any analysis and suggestions would be very much appreciated, Omar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 27 12:51:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (c228380-a.sfmissn1.sfba.home.com [24.20.90.44]) by hub.freebsd.org (Postfix) with ESMTP id 54A3137B69B; Sat, 27 Jan 2001 12:50:48 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0RKojx00993; Sat, 27 Jan 2001 12:50:45 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101272050.f0RKojx00993@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Omar Thameen Cc: freebsd-hardware@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Mylex AcceleRAID 150 problems In-reply-to: Your message of "Sat, 27 Jan 2001 01:35:45 EST." <20010127013545.A21945@clifford.inch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Jan 2001 12:50:45 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a Mylex AcceleRAID 150 running in a 4.2-RELEASE server and I've > run into a couple problems and need some advice. > > First, the simple one. The 150 came with 4M of memory, and I'm trying to > purchase a 16M SIMM from crucial.com (or wherever) to avoid the > exorbitant Mylex prices for additional memory. As best as I could > determine, the memory is EDO Parity RAM, 36 pin, 60 ns, SIMM. I bought > exactly that from Crucial in 16M size (# CT4M36E2M6), but the server > will not display or do anything when powered up, even rendering the > power toggle functionless. Is there some spec that I'm missing? Yes. The card requires 40-bit memory (byte-ECC), and Mylex' pricing is actually fairly reasonable. However, adding more memory won't do you a lot of good - the card has no battery backup, so you can't use it as write cache, and the OS already read-caches better than the card does. The 4M on the 150 and the 8M on the 250 are actually quite reasonable configurations for those adapters. (We've been running an 8M AcceleRAID 250 in freefall.freebsd.org for nearly a year now, for example.) > Second, about 3 out of 5 times, the system fails to boot. It gets to the > "press enter to boot [kernel]..." phase, then shows me the slash ( / ), > then hangs, again rendering the power toggle functionless, but not the > reset switch. I've checked the motherboard and mobo BIOS, and swapped > out the RAM, eliminating those as problems. This one's beyond me; if it's intermittent and you can't find *any* correspondence between any external factor and the failures, then I'd be getting pretty desperate. Does the card work OK once the system is up and running? > Admittedly, I am running > the Mylex Firmware/BIOS that came with the card: > Firmware version 4.06-0-29 > BIOS 4.10-41 Feb 2, 1999 > but I am *highly* reluctant to try and upgrade, as a very competent > colleague of mine had not one, but 2 of the same cards get hosed after > trying the upgrade and speaking with Mylex tech support. I've done a lot of upgrades on these cards, and never fried one. If you follow the instructions, it just works. Having said that, unless you're having issues with disk interaction, updating probably won't help you a lot. > The only > other thing I can think that might be relevant to troubleshooting is > that both motherboards that I've used have on-board SCSI (and a SCSI > CDROM is plugged in and works). This would only be an issue if the controller thinks that it's handling the onboard SCSI as well, and I doubt that (eg. if it's a Symbios part, and if it shows up in the RAID config tool then you might have problems). > Any analysis and suggestions would be very much appreciated, I'm afraid I don't have a lot here; check your SCSI cabling, check the card is properly seated and the memory on the card is installed. Check your jumpers, and that you have the activity LED plugged in properly (if it's connected at all). Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 27 15:58:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from shrubbery.satx.bikeworld.net (shrubbery.satx.bikeworld.net [209.142.99.220]) by hub.freebsd.org (Postfix) with ESMTP id 12EA937B401 for ; Sat, 27 Jan 2001 15:58:17 -0800 (PST) Received: from roscoe ([10.0.0.2] helo=roscoe.ah.bikeworld.net ident=mailserv) by shrubbery.satx.bikeworld.net with esmtp (Exim 3.16 #1) id 14MfEM-000Gvw-00 for freebsd-scsi@freebsd.org; Sat, 27 Jan 2001 17:58:06 -0600 Received: from roscoe.ah.bikeworld.net ([10.0.0.2] ident=root) by roscoe.ah.bikeworld.net with esmtp (Exim 3.16 #1) id 14MfEL-000OiT-00 for freebsd-scsi@freebsd.org; Sat, 27 Jan 2001 17:58:05 -0600 Date: Sat, 27 Jan 2001 17:58:05 -0600 (CST) From: Chris Snell X-Sender: chris@roscoe.ah.bikeworld.net To: freebsd-scsi@freebsd.org Subject: battery backup, cache on Adaptec 3200S 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 Howdy, Is there anything special that I need to do in order to enable write caching on our Adaptec 3200S controller? I do have the battery backup installed. I'm guessing that it is enabled by default but I just want to make sure. thanks, Chris -- "Responsibility is a heavy responsibility, man." - Cheech Marin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 27 17:56:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 4543D37B404 for ; Sat, 27 Jan 2001 17:55:56 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0S1tii00853; Sat, 27 Jan 2001 17:55:48 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101280155.f0S1tii00853@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Snell Cc: freebsd-scsi@freebsd.org Subject: Re: battery backup, cache on Adaptec 3200S In-reply-to: Your message of "Sat, 27 Jan 2001 17:58:05 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Jan 2001 17:55:44 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is there anything special that I need to do in order to enable write > caching on our Adaptec 3200S controller? I do have the battery backup > installed. I'm guessing that it is enabled by default but I just want to > make sure. You should be able to check this in the card's BIOS setup. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message