syslog error mesgs about tape drive

[Ali Imran Abbas]

I have the following error mesg on syslog of my production unix server.

Feb 13 02:31:30 usunx07 EMS [6513]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/tapes/SCSI_tape/2_0_1_1_0_4_0.98.36.255.1.3.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 426835997 -r /storage/events/tapes/SCSI_tape/2_0_1_1_0_4_0.98.36.255.1.3.0 -n 426835971 -a

can any one help me to troubleshoot and diagnse the problem?

[Marco A. · Accepted solution]

Hello,

Excecute the command that the erros ask you to run to get additional information about it, additionally it's very important to know the EMS error number, try it and let us know the details.

In addition, have tried something new in the server, related with the storage environment.
What equipment it is connected there?

Regards,

Marco

[OldSchool]

well first, as the message says:

Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 426835997 -r /storage/events/tapes/SCSI_tape/2_0_1_1_0_4_0.98.36.255.1.3.0 -n 426835971 -a

also take a look at the output of:

ioscan -nfC tape
/opt/resmon/bin/set_fixed -L

[Ali Imran Abbas]

here is the output of running the diagnostic command as indicated by the error mesg:

usunx07:# apes/SCSI_tape/2_0_1_1_0_4_0.98.36.255.1.3.0 -n 426835971 -a <

CURRENT MONITOR DATA:

Event Time..........: Wed Feb 13 02:31:29 2008
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 101137
System..............: usunx07

Summary:
Tape at hardware path 2/0/1/1/0/4/0.98.36.255.1.3.0 : Media failure


Description of Error:

The device was unsuccessful in reading or writing data for the current I/O
request due to an error on the medium. The data could not be recovered.

For further isolation of the problem, it may be possible that the
combination of values of Sense Code, Sense Qualifier and Sense Key may be
vendor specific. In that case, please contact the manufacturer of the
device. It may also be possible that the combination of SCSI Sense
Code/Qual/Key was not intended to be used by this type of device.

Probable Cause / Recommended Action:

Reformatting the medium may fix the problem.

Alternatively, the medium in the device is flawed. If the medium is
removable, replace the medium with a fresh one.

Alternatively, if the medium is not removable, the device has experienced
a hardware failure. Contact your HP support representative to have the
device checked.

Additional Event Data:
System IP Address...: 10.101.202.107
Event Id............: 0x47b29cd100000000
Monitor Version.....: B.01.05
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_stape.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x47b29cd100000000
Additional System Data:
System Model Number.............: 9000/800/rp8420
OS Version......................: B.11.11
System Firmware Version.........: 22.2
System Serial Number............: USE4415CFH
System Software ID..............: 857850114
EMS Version.....................: A.04.00
STM Version.....................: A.47.00
System Current Product Number...: A6912A
System Original Product Number..: A6912A
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#101137

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 2/0/1/1/0/4/0.98.36.255.1.3.0
Inquiry Vendor ID.......: IBM
Inquiry Product ID......: ULTRIUM-TD2
Firmware Version........: 5AT0
Serial Number...........: 9110078489

Product/Device Data:

Logger ID.........: stape
Product Identifier: SCSI Tape
Product Qualifier.: IBMULTRIUM-TD2
SCSI Target ID....: 0x03
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x00000005
Length of Logged Hardware Status....: 40 bytes.
Offset to Logged Manager Information: 40 bytes.
Length of Logged Manager Information: 30 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 02 70 00 03 00 00 00 00 1C 00 00 00 00
0x0010: 53 00 36 00 2E 12 00 00 00 02 20 20 20 20 20 20
0x0020: 20 00 00 00 2F C0 00 06

SCSI Status...: CHECK CONDITION (0x02)
Indicates that a contingent allegiance condition has occurred. Any
error, exception, or abnormal condition that causes sense data to be
set will produce the CHECK CONDITION status.

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 03 00 00 00 00 1C 00 00 00 00 53 00 36 00
0x0010: 2E 12 00 00 00 02 20 20 20 20 20 20 20 00 00 00
0x0020: 2F C0 00 06

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x03
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 28
Command Specific : 0x00000000
Additional Sense Code : 0x53
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x36
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x2E 0x12

Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
with a nonrecovered error condition that was probably caused by a
flaw in the medium or an error in the recorded data. This sense key
may also be returned if the device is unable to distinguish between a
flaw in the medium and a specific hardware failure (sense key 0x04).

The combination of Additional Sense Code and Sense Qualifier (0x5300)
indicates: Media load or eject failed.

SCSI Command Data Block: (not present in log record)

Manager-Specific Information:

Raw Manager Data:
0x0000: 2F 34 7F 1F 00 00 00 00 00 00 00 02 00 00 00 00
0x0010: 2F 03 00 24 FE 00 00 06 00 00 00 00 00 00

ioscan still can scan the tape drive

[Marco A.]

Hello Ali,


I think that the error information, recommended action , etc, its very clear.

The media itseft is failing and you need to replace it, if it's a new media, call to the vendor and ask how to get a new one.

Regards,


Marco

[Torsten.]

First try a new tape.


BTW, is this a rp8420?
Your diagnostic version is pretty old and unsupported (Dec 2004) - consider to update the diagnostics!

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

[Marco A.]

Torsten ...that's a good one, I forgot the EMS, thanks!!! ..

Marco

[Bill Hassell]

This is a "normal" error for a bad tape of a dirty tape drive. Try another tape and if the error persists, use the cleaning tape.

Note that the diagnostics MUST be updated yearly because they are critically tied to new hardware and firmware changes. The current version is A.59.05