- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: locate scsi command failed, key = 0x3, asc = 0...
StoreEver Tape Storage
1752829
Members
3477
Online
108789
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
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-27-2004 08:04 PM
тАО11-27-2004 08:04 PM
locate scsi command failed, key = 0x3, asc = 0x14, ascq = 0x0
when backup,tape mounted,but when position,display warning messages:Warning bptm(pid=12030) cannot locate on drive index 2, locate scsi command failed, key = 0x3, asc = 0x14, ascq = 0x0
whether the tape drive have something wrong.harware failure or tape failure.
how to deal with it?
there is information from root mail:
# mail
From root@hr02 Sun Nov 28 16:02:00 EAT 2004
Received: (from root@localhost)
by hr02 (8.9.3/8.9.3) id QAA14719;
Sun, 28 Nov 2004 16:02:00 +0800 (EAT)
Date: Sun, 28 Nov 2004 16:02:00 +0800 (EAT)
Message-Id: <200411280802.QAA14719@hr02>
To: root@hr02
From: root@hr02
Subject: hr02: Event Monitor Notification
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Sun Nov 28 16:02:00 2004
hr02 sent Event Monitor notification information:
/storage/events/tapes/SCSI_tape/0_0_10_0_0.2.25.255.0.0.2
is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time..........: Sun Nov 28 16:02:00 2004
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 100243
System..............: hr02
Summary:
Tape at hardware path 0/0/10/0/0.2.25.255.0.0.2 : Media failure
Description of Error:
The device was unsuccessful in reading data for the current I/O request
because it could not find the requested recorded entity on the medium. The
request may have been processed in a way which could cause damage to or
loss of data.
For furthur 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...: 172.20.4.89
Event Id............: 0x41a985f800000000
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):
0x41a985f800000000
Additional System Data:
System Model Number.............: 9000/800/rp7410
OS Version......................: B.11.11
System Firmware Version.........: 16.11
System Serial Number............: SGH43241LS
System Software ID..............: 729066710
EMS Version.....................: A.03.20
STM Version.....................: A.35.00
System Current Product Number...: A6752A
System Original Product Number..: A6752A
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100243
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....: 0/0/10/0/0.2.25.255.0.0.2
Inquiry Vendor ID.......: HP
Inquiry Product ID......: Ultrium 1-SCSI
Firmware Version........: E38W
Serial Number...........: HU73A02465
Product/Device Data:
Logger ID.........: stape
Product Identifier: SCSI Tape
Product Qualifier.: HPUltrium
SCSI Target ID....: 0x00
SCSI LUN..........: 0x02
I/O Log Event Data:
Driver Status Code..................: 0x00000005
Length of Logged Hardware Status....: 26 bytes.
Offset to Logged Manager Information: 32 bytes.
Length of Logged Manager Information: 30 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 F0 00 03 00 00 00 00 0E 00 00 00 00
0x0010: 14 00 00 00 50 90 00 00 00 00
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: F0 00 03 00 00 00 00 0E 00 00 00 00 14 00 00 00
0x0010: 50 90 00 00 00 00
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 : TRUE
Information Field : 0x00000000
Additional Sense Length : 14
Command Specific : 0x00000000
Additional Sense Code : 0x14
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x50 0x90
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 (0x1400)
indicates: Recorded entity not found.
SCSI Command Data Block: (not present in log record)
Manager-Specific Information:
Raw Manager Data:
0x0000: 04 40 13 BE 00 00 04 00 00 00 00 02 00 00 00 00
0x0010: 04 00 02 16 FE 00 00 06 08 00 00 04 00 00
>---------- End Event Monitoring Service Event Notification ----------<
?
whether the tape drive have something wrong.harware failure or tape failure.
how to deal with it?
there is information from root mail:
From root@hr02 Sun Nov 28 16:02:00 EAT 2004
Received: (from root@localhost)
by hr02 (8.9.3/8.9.3) id QAA14719;
Sun, 28 Nov 2004 16:02:00 +0800 (EAT)
Date: Sun, 28 Nov 2004 16:02:00 +0800 (EAT)
Message-Id: <200411280802.QAA14719@hr02>
To: root@hr02
From: root@hr02
Subject: hr02: Event Monitor Notification
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Sun Nov 28 16:02:00 2004
hr02 sent Event Monitor notification information:
/storage/events/tapes/SCSI_tape/0_0_10_0_0.2.25.255.0.0.2
is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time..........: Sun Nov 28 16:02:00 2004
Severity............: CRITICAL
Monitor.............: dm_stape
Event #.............: 100243
System..............: hr02
Summary:
Tape at hardware path 0/0/10/0/0.2.25.255.0.0.2 : Media failure
Description of Error:
The device was unsuccessful in reading data for the current I/O request
because it could not find the requested recorded entity on the medium. The
request may have been processed in a way which could cause damage to or
loss of data.
For furthur 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...: 172.20.4.89
Event Id............: 0x41a985f800000000
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):
0x41a985f800000000
Additional System Data:
System Model Number.............: 9000/800/rp7410
OS Version......................: B.11.11
System Firmware Version.........: 16.11
System Serial Number............: SGH43241LS
System Software ID..............: 729066710
EMS Version.....................: A.03.20
STM Version.....................: A.35.00
System Current Product Number...: A6752A
System Original Product Number..: A6752A
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100243
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....: 0/0/10/0/0.2.25.255.0.0.2
Inquiry Vendor ID.......: HP
Inquiry Product ID......: Ultrium 1-SCSI
Firmware Version........: E38W
Serial Number...........: HU73A02465
Product/Device Data:
Logger ID.........: stape
Product Identifier: SCSI Tape
Product Qualifier.: HPUltrium
SCSI Target ID....: 0x00
SCSI LUN..........: 0x02
I/O Log Event Data:
Driver Status Code..................: 0x00000005
Length of Logged Hardware Status....: 26 bytes.
Offset to Logged Manager Information: 32 bytes.
Length of Logged Manager Information: 30 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 F0 00 03 00 00 00 00 0E 00 00 00 00
0x0010: 14 00 00 00 50 90 00 00 00 00
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: F0 00 03 00 00 00 00 0E 00 00 00 00 14 00 00 00
0x0010: 50 90 00 00 00 00
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 : TRUE
Information Field : 0x00000000
Additional Sense Length : 14
Command Specific : 0x00000000
Additional Sense Code : 0x14
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x50 0x90
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 (0x1400)
indicates: Recorded entity not found.
SCSI Command Data Block: (not present in log record)
Manager-Specific Information:
Raw Manager Data:
0x0000: 04 40 13 BE 00 00 04 00 00 00 00 02 00 00 00 00
0x0010: 04 00 02 16 FE 00 00 06 08 00 00 04 00 00
>---------- End Event Monitoring Service Event Notification ----------<
?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2004 03:02 AM
тАО11-28-2004 03:02 AM
Re: locate scsi command failed, key = 0x3, asc = 0x14, ascq = 0x0
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2004 08:00 PM
тАО11-28-2004 08:00 PM
Re: locate scsi command failed, key = 0x3, asc = 0x14, ascq = 0x0
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Thx,marino.
Enviroment:Veritas Netbackup 4.5 fp3+hp-ux 11.11+Compaq msl5060.
Maybe it is media failure.but there is too many medias which write error,then those medias were frozen.so i have to put many medias into the library.Why so many medias is failure?It looks so abnormal.
Yes,i have installed hp-ltt in my master server,but i don't know how to use it.
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Sese code 03 is refered as Medium error (Medium a the tape not as the level)
ASC 14 00 mean:
- Recorded entity not found
A SPACE or Locate failed because a format violation prevented the target of the operation from being found.
I can suggest you to install L&TT and run R/W test on a brand new cartridge, so you will be able to see if the problem come from the tape or from the R/W head fo the LTO
marino
Thx,marino.
Enviroment:Veritas Netbackup 4.5 fp3+hp-ux 11.11+Compaq msl5060.
Maybe it is media failure.but there is too many medias which write error,then those medias were frozen.so i have to put many medias into the library.Why so many medias is failure?It looks so abnormal.
Yes,i have installed hp-ltt in my master server,but i don't know how to use 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