From owner-freebsd-scsi Fri Apr 21 13:31:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from PLUTO.forumone.com (host04.forumone.com [207.197.235.4]) by hub.freebsd.org (Postfix) with ESMTP id CFC2137BA36 for ; Fri, 21 Apr 2000 13:31:48 -0700 (PDT) (envelope-from adhir@forumone.com) Received: by PLUTO.forumone.com with Internet Mail Service (5.5.2650.21) id <2GYQAT1G>; Fri, 21 Apr 2000 16:31:47 -0400 Message-ID: From: Alok Dhir To: "'scsi@freebsd.org'" Subject: FW: Ontream ADR50 Date: Fri, 21 Apr 2000 16:31:41 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm forwarding this to the scsi@ list since I just discovered it and it seems more appropriate... I do not subscribe to the scsi@ list, so please reply directly and I will post a summary. -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Alok K. Dhir Sent: Friday, April 21, 2000 3:13 PM To: stable@freebsd.org Subject: Ontream ADR50 Hey all - I'm trying to get an Onstream ADR50 drive working with FreeBSD-stable. I bought the drive because Onstream's site claims that this drive works under FreeBSD (basically, it should act like a 'normal' SCSI tape drive unlike their older line of SCxx drives which don't). Unfortunately, this one isn't working either. I'm hoping the problem is something I'm doing wrong. Anytime I try to do any operation with the drive, I get an "Invalid Argument" error from mt. I.e.: [root@dipper:~] mt rew mt: /dev/nrsa0: Invalid argument The only thing I can do is: [root@dipper:~] mt -f /dev/rsa0.ctl status Mode Density Blocksize bpi Compression Current: default 32768 bytes 0 disabled ---------available modes--------- 0: default 32768 bytes 0 0x3 1: default 32768 bytes 0 0x3 2: default 32768 bytes 0 0x3 3: default 32768 bytes 0 0x3 --------------------------------- Current Driver State: at rest. Anything else with the drive, including dump, tar, etc, ends with an error. In dump's case, its something like 'could not open output'. I'm guessing the problem has something to do with our sa driver. Can anyone suggest a workaround other than returning the drive? Thanks Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message