From owner-freebsd-questions@FreeBSD.ORG Fri Jul 8 16:01:12 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A51C4106566C for ; Fri, 8 Jul 2011 16:01:12 +0000 (UTC) (envelope-from sdb@ssr.com) Received: from mailhost.ssr.com (mailhost.ssr.com [199.4.235.5]) by mx1.freebsd.org (Postfix) with SMTP id 21A848FC12 for ; Fri, 8 Jul 2011 16:01:11 +0000 (UTC) Received: (qmail 47423 invoked from network); 8 Jul 2011 15:30:56 -0000 Received: from pool-71-167-224-193.nycmny.east.verizon.net (HELO irelay.ssr.com) (sdb@71.167.224.193) by 199.4.235.5 with SMTP; 8 Jul 2011 15:30:56 -0000 Received: (qmail 74808 invoked by uid 103); 8 Jul 2011 15:21:35 -0000 Date: 8 Jul 2011 15:21:35 -0000 Message-ID: <20110708152135.74807.qmail@irelay.ssr.com> From: Scott Ballantyne To: freebsd-questions@freebsd.org Subject: EXABYTE 8200 on FreeBSD 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2011 16:01:12 -0000 I know this is ancient technology, but we have a pile of exabyte tapes made on an 8200 and would like to recover some of the data on them. We have an old 5.3 machine which has an adaptec 2120S, and the Exabyte is connected to that. The kernel identifies the Exabyte on boot, but it's all downhill after that. The driver sometimes spits out a pile of errors (I'll append a sample at the end) and mt doesn't seem to do simple commands (like a retension). I note that the MT page for 5.3 says that not all SCSI-1 devices are supported. So before I invest more time in this, I am wondering if anyone can tell if the support is there for this configuration? If not, what (inexpensive) options do I have for possibly retrieving this data? Thanks a lot, Scott -- sdb@ssr.com An "mt status" causes the driver to report: (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information (sa0:aacp0:0:4:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:aacp0:0:4:0): ILLEGAL REQUEST asc:0,0 (sa0:aacp0:0:4:0): No additional sense information While mt reports: Mode Density Blocksize bpi Compression Current: default variable 0 unsupported ---------available modes--------- 0: default variable 0 unsupported 1: default variable 0 unsupported 2: default variable 0 unsupported 3: default variable 0 unsupported --------------------------------- Current Driver State: at rest. --------------------------------- File Number: 0 Record Number: 0 Residual Count 0