From owner-freebsd-hardware Mon Jun 17 18:17:36 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA14169 for hardware-outgoing; Mon, 17 Jun 1996 18:17:36 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA14164 for ; Mon, 17 Jun 1996 18:17:34 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id SAA00342 for hardware@freebsd.org; Mon, 17 Jun 1996 18:17:32 -0700 Date: Mon, 17 Jun 1996 18:17:32 -0700 From: Sean Eric Fagan Message-Id: <199606180117.SAA00342@kithrup.com> To: hardware@freebsd.org Subject: Re: Tape drive questions/recommendations Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk And the winner is: aha0 targ 5 lun 0: type 1(sequential) removable SCSI2 aha0 targ 5 lun 0: st0: density code 0x13, drive empty Internal unit; it's got a 4 tape cartridge for the autoloader (and the manual says I can get a 12 tape cartridge, if I feel a need ;)). Although it says it's an Archive Python, the documentation that came with it says it's a Connor. I spent a total of about two hours getting it set up; the first problem was getting the damned SCSI cable facing the right way. The second problem was that I had to remove the terminators from the tape drive -- with them in, all the SCSI busses said "Hi! Here's what I am:" but doing any I/O to anything other than the tape drive didn't work, and caused a controller timeout (funky that the new device worked ;)). Anyway, I fixed that, and then tested it by doing a level 0 backup; that seemed to work (although I haven't read the tape back yet to verify it). The doc didn't say whether it was DDS or DDS-2; it does have automagic LZW compression, but I don't think that that alone makes it DDS-2, no? One problem, that I also had with the previous tape drive: if it boots with a tape mounted, it says that the "density code" is 0x0; with the last one, that then meant that I would get an error when I wrote a tape. (This may be a problem with the 1.1++ SCSI driver, admittedly.) Sean.