From owner-freebsd-scsi Sun Jan 25 00:06:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22588 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 00:06:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22566 for ; Sun, 25 Jan 1998 00:05:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA12845; Sun, 25 Jan 1998 19:04:13 +1100 Date: Sun, 25 Jan 1998 19:04:13 +1100 From: Bruce Evans Message-Id: <199801250804.TAA12845@godzilla.zeta.org.au> To: dburr@POBoxes.com, gibbs@narnia.plutotech.com Subject: Re: Minor annoyances with ZIP Plus Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>["normal" errors for zip disks] >This isn't the case. FreeBSD was being silly in asking for the optional, >rigid geometry page, which the IOMega guys chose not to implement. Since >FreeBSD stopped using physical geometry to "optimize" disk I/O (which >doesn't work on the ZBR drives of today), Actually, FreeBSD only stopped using the (possibly-non-physical) geometry in the disk label as a default for newfs. This changed about 3 years ago (before 2.0.5 was released). >asking for the rigid geometry >wasn't buying us anything and the code was recently changed to use the >information returned by the Read Capacity command instead. This hasn't actually changed (at least in the current sd driver). All that changed recently is that Read Capacity is now used to determine the sector size. Read Capacity has always been used to determine the disk size, and Mode Sense of the rigid geometry page has always been used to initialize default values for the geometry in the dummy label for the whole disk. If there is a valid DOS partition on the disk, as is normally(?) the case for new zip disks, then these default values are not used. In any case, the geometry in the dummy label for fdisk is only used by fdisk and sysinstall. Initialization of disk labels normally involves copying the geometry reported by fdisk to the labels, where it is normally not used because of the 3 year old hack to newfs. Summary: everything just works, but the lowest layer is too verbose and the highest layer (newfs) is too smart. Bruce From owner-freebsd-scsi Sun Jan 25 09:38:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26102 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 09:38:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from acd.ufrj.br (acd.ufrj.br [146.164.2.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA26093 for ; Sun, 25 Jan 1998 09:38:24 -0800 (PST) (envelope-from jonny@acd.ufrj.br) Received: by acd.ufrj.br (AIX 4.1/UCB 5.64/4.03) id AA17364; Sun, 25 Jan 1998 15:33:55 -0300 From: jonny@acd.ufrj.br (Joao Carlos Mendes Luis) Message-Id: <9801251833.AA17364@acd.ufrj.br> Subject: Joliet+RockRidge in one CD ? To: freebsd-scsi@FreeBSD.ORG Date: Sun, 25 Jan 1998 15:33:55 -0300 (GRNLNDST) Reply-To: jonny@coppe.ufrj.br X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I know this is not SCSI related, but this list is where I think I can find those who know best about the issue. I want to burn a CD-R with long filenames. Is it possible to make one that could work both under Win95 and Unix ? I think that Joliet and RockRidge are not mutually exclusive. Win95 would see the Joliet LongNames, and Unix would see the short names plus the trans.tbl files. Have somebody already done this ? Is there a utility to create the trans.tbl files on a existing Win95 directory ? Also, does rockridge supports spaces in filenames ? I plan to use Adaptec EZCDPro2 to make the ISO image, if that matters. Thanks for any answer, Jonny PS: Microsoft, always reinventing (and redefining) the wheel... :( From owner-freebsd-scsi Sun Jan 25 16:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04333 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 16:02:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bob.tri-lakes.net (BOB.tri-lakes.net [207.3.81.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA04328 for ; Sun, 25 Jan 1998 16:02:37 -0800 (PST) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.151] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ua441942 for ; Sun, 25 Jan 1998 18:03:00 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 25 Jan 1998 17:56:03 -0600 (CST) From: Chris Dillon To: Donald Burr Subject: RE: Minor annoyances with ZIP Plus Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Jan-98 Donald Burr wrote: >>I just got a IOMega ZIP Plus and am using it with an Adaptec 1522 >>(AIC6360, >>aic0). It works fine in Win95, and fine in FreeBSD for the most part, >>other >>than some rather annoying error messages when trying to use it for >>various >>things. Any time I mount/umount a disk, change it, and do the same again >>(or >>even use mtools). You'll notice an error when probing the drive attached >>to >>aic0 and all the errors at the bottom (which occur when I try to use it >>after >>changing disks): > >Don't worry; these errors are "normal". Well, as "normal" as Iomega SCSI >devices get, anyway. Apparently Iomega subscribes to some "weird", >non-standard variant of SCSI, in that their devices do not support certain >SCSI commands mandated by the SCSI specification, specifically, those SCSI >commansd that ask a device to specify its geometry (size, # >heads/sectors/etc.). When presented with this anomalous behavior, the >FreeBSD driver guesses the device's geometry, and so everything still >works. Aaah, and the light comes on over my head. ;-> I guess Justin's new CAM code and the 'quirk entries' will be able to provide a neat hack for this problem? Any tested hacks I can apply to this non-CAM (2.2.5-STABLE) system to make this thing shut up? > >I see the same behavior with my Iomega Jaz drive, and with a prevous Zip >drive I used to own. > >My advice is not to worry about it, shake your head sadly at Iomega's lack >of direction, and move on with life. :) I would have chosen something besides this lousy ZIP drive, but this seems to be the direction everybody is going with removable media, even though there are several products out there that are faster/hold more/cheaper, etc. etc... (sigh) I think we need to get everyone we can to complain to IOMega about their (lack-of) following standards. I wonder if the firmware in these things is flash upgradable. No mention of it in their specs, that I can see. Hmmmm.... --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers. ---- (http://www.freebsd.org) From owner-freebsd-scsi Sun Jan 25 16:08:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04552 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 16:08:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bob.tri-lakes.net (BOB.tri-lakes.net [207.3.81.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA04544 for ; Sun, 25 Jan 1998 16:08:14 -0800 (PST) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.151] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id da441951 for ; Sun, 25 Jan 1998 18:08:37 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199801250656.XAA23323@narnia.plutotech.com> Date: Sun, 25 Jan 1998 18:04:39 -0600 (CST) From: Chris Dillon To: "Justin T. Gibbs" Subject: Re: Minor annoyances with ZIP Plus Cc: scsi@FreeBSD.ORG, Donald Burr Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Jan-98 Justin T. Gibbs wrote: >> Don't worry; these errors are "normal". Well, as "normal" as Iomega SCSI >> devices get, anyway. Apparently Iomega subscribes to some "weird", >> non-standard variant of SCSI, in that their devices do not support certain >> SCSI commands mandated by the SCSI specification, specifically, those SCSI >> commansd that ask a device to specify its geometry (size, # >> heads/sectors/etc.). When presented with this anomalous behavior, the >> FreeBSD driver guesses the device's geometry, and so everything still >> works. > >This isn't the case. FreeBSD was being silly in asking for the optional, >rigid geometry page, which the IOMega guys chose not to implement. Since >FreeBSD stopped using physical geometry to "optimize" disk I/O (which >doesn't work on the ZBR drives of today), asking for the rigid geometry >wasn't buying us anything and the code was recently changed to use the >information returned by the Read Capacity command instead. Just how recently was this? :-) If within the last couple of days in stable, i'll compile a new kernel and see how I fare. If its only in current, i'll just have to put up with the errors for now, i guess (i'm feeling adventurous enough to try current, though). --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers. ---- (http://www.freebsd.org) From owner-freebsd-scsi Sun Jan 25 17:40:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16167 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 17:40:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16162 for ; Sun, 25 Jan 1998 17:40:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA04374; Sun, 25 Jan 1998 17:33:46 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd004372; Sun Jan 25 17:33:41 1998 Date: Sun, 25 Jan 1998 17:30:17 -0800 (PST) From: Julian Elischer To: Chris Dillon cc: Donald Burr , freebsd-scsi@FreeBSD.ORG Subject: RE: Minor annoyances with ZIP Plus 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 even the old code can do this.. I'll look at doint that. On Sun, 25 Jan 1998, Chris Dillon wrote: > > On 25-Jan-98 Donald Burr wrote: > >>I just got a IOMega ZIP Plus and am using it with an Adaptec 1522 > >>(AIC6360, > >>aic0). It works fine in Win95, and fine in FreeBSD for the most part, > >>other > >>than some rather annoying error messages when trying to use it for > >>various > >>things. Any time I mount/umount a disk, change it, and do the same again > >>(or > >>even use mtools). You'll notice an error when probing the drive attached > >>to > >>aic0 and all the errors at the bottom (which occur when I try to use it > >>after > >>changing disks): > > > >Don't worry; these errors are "normal". Well, as "normal" as Iomega SCSI > >devices get, anyway. Apparently Iomega subscribes to some "weird", > >non-standard variant of SCSI, in that their devices do not support certain > >SCSI commands mandated by the SCSI specification, specifically, those SCSI > >commansd that ask a device to specify its geometry (size, # > >heads/sectors/etc.). When presented with this anomalous behavior, the > >FreeBSD driver guesses the device's geometry, and so everything still > >works. > > Aaah, and the light comes on over my head. ;-> I guess Justin's new CAM code > and the 'quirk entries' will be able to provide a neat hack for this problem? > Any tested hacks I can apply to this non-CAM (2.2.5-STABLE) system to make this > thing shut up? > > > > >I see the same behavior with my Iomega Jaz drive, and with a prevous Zip > >drive I used to own. > > > >My advice is not to worry about it, shake your head sadly at Iomega's lack > >of direction, and move on with life. :) > > I would have chosen something besides this lousy ZIP drive, but this seems to > be the direction everybody is going with removable media, even though there are > several products out there that are faster/hold more/cheaper, etc. etc... (sigh) > I think we need to get everyone we can to complain to IOMega about their > (lack-of) following standards. I wonder if the firmware in these things is > flash upgradable. No mention of it in their specs, that I can see. Hmmmm.... > > > --- Chris Dillon > --- cdillon@tri-lakes.net > --- Powered by FreeBSD, the best operating system on the planet > for Intel x86 based computers. > ---- (http://www.freebsd.org) > From owner-freebsd-scsi Sun Jan 25 20:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04044 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 20:52:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04004 for ; Sun, 25 Jan 1998 20:51:58 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id VAA13285; Sun, 25 Jan 1998 21:51:53 -0700 (MST) Message-Id: <199801260451.VAA13285@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Chris Dillon cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG, Donald Burr Subject: Re: Minor annoyances with ZIP Plus In-reply-to: Your message of "Sun, 25 Jan 1998 18:04:39 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jan 1998 21:49:22 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Just how recently was this? :-) If within the last couple of days in stable, >i'll compile a new kernel and see how I fare. If its only in current, i'll >just have to put up with the errors for now, i guess (i'm feeling adventurous >enough to try current, though). I think it was just committed to current, but Julian E. would know for sure. >--- Chris Dillon >--- cdillon@tri-lakes.net >--- Powered by FreeBSD, the best operating system on the planet > for Intel x86 based computers. >---- (http://www.freebsd.org) > -- Justin From owner-freebsd-scsi Sun Jan 25 22:00:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10540 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 22:00:16 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10535 for ; Sun, 25 Jan 1998 22:00:14 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA08478; Sun, 25 Jan 1998 21:56:50 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd008476; Sun Jan 25 21:56:43 1998 Date: Sun, 25 Jan 1998 21:53:18 -0800 (PST) From: Julian Elischer To: "Justin T. Gibbs" cc: Chris Dillon , scsi@FreeBSD.ORG, Donald Burr Subject: Re: Minor annoyances with ZIP Plus In-Reply-To: <199801260451.VAA13285@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org it was only in -current, but no-one has screamed so I might moerge it to stable in the next few days. I'll also make it a bit less verbose. On Sun, 25 Jan 1998, Justin T. Gibbs wrote: > >Just how recently was this? :-) If within the last couple of days in stable, > >i'll compile a new kernel and see how I fare. If its only in current, i'll > >just have to put up with the errors for now, i guess (i'm feeling adventurous > >enough to try current, though). > > I think it was just committed to current, but Julian E. would know for > sure. > > >--- Chris Dillon > >--- cdillon@tri-lakes.net > >--- Powered by FreeBSD, the best operating system on the planet > > for Intel x86 based computers. > >---- (http://www.freebsd.org) > > > > -- > Justin > > > From owner-freebsd-scsi Sun Jan 25 23:13:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15767 for freebsd-scsi-outgoing; Sun, 25 Jan 1998 23:13:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15762 for ; Sun, 25 Jan 1998 23:13:24 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA24115; Mon, 26 Jan 1998 08:13:22 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA25376; Mon, 26 Jan 1998 08:05:26 +0100 (MET) Message-ID: <19980126080526.33565@uriah.heep.sax.de> Date: Mon, 26 Jan 1998 08:05:26 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: jonny@coppe.ufrj.br Subject: Re: Joliet+RockRidge in one CD ? Reply-To: Joerg Wunsch References: <9801251833.AA17364@acd.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <9801251833.AA17364@acd.ufrj.br>; from Joao Carlos Mendes Luis on Sun, Jan 25, 1998 at 03:33:55PM -0300 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Joao Carlos Mendes Luis wrote: > I want to burn a CD-R with long filenames. Is it possible to make > one that could work both under Win95 and Unix ? Should be possible. > I plan to use Adaptec EZCDPro2 to make the ISO image, if that matters. I have no idea about this one. Does it run on FreeBSD? :-) I think there are Joliet patches around for mkisofs, i'm not sure whether they have already been integrated into the latest official version, however. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Jan 26 04:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA15170 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 04:18:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bob.tri-lakes.net (BOB.tri-lakes.net [207.3.81.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA15162 for ; Mon, 26 Jan 1998 04:18:40 -0800 (PST) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.148] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ha442553 for ; Mon, 26 Jan 1998 06:18:57 -0600 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD In-Reply-To: Date: Mon, 26 Jan 1998 06:07:10 -0600 (CST) From: Chris Dillon To: Julian Elischer Subject: Re: Minor annoyances with ZIP Plus Cc: Donald Burr , scsi@FreeBSD.ORG, "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 26-Jan-98 Julian Elischer wrote: >it was only in -current, but no-one has screamed so I might moerge it to >stable in the next few days. I'll also make it a bit less verbose. > > >On Sun, 25 Jan 1998, Justin T. Gibbs wrote: > >> >Just how recently was this? :-) If within the last couple of days in >stable, >> >i'll compile a new kernel and see how I fare. If its only in current, i'll >> >just have to put up with the errors for now, i guess (i'm feeling >adventurous >> >enough to try current, though). >> >> I think it was just committed to current, but Julian E. would know for >> sure. >> Thanks, Julian. Thanks to Donald and Justin, too. Hopefully nobody using stable will scream, either. :-) --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers. ---- (http://www.freebsd.org) From owner-freebsd-scsi Mon Jan 26 09:57:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25450 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 09:57:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25437 for ; Mon, 26 Jan 1998 09:57:02 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA27413; Mon, 26 Jan 1998 10:54:17 -0700 (MST) Date: Mon, 26 Jan 1998 10:54:17 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801261754.KAA27413@narnia.plutotech.com> To: Bruce Evans cc: scsi@FreeBSD.ORG Subject: Re: Minor annoyances with ZIP Plus Newsgroups: pluto.freebsd.scsi In-Reply-To: <199801250804.TAA12845@godzilla.zeta.org.au> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>asking for the rigid geometry >>wasn't buying us anything and the code was recently changed to use the >>information returned by the Read Capacity command instead. > > This hasn't actually changed (at least in the current sd driver). All > that changed recently is that Read Capacity is now used to determine the > sector size. Yes. It's my fault for thinking in terms of what the CAM disk driver has been doing for some time. > Read Capacity has always been used to determine the disk size, and Mode > Sense of the rigid geometry page has always been used to initialize > default values for the geometry in the dummy label for the whole disk. > If there is a valid DOS partition on the disk, as is normally(?) the > case for new zip disks, then these default values are not used. In any > case, the geometry in the dummy label for fdisk is only used by fdisk > and sysinstall. Which is exactly the reason why we shouldn't be using the RG page at all. Almost every SCSI adapter we support will not properly boot a system with a physical geometry in the MBR and when you get a new disk drive it doesn't have a valid MBR to override the dummy label. This is why CAM offers a facility to determine the controller translated geometry and to use that in the dummy label. > Summary: everything just works, but the lowest layer is too verbose and > the highest layer (newfs) is too smart. If it just worked, we wouldn't get so many complaints about geometry problems during installs. > Bruce -- Justin From owner-freebsd-scsi Mon Jan 26 10:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26293 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 10:03:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lithium.elemental.org (daleg@lithium.elemental.org [204.91.240.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26280 for ; Mon, 26 Jan 1998 10:03:06 -0800 (PST) (envelope-from daleg@lithium.elemental.org) Received: from localhost (daleg@localhost) by lithium.elemental.org (8.8.8/8.8.4) with SMTP id MAA15964; Mon, 26 Jan 1998 12:49:51 -0500 Date: Mon, 26 Jan 1998 12:49:51 -0500 (EST) From: Dale Ghent Reply-To: Dale Ghent To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Jazz disks (was: Re: Minor annoyances with ZIP Plus) In-Reply-To: <199801261754.KAA27413@narnia.plutotech.com> Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One off-topic question I have.... is there a utility around you can use to turn off RO on a Jazz disk? The setup isa bit retarded... there no shutter you open or close to wrte-protect a jaxx disk... You have to make the disk that comes with the drive rw by using a windows-only utility. Is there something comperable to theis util I can compile up and use to unlock the disk? -Dale From owner-freebsd-scsi Mon Jan 26 10:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02226 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 10:40:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02190 for ; Mon, 26 Jan 1998 10:40:15 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA06363; Tue, 27 Jan 1998 05:30:21 +1100 Date: Tue, 27 Jan 1998 05:30:21 +1100 From: Bruce Evans Message-Id: <199801261830.FAA06363@godzilla.zeta.org.au> To: bde@zeta.org.au, gibbs@narnia.plutotech.com Subject: Re: Minor annoyances with ZIP Plus Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Which is exactly the reason why we shouldn't be using the RG page at all. >Almost every SCSI adapter we support will not properly boot a system with >a physical geometry in the MBR and when you get a new disk drive it doesn't >have a valid MBR to override the dummy label. Sure it will. You just can't put a physical geometry in the MBR for almost any drive less than 8 years old :-). >> Summary: everything just works, but the lowest layer is too verbose and >> the highest layer (newfs) is too smart. > >If it just worked, we wouldn't get so many complaints about geometry >problems during installs. I meant low-level everythings, especially for Zip disks. Bruce From owner-freebsd-scsi Mon Jan 26 11:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06816 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 11:07:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06777 for ; Mon, 26 Jan 1998 11:07:23 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA13940; Mon, 26 Jan 1998 11:08:55 -0700 (MST) Message-Id: <199801261808.LAA13940@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Dale Ghent cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Jazz disks (was: Re: Minor annoyances with ZIP Plus) In-reply-to: Your message of "Mon, 26 Jan 1998 12:49:51 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jan 1998 11:06:25 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >One off-topic question I have.... is there a utility around you can use to >turn off RO on a Jazz disk? The setup isa bit retarded... there no shutter >you open or close to wrte-protect a jaxx disk... You have to make the disk >that comes with the drive rw by using a windows-only utility. Is there >something comperable to theis util I can compile up and use to unlock the >disk? > > -Dale Unfortunately I don't own a Jaz, but if I could get my hands on one I could sniff the SCSI bus and write a program to do it. My guess is that it's a vendor specific command, but there may be something in the SCSI spec to do this. -- Justin From owner-freebsd-scsi Mon Jan 26 17:33:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10444 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 17:33:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-112-190.la.inreach.net [206.18.112.190]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10434 for ; Mon, 26 Jan 1998 17:33:42 -0800 (PST) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.7/8.8.7) id RAA02072; Mon, 26 Jan 1998 17:34:05 -0800 (PST) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 26 Jan 1998 17:32:18 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Dale Ghent Subject: RE: Jazz disks (was: Re: Minor annoyances with ZIP Plus) Cc: scsi@FreeBSD.ORG, "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 26-Jan-98, Dale Ghent wrote: >One off-topic question I have.... is there a utility around you can use >to >turn off RO on a Jazz disk? The setup isa bit retarded... there no >shutter >you open or close to wrte-protect a jaxx disk... You have to make the >disk >that comes with the drive rw by using a windows-only utility. Is there >something comperable to theis util I can compile up and use to unlock the >disk? Check out: http://www.torque.net/linux-pp.html On this page, there is a utility called ziptool.c, which does what you ask (and more) for Iomega Zip drives. It may or may not (I don't know which) work for Jaz disks. Go ahead and get the code and try it, and you can e-mail the maintainer for more info or questions. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNM05jPjpixuAwagxAQG3JgP/QZgyIS8sRbD7dp7ntlQxtT9A4gOQ8JTQ 4avI06A/vYEmeOAHmm1+3fTTVGeymr30h2kJtTdliFw0BVCrz2DfL+vsRiD/iXyE YUX2z1L94QtnisHLvM+Lfr4lZm2zbHrhw7Nrgf9lbPqQm1irRCvXT6VfS5+C6XMa Wf2ZddmN5M0= =xQ8A -----END PGP SIGNATURE----- From owner-freebsd-scsi Mon Jan 26 17:46:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11647 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 17:46:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11641 for ; Mon, 26 Jan 1998 17:46:47 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA06800; Mon, 26 Jan 1998 17:46:32 -0800 (PST) Date: Mon, 26 Jan 1998 17:46:28 -0800 (PST) From: Jaye Mathisen To: "Justin T. Gibbs" cc: Dale Ghent , scsi@FreeBSD.ORG Subject: Re: Jazz disks (was: Re: Minor annoyances with ZIP Plus) In-Reply-To: <199801261808.LAA13940@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just scsifmt the little suckers, and the ro bit goes away. Use dozens of them this way. Or low-level format them from the Adapter BIOS. Either way. On Mon, 26 Jan 1998, Justin T. Gibbs wrote: > > > >One off-topic question I have.... is there a utility around you can use to > >turn off RO on a Jazz disk? The setup isa bit retarded... there no shutter > >you open or close to wrte-protect a jaxx disk... You have to make the disk > >that comes with the drive rw by using a windows-only utility. Is there > >something comperable to theis util I can compile up and use to unlock the > >disk? > > > > -Dale > > Unfortunately I don't own a Jaz, but if I could get my hands on one I > could sniff the SCSI bus and write a program to do it. My guess is that > it's a vendor specific command, but there may be something in the SCSI > spec to do this. > > -- > Justin > > From owner-freebsd-scsi Mon Jan 26 19:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24577 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 19:38:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lithium.elemental.org (daleg@lithium.elemental.org [204.91.240.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24572 for ; Mon, 26 Jan 1998 19:38:33 -0800 (PST) (envelope-from daleg@lithium.elemental.org) Received: from localhost (daleg@localhost) by lithium.elemental.org (8.8.8/8.8.4) with SMTP id WAA05672; Mon, 26 Jan 1998 22:24:51 -0500 Date: Mon, 26 Jan 1998 22:24:50 -0500 (EST) From: Dale Ghent Reply-To: Dale Ghent To: Donald Burr cc: scsi@FreeBSD.ORG, "Justin T. Gibbs" Subject: RE: Jazz disks (was: Re: Minor annoyances with ZIP Plus) In-Reply-To: Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw 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, 26 Jan 1998, Donald Burr wrote: | Check out: | | http://www.torque.net/linux-pp.html | | On this page, there is a utility called ziptool.c, which does what you ask | (and more) for Iomega Zip drives. It may or may not (I don't know which) | work for Jaz disks. Go ahead and get the code and try it, and you can | e-mail the maintainer for more info or questions. Just FWIW, I got this, removed the check for the Zip drive so that it'll like the Jazz, and I can get the status of the disk (its in password-protected RO), so now all I have to do is figure out the password to the disk -Dale From owner-freebsd-scsi Mon Jan 26 23:20:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28658 for freebsd-scsi-outgoing; Mon, 26 Jan 1998 23:20:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lithium.elemental.org (daleg@lithium.elemental.org [204.91.240.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28624 for ; Mon, 26 Jan 1998 23:19:58 -0800 (PST) (envelope-from daleg@lithium.elemental.org) Received: from localhost (daleg@localhost) by lithium.elemental.org (8.8.8/8.8.4) with SMTP id CAA14648; Tue, 27 Jan 1998 02:06:29 -0500 Date: Tue, 27 Jan 1998 02:06:29 -0500 (EST) From: Dale Ghent Reply-To: Dale Ghent To: Donald Burr cc: scsi@FreeBSD.ORG, "Justin T. Gibbs" Subject: HAHA! RE: Jazz disks (was: Re: Minor annoyances with ZIP Plus) In-Reply-To: Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw 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, 26 Jan 1998, Dale Ghent wrote: | Just FWIW, I got this, removed the check for the Zip drive so that it'll | like the Jazz, and I can get the status of the disk (its in | password-protected RO), so now all I have to do is figure out the password | to the disk After a gander thru DejaNews, I found that the factory-set password on the jaz disks is APlaceForYourStuff. Using the modified linux ziptool program, I was able to turn the RO off. thanks for all your help. -Dale From owner-freebsd-scsi Tue Jan 27 09:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28265 for freebsd-scsi-outgoing; Tue, 27 Jan 1998 09:55:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from damon.com (btUziG+UCDJjLpv1cUSO2KQipRzCIEjl@damon.com [207.170.114.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28244 for ; Tue, 27 Jan 1998 09:55:49 -0800 (PST) (envelope-from dap@damon.com) Received: (from dap@localhost) by damon.com (8.8.7/8.8.7) id LAA06097; Tue, 27 Jan 1998 11:55:26 -0600 (CST) (envelope-from dap) From: Damon Permezel Message-Id: <199801271755.LAA06097@damon.com> Subject: Jazzm In-Reply-To: from Dale Ghent at "Jan 27, 98 02:06:29 am" To: daleg@elemental.org Date: Tue, 27 Jan 1998 11:55:26 -0600 (CST) Cc: dburr@POBoxes.com, scsi@FreeBSD.ORG, gibbs@narnia.plutotech.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone else having reliability problems with Jazz? I had to sent the first 3 back before I got one which would not eat the disk and refuse to eject it. Each time you send the drive back, including the disc, you lose the disc, donating its contents to whoever gets to liberate it. My current drive works ok, but now I am having some of my media start to die. When inserted, the drive makes horrible sounds for a while, then subsides, but the media is unreadable. It rejects mode sense. When I use the Adaptec 2940 low level formatter, it usually fails with a media error. Once (different Adaptec adapter, different firmware) it formatted all the way thru, and verified, but once I moved it back, it died. This was "used once or twice" media. My other media still works, so far.... I have dedicated 2940 adapters for externally connected narrow devices, and I never connect more than one device at a time, on a 3' cable, and yes, I understand the need for correct termination. My general impression, though, is that this is not anything I want to consider for archive, or backup, or even casual use. Are others having similar experiences? From owner-freebsd-scsi Tue Jan 27 10:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11979 for freebsd-scsi-outgoing; Tue, 27 Jan 1998 10:55:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11963 for ; Tue, 27 Jan 1998 10:55:05 -0800 (PST) (envelope-from mango@staff.communique.net) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Tue, 27 Jan 1998 12:54:15 -0600 Message-ID: From: Raul Zighelboim To: "'scsi@freebsd.org'" Subject: buss problems ??? Date: Tue, 27 Jan 1998 12:54:13 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there. I had this machine running for quite some time: FreeBSD 2.2.2-RELEASE #0: Thu Nov 6 07:55:43 CST 1997 And this morning I had a crash. It looks like problems in the scsi bus, and I would guess some hardware going bad. I am including the /kernel messages as well as the boot dmesg scsi related output; So, how do I track the problem and correct it ? Thanks, ================================================== Raul Zighelboim mango@staff.communique.net [Raul Zighelboim] ========/var/log/messages Jan 27 01:12:16 kiyoko /kernel: sd1(ahc0:0:0): Target Busy > Jan 27 01:12:17 kiyoko /kernel: sd1(ahc0:0:0): data overrun of > 16777215 bytes detected in Data-Out phase. Tag > == 0xd. Forcing a retry. > Jan 27 01:12:17 kiyoko /kernel: sd1(ahc0:0:0): Have seen Data Phase. > Length = 16384. NumSGs = 4. > Jan 27 01:12:17 kiyoko /kernel: sg[0] - Addr 0xa781000 : Length 4096 > Jan 27 01:12:17 kiyoko /kernel: sg[1] - Addr 0x1d02000 : Length 4096 > Jan 27 01:12:17 kiyoko /kernel: sg[2] - Addr 0x19203000 : Length 4096 > Jan 27 01:12:17 kiyoko /kernel: sg[3] - Addr 0x15304000 : Length 4096 > Jan 27 01:12:17 kiyoko /kernel: sd1(ahc0:0:0): data overrun of > 16777215 bytes detected in Data-Out phase. Tag == 0xd. Forcing a > retry. > Jan 27 01:12:17 kiyoko /kernel: sd1(ahc0:0:0): Have seen Data Phase. > Length = 8192. NumSGs = 2. > Jan 27 01:12:17 kiyoko /kernel: sg[0] - Addr 0x1ce87000 : Length 4096 > Jan 27 01:12:17 kiyoko /kernel: sg[1] - Addr 0xbc8000 : Length 4096 > Jan 27 01:12:26 kiyoko /kernel: sd1(ahc0:0:0): SCB 0xa - timed out > while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 > Jan 27 01:12:26 kiyoko /kernel: SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = > 0x27 SSTAT1 = 0xb > Jan 27 01:12:26 kiyoko /kernel: Ordered Tag queued > Jan 27 01:12:26 kiyoko /kernel: sd1(ahc0:0:0): SCB 0x2 timedout while > recovery in progress > Jan 27 01:12:26 kiyoko /kernel: Ordered Tag sent > Jan 27 01:12:31 kiyoko /kernel: sd1(ahc0:0:0): SCB 0xa - timed out in > datain phase, SCSISIGI == 0xc6 > Jan 27 01:12:31 kiyoko /kernel: SEQADDR = 0x12b SCSISEQ = 0x12 SSTAT0 > = 0x5 SSTAT1 = 0x13 > Jan 27 01:12:31 kiyoko /kernel: sd0(ahc0:3:0): abort message in > message buffer > Jan 27 01:12:31 kiyoko /kernel: sd0(ahc0:3:0): SCB 13 - Abort Tag > Completed. > Jan 27 01:12:31 kiyoko /kernel: sd0(ahc0:3:0): no longer in timeout > Jan 27 01:12:36 kiyoko /kernel: sd1(ahc0:0:0): SCB 0x2 - timed out > while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 > Jan 27 01:12:36 kiyoko /kernel: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = > 0x27 SSTAT1 = 0xb > Jan 27 01:12:36 kiyoko /kernel: Ordered Tag queued > Jan 27 01:12:36 kiyoko /kernel: Ordered Tag sent Jan 27 09:23:41 kiyoko /kernel: Copyright (c) 1992-1997 FreeBSD Inc. Jan 27 09:23:41 kiyoko /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 27 09:23:41 kiyoko /kernel: The Regents of the University of California. All rights reserved. Jan 27 09:23:41 kiyoko /kernel: Jan 27 09:23:41 kiyoko /kernel: FreeBSD 2.2.2-RELEASE #0: Thu Nov 6 07:55:43 CST 1997 ==============dmesg ahc0 rev 0 int a irq 9 on pci0:12 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 sd1(ahc0:0:0): Direct-Access 8669MB (17755614 512 byte sectors) ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 sd2(ahc0:1:0): Direct-Access 8669MB (17755614 512 byte sectors) ahc0: target 2 Tagged Queuing Device (ahc0:2:0): "SEAGATE ST410800W 0006" type 0 fixed SCSI 2 sd3(ahc0:2:0): Direct-Access 8669MB (17755614 512 byte sectors) ahc0: target 3 Tagged Queuing Device (ahc0:3:0): "QUANTUM VIKING 4.5 WSE 8808" type 0 fixed SCSI 2 sd0(ahc0:3:0): Direct-Access 4345MB (8899737 512 byte sectors) ahc1 rev 0 int a irq 10 on pci0:13 ahc1: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc1 waiting for scsi devices to settle ahc1: target 1 Tagged Queuing Device (ahc1:1:0): "QUANTUM VIKING 2.3 WSE 8808" type 0 fixed SCSI 2 sd5(ahc1:1:0): Direct-Access 2171MB (4446801 512 byte sectors) ahc1: target 2 Tagged Queuing Device (ahc1:2:0): "QUANTUM VIKING 2.3 WSE 8808" type 0 fixed SCSI 2 sd6(ahc1:2:0): Direct-Access 2171MB (4446801 512 byte sectors) ahc1: target 3 Tagged Queuing Device (ahc1:3:0): "QUANTUM VIKING 2.3 WSE 8808" type 0 fixed SCSI 2 sd7(ahc1:3:0): Direct-Access 2171MB (4446801 512 byte sectors) ahc1: target 4 Tagged Queuing Device (ahc1:4:0): "QUANTUM VIKING 2.3 WSE 8808" type 0 fixed SCSI 2 sd8(ahc1:4:0): Direct-Access 2171MB (4446801 512 byte sectors) ======KERNEL options AHC_TAGENABLE options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE controller ahc0 controller ahc1 controller scbus0 at ahc0 bus 0 controller scbus2 at ahc1 bus 0 disk sd1 at scbus0 target 0 disk sd2 at scbus0 target 1 disk sd3 at scbus0 target 2 disk sd0 at scbus0 target 3 disk sd5 at scbus2 target 1 disk sd6 at scbus2 target 2 disk sd7 at scbus2 target 3 disk sd8 at scbus2 target 4 From owner-freebsd-scsi Tue Jan 27 17:21:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02698 for freebsd-scsi-outgoing; Tue, 27 Jan 1998 17:21:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-113-179.la.inreach.net [206.18.113.179]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02660 for ; Tue, 27 Jan 1998 17:21:35 -0800 (PST) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.7/8.8.7) id RAA00838; Tue, 27 Jan 1998 17:22:01 -0800 (PST) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199801271755.LAA06097@damon.com> Date: Tue, 27 Jan 1998 17:20:47 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Damon Permezel Subject: RE: Jazzm Cc: gibbs@narnia.plutotech.com, scsi@FreeBSD.ORG, daleg@elemental.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 27-Jan-98, Damon Permezel wrote: >My general impression, though, is that this is not anything I want to >consider >for archive, or backup, or even casual use.\ That's funny. I've been heavily using my Jaz drive, for both backup AND archive, since June of last year, with absolutely no problems. I always have a Jaz disk mounted 24/7. Are you aware that there is a recall on some Jaz cartridges, due to somewhat defective parts? Check the Iomega website (http://www.iomega.com/) for more info. It's possible that some of your carts fall into this category. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNM6IOfjpixuAwagxAQFN4gP/XZnCgf4eSZqiWJysoMAzL/cf6F7itZWV 6XjtFKSaFe6w7eGSeyF1u1T6D9MKjyfSvxtwjuZMmWVnAXqQo61sF+n/jaZ4Aeeo iBQza+E3TvONnJgl2zpH8niqOIJWR4mdxMl0SzNzZmdXNm/opC4+gfSkA2YYQJdK NbCbppuEtxs= =XMlK -----END PGP SIGNATURE----- From owner-freebsd-scsi Wed Jan 28 00:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20306 for freebsd-scsi-outgoing; Wed, 28 Jan 1998 00:49:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zaz.kom.auc.dk (root@zaz.kom.auc.dk [130.225.51.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA20298 for ; Wed, 28 Jan 1998 00:49:46 -0800 (PST) (envelope-from aneks@kom.auc.dk) Received: from opel.kom.auc.dk [130.225.51.14] (root) by zaz.kom.auc.dk with smtp (Exim 1.80 #1) id 0xxTBh-0002Qf-00; Wed, 28 Jan 1998 09:49:37 +0100 Received: from aneks by opel.kom.auc.dk with local (Exim 1.80 #1) id 0xxTBg-0003rD-00; Wed, 28 Jan 1998 09:49:36 +0100 From: Arne Norre Ekstroem To: scsi@FreeBSD.ORG Subject: Re: Jazzm In-Reply-To: <199801271755.LAA06097@damon.com> References: <199801271755.LAA06097@damon.com> Message-Id: Date: Wed, 28 Jan 1998 09:49:36 +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "Damon" == Damon Permezel writes: Damon> Is anyone else having reliability problems with Jazz? I had to Damon> sent the first 3 back before I got one which would not eat the Damon> disk and refuse to eject it. Damon> Each time you send the drive back, including the disc, you lose Damon> the disc, donating its contents to whoever gets to liberate it. Damon> My current drive works ok, but now I am having some of my media Damon> start to die. Damon> When inserted, the drive makes horrible sounds for a while, then Damon> subsides, but the media is unreadable. It rejects mode sense. Damon> When I use the Adaptec 2940 low level formatter, it usually fails Damon> with a media error. Once (different Adaptec adapter, different Damon> firmware) it formatted all the way thru, and verified, but once I Damon> moved it back, it died. Damon> This was "used once or twice" media. My other media still works, Damon> so far.... I have dedicated 2940 adapters for externally Damon> connected narrow devices, and I never connect more than one Damon> device at a time, on a 3' cable, and yes, I understand the need Damon> for correct termination. Damon> My general impression, though, is that this is not anything I Damon> want to consider for archive, or backup, or even casual use. Damon> Are others having similar experiences? Yep, I have a Jaz drive at the office, and one at home. 100% of the media I have ever bought have wound up being defective :-( The problem is that I don't know which drive is trashing the discs. I hate to think about the things on which I could have spent my money if I hadn't bought the drive (and controller)... \Arne From owner-freebsd-scsi Wed Jan 28 13:15:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24997 for freebsd-scsi-outgoing; Wed, 28 Jan 1998 13:15:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crb.mnsinc.com [206.239.213.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24941 for ; Wed, 28 Jan 1998 13:15:32 -0800 (PST) (envelope-from crb@ChrisBowman.com) Received: from localhost (crb@localhost) by quark.ChrisBowman.com (8.8.8/8.8.7) with SMTP id PAA01291; Wed, 28 Jan 1998 15:53:01 -0500 (EST) (envelope-from crb@ChrisBowman.com) X-Authentication-Warning: quark.ChrisBowman.com: crb owned process doing -bs Date: Wed, 28 Jan 1998 15:53:01 -0500 (EST) From: "Christopher R. Bowman" To: Damon Permezel cc: daleg@elemental.org, dburr@POBoxes.com, scsi@FreeBSD.ORG, gibbs@narnia.plutotech.com Subject: Re: Jazzm In-Reply-To: <199801271755.LAA06097@damon.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 27 Jan 1998, Damon Permezel wrote: >Is anyone else having reliability problems with Jazz? I had to sent >the first 3 back before I got one which would not eat the disk and >refuse to eject it. > >Each time you send the drive back, including the disc, you lose the disc, >donating its contents to whoever gets to liberate it. > >My current drive works ok, but now I am having some of my media start to die. > >When inserted, the drive makes horrible sounds for a while, then >subsides, but the media is unreadable. It rejects mode sense. >When I use the Adaptec 2940 low level formatter, it usually fails >with a media error. Once (different Adaptec adapter, different >firmware) it formatted all the way thru, and verified, but once I >moved it back, it died. > >This was "used once or twice" media. My other media still works, >so far.... I have dedicated 2940 adapters for externally connected >narrow devices, and I never connect more than one device at a time, >on a 3' cable, and yes, I understand the need for correct termination. > >My general impression, though, is that this is not anything I want to consider >for archive, or backup, or even casual use. > >Are others having similar experiences? How hot are the discs when they come out? I really liked my syjet until I filled up the other bays in my case. Then things didn't work so well, I would start to lose sectors. The drive runs pretty hot, but when I stacked other drives around it, it just couldn't handle it. I haven't as yet had a chance to add a fan to see if that will do enough to fix the problem, but if I only use the syjet for the first few minutes after I start up the machine, I don't have any problems and it indeed works really nicely. --------- Christopher R. Bowman crb@ChrisBowman.com My home page From owner-freebsd-scsi Thu Jan 29 03:42:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21143 for freebsd-scsi-outgoing; Thu, 29 Jan 1998 03:42:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpham.uni-mb.si (alpham.uni-mb.si [164.8.1.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20883 for ; Thu, 29 Jan 1998 03:39:55 -0800 (PST) (envelope-from vrtin@uni-mb.si) Received: from unicorn.uni-mb.si by alpham.uni-mb.si (PMDF V5.1-9 #7554) with ESMTP id <01ISY8XDM6VW000898@alpham.uni-mb.si> for freebsd-scsi@freebsd.org; Thu, 29 Jan 1998 13:39:18 MET Received: from localhost (david@localhost) by unicorn.uni-mb.si (8.8.8/8.8.8/19970814) with SMTP id MAA12000 for ; Thu, 29 Jan 1998 12:39:17 +0100 (CET) Date: Thu, 29 Jan 1998 12:39:12 +0100 (CET) From: David Vrtin Subject: DAT/dump problem To: freebsd-scsi@FreeBSD.ORG Reply-to: David Vrtin Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-No-Archive: Yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" Hello, "man dump" says: -a ``auto-size''. Bypass all tape length considerations, and enforce writing until an end-of-media indication is returned. This fits best for most modern tape drives. Use of this option is particu- larly recommended when appending to an existing tape, or using a tape drive with hardware compression (where you can never be sure about the compression ratio). I have Sony DDS DG90M (90m/295feet) data carttridge and: (ncr0:6:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2 st0(ncr0:6:0): Sequential-Access st0(ncr0:6:0): 6.7 MB/s (150 ns, offset 8) density code 0x13, drive empty Do I have "modern tape driver" or not? :-) # mt rewind # printenv TAPE /dev/tape # ls -la /dev/tape lrwxrwxrwx 1 root wheel 5 Apr 15 1997 /dev/tape -> nrst0 # dump -0au /u [...] DUMP: 63.53% done, finished in 0:37 DUMP: 68.49% done, finished in 0:32 DUMP: 74.53% done, finished in 0:25 DUMP: 79.67% done, finished in 0:20 DUMP: 82.92% done, finished in 0:17 DUMP: write error 1773020 blocks into volume 1 DUMP: Do you want to restart?: ("yes" or "no") no DUMP: "Yes" or "No"? DUMP: Do you want to restart?: ("yes" or "no") no DUMP: The ENTIRE dump is aborted. On console: ncr0: SCSI phase error fixup: CCB already dequeued (0xf0940400) ncr0: timeout ccb=f0940800 (skip) ncr0: timeout ccb=f0940400 (skip) ncr0: timeout ccb=f0940000 (skip) and then: swap_pager: indefinite wait buffer: device: 132097, blkno: 2848, size 4096 swap_pager: indefinite wait buffer: device: 132097, blkno: 2848, size 4096 swap_pager: indefinite wait buffer: device: 132097, blkno: 19200, size 4096 swap_pager: indefinite wait buffer: device: 132097, blkno: 2848, size 4096 Etc.. Box freezes, hand reset.... :( I have 2.2.5-STABLE from 11. jan. 1998. How can I dump 3GB disk file system to 2GB DAT?? If I use "a" options, I will never get "Is the new volume mounted and ready to go?:" prompt. Some bug in dump? Another strange example: # dump -0u -s 295 -d 61000 /usr DUMP: Date of this level 0 dump: Mon Jan 19 09:44:04 1998 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0s1g (/usr) to /dev/tape DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 625024 tape blocks on 6.82 tape(s). ^^^^ 6.82 tapes?????? DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: Closing /dev/tape DUMP: Change Volumes: Mount volume #2 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes DUMP: Volume 2 begins with blocks from inode 24562 DUMP: 13.95% done, finished in 0:38 DUMP: Closing /dev/tape DUMP: Change Volumes: Mount volume #3 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes DUMP: Volume 3 begins with blocks from inode 46553 DUMP: 34.66% done, finished in 0:21 DUMP: Closing /dev/tape DUMP: Change Volumes: Mount volume #4 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") no DUMP: Do you want to abort?: ("yes" or "no") yes DUMP: The ENTIRE dump is aborted. # Thanks for any help, David -- David Vrtin (system manager) # tel: +386 62 220-7129 University of Maribor, Faculty of EE and CS # fax: +386 62 211-178 Smetanova 17, SI-2000 Maribor, Slovenia # www.uni-mb.si/~david/ From owner-freebsd-scsi Thu Jan 29 04:23:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28287 for freebsd-scsi-outgoing; Thu, 29 Jan 1998 04:23:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28272 for ; Thu, 29 Jan 1998 04:23:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id MAA08377; Thu, 29 Jan 1998 12:22:30 GMT Message-ID: <19980129042230.43963@relay.nuxi.com> Date: Thu, 29 Jan 1998 04:22:30 -0800 From: "David E. O'Brien" To: David Vrtin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DAT/dump problem Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: ; from David Vrtin on Thu, Jan 29, 1998 at 12:39:12PM +0100 X-Warning: Mutt Bites! X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" > "man dump" says: > > -a ``auto-size''. Bypass all tape length considerations, and enforce > writing until an end-of-media indication is returned. This fits > best for most modern tape drives. Use of this option is particu- > larly recommended when appending to an existing tape, or using a > tape drive with hardware compression (where you can never be sure > about the compression ratio). This is a hope, not current reality. ``dump -a'' is broken on -STABLE and -CURRENT. The new CAM subsystem for -CURRENT either fixes this, or promisses to fix this. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) From owner-freebsd-scsi Fri Jan 30 15:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17171 for freebsd-scsi-outgoing; Fri, 30 Jan 1998 15:13:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from condor.physics.montana.edu (condor.physics.montana.edu [153.90.192.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17163 for ; Fri, 30 Jan 1998 15:13:10 -0800 (PST) (envelope-from abenner@condor.physics.montana.edu) Received: from localhost (abenner@localhost) by condor.physics.montana.edu (8.8.5/8.7.3) with SMTP id QAA04626; Fri, 30 Jan 1998 16:13:39 -0700 (MST) Date: Fri, 30 Jan 1998 16:13:36 -0700 (MST) From: Aaron Benner To: scsi@FreeBSD.ORG cc: Aaron Benner Subject: Re: AIC7880P, help needed. 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 X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" At the beginning of this month I posted a problem to the -STABLE list regarding a bios (or other) conflict with an adaptec ahc2940 Ultra Wide controller. The card hangs during the boot probe. The *same* machine, in the *same* configuration, will boot win95 using adaptec's drivers and address the card without a problem, so I can verify that it's not the card and it's not somthing like termination. The box the card in is is a DEC venturis FX 5133, with a PhoenixBIOS 4.04, the DEC overlay is revision 1.10. The boot messages given from a 2.2.5-RELEASE generic kernel are as follows: ahc0 rev 1 int a irq11 on pci0:12 mapreg[10] type=1 addr=000e800 size=0100 mapreg[14] type=0 addr=fedff000 size=1000 ahc0: reading SEEPROM...done internal50 cable not present internal68 calbe not present brdctl == 0xec external cable is present eprom is present brdctl == 0xac low byte termination enabled, high byte termination enabled ahc0: AIC7880 Wide channel, SCSI id=7, 16 SCBs ahc0: resetting channel A ahc0: downlading sequencer program...ahc0: 366 instructions ahc0: probing channel A ahc0: waiting for devices to settle ahc0: tgt0 using 16 bit transfers ahc0: board not responding (ahc0:0:0): SCB 0x0 - timed out in message phase, SCSISIGI==0x46 SEQADDR=0x15f SCSISEQ=0x12 SSTAT0=0x6 SSTAT1=0x3 (ahc0:0:0): abort message in message buffer ahc0: board not responding cmd fail (ahc0:0:0) SCB 0x1 timeout while in recovery process (ahc0:0:0) "unknown unknown ????" type 13 fixed SCSI 0 unk0(ahc0:0:0): unknown ..... (From the "board not responding message" it repeats for each SCB) ---------- Forwarded message ---------- Date: Wed, 7 Jan 1998 20:26:21 -0700 (MST) From: "Justin T. Gibbs" To: Aaron Benner Cc: scsi@FreeBSD.org Subject: Re: AIC7880P Newsgroups: pluto.freebsd.stable In article you wrote: > I've got a problem, and I need to know if I sliced hairs too thin. > We recently aquired a pair of seagate barracuda 9 gig Ultra Wide scsi > drives, and an adaptec 2940UW (AIC7880P controller chip). You should send these kinds of bug reports to the SCSI list. > I need to know if, as the evidence seems to support, there is enough > difference between the AIC7880 and the AIC7880P for the Ultra Wide > controller to be incompatible with FreeBSD. They both work just fine with FreeBSD. > The current symptom is a hang at the kernel probe, the kernel recognizes > the card as a 2940 with a wide channel, reports the right card status, and > then the "waiting for SCSI devices to settle" just sits there like a lump. Sounds like a termination or cabling problem. Boot with the -v flag and write down everything that gets spit out during the aic7xxx probe. From owner-freebsd-scsi Sat Jan 31 02:41:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25023 for freebsd-scsi-outgoing; Sat, 31 Jan 1998 02:41:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24992 for ; Sat, 31 Jan 1998 02:41:01 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from pacific.jrc.it (pacific.jrc.it [139.191.72.150]) by mrelay.jrc.it (LMC5688) with SMTP id LAA19874 for ; Sat, 31 Jan 1998 11:40:58 +0100 (MET) Received: from ross.jrc.it by pacific.jrc.it (4.1/IRSA-ME_1.3m) id AA05579; Sat, 31 Jan 98 11:40:58 +0100 Posted-Date: Sat, 31 Jan 1998 11:40:57 +0100 (MET) Date: Sat, 31 Jan 1998 11:40:57 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@ross.jrc.it Reply-To: Nick Hibma To: freebsd-scsi@FreeBSD.ORG Subject: patches for timeouts: Message-Id: Reply-Path: Nick.Hibma@jrc.it Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1806850893-886242799=:24374" Content-Id: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-1806850893-886242799=:24374 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Modification of time out values for FreeBSD-2.2.1 & FreeBSD 3.0-970522-SNAP During playing around with my removable media daemon I had this experience that a number of time outs were a bit on the short side: scsi_start_unit scsi_stop_unit Spin down takes approximately 15 seconds on the JAZ drive. When you send the drive a command during the spin down, it locks up and needs to be switched on and off to restore proper behaviour. This solution has been found somewhere in the archives for Linux. Another one is the recognition of the tape drives. Can't remember what I exactly did to that one, but upon recognition of an old Archive Viper with a tape inserted it takes about 40 seconds to get online. FreeBSD in the meantime decides that it needs to pop round the errors departement and go read through those message, aloud. I will post this one as soon as I get that one here. (Don't you love free OS's?) Nick Hibma *** scsi_base.c Sun Dec 21 18:00:38 1997 --- scsi_base.c.NWH Sun Dec 21 16:53:54 1997 *************** *** 331,337 **** 0, 0, 2, ! 10000, NULL, flags)); } --- 331,339 ---- 0, 0, 2, ! /* 10000 - JAZ drive needs >10s - nick.hibma@jrc.it **** NWH */ ! 15000, ! /* End ************************************************* NWH */ NULL, flags)); } *************** *** 359,365 **** 0, 0, 2, ! 10000, NULL, flags)); } --- 361,369 ---- 0, 0, 2, ! /* 10000 - JAZ drive needs >10s - nick.hibma@jrc.it **** NWH */ ! 15000, ! /* End ************************************************* NWH */ NULL, flags)); } ME-SAI, Joint Research Centre, Italy building: 69 tel.: +39 332 78 9943 fax.: +39 332 78 9648 ---559023410-1806850893-886242799=:24374 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=patches Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: patches for timeouts to scsi_base.c KioqIHNjc2lfYmFzZS5jCVN1biBEZWMgMjEgMTg6MDA6MzggMTk5Nw0KLS0t IHNjc2lfYmFzZS5jLk5XSAlTdW4gRGVjIDIxIDE2OjUzOjU0IDE5OTcNCioq KioqKioqKioqKioqKg0KKioqIDMzMSwzMzcgKioqKg0KICAJCTAsDQogIAkJ MCwNCiAgCQkyLA0KISAJCTEwMDAwLA0KICAJCU5VTEwsDQogIAkJZmxhZ3Mp KTsNCiAgfQ0KLS0tIDMzMSwzMzkgLS0tLQ0KICAJCTAsDQogIAkJMCwNCiAg CQkyLA0KISAJCS8qIDEwMDAwIC0gSkFaIGRyaXZlIG5lZWRzID4xMHMgLSBu aWNrLmhpYm1hQGpyYy5pdCAqKioqIE5XSCAqLw0KISAJCTE1MDAwLA0KISAJ CS8qIEVuZCAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqIE5XSCAqLw0KICAJCU5VTEwsDQogIAkJZmxhZ3MpKTsN CiAgfQ0KKioqKioqKioqKioqKioqDQoqKiogMzU5LDM2NSAqKioqDQogIAkJ MCwNCiAgCQkwLA0KICAJCTIsDQohIAkJMTAwMDAsDQogIAkJTlVMTCwNCiAg CQlmbGFncykpOw0KICB9DQotLS0gMzYxLDM2OSAtLS0tDQogIAkJMCwNCiAg CQkwLA0KICAJCTIsDQohIAkJLyogMTAwMDAgLSBKQVogZHJpdmUgbmVlZHMg PjEwcyAtIG5pY2suaGlibWFAanJjLml0ICoqKiogTldIICovDQohIAkJMTUw MDAsDQohIAkJLyogRW5kICoqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKiogTldIICovDQogIAkJTlVMTCwNCiAgCQlm bGFncykpOw0KICB9DQo= ---559023410-1806850893-886242799=:24374-- From owner-freebsd-scsi Sat Jan 31 02:46:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25356 for freebsd-scsi-outgoing; Sat, 31 Jan 1998 02:46:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25351 for ; Sat, 31 Jan 1998 02:46:11 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from pacific.jrc.it (pacific.jrc.it [139.191.72.150]) by mrelay.jrc.it (LMC5688) with SMTP id LAA19928 for ; Sat, 31 Jan 1998 11:46:08 +0100 (MET) Received: from ross.jrc.it by pacific.jrc.it (4.1/IRSA-ME_1.3m) id AA05588; Sat, 31 Jan 98 11:46:08 +0100 Posted-Date: Sat, 31 Jan 1998 11:46:07 +0100 (MET) Date: Sat, 31 Jan 1998 11:46:07 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@ross.jrc.it Reply-To: Nick Hibma To: freebsd-scsi@FreeBSD.ORG Subject: removable media daemon Message-Id: Reply-Path: Nick.Hibma@jrc.it Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" Removable Media Daemon v0.3 BETA VERSION by Nick Hibma Rmd is a program is ment to make your live easier by supplying a easy to use but relatively safe way of mounting removable media. It consists of a daemon and a set of scripts interfacing with it. The daemon executes as root and tries to minimise its activity to the bare minimum. It does not prevent users from interfering with each other (neither does the Solaris version of rmd). The scripts run completely in user land and can safely be used by nobody ... I mean user nobody. rmd uses pthreads. Features: x Mounting/Unmounting/Ejecting removable media from userland x Supports: CDROM (SCSI,IDE), JAZ drives, floopies x SCSI: Automatic mounting on insertion of the medium Negative aspects: x Extra SCSI traffic, including blinking of front panel LED of SCSI controller when no media is present. x Use of FIFO does not return any errors to the user, only through console. x Requires patching of the kernel for - Silence about Medium not present errors - Adding of SCIO ioctl controls - Modification of timeouts for JAZ drive x No support for audio CD's like vold for Solaris has. Read the DISCLAIMER after downloading. Also, the README file contains valuable information. Finally by downloading that piece of software you promise to forward any comments to nick.hibma@jrc.it, so I can improve the junk I call rmd. URL: ftp://mat075207.student.utwente.nl/private/n_hibma/rmd-0.3.tar.gz ME-SAI, Joint Research Centre, Italy building: 69 tel.: +39 332 78 9943 fax.: +39 332 78 9648 From owner-freebsd-scsi Sat Jan 31 11:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24456 for freebsd-scsi-outgoing; Sat, 31 Jan 1998 11:40:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA24451 for ; Sat, 31 Jan 1998 11:40:53 -0800 (PST) (envelope-from patl@phoenix.volant.org) From: patl@phoenix.volant.org Received: from asimov.phoenix.volant.org [205.179.79.65] by phoenix.volant.org with smtp (Exim 1.62 #1) id 0xyimb-0007Xa-00; Sat, 31 Jan 1998 11:40:53 -0800 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id LAA06640; Sat, 31 Jan 1998 11:39:01 -0800 Date: Sat, 31 Jan 1998 11:39:01 -0800 (PST) Reply-To: patl@phoenix.volant.org Subject: Re: Jazzm To: scsi@FreeBSD.ORG 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 X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" > >>>>> "Damon" == Damon Permezel writes: > > Damon> Is anyone else having reliability problems with Jazz? I had to > Damon> sent the first 3 back before I got one which would not eat the > Damon> disk and refuse to eject it. > > Damon> Each time you send the drive back, including the disc, you lose > Damon> the disc, donating its contents to whoever gets to liberate it. Since you've powered off with the disk still inside, you can liberate the cartridge yourself. Simply straighten out a paper clip and stick the end into the tiny hole that is about 3mm beneath the cartridge slot. On the internal drives, it is just to the left of the LED. On the external drives, it is about 2.5cm from the left edge of the slot. (The hole is in the same place, the LED moved.) You will feel some resistance. Push gently until the cartridge pops out. NEVER DO THIS WITH THE POWER ON !!! NOTE that power-down with the cartridge installed is NOT recommended. See the docs that came with the drive and/or the iomega Web page for various dire warnings. You haven't said anything about the circumstances under which this occurs. I am using a Jaz as the primary (boot) disk for one of my machines so that I can easily use multiple OSes without worrying about compatible boot blocks, or what some brain-dead (read M$) install might trash. I have noticed that when FreeBSD is shutdown it does not release the mount lock on the boot drive; so the disk cannot be ejected. The work-around is to reset the machine so that the BIOS will do a SCSI reset, then eject the drive before the boot sequence brings FreeBSD back up. This may not be your problem; but it does illustrate that a correctly functioning Jaz drive may refuse to eject the cartridge. > Damon> My current drive works ok, but now I am having some of my media > Damon> start to die. > > Damon> When inserted, the drive makes horrible sounds for a while, then > Damon> subsides, but the media is unreadable. It rejects mode sense. All Jaz drives reject mode sense. Ignore it, it's harmless. The horrible sounds are probably something to worry about. > Damon> When I use the Adaptec 2940 low level formatter, it usually fails > Damon> with a media error. Once (different Adaptec adapter, different > Damon> firmware) it formatted all the way thru, and verified, but once I > Damon> moved it back, it died. > > Damon> This was "used once or twice" media. My other media still works, > Damon> so far.... It is possible that this cartridge was damaged by a previous drive. One of the hazards of rigid removable media is that once you've had a head crash, both the drive and the cartridge involved are likely to damage any other unit that they are used with. That unit then spreads the damage, etc. (I could tell horror stories about when I was working for a startup that was trying to use the first SyQuest drives when they were still in Beta. And even into production. In fact, it was over ten years before I tried SyQuest drives again. It was a mistake - the 270 gave me just as much trouble as the old 5M drives had. The Jazz, on the other hand, has given me no trouble at all; and I now own four of them.) > I have dedicated 2940 adapters for externally > Damon> connected narrow devices, and I never connect more than one > Damon> device at a time, on a 3' cable, and yes, I understand the need > Damon> for correct termination. > > Damon> My general impression, though, is that this is not anything I > Damon> want to consider for archive, or backup, or even casual use. > > Damon> Are others having similar experiences? > > Yep, I have a Jaz drive at the office, and one at home. 100% of the > media I have ever bought have wound up being defective :-( The problem > is that I don't know which drive is trashing the discs. It's a pretty easy thing to check - for each drive you allocate one new cartridge, and never use it on any other drive. Wait for one to fail. (Note that I said easy, not cheap.) The problem is, of course, that you are left with a pile of possibly defective cartridges; each of which could damage any drive into which it is inserted. (Depending upon the nature of the damage.) Then that drive could damage any cartridge inserted into it, etc. This problem is common to -all- rigid removable media drives. The bottom line is - once you have good reason to belive that a particular cartridge is bad, you should immediately stop using it. Once you have reason to believe that a particular drive is bad, you should stop using it. (Except, possibly, to try to read the bad cartridges and copy any retrievable data to a good drive/cartridge.) Once you have reason to belive that one of your drives is bad, you should stop using your live data or archival cartridges in any suspect drive; and take vigorous measures to determine which drive is the culpret. All of which gets pretty expensive for those of us working on a personal or small corporate budget... (Which is why I am so happy with my trouble-free Jaz drives.) > I hate to think about the things on which I could have spent my money if > I hadn't bought the drive (and controller)... Just what I thought about my SyQuest 270s. -Pat From owner-freebsd-scsi Sat Jan 31 13:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10237 for freebsd-scsi-outgoing; Sat, 31 Jan 1998 13:32:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from damon.com (rZvr/vs/bfpgTVpR0TRhPaLQbZwGGkO3@damon.com [207.170.114.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10211 for ; Sat, 31 Jan 1998 13:32:36 -0800 (PST) (envelope-from dap@damon.com) Received: (from dap@localhost) by damon.com (8.8.7/8.8.7) id PAA29241; Sat, 31 Jan 1998 15:30:43 -0600 (CST) (envelope-from dap) From: Damon Permezel Message-Id: <199801312130.PAA29241@damon.com> Subject: Re: Jazzm In-Reply-To: from "patl@phoenix.volant.org" at "Jan 31, 98 11:39:01 am" To: patl@phoenix.volant.org Date: Sat, 31 Jan 1998 15:30:43 -0600 (CST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-scsi" "patl@phoenix.volant.org sez: " > > >>>>> "Damon" == Damon Permezel writes: > > > > Damon> Is anyone else having reliability problems with Jazz? I had to > > Damon> sent the first 3 back before I got one which would not eat the > > Damon> disk and refuse to eject it. > > > > Damon> Each time you send the drive back, including the disc, you lose > > Damon> the disc, donating its contents to whoever gets to liberate it. > > Since you've powered off with the disk still inside, you can liberate > the cartridge yourself. Simply straighten out a paper clip and stick > the end into the tiny hole that is about 3mm beneath the cartridge slot. > On the internal drives, it is just to the left of the LED. On the > external drives, it is about 2.5cm from the left edge of the slot. > (The hole is in the same place, the LED moved.) You will feel some > resistance. Push gently until the cartridge pops out. NEVER DO THIS > WITH THE POWER ON !!! One might wonder why tech support received 3 of these back from me without getting me to try this procedure... I tried this to no avail prior to calling for my RMA. The tech on the other end (and this was IOmega, not the distributor) made me go thru the same steps. The disc was recalcitrant, and ossified, and shipped back with the unit.