From owner-freebsd-doc Sun Sep 28 14:33:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA24117 for doc-outgoing; Sun, 28 Sep 1997 14:33:17 -0700 (PDT) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA24099 for ; Sun, 28 Sep 1997 14:33:08 -0700 (PDT) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id QAA16597 for freebsd-doc@freebsd.org; Sun, 28 Sep 1997 16:33:12 -0500 (CDT) From: Kevin Day Message-Id: <199709282133.QAA16597@home.dragondata.com> Subject: Archive 96G autoloader To: freebsd-doc@freebsd.org Date: Sun, 28 Sep 1997 16:33:11 -0500 (CDT) 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-doc@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've had good luck in getting Archive/Conner's 4584NP DAT autoloader drive to work in FreeBSD. Here's how it appears on boot: "ARCHIVE Python 28849-XXX 4.CM" type 1 removable SCSI 2 Sequential-Access density code 0x13, drive empty There also is a LUN 1 device showing up under the same ID: "ARCHIVE Python 28849-XXX 4.CM" type 8 removable SCSI uk0(ahc0:1:1): Unknown If you load the 'ch0' driver for bsd, it will recognize the LUN 1 device as an autoloader, but it's not necessary to use the drive. Ignore the uk0 device. The actual tape drive in the unit is at ID 1. Each tape slot has an ID from 0x2 - 0x5 or 0x2 - 0xd depending on if you are using the 4 tape or the 12 tape magazine. To move a tape, you use this command: scsi -f /dev/rst0.ctl -s 50 -c "a5 20 0 0 0 0 0 0 0 0" If you wanted to take the #4 tape (ID 5), and put in the drive (ID 1) you would issue the command: scsi -f /dev/rst0.ctl -s 50 -c "a5 20 0 0 0 5 0 1 0 0 0 0" Then to remove it from the drive, and put it in slot 2(ID 3): scsi -f /dev/rst0.ctl -s 50 -c "a5 20 0 0 0 1 0 3 0 0 0 0" Make sense? It will get about 8GB compressed on a 120M dat, with some of the highest speeds I've seen in quite a while. Kevin Day toasty@dragondata.com