This one has me pulling out my hair, so before I go bald:
I just upgraded my Alpha1000a to Digital Unix 4.0d with Jumbo Patch
#0002. I can no longer read or write from my TKZ62CL tape drive (this
reads IBM 3480 and 3490 tape cartridges).
The actual error entered in /var/adm/messages when I attempt a tar or dd
action is:
Oct 4 21:42:02 tim vmunix: [2/3/0] ctape_ioctl: unmapped scsi density
code (0x93) - DDR entry needed
Oct 6 13:53:54 tim vmunix: [2/3/0] ctape_ioctl: unmapped scsi density
code (0x90) - DDR entry needed
Oct 9 13:42:36 tim vmunix: [2/3/0] ctape_ioctl: unmapped scsi density
code (0x92) - DDR entry needed
I CAN do a file on the tape device:
/dev/rmt2h: character special (9/35842) SCSI #2 TKZ62CL tape #3
(SCSI ID #3) (SCSI LUN #0) loader 6666_bpi
I can also do mt -f /dev/rmt2h status and get the following:
DEVIOGET ELEMENT CONTENTS
---------------- --------
category DEV_TAPE
bus DEV_SCSI
interface SCSI
device TKZ62CL
adpt_num 0
nexus_num 0
bus_num 2
ctlr_num 2
slave_num 3
dev_name tz
unit_num 3
soft_count 0
hard_count 0
stat 0x1
DEV_BOM
category_stat 0x480
DEV_LOADER DEV_6666BPI
DEVGETINFO ELEMENT CONTENTS
------------------ --------
media_status 0x10001
BOM POS_VALID
unit_status 0x1a9
Ready Loader 2_FM_Close Rewind Compacting
Buffered
record_size 0
density (current) 6666 BPI
density (on write) 37871 BPI
Filemark Cnt 0
Record Cnt 0
Class 0 - <unspecified>
MTIOCGET ELEMENT CONTENTS
---------------- --------
mt_type MT_ISSCSI
mt_dsreg 0x1
DEV_BOM
mt_erreg 0x6 Target reset or medium changed.
mt_resid 0
mt_fileno 0
mt_blkno 0
DEV_EEI_STATUS
version 0x2
status 0x6400 Device/bus reset occured
flags 0x1000007
CAM_STATUS SCSI_STATUS SCSI_SENSE CAM_DATA
cam_status 0x4 CCB request completed with an err
scsi_status 0x2 SCSI_STAT_CHECK_CONDITION
scsi_sense_data (hex)
70 0 6 0 0 0 0 c
0 0 0 0 29 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0
ASC/ASQ = 29/0 Power on, reset, bus device reset occurred
******************************************
So, my tape drive is online, but apparently there are some wrong entries
in ddr.dbase. At least that is my guess. The density entries in
ddr.dbase are far different from the ones specified in my error
messages.
DEC Support has had me try the following:
- Add a CAM SCSI subset for "CLC" that is new than comes with 4.0d:
CLCMC313 installed SCSI CAM Medium Changer Driver V3.1C
CLCOP313 installed SCSI CAM Optical Disk Driver V3.1C
- Rebuild ddr_config with generic kernel and new kernels built.
Now DEC is checking to see if my tape drive has been "retired" from
Digital Unix 4.0d. I think that unlikely as these tape drives are not
that old, and IBM 3480 media is still used quite a bit. Besides, I have
a TKZ60 on the same machine that runs just fine - it's basically the
same drive. Unfortunately, it can only read 3480's not 3490's.
Any ideas from those of you out there who know ddr.dbase?
TIA
susrod_at_hbsi.com
Received on Sat Oct 10 1998 - 18:12:19 NZDT