- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: file on tape device file
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 02:12 AM
тАО06-09-2004 02:12 AM
file on tape device file
#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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 03:13 AM
тАО06-09-2004 03:13 AM
Re: file on tape device file
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 03:24 AM
тАО06-09-2004 03:24 AM
Re: file on tape device file
replace it
Mohamed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 03:26 AM
тАО06-09-2004 03:26 AM
Re: file on tape device file
have a look in binary errlog.
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 08:30 AM
тАО06-09-2004 08:30 AM
Re: file on tape device file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2004 09:11 PM
тАО06-09-2004 09:11 PM
Re: file on tape device file
#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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2004 12:26 AM
тАО06-10-2004 12:26 AM
Re: file on tape device file
If you enter the mt status command and no tape is in the drive, the hardware counter should be increased.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2004 01:09 AM
тАО06-10-2004 01:09 AM
Re: file on tape device file
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2004 07:17 PM
тАО06-10-2004 07:17 PM
Re: file on tape device file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2004 08:08 PM
тАО06-20-2004 08:08 PM