- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSSI error
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
тАО07-28-2008 08:37 AM
тАО07-28-2008 08:37 AM
SCSSI error
Jul 28 04:35:00 APPLE EMS [1102]: ------ EMS Event Notification ------ Value: "
CRITICAL (5)" for Resource: "/storage/events/disks/default/10_4_12.4.0" (Thr
eshold: >= " 3") Execute the following command to obtain event details: /o
pt/resmon/bin/resdata -R 72221092 -r /storage/events/disks/default/10_4_12.4.0 -
n 72220673 -a
When I executed the proposed command, it gives the following details:
CURRENT MONITOR DATA:
Event Time : Mon Jul 28 04:34:59 2008
Hostname : HERA.rpcsap.com IP Address : 206.199.230.104
Event Id : 0x00488d84b300000000 Monitor : disk_em
Event # : 100037 Event Class : I/O
Severity : CRITICAL
Disk at hardware path 10/4/12.4.0 : Media failure
Associated OS error log entry id(s):
000000000000000000
Description of Error:
The device was unsuccessful in reading or writing data for the current I/O
request due to a data synchronization mark error on the medium. The
request may have been processed in a way which could cause damage to or
loss of data.
Probable Cause / Recommended Action:
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. Repair or replace the device, as necessary.
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
Product/Device Identification Information:
Logger ID.........: disc30
Product Identifier: SCSI Disk
Product Qualifier.: SEAGATEST19171N
SCSI Target ID....: 0x02
SCSI LUN..........: 0x00
I/O Log Event Information:
I/O Event Class.....................: Hardware Triggered Event
I/O Transaction Number..............: 0x800029BC
Length of Hardware Status Logged....: 22 bytes
Length of Driver Information Logged.: 31 bytes
I/O retry information:
All retries are being logged, and this retry of the I/O FAILED.
0 retries have been performed so far. I/O will NOT be retried again.
Low Level I/O (LLIO) Status: 0x02ff042d
Subsystem field = "scsi3"; Proc. Num. = -1; Error Num. = 2
"scsi3" Device Adapter Manager reports Warning: NON GOOD STATUS: SCSI
device returned a non-successful SCSI status.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 F0 00 03 00 07 BF B1 0A 00 00 00 00
0x0010: 16 00 D2 80 00 5B
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 07 BF B1 0A 00 00 00 00 16 00 D2 80
0x0010: 00 5B
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 : 0x0007BFB1
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x16
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0xD2
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x80 0x00 0x5B
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).
For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,
the Sense Key Specific data indicates that 91 retries were attempted.
The combination of Additional Sense Code and Sense Qualifier (0x1600)
indicates: Data synchronization mark error.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 28 00 00 07 BF 80 00 00 80 00
Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x28)..: READ
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 507776 (0x0007BF80)
Transfer Length..................: 128 (0x0080)
Manager-Specific Data Fields:
Subsystem..............: 0x0415
SCSI Target Address....: 4
SCSI LUN...............: 0x00
Driver State...........: Available
Config Sub State.......: Null substate
Message Type...........: 131
Can some one give me an idea whats wrong with it? I can still see the pvdisplay and vgdisplay output and this shows this PV as available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 08:41 AM
тАО07-28-2008 08:41 AM
Re: SCSSI error
To be sure read the entire contents of the disk
dd if=/dev/rdsk/cxtxtdx of=/dev/null bs=1024
Should get an io error eventually.
Replace the disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 08:42 AM
тАО07-28-2008 08:42 AM
Re: SCSSI error
" 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. Repair or replace the device, as necessary."
The disk had a hardware failure (head crash?) and needs to be replaced.
You can confirm by running dd against the device:
dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k Replace X, Y, and Z with the proper values)
If you get an I/O error, your disk is indeed dead.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2008 10:00 AM
тАО07-28-2008 10:00 AM
Re: SCSSI error
Only due to the age a failure is some likely.
Test as advised above, question is about a replacement. Can you still get such disk?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2008 02:19 AM
тАО07-29-2008 02:19 AM