Greetings again, fellow sys admins-
I thought I had the problem solved, but the tape was simply
pretending to function properly [sic]. After a few days of
avoiding bothering you again, I'm desperate to remove one
variable from my troubleshooting:
...the ddr.dbase entry.
Does anyone out there successfully run an ARCHIVE Python (ie., Seagate, I
gather) DDS-3 tape drive on narrow scsi, under Tru64 4.0D/F? If so, a
working ddr.dbase entry would be MUCH appreciated. I seem to have made
things worse by adopting a ddr.dbase entry straight from DEC/COMPAQ
(namely, a clone of the TLZ10 entry in the default ddr.dbase).
[I'm no longer even sure what the BPI rating of this drive should be...
I'd gotten used to 61000_bpi for DDS-2 (4GB native on 120m of tape), but
I'm beginning to think that this might actually be for DDS-1, and that our
hand-me-down DDS-3 drive is reporting DDS-2 density at 97000_bpi (see
below) instead of DDS-3. Technical papers on DDS-3 indicate that the
linear track density is 122kbpi... e.g.,
http://www.dds-tape.com/ddswh.html]
Here's the entry I'm currently using:
SCSIDEVICE
#
# Clone of TLZ10, for new Python DDS3
#
Type = tape
Name = "ARCHIVE" "Python" "7270"
#
PARAMETERS:
TypeSubClass = rdat, loader
TagQueueDepth = 0
MaxTransferSize = 0x0ffffff # (16MB - 1)
ReadyTimeSeconds = 90 # seconds
DENSITY:
#
DensityNumber = 0,3,4,5,6,7
DensityCode = default
CompressionCode = 0x0
Buffered = 0x1
DENSITY:
#
DensityNumber = 1,2
DensityCode = default
CompressionCode = 0x1
Buffered = 0x1
As things sit right now, an 'mt stat' returns:
DEVIOGET ELEMENT CONTENTS
---------------- --------
category DEV_TAPE
bus DEV_SCSI
interface SCSI
device Python 0
adpt_num 0
nexus_num 0
bus_num 0
ctlr_num 0
slave_num 3
dev_name tz
unit_num 3
soft_count 0
hard_count 3
stat 0x1
DEV_BOM
category_stat 0x400
DEV_LOADER DEV_97000_BPI
DEVGETINFO ELEMENT CONTENTS
------------------ --------
media_status 0x10001
BOM POS_VALID
unit_status 0x189
Ready Loader 2_FM_Close NO_Rewind Compacting
Buffered
record_size 0
density (current) 97000 BPI
density (on write) 0 BPI
Filemark Cnt 0
Record Cnt 0
Class 0 - <unspecified>
MTIOCGET ELEMENT CONTENTS
---------------- --------
mt_type MT_ISSCSI
mt_dsreg 0x1
DEV_BOM
mt_erreg 0x0 No error or no sense info.
mt_resid 0
mt_fileno 0
mt_blkno 0
DEV_EEI_STATUS
version 0x2
status 0x0 No EEI status available
flags 0x1000000
CAM_DATA
cam_status 0x0 No CAM status available
scsi_status 0x0 SCSI_STAT_GOOD
scsi_sense_data not valid
VERY confusingly, while it seems clear that the drive is having trouble
sensing the media (a standard 125m DDS-3 tape), the unit number is coming
up as "3" (?! - Before booting, >>>show dev reports SCSI target 5, as does
the switch on the drive housing, and the device /dev/nrmt0h - the default
we're using - is built accordingly;
# ls -lart /dev/nrmt0h
crw-r--r-- 1 root system 9,5123 Oct 4 03:41 /dev/nrmt0h
Of course, the write BPI is zero while the drive is seeems ready to read
at 97000...
...in short - help.
Thanks again in advance.
Chris
======================================================================
Christopher C Stevenson C3004 office: (709) 737-2624
Dept. of Physics & Physical Oceanography fax: (709) 737-8739
Memorial University of Newfoundland
St. John's, Newfoundland, CANADA A1B 3X7
URL:
http://www.physics.mun.ca/~csteven
======================================================================
"A scientific truth does not triumph by convincing
its opponents and making them see the light, but
rather because its opponents eventually die and a
new generation grows up that is familiar with it."
-- Max Planck
"We are all in the gutter, but some of us are looking at the stars."
-- Oscar Wilde
Received on Wed Oct 04 2000 - 13:44:50 NZDT