From owner-freebsd-current Wed Sep 11 07:27:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA05835 for current-outgoing; Wed, 11 Sep 1996 07:27:47 -0700 (PDT) Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA05828 for ; Wed, 11 Sep 1996 07:27:44 -0700 (PDT) Received: from sparcmill.grauel.com (sparcmill.grauel.com [199.233.104.34]) by watson.grauel.com (8.7.5/8.7.3) with SMTP id JAA14905; Wed, 11 Sep 1996 09:37:00 -0500 (EST) Received: by sparcmill.grauel.com (SMI-8.6/SMI-SVR4) id JAA20003; Wed, 11 Sep 1996 09:28:30 -0500 Date: Wed, 11 Sep 1996 09:28:30 -0500 Message-Id: <199609111428.JAA20003@sparcmill.grauel.com> From: Richard J Kuhns To: John Fieber CC: freebsd-current@freebsd.org Subject: Re: SCSI tape drive problem in -current In-Reply-To: References: <199609101441.JAA02613@sparcmill.grauel.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John Fieber writes: > On Tue, 10 Sep 1996, Richard J Kuhns wrote: > > > (bt0:6:0): "ARCHIVE VIPER 2525 25462 -007" type 1 removable SCSI 1 > > st0(bt0:6:0): Sequential-Access density code 0x0, drive empty > > Just as I suspected. See if the patch below to > src/sys/scsi/scsiconf.c makes your drive happy. > > -john > > == jfieber@indiana.edu =========================================== > == http://fallout.campusview.indiana.edu/~jfieber ================ > > Index: scsiconf.c > =================================================================== > RCS file: /home/ncvs/src/sys/scsi/scsiconf.c,v > retrieving revision 1.63 > diff -c -r1.63 scsiconf.c > *** scsiconf.c 1996/09/08 10:44:16 1.63 > --- scsiconf.c 1996/09/10 14:52:29 > *************** > *** 284,290 **** > "st", SC_ONE_LU, ST_Q_SNS_HLP|ST_Q_NO_1024, mode_tandberg4200 > }, > { > ! T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "VIPER 2525*", "-005", > "st", SC_ONE_LU, 0, mode_archive2525 > }, > { > --- 284,290 ---- > "st", SC_ONE_LU, ST_Q_SNS_HLP|ST_Q_NO_1024, mode_tandberg4200 > }, > { > ! T_SEQUENTIAL, T_SEQUENTIAL, T_REMOV, "ARCHIVE", "VIPER 2525 *", "*", > "st", SC_ONE_LU, 0, mode_archive2525 > }, > { > > I applied this patch, rebuilt the kernel, and rebooted (I'd left the tape in the drive). The probe info was (bt0:6:0): "ARCHIVE VIPER 2525 25462 -007" type 1 removable SCSI 1d st0(bt0:6:0): Sequential-Access density code 0x0, 1024-byte blocks, write-enabled `mt status' said Present Mode: Density = QIC-320 Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = QIC-320 Blocksize variable Mode 2: Density = QIC-150 Blocksize variable Mode 3: Density = QIC-120 Blocksize variable which is a major change. At this point, the tape was still unreadable. A couple of people had suggested setting the blocksize explicitly, so I tried "mt blocksize 1024" -- I could then read the tape without any problems. So, even with the patch above, the default blocksize apparently isn't being set to what the probe indicates. I'll hang on to these old backups for a while longer, in case anyone wants me to try anything else. Thanks, everyone. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (317)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 /