Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Tape Libraries and Drives
cancel
Showing results for 
Search instead for 
Did you mean: 

Event log error on the tape.

SOLVED
Go to solution
Darren Poh_1
Frequent Advisor

Event log error on the tape.

I had received a warning from the event log, I do not know what cause it. The backup went thru successfully that night. Can anyone please explain?

===========================================
/storage/events/tapes/SCSI_tape/0_3_0_0.5.0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Wed Oct 19 22:22:12 2005
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 102676
System..............: hpux01.slsbearing.com.sg

Summary:
Disk at hardware path 0/3/0/0.5.0 : Software configuration error


Description of Error:

A condition has occurred for which SCSI sense data is available. The
device driver has not requested the sense data.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.
=============================================
8 REPLIES
Mei Jiao
Respected Contributor

Re: Event log error on the tape.

Hi Darren,

Hope the following information helps:

Summary:
Disk at hardware path 8/16/5.2.0 : Software configuration error

As you know, the IPR 0109 version of Diagnostics will not report
failures for devices for which the firmware does NOT start with "hp".
This behavior unfortunately does NOT apply to a device when it''s Test
Unit Ready SCSI commands fail however. As a result, the TUR''s continue
to be sent to the device once per hour and continue to generate
events. This is NOT the result we were hoping to see with the
enhancements made to IPR0109 regarding the disk_em monitor.

From my research, the communication error seems could be resolved by new FW version. Have you checked if it's having the latest firmware version already?

BR,
Mei
Mei Jiao
Respected Contributor

Re: Event log error on the tape.

In addition to FW version, please kindly check the patch level as well.

BR,
Mei
Darren Poh_1
Frequent Advisor

Re: Event log error on the tape.

hi mei jiao,

the research is good, but this has only 1 occurance, could it be the media that is having the problem?
Mei Jiao
Respected Contributor

Re: Event log error on the tape.

Hi Darren,

If it's only 1 occurance, then please check what the user is doing at this time:
Wed Oct 19 22:22:12 2005

If the user was doing backup, or was manipulating the media. Then yes it could be a media issue. However you mentioned that the backup was successful?

Mind to check what was happening at that time Wed Oct 19 22:22:12 2005? And if it's running a DP backup, please send me the session report for me to have a look?
# omnidb -session -report
# omnidb -session -media

Thank you.

BR,
Mei
Darren Poh_1
Frequent Advisor

Re: Event log error on the tape.

great.. i will check on the logs and revert back shortly.
Darren Poh_1
Frequent Advisor

Re: Event log error on the tape.

hi mei jiao,

here is the logs,

[Normal] From: BMA@hpux01.slsbearing.com.sg "Drive1" Time: 10/19/05 22:20:17

Loading medium from slot 5 to device /dev/rmt/3m



[Normal] From: OB2BAR@hpux01.slsbearing.com.sg "b733" Time: 10/19/05 22:22:57

Starting OB2BAR Backup: 05 hpux01.slsbearing.com.sg:Wed_RMAN_TS_Bkp<572133656:1>.dbf // Oracle8



# omnidb -session 2005/10/19-3 -d md edia

Medium Label Medium ID Free Blocks

===============================================================================

Wk1-Wed-1 c0a80af6:3f704ea2:5d0a:0001 0

# omnidb -session 2005/10/1+ 9-4 -d media

No medium found.

# omnidb -session 2005/10/19- 20-1 -media

Medium Label Medium ID Free Blocks

===============================================================================

Wk1-Wed-1 c0a80af6:3f704ea2:5d0a:0001 0

What do u think?
Mei Jiao
Respected Contributor
Solution

Re: Event log error on the tape.

Hi Darren,

Since you see the time the event was logged is when doing loading medium from slot 5 to device /dev/rmt/3m, I could only think of that it may be due to the loading medium activity.

Besides you mentioned that it only occured once? So what do you think yourself? Have you made sure that the drive /dev/rmt/3m is working fine? And the medium labelled 'Wk1-Wed-1' is in good condition?

Plus, the media has 0 free block? Keep me wondering...

BR,
Mei
Andrew Merritt_2
Honored Contributor

Re: Event log error on the tape.

Hi Darren,
What version of the OnlineDiags do you have installed? My guess is that this message is caused by an old version of dm_stape, which polls the hardware and happened to do so at the moment the media was being changed.

If everything else is working, there really isn't anything to worry about. In fact, the tape monitor is no longer supplied or supported in the latest version of the OnlineDiags, so when you've moved to that you won't see any more such events being logged.

The Library and Tape Tools from HP are the recommended tools to use now.

Andrew