From owner-freebsd-scsi Mon Apr 22 05:23:10 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA01594 for freebsd-scsi-outgoing; Mon, 22 Apr 1996 05:23:10 -0700 (PDT) Received: from uuneo.neosoft.com (root@uuneo.neosoft.com [206.109.1.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA01589 for ; Mon, 22 Apr 1996 05:23:08 -0700 (PDT) Received: (from taronga@localhost) by uuneo.neosoft.com (8.7.5/8.7.4) with UUCP id GAA18513 for scsi@freebsd.org; Mon, 22 Apr 1996 06:32:01 -0500 (CDT) Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id GAA14220; Mon, 22 Apr 1996 06:24:17 -0500 Date: Mon, 22 Apr 1996 06:24:17 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199604221124.GAA14220@bonkers.taronga.com> To: scsi@freebsd.org Subject: Problems with Archive Anaconda... References: <199604220259.WAA01811@phantasma.bevc.blacksburg.va.us> Organization: I can usually find things six months later without looking for them. That's organized enough for me. Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > hmmm this is a semantic change that was introduced recently... > prior to this, a 'mount session' lasted until you explicitly > ended it by unloading the tape (or using the rst device instead of the nrst > device.) Recently it was decided that if the device was closed, then the] > user should have the option of ending the session by pressing the 'eject' > button. This would have the effect of causing a mount session reset at > the next open. In effect it would be the same as retrospectively > changing the last close to a close and unmount. Ah! I was wondering why I couldn't eject a tape that wasn't open on my new Archive Anaconda. That explains it. Thanks for changing the semantics there, even if I'll have to upgrade to take advantage of it... Anyway, I've got some problems withthis drive, and I've been respectfully informed that FreeBSD-SCSI is the place to bring them up. First of all, I have to do the following sequence (thanks for the help figuring it out!) to load a new tape: Insert the tape. Eject the tape. Insert the tape. Drive spins. Run "mt -f /dev/rst0 fsf 1". Drive spins. Error message. Eject the tape. Insert the tape. FreeBSD 2.0.5, Adaptec 1540B, Archive Anaconda: (aha0:5:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2 st0(aha0:5:0): Sequential-Access density code 0x0, drive empty If I skip the various steps I get the following results: First insert and eject: st0(aha0:5:0): NOT READY asc:4,1 st0(aha0:5:0): Logical unit is in process of becoming ready Doesn't matter how long I wait. Don't mt -f /dev/rst0 fsf 1: st0(aha0:5:0): MEDIUM ERROR info:2b4 asc:c,0 Write error st0(aha0:5:0): MEDIUM ERROR asc:c,0 Write error Doesn't matter how often I try, it does this. Don't eject after this: This seems to lock the device. I can't open the device, it says it's busy, but nothing has it open. It's like the SCSI or tape driver is wedged somewhere. Sometimes one of my attempts to open the device after this *will* hang uninterruptably. Also, it recognised DC600 tapes (I put the tape in, do an mt status, and it says it's a QIC-120) but can't read or write them. Possibly I've just got a flakey drive. I'm going to buy an external SCSI enclosure so I can try it on my Bt747, but that can't be until the next paycheck (it's not a total waste of money: I need the enclosure for other stuff), but if the drive's flakey I'd rather not. Input?