<?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: SCSI lbolt errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145216#M453453</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Two sources of these kind of message.&lt;BR /&gt;&lt;BR /&gt;Benign: Recent replacement or pull on a hot swap disk. dmesg - will clear it as will a boot.&lt;BR /&gt;&lt;BR /&gt;Problem: Actual disk or scsi controller failure.&lt;BR /&gt;&lt;BR /&gt;The second cause requires correction, usually replacement of the disk in question.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-3385/ch04s08.html" target="_blank"&gt;http://docs.hp.com/en/5992-3385/ch04s08.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-3385/ch04s08.html#lvm.trouble.nmnb" target="_blank"&gt;http://docs.hp.com/en/5992-3385/ch04s08.html#lvm.trouble.nmnb&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 08 Dec 2008 17:07:59 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2008-12-08T17:07:59Z</dc:date>
    <item>
      <title>SCSI lbolt errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145214#M453451</link>
      <description>I am receiving SCSI lbolt errors in syslog.log:&lt;BR /&gt;&lt;BR /&gt;Dec  8 10:53:22 odcign1 vmunix: SCSI:  -- lbolt: 960015433, dev: 1f048000&lt;BR /&gt;Dec  8 10:53:22 odcign1 vmunix:                 lbolt_at_timeout: 0, lbolt_at_start: 0&lt;BR /&gt;Dec  8 10:53:23 odcign1 vmunix: SCSI: Resetting SCSI -- lbolt: 960015533, bus: 4 path: 0/4/1/0&lt;BR /&gt;Dec  8 10:53:23 odcign1 vmunix: SCSI: Reset detected -- lbolt: 960015533, bus: 4 path: 0/4/1/0&lt;BR /&gt;&lt;BR /&gt;and associated EMS messages:&lt;BR /&gt;&lt;BR /&gt;Event Monitor notification information:&lt;BR /&gt;&lt;BR /&gt;/storage/events/disks/default/0_4_1_0.10.0 is &amp;gt;= 3.&lt;BR /&gt;Its current value is MAJORWARNING(3).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Event data from monitor:&lt;BR /&gt;&lt;BR /&gt;Event Time..........: Sat Dec  6 17:04:09 2008&lt;BR /&gt;Severity............: MAJORWARNING&lt;BR /&gt;Monitor.............: disk_em&lt;BR /&gt;Event #.............: 100091              &lt;BR /&gt;System..............: odcign1&lt;BR /&gt;&lt;BR /&gt;Summary:&lt;BR /&gt;     Disk at hardware path 0/4/1/0.10.0 : Software configuration error&lt;BR /&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;Additional Event Data: &lt;BR /&gt;     System IP Address...: 155.90.142.32&lt;BR /&gt;     Event Id............: 0x493af6d900000004&lt;BR /&gt;     Monitor Version.....: B.01.01&lt;BR /&gt;     Event Class.........: I/O&lt;BR /&gt;     Client Configuration File...........:&lt;BR /&gt;     /var/stm/config/tools/monitor/default_disk_em.clcfg &lt;BR /&gt;     Client Configuration File Version...: A.01.00 &lt;BR /&gt;          Qualification criteria met.&lt;BR /&gt;               Number of events..: 1 &lt;BR /&gt;     Associated OS error log entry id(s): &lt;BR /&gt;          0x493af6d800000003&lt;BR /&gt;     Additional System Data:&lt;BR /&gt;          System Model Number.............: 9000/800/rp3410   &lt;BR /&gt;          OS Version......................: B.11.11 &lt;BR /&gt;          STM Version.....................: A.59.00 &lt;BR /&gt;          EMS Version.....................: A.04.20 &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;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;Component Data: &lt;BR /&gt;     Physical Device Path...: 0/4/1/0.10.0&lt;BR /&gt;     Device Class...........: Disk&lt;BR /&gt;     Inquiry Vendor ID......: ModusLnk&lt;BR /&gt;     Inquiry Product ID.....: MXJ3147SC800600X&lt;BR /&gt;     Firmware Version.......: HPB2&lt;BR /&gt;     Serial Number..........:   ML00019855&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.: ModusLnkMXJ3147SC800600X&lt;BR /&gt;     SCSI Target ID....: 0x0A&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..................: 0x0000000B &lt;BR /&gt;     Length of Logged Hardware Status....: 36 bytes. &lt;BR /&gt;     Offset to Logged Manager Information: 40 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 28   00 00 00 00&lt;BR /&gt;          0x0010: 29 02 00 00   00 00 0A 28   00 99 01 80   00 00 00 00&lt;BR /&gt;          0x0020: 00 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 28   00 00 00 00   29 02 00 00&lt;BR /&gt;          0x0010: 00 00 0A 28   00 99 01 80   00 00 00 00   00 00 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         : 40&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          : 0x00&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;          The combination of Additional Sense Code and Sense Qualifier (0x2902)&lt;BR /&gt;          indicates: SCSI bus reset occurred.&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 10 A2   74 00 00 01   F0 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............: 279081984 (0x10A27400)&lt;BR /&gt;          Transfer Length..................: 496 (0x01F0)&lt;BR /&gt;&lt;BR /&gt;Manager-Specific Data Fields: &lt;BR /&gt;     Request ID.............: 0x04EE3874 &lt;BR /&gt;     Data Residue...........: 0x0003E000 &lt;BR /&gt;     CDB status.............: 0x00000002 &lt;BR /&gt;     Sense Status...........: 0x00000000 &lt;BR /&gt;     Bus ID.................: 0x04 &lt;BR /&gt;     Target ID..............: 0x0A &lt;BR /&gt;     LUN ID.................: 0x00 &lt;BR /&gt;     Sense Data Length......: 0x20 &lt;BR /&gt;     Q Tag..................: 0x7E &lt;BR /&gt;     Retry Count............: 1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;---------- End Event Monitoring Service Event Notification ----------&amp;lt;</description>
      <pubDate>Mon, 08 Dec 2008 16:01:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145214#M453451</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2008-12-08T16:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI lbolt errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145215#M453452</link>
      <description>A good reference here..&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=219110" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=219110&lt;/A&gt;</description>
      <pubDate>Mon, 08 Dec 2008 16:45:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145215#M453452</guid>
      <dc:creator>john123</dc:creator>
      <dc:date>2008-12-08T16:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI lbolt errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145216#M453453</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Two sources of these kind of message.&lt;BR /&gt;&lt;BR /&gt;Benign: Recent replacement or pull on a hot swap disk. dmesg - will clear it as will a boot.&lt;BR /&gt;&lt;BR /&gt;Problem: Actual disk or scsi controller failure.&lt;BR /&gt;&lt;BR /&gt;The second cause requires correction, usually replacement of the disk in question.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-3385/ch04s08.html" target="_blank"&gt;http://docs.hp.com/en/5992-3385/ch04s08.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5992-3385/ch04s08.html#lvm.trouble.nmnb" target="_blank"&gt;http://docs.hp.com/en/5992-3385/ch04s08.html#lvm.trouble.nmnb&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 08 Dec 2008 17:07:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145216#M453453</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-12-08T17:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI lbolt errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145217#M453454</link>
      <description>Thanks</description>
      <pubDate>Wed, 10 Dec 2008 13:47:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-lbolt-errors/m-p/5145217#M453454</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2008-12-10T13:47:14Z</dc:date>
    </item>
  </channel>
</rss>

