<?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: What's this critical error message mean? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284383#M180983</link>
    <description>Here is the check message&lt;BR /&gt;# ioscan -fnkCdisk &lt;BR /&gt;disk      6  0/7/0/1.9.0           sdisk    CLAIMED     DEVICE       SEAGATE ST136403LC&lt;BR /&gt;                                  /dev/dsk/c5t9d0   /dev/rdsk/c5t9d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# diskinfo /dev/rdsk/cxtydz&lt;BR /&gt;diskinfo /dev/rdsk/c5t9d0&lt;BR /&gt;SCSI describe of /dev/rdsk/c5t9d0:&lt;BR /&gt;             vendor: SEAGATE&lt;BR /&gt;         product id: ST136403LC&lt;BR /&gt;               type: direct access&lt;BR /&gt;               size: 35566480 Kbytes&lt;BR /&gt;   bytes per sector: 512&lt;BR /&gt;&lt;BR /&gt;Is the disk ok?&lt;BR /&gt;&lt;BR /&gt;And I find another disk /dev/dsk/c5t8d0 has the same problem.&lt;BR /&gt;This server use SCSI line connected to Disk Array.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 24 May 2004 04:41:03 GMT</pubDate>
    <dc:creator>eagle_2</dc:creator>
    <dc:date>2004-05-24T04:41:03Z</dc:date>
    <item>
      <title>What's this critical error message mean?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284380#M180980</link>
      <description>&amp;gt;------------ Event Monitoring Service Event Notification ------------&amp;lt;&lt;BR /&gt;&lt;BR /&gt;Notification Time: Sun May 23 15:27:04 2004&lt;BR /&gt;&lt;BR /&gt;L2000_cn sent Event Monitor notification information:&lt;BR /&gt;&lt;BR /&gt;/storage/events/disks/default/0_7_0_1.9.0 is &amp;gt;= 3.&lt;BR /&gt;Its current value is CRITICAL(5).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Event data from monitor:&lt;BR /&gt;&lt;BR /&gt;Event Time : Sun May 23 15:27:04 2004&lt;BR /&gt;Hostname : L2000_cn      IP Address  : 10.56.10.71&lt;BR /&gt;Event Id : 0x0040b0524800000000      Monitor     : disk_em&lt;BR /&gt;Event #  : 100091                    Event Class : I/O&lt;BR /&gt;Severity : CRITICAL&lt;BR /&gt;&lt;BR /&gt;Disk at hardware path 0/7/0/1.9.0 : Software configuration error&lt;BR /&gt;&lt;BR /&gt;Associated OS error log entry id(s): &lt;BR /&gt;     0x40b0524800000000&lt;BR /&gt;&lt;BR /&gt;Latest information on this event:&lt;BR /&gt;     &lt;A href="http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091" target="_blank"&gt;http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Description of Error:&lt;BR /&gt;&lt;BR /&gt;     The device is in a condition where it requires action on the part of the&lt;BR /&gt;     device driver or a human operator. &lt;BR /&gt;&lt;BR /&gt;Probable Cause / Recommended Action:&lt;BR /&gt;&lt;BR /&gt;     The device has been reset by a Bus Device Reset message, a hard reset&lt;BR /&gt;     condition, or a power-on reset.&lt;BR /&gt;&lt;BR /&gt;     If this is the case, no action is necessary.&lt;BR /&gt;&lt;BR /&gt;     Alternatively, a removable medium has been loaded or replaced.&lt;BR /&gt;&lt;BR /&gt;     If this is the case, no action is necessary.&lt;BR /&gt;&lt;BR /&gt;     Alternatively, the mode parameters, microcode, or inquiry data for the&lt;BR /&gt;     device have been changed.&lt;BR /&gt;&lt;BR /&gt;     If this is the case, no action is necessary.&lt;BR /&gt;&lt;BR /&gt;     Alternatively, the installed version of the device driver does not match&lt;BR /&gt;     that of the installed version of HP-UX. Install the correct version of the&lt;BR /&gt;     driver.&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.........: sdisk&lt;BR /&gt;     Product Identifier: SCSI Disk&lt;BR /&gt;     Product Qualifier.: SEAGATEST136403LC&lt;BR /&gt;     SCSI Target ID....: 0x09&lt;BR /&gt;     SCSI LUN..........: 0x00&lt;BR /&gt;&lt;BR /&gt;I/O Log Event Data: &lt;BR /&gt;&lt;BR /&gt;     Driver Status Code..................: 0x0000007E &lt;BR /&gt;     Length of Logged Hardware Status....: 22 bytes. &lt;BR /&gt;     Offset to Logged Manager Information: 24 bytes. &lt;BR /&gt;     Length of Logged Manager Information: 34 bytes. &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   70 00 06 00   00 00 00 0A   00 00 00 00&lt;BR /&gt;          0x0010: 29 02 02 00   00 00&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: 70 00 06 00   00 00 00 0A   00 00 00 00   29 02 02 00&lt;BR /&gt;          0x0010: 00 00&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                       : 0x06&lt;BR /&gt;          Information Field Valid         : FALSE               &lt;BR /&gt;          Information Field               : 0x00000000&lt;BR /&gt;          Additional Sense Length         : 10&lt;BR /&gt;          Command Specific                : 0x00000000&lt;BR /&gt;          Additional Sense Code           : 0x29&lt;BR /&gt;          Additional Sense Qualifier      : 0x02&lt;BR /&gt;          Field Replaceable Unit          : 0x02&lt;BR /&gt;          Sense Key Specific Data Valid   : FALSE               &lt;BR /&gt;          Sense Key Specific Data         : 0x00 0x00 0x00&lt;BR /&gt;                       &lt;BR /&gt;          Sense Key 0x06, UNIT ATTENTION, indicates that the target has been&lt;BR /&gt;          reset by a BUS DEVICE RESET message, a hard reset condition, or by a&lt;BR /&gt;          power-on reset. If not a reset, then one of the following may have&lt;BR /&gt;          occurred.&lt;BR /&gt;             1. A removable medium may have been changed.&lt;BR /&gt;             2. The mode parameters in effect for this initiator have been&lt;BR /&gt;             changed by another initiator.&lt;BR /&gt;             3. The version or level of microcode has been changed.&lt;BR /&gt;             4. Tagged commands queued for this initiator were cleared by&lt;BR /&gt;             another initiator.&lt;BR /&gt;             5. INQUIRY data has been changed.&lt;BR /&gt;             6. The mode parameters in effect for this initiator have been&lt;BR /&gt;             restored from non-volatile memory.&lt;BR /&gt;             7. A change in the condition of a synchronized spindle.&lt;BR /&gt;             8. Any other event that requires the attention of the initiator.&lt;BR /&gt;&lt;BR /&gt;SCSI Command Data Block:&lt;BR /&gt;&lt;BR /&gt;     Command Data Block Contents:&lt;BR /&gt;          0x0000: 2A 00 00 6F   3A 90 00 00   10 00&lt;BR /&gt;     &lt;BR /&gt;     Command Data Block Fields (10-byte fmt):&lt;BR /&gt;          Command Operation Code...(0x2A)..: WRITE&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............: 7289488 (0x006F3A90)&lt;BR /&gt;          Transfer Length..................: 16 (0x0010)&lt;BR /&gt;&lt;BR /&gt;Manager-Specific Data Fields: &lt;BR /&gt;     Request ID.............: 0x05C46668 &lt;BR /&gt;     Data Residue...........: 0x00002000 &lt;BR /&gt;     CDB status.............: 0x00000002 &lt;BR /&gt;     Sense Status...........: 0x00000000 &lt;BR /&gt;     Bus ID.................: 0x05 &lt;BR /&gt;     Target ID..............: 0x09 &lt;BR /&gt;     LUN ID.................: 0x00 &lt;BR /&gt;     Sense Data Length......: 0x12 &lt;BR /&gt;     Q Tag..................: 0x73 &lt;BR /&gt;     Retry Count............: 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;---------- End Event Monitoring Service Event Notification ----------&amp;lt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In the syslog contents I find the following message:&lt;BR /&gt;May 23 15:26:59 L2000_cn vmunix: SCSI: Resetting SCSI -- lbolt: 196686456, bus:&lt;BR /&gt;5&lt;BR /&gt;May 23 15:26:59 L2000_cn vmunix: SCSI: Reset detected -- lbolt: 196686456, bus:&lt;BR /&gt;5 &lt;BR /&gt;and from May 1 this message shows several times each day.&lt;BR /&gt;&lt;BR /&gt;But my application on the disk array is ok now &lt;BR /&gt;&lt;BR /&gt;The attachment is the syslog file.&lt;BR /&gt;&lt;BR /&gt;So I want to know what's the matter.&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Mon, 24 May 2004 03:18:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284380#M180980</guid>
      <dc:creator>eagle_2</dc:creator>
      <dc:date>2004-05-24T03:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: What's this critical error message mean?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284381#M180981</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check this hardware path. 0/7/0/1.9.0 &lt;BR /&gt;&lt;BR /&gt;# ioscan -fnkCdisk &lt;BR /&gt;&lt;BR /&gt;# diskinfo /dev/rdsk/cxtydz&lt;BR /&gt;&lt;BR /&gt;Is it still available ?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Mon, 24 May 2004 03:38:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284381#M180981</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2004-05-24T03:38:14Z</dc:date>
    </item>
    <item>
      <title>Re: What's this critical error message mean?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284382#M180982</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;This means the SCSI bus is constantly resetting as its being upset by "Disk at hardware path 0/7/0/1.9.0 : Software configuration error" as Robert suggested start checking the disk.&lt;BR /&gt;&lt;BR /&gt;If you type lbolt in the search box at the top of the page you will find lots of threads to similar problems&lt;BR /&gt;&lt;BR /&gt;:-) John.</description>
      <pubDate>Mon, 24 May 2004 03:53:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284382#M180982</guid>
      <dc:creator>John Carr_2</dc:creator>
      <dc:date>2004-05-24T03:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: What's this critical error message mean?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284383#M180983</link>
      <description>Here is the check message&lt;BR /&gt;# ioscan -fnkCdisk &lt;BR /&gt;disk      6  0/7/0/1.9.0           sdisk    CLAIMED     DEVICE       SEAGATE ST136403LC&lt;BR /&gt;                                  /dev/dsk/c5t9d0   /dev/rdsk/c5t9d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;# diskinfo /dev/rdsk/cxtydz&lt;BR /&gt;diskinfo /dev/rdsk/c5t9d0&lt;BR /&gt;SCSI describe of /dev/rdsk/c5t9d0:&lt;BR /&gt;             vendor: SEAGATE&lt;BR /&gt;         product id: ST136403LC&lt;BR /&gt;               type: direct access&lt;BR /&gt;               size: 35566480 Kbytes&lt;BR /&gt;   bytes per sector: 512&lt;BR /&gt;&lt;BR /&gt;Is the disk ok?&lt;BR /&gt;&lt;BR /&gt;And I find another disk /dev/dsk/c5t8d0 has the same problem.&lt;BR /&gt;This server use SCSI line connected to Disk Array.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 24 May 2004 04:41:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284383#M180983</guid>
      <dc:creator>eagle_2</dc:creator>
      <dc:date>2004-05-24T04:41:03Z</dc:date>
    </item>
    <item>
      <title>Re: What's this critical error message mean?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284384#M180984</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;it is probably a scsi reset since the disk is now claimed. do this to confirm condition of disks:&lt;BR /&gt;&lt;BR /&gt;# dd if=dev/rdsk/c5t9d0 of=/dev/null bs=256&lt;BR /&gt;&lt;BR /&gt;break the above command after about 5 minutes, check if the input and output are the same. if same, it should be alright. do this for the other disk as well&lt;BR /&gt;&lt;BR /&gt;regards.</description>
      <pubDate>Mon, 24 May 2004 04:45:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/what-s-this-critical-error-message-mean/m-p/3284384#M180984</guid>
      <dc:creator>Joseph Loo</dc:creator>
      <dc:date>2004-05-24T04:45:11Z</dc:date>
    </item>
  </channel>
</rss>

