- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: about tape!
Operating System - Tru64 Unix
1753882
Members
7226
Online
108809
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО11-12-2003 01:51 PM
тАО11-12-2003 01:51 PM
my customer said his tape drive is physically damaged
i checked the system log
including binary.errlog,messages and the files under syslog.dated directory
but i found nothing wrong about tape !
how can identify the tape error remotely!
system is alpha server 4100
os is tru64 4.0D
i checked the system log
including binary.errlog,messages and the files under syslog.dated directory
but i found nothing wrong about tape !
how can identify the tape error remotely!
system is alpha server 4100
os is tru64 4.0D
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2003 07:58 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2003 06:55 PM
тАО11-16-2003 06:55 PM
Re: about tape!
the following messges is the output of mt status command
which entry can prove the tape drive is physically wrong?
DEVIOGET ELEMENT CONTENTS
---------------- --------
category DEV_TAPE
bus DEV_SCSI
interface SCSI
device TLZ09
adpt_num 0
nexus_num 0
bus_num 1
ctlr_num 1
slave_num 43
dev_name tz
unit_num 43
soft_count 0
hard_count 0
stat 0x5
DEV_BOM DEV_OFFLINE
category_stat 0x20000
DEV_61000_BPI
DEVGETINFO ELEMENT CONTENTS
------------------ --------
media_status 0x10001
BOM POS_VALID
unit_status 0x1a2
Offline 2_FM_Close Rewind Compacting Buffered
record_size 0
density (current) 61000 BPI
density (on write) 0 BPI
Filemark Cnt 1
Record Cnt 0
Class 2 - RDAT
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 1
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 12
0 0 0 0 3a 0 0 0
0 0 0 0 0 0 8 3a
6b 40 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0
ASC/ASQ = 3a/0 Medium not present
which entry can prove the tape drive is physically wrong?
DEVIOGET ELEMENT CONTENTS
---------------- --------
category DEV_TAPE
bus DEV_SCSI
interface SCSI
device TLZ09
adpt_num 0
nexus_num 0
bus_num 1
ctlr_num 1
slave_num 43
dev_name tz
unit_num 43
soft_count 0
hard_count 0
stat 0x5
DEV_BOM DEV_OFFLINE
category_stat 0x20000
DEV_61000_BPI
DEVGETINFO ELEMENT CONTENTS
------------------ --------
media_status 0x10001
BOM POS_VALID
unit_status 0x1a2
Offline 2_FM_Close Rewind Compacting Buffered
record_size 0
density (current) 61000 BPI
density (on write) 0 BPI
Filemark Cnt 1
Record Cnt 0
Class 2 - RDAT
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 1
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 12
0 0 0 0 3a 0 0 0
0 0 0 0 0 0 8 3a
6b 40 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
тАО11-17-2003 12:00 AM
тАО11-17-2003 12:00 AM
Re: about tape!
with the mt status command you can check if the device is recognized and if the tape itself respond to queries.
In your case there is no magnetic tape in the slot.
If you want to know if there are physical problems use
# uerf -R -o full
and check for SCSI Tape entries.
In your case there is no magnetic tape in the slot.
If you want to know if there are physical problems use
# uerf -R -o full
and check for SCSI Tape entries.
Help() { FirstReadManual(urgently); Go_to_it;; }
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP