file on tape device file

[Dan Boxall]

Could someone clairfy the output of the following command:

#file /dev/nrmt3h
/dev/nrmt3h: character special (9/68611) SCSI #4 TZ89 tape #26 (SCSI ID #3) (SCSI LUN #0) errors = 0/1 offline

In particular I would like to know what the errors = 0/1 relates to. Does this indicate h/ware problems with tape drive?

TIA

[Abdul Rahiman]

I think errors = 0/1 can be interpreted as
errors = soft_error/hard_error

Run # mt -f /dev/nrmt3h status
to verify the soft_count and hard_count values.

This probably would indicate that your tape drive has some physical errors.

[Mohamed K Ahmed]

looks like you are having some errors with the tape drive itself
replace it

Mohamed

[Michael Schulte zur Sur]

Hi,

have a look in binary errlog.

Michael

[Ralf Puchner]

please have a look into the binary.errlog. What does "mt status" tell us?

[Dan Boxall]

After running:
#mt -f /dev/nrmt3h status
I can see the connection with errors = 0/1 with 1 relating to hard count.

If I run the following:
#scu -f /dev/nrmt3h
scu> reset device

and then repeat #mt -f /dev/nrmt3h the output is as follows:

/dev/nrmt3h: character special (9/68611) SCSI #4 TZ89 tape #26 (SCSI ID #3) (SCSI LUN #0) errors = 0/2 85700_bpi

From that I can see the hard count has incremented by 1. Is this normal/to be expected?
Querying the binary.errlog I have the following entry:

----- EVENT INFORMATION -----
EVENT CLASS
ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 2155.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Jun 10 09:58:59 2004
OCCURRED ON SYSTEM d1ts
SYSTEM ID x00000000
SYSTYPE x0000000A
PROCESSOR COUNT 4.
PROCESSOR WHO LOGGED x0000000A
----- UNIT INFORMATION -----
CLASS x0001 TAPE
SUBSYSTEM x0000 DISK
BUS # x0004
x0118 LUN x0
TARGET x3

This tape device sits in a TL896 Library and all the devices attached to the system do the same as above. Now would this point to a problem with the HBA, commuication channel??? Any pointers/assistance is greatly appreciated!

[Ralf Puchner]

you interpreted the output but you should post it! Please do not post any conclusion, post the simple output of the commands!!!

If you enter the mt status command and no tape is in the drive, the hardware counter should be increased.

[Dan Boxall]

Apologies, I did try to interpret the output, but it was not a conclusion, as I am bemused as to why or what the error is.
The output of mt status without a tape is as follows:

DEVIOGET ELEMENT CONTENTS
---------------- --------
category DEV_TAPE
bus DEV_SCSI
interface SCSI
device TZ89
adpt_num 0
nexus_num 0
bus_num 4
ctlr_num 4
slave_num 26
dev_name tz
unit_num 26
soft_count 0
hard_count 2
stat 0x5
DEV_BOM DEV_OFFLINE
category_stat 0x0
DEV_85700_BPI

DEVGETINFO ELEMENT CONTENTS
------------------ --------
media_status 0x10001
BOM POS_VALID
unit_status 0x182
Offline 2_FM_Close NO_Rewind Compacting Buffered
record_size 0
density (current) 85700 BPI
density (on write) 0 BPI
Filemark Cnt 0
Record Cnt 0
Class 1 - DLT (tk)

MTIOCGET ELEMENT CONTENTS
---------------- --------
mt_type MT_ISSCSI
mt_dsreg 0x5
DEV_BOM DEV_OFFLINE
mt_erreg 0x2 Unit is not ready.
mt_resid 0
mt_fileno 0
mt_blkno 0
DEV_EEI_STATUS
version 0x2
status 0x3200 Device inoperable (needs initialize)
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 2 0 0 0 0 16
0 0 0 0 3a 0 0 0
0 0 82 5 55 0 0 9b
9b 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
ASC/ASQ = 3a/0 Medium not present

[Ralf Puchner]

now check if "error" counter increased if executing "mt status" without a tape within the drive.

[Dan Boxall]

The error counter has not increased after mt status without tape in drive.