<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SCSSI error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241514#M330063</link>
    <description>You have a media failure on the disk, the disk is going bad..  pvdisplay and vgdisplay only display the header info.  There is one or more bad blocks on the disk.&lt;BR /&gt;&lt;BR /&gt;To be sure read the entire contents of the disk&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/rdsk/cxtxtdx of=/dev/null bs=1024&lt;BR /&gt;&lt;BR /&gt;Should get an io error eventually.&lt;BR /&gt;&lt;BR /&gt;Replace the disk.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 28 Jul 2008 15:41:22 GMT</pubDate>
    <dc:creator>Tim Nelson</dc:creator>
    <dc:date>2008-07-28T15:41:22Z</dc:date>
    <item>
      <title>SCSSI error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241513#M330062</link>
      <description>We had an error log in the syslog:&lt;BR /&gt;&lt;BR /&gt;Jul 28 04:35:00 APPLE EMS [1102]: ------ EMS Event Notification ------   Value: "&lt;BR /&gt;CRITICAL (5)" for Resource: "/storage/events/disks/default/10_4_12.4.0"     (Thr&lt;BR /&gt;eshold:  &amp;gt;= " 3")    Execute the following command to obtain event details:   /o&lt;BR /&gt;pt/resmon/bin/resdata -R 72221092 -r /storage/events/disks/default/10_4_12.4.0 -&lt;BR /&gt;n 72220673 -a &lt;BR /&gt;&lt;BR /&gt;When I executed the proposed command, it gives the following details:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;CURRENT MONITOR DATA:&lt;BR /&gt;&lt;BR /&gt;Event Time : Mon Jul 28 04:34:59 2008&lt;BR /&gt;Hostname : HERA.rpcsap.com      IP Address  : 206.199.230.104&lt;BR /&gt;Event Id : 0x00488d84b300000000      Monitor     : disk_em&lt;BR /&gt;Event #  : 100037                    Event Class : I/O&lt;BR /&gt;Severity : CRITICAL&lt;BR /&gt;&lt;BR /&gt;Disk at hardware path 10/4/12.4.0 : Media failure&lt;BR /&gt;Associated OS error log entry id(s): &lt;BR /&gt;      000000000000000000&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt;     The device was unsuccessful in reading or writing data for the current I/O&lt;BR /&gt;     request due to a data synchronization mark error on the medium. The&lt;BR /&gt;     request may have been processed in a way which could cause damage to or&lt;BR /&gt;     loss of data.&lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;     The medium in the device is flawed. If the medium is removable, replace&lt;BR /&gt;     the medium with a fresh one.&lt;BR /&gt;&lt;BR /&gt;     Alternatively, if the medium is not removable, the device has experienced&lt;BR /&gt;     a hardware failure. Repair or replace the device, as necessary.&lt;BR /&gt;&lt;BR /&gt;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&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Product/Device Identification Information:&lt;BR /&gt;&lt;BR /&gt;     Logger ID.........: disc30&lt;BR /&gt;     Product Identifier: SCSI Disk&lt;BR /&gt;     Product Qualifier.: SEAGATEST19171N&lt;BR /&gt;     SCSI Target ID....: 0x02&lt;BR /&gt;     SCSI LUN..........: 0x00&lt;BR /&gt;&lt;BR /&gt;I/O Log Event Information: &lt;BR /&gt;&lt;BR /&gt;     I/O Event Class.....................: Hardware Triggered Event &lt;BR /&gt;     I/O Transaction Number..............: 0x800029BC &lt;BR /&gt;     Length of Hardware Status Logged....: 22 bytes &lt;BR /&gt;     Length of Driver Information Logged.: 31 bytes&lt;BR /&gt;     I/O retry information:  &lt;BR /&gt;          All retries are being logged, and this retry of the I/O FAILED. &lt;BR /&gt;          0 retries have been performed so far. I/O will NOT be retried again.&lt;BR /&gt;&lt;BR /&gt;Low Level I/O (LLIO) Status:  0x02ff042d  &lt;BR /&gt;     Subsystem field = "scsi3"; Proc. Num. = -1; Error Num. = 2 &lt;BR /&gt;     "scsi3" Device Adapter Manager reports Warning: NON GOOD STATUS: SCSI&lt;BR /&gt;     device returned a non-successful SCSI status.&lt;BR /&gt;&lt;BR /&gt;Hardware Status: &lt;BR /&gt;&lt;BR /&gt;     Raw H/W Status:&lt;BR /&gt;          0x0000: 00 00 00 02   F0 00 03 00   07 BF B1 0A   00 00 00 00&lt;BR /&gt;          0x0010: 16 00 D2 80   00 5B&lt;BR /&gt;&lt;BR /&gt;     SCSI Status...: CHECK CONDITION (0x02) &lt;BR /&gt;          Indicates that a contingent allegiance condition has occurred.  Any&lt;BR /&gt;          error, exception, or abnormal condition that causes sense data to be&lt;BR /&gt;          set will produce the CHECK CONDITION status.&lt;BR /&gt;     &lt;BR /&gt;SCSI Sense Data: &lt;BR /&gt;&lt;BR /&gt;     Undecoded Sense Data:&lt;BR /&gt;          0x0000: F0 00 03 00   07 BF B1 0A   00 00 00 00   16 00 D2 80&lt;BR /&gt;          0x0010: 00 5B&lt;BR /&gt;     &lt;BR /&gt;     SCSI Sense Data Fields:&lt;BR /&gt;          Error Code                      : 0x70&lt;BR /&gt;          Segment Number                  : 0x00&lt;BR /&gt;          Bit Fields:      &lt;BR /&gt;               Filemark                   : 0&lt;BR /&gt;               End-of-Medium              : 0&lt;BR /&gt;               Incorrect Length Indicator : 0&lt;BR /&gt;          Sense Key                       : 0x03&lt;BR /&gt;          Information Field Valid         : TRUE&lt;BR /&gt;          Information Field               : 0x0007BFB1&lt;BR /&gt;          Additional Sense Length         : 10&lt;BR /&gt;          Command Specific                : 0x00000000&lt;BR /&gt;          Additional Sense Code           : 0x16&lt;BR /&gt;          Additional Sense Qualifier      : 0x00&lt;BR /&gt;          Field Replaceable Unit          : 0xD2&lt;BR /&gt;          Sense Key Specific Data Valid   : FALSE               &lt;BR /&gt;          Sense Key Specific Data         : 0x80 0x00 0x5B&lt;BR /&gt;                       &lt;BR /&gt;          Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated&lt;BR /&gt;          with a nonrecovered error condition that was probably caused by a&lt;BR /&gt;          flaw in the medium or an error in the recorded data.  This sense key&lt;BR /&gt;          may also be returned if the device is unable to distinguish between a&lt;BR /&gt;          flaw in the medium and a specific hardware failure (sense key 0x04).&lt;BR /&gt;          For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,&lt;BR /&gt;          the Sense Key Specific data indicates that 91 retries were attempted.&lt;BR /&gt;                       &lt;BR /&gt;          The combination of Additional Sense Code and Sense Qualifier (0x1600)&lt;BR /&gt;          indicates: Data synchronization mark error.&lt;BR /&gt;&lt;BR /&gt;SCSI Command Data Block:&lt;BR /&gt;&lt;BR /&gt;     Command Data Block Contents:&lt;BR /&gt;          0x0000: 28 00 00 07   BF 80 00 00   80 00&lt;BR /&gt;     &lt;BR /&gt;     Command Data Block Fields (10-byte fmt):&lt;BR /&gt;          Command Operation Code...(0x28)..: READ&lt;BR /&gt;          Logical Unit Number..............: 0&lt;BR /&gt;          DPO Bit..........................: 0&lt;BR /&gt;          FUA Bit..........................: 0&lt;BR /&gt;          Relative Address Bit.............: 0&lt;BR /&gt;          Logical Block Address............: 507776 (0x0007BF80)&lt;BR /&gt;          Transfer Length..................: 128 (0x0080)&lt;BR /&gt;&lt;BR /&gt;Manager-Specific Data Fields: &lt;BR /&gt;     Subsystem..............: 0x0415 &lt;BR /&gt;     SCSI Target Address....: 4 &lt;BR /&gt;     SCSI LUN...............: 0x00 &lt;BR /&gt;     Driver State...........: Available &lt;BR /&gt;     Config Sub State.......: Null substate &lt;BR /&gt;     Message Type...........: 131&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Jul 2008 15:37:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241513#M330062</guid>
      <dc:creator>Waqar Razi</dc:creator>
      <dc:date>2008-07-28T15:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: SCSSI error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241514#M330063</link>
      <description>You have a media failure on the disk, the disk is going bad..  pvdisplay and vgdisplay only display the header info.  There is one or more bad blocks on the disk.&lt;BR /&gt;&lt;BR /&gt;To be sure read the entire contents of the disk&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/rdsk/cxtxtdx of=/dev/null bs=1024&lt;BR /&gt;&lt;BR /&gt;Should get an io error eventually.&lt;BR /&gt;&lt;BR /&gt;Replace the disk.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Jul 2008 15:41:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241514#M330063</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2008-07-28T15:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: SCSSI error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241515#M330064</link>
      <description>This part pretty much sums it up:&lt;BR /&gt;&lt;BR /&gt;" The medium in the device is flawed. If the medium is removable, replace the medium with a fresh one.&lt;BR /&gt;&lt;BR /&gt;Alternatively, if the medium is not removable, the device has experienced a hardware failure. Repair or replace the device, as necessary."&lt;BR /&gt;&lt;BR /&gt;The disk had a hardware failure (head crash?) and needs to be replaced.&lt;BR /&gt;&lt;BR /&gt;You can confirm by running dd against the device:&lt;BR /&gt;&lt;BR /&gt;dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k Replace X, Y, and Z with the proper values)&lt;BR /&gt;&lt;BR /&gt;If you get an I/O error, your disk is indeed dead.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Mon, 28 Jul 2008 15:42:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241515#M330064</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2008-07-28T15:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: SCSSI error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241516#M330065</link>
      <description>Wow, such an old disk.&lt;BR /&gt;&lt;BR /&gt;Only due to the age a failure is some likely.&lt;BR /&gt;&lt;BR /&gt;Test as advised above, question is about a replacement. Can you still get such disk?</description>
      <pubDate>Mon, 28 Jul 2008 17:00:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241516#M330065</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-07-28T17:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: SCSSI error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241517#M330066</link>
      <description>does this disk belongs to vg00? are the data mirrored? then it is easier to replace online.</description>
      <pubDate>Tue, 29 Jul 2008 09:19:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scssi-error/m-p/4241517#M330066</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-07-29T09:19:33Z</dc:date>
    </item>
  </channel>
</rss>

