Strange SCSI tape problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have an unusual problem with a SCSI tape drive. It is an old DAT 2
drive. It works with a RH 7.3 system, but with the same controller,
it does not work when used with FC-6 or F7. But the strange things
is that it will work with a USB to SCSI adapter. What happens is
that I get a tape I/O error from the drive when I put in a tape. I
suspect that when the drive is initialized when connected to the PCI
SCSI card, the drive is put in a mode where it will not detect the
proper block size of the tape.

Host: scsi2 Channel: 00 Id: 03 Lun: 00
  Vendor: ARCHIVE  Model: Python 25501-XXX Rev: 5.45
  Type:   Sequential-Access                ANSI  SCSI revision: 02

With USB SCSI:
Aug  7 14:42:07 asus kernel: st 2:0:3:0: Attached scsi tape st0
Aug  7 14:42:07 asus kernel: st 2:0:3:0: st0: try direct i/o: yes
(alignment 512 B)
Aug  7 14:42:07 asus kernel: st 2:0:3:0: Attached scsi generic sg2
type 1
Aug  7 14:42:07 asus kernel: osst :I: Tape driver with OnStream
support version 0.99.4
Aug  7 14:42:07 asus kernel: osst :I: $Id: osst.c,v 1.73 2005/01/01
21:13:34 wriede Exp $

With Adaptec AVA-29030 PCI SCSI controller:
Jul 27 01:21:51 toshiba kernel: osst :I: Tape driver with OnStream
support version 0.99.4
Jul 27 01:21:51 toshiba kernel: osst :I: $Id: osst.c,v 1.73
2005/01/01 21:13:34 wriede Exp $
Jul 27 01:21:51 toshiba kernel: st: Version 20070203, fixed bufsize
32768, s/g segs 256
Jul 27 01:21:51 toshiba kernel: st 2:0:5:0: Attached scsi tape st0
Jul 27 01:21:51 toshiba kernel: st 2:0:5:0: st0: try direct i/o: yes
(alignment 512 B)

Status message from mt when working:
# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (41010000):
 BOT ONLINE IM_REP_EN

I should have saved the status message from when I put is a new
tape, and did a status when I was attached to the PCI SCSI
controller card. But I didn't, and I do not have any more new tapes
right now. After I tried writing to a new tape, the drive would
error out when I would tray and access the tape again. (The same
tape still works when I use the USB controller.)

I tried a Google search, but I didn't turn up anything helpful. I
guess I am not searching for the right things...

I am hoping someone has run into this before. If not, the next thing
I will try is putting the SCSI controller/tape drive back in the F7
box, and feeding the tape drive the density code and block size and
see if that helps. But I am puzzled by the fact that it works when
hot-plugged using the USB SCSI controller, but not the PCI SCSI
controller. I would suspect SCSI problems, except that it works with
RH-7.3 (I was hoping to retire that system...)

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

Attachment: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux