From owner-freebsd-isp Fri Jan 23 08:37:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16801 for freebsd-isp-outgoing; Fri, 23 Jan 1998 08:37:16 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16796 for ; Fri, 23 Jan 1998 08:37:14 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id KAA19671; Fri, 23 Jan 1998 10:36:44 -0600 (CST) From: Kevin Day Message-Id: <199801231636.KAA19671@home.dragondata.com> Subject: Re: SCSI backup tape drive recommendations (again) In-Reply-To: <7440.885543435@localhost> from Dave Truesdell at "Jan 23, 98 00:17:15 am" To: davet@geoplex.com Date: Fri, 23 Jan 1998 10:36:44 -0600 (CST) Cc: grog@lemis.com, lamaster@george.arc.nasa.gov, freebsd-isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > >> Check out http://www.corpsys.com/cgi-bin/select?1130679869093&inventory&T > >> for one supplier ($379 for a 4-tape changer). If you buy one and have > >> trouble, let me know: I have one and have had none, but some people have > >> had problems with refurbs which suggest a defective unit. > >> > >> Greg > >> > > > >I've got several of those drives, and they work great. They need a *ton* of > >airflow though, so if you mount them internally, put a fan behind them. > > > >I submitted a PR a while back showing how to use the scsi command to > >autoload with them. (ch0 doesn't work on this drive) > > I've had one of these drives controlled with ch0 for over a year and a half. > Did you forget to hack scsiconf.c so the other LUNs get probed? > Tried that.... It worked, but after 4-5 changes, the drive would either display 'ERROR 43' or say 'LOAD 0' and try to load a tape above where it could reach, and lock up.... It was sending goofy commands to it I think... Kevin