<?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 error on dmesg in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087261#M309910</link>
    <description>hi hope someone can help me.&lt;BR /&gt;&lt;BR /&gt;how can i see the details of this alarm found on dmesg (syslog)?&lt;BR /&gt;&lt;BR /&gt;what is the possible cause of this alarm?&lt;BR /&gt;&lt;BR /&gt;"SCSI: Unexpected Disconnect -- lbolt: 47866821, dev: cb0df002, io_id: d0000b9"&lt;BR /&gt;&lt;BR /&gt;thanks.</description>
    <pubDate>Tue, 16 Oct 2007 20:22:06 GMT</pubDate>
    <dc:creator>remer</dc:creator>
    <dc:date>2007-10-16T20:22:06Z</dc:date>
    <item>
      <title>error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087261#M309910</link>
      <description>hi hope someone can help me.&lt;BR /&gt;&lt;BR /&gt;how can i see the details of this alarm found on dmesg (syslog)?&lt;BR /&gt;&lt;BR /&gt;what is the possible cause of this alarm?&lt;BR /&gt;&lt;BR /&gt;"SCSI: Unexpected Disconnect -- lbolt: 47866821, dev: cb0df002, io_id: d0000b9"&lt;BR /&gt;&lt;BR /&gt;thanks.</description>
      <pubDate>Tue, 16 Oct 2007 20:22:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087261#M309910</guid>
      <dc:creator>remer</dc:creator>
      <dc:date>2007-10-16T20:22:06Z</dc:date>
    </item>
    <item>
      <title>Re: error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087262#M309911</link>
      <description>The lbolt value means very little; it's simply the number of clock ticks since boot. The device id is key:&lt;BR /&gt;&lt;BR /&gt;The first two hex digits (cb) indicate the major device. 0xCB = 203 (dec). Do an lsdev and see what device corresponds to this value. (Probably a tape drive, possibly a robotics device but lsdev will identify it on your particular system). &lt;BR /&gt;&lt;BR /&gt;The next two hex digits (0d) indicate the controller instance, c13.&lt;BR /&gt;&lt;BR /&gt;The next hex digit (f) indevicate the SCSI ID (or target) t15. The next hex digit (0) indicates the LUN (d0). The last two hex digits (02) are device dependent. If 203 is a tape device major number then the&lt;BR /&gt;device with the problem is /dev/rmt/c13t15d0.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Oct 2007 20:59:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087262#M309911</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-10-16T20:59:55Z</dc:date>
    </item>
    <item>
      <title>Re: error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087263#M309912</link>
      <description>thanks&lt;BR /&gt;upon checking cb (first two hexa digit) is a 203 which upon checking using lsdev is a:&lt;BR /&gt;&lt;BR /&gt;# lsdev |grep 203&lt;BR /&gt;      203          -1         sctl            ctl&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;using ioscan.&lt;BR /&gt;# ioscan -nfC ctl&lt;BR /&gt;Class     I  H/W Path        Driver S/W State   H/W Type     Description&lt;BR /&gt;=========================================================================&lt;BR /&gt;ctl       0  0/0/0/2/0.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c0t7d0&lt;BR /&gt;ctl       1  0/0/0/2/1.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c1t7d0&lt;BR /&gt;ctl       2  0/0/0/3/0.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c2t7d0&lt;BR /&gt;ctl       3  0/0/0/3/1.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c3t7d0&lt;BR /&gt;ctl      12  0/0/6/0/0.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c14t7d0&lt;BR /&gt;ctl      11  0/0/12/0/0.7.0  sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c13t7d0&lt;BR /&gt;ctl       4  1/0/0/2/0.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c4t7d0&lt;BR /&gt;ctl       5  1/0/0/2/1.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c5t7d0&lt;BR /&gt;ctl       6  1/0/0/3/0.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c6t7d0&lt;BR /&gt;ctl       7  1/0/0/3/1.7.0   sctl   CLAIMED     DEVICE       Initiator&lt;BR /&gt;                            /dev/rscsi/c7t7d0&lt;BR /&gt;ctl      21  1/0/2/0/0.2.0.255.0.1.0   sctl   CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/rscsi/c30t1d0&lt;BR /&gt;ctl      22  1/0/14/0/0.1.0.255.0.1.0  sctl   CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/rscsi/c31t1d0&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;so i can say the problem is a third party device? &lt;BR /&gt;&lt;BR /&gt;thanks.&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Oct 2007 21:42:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087263#M309912</guid>
      <dc:creator>remer</dc:creator>
      <dc:date>2007-10-16T21:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087264#M309913</link>
      <description>btw, what does the lbolt number mean? and the io_id mean? do i need to convert it to decimal to get something on it?&lt;BR /&gt;&lt;BR /&gt;thanks again...</description>
      <pubDate>Tue, 16 Oct 2007 21:47:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087264#M309913</guid>
      <dc:creator>remer</dc:creator>
      <dc:date>2007-10-16T21:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087265#M309914</link>
      <description>I would do this:&lt;BR /&gt;&lt;BR /&gt;ls -l /dev/*/c13t15d0* and see what devices are displayed. sctl is the SCSI pass-thru driver and is very commonly used for robotic (e.g. tape library) devices.</description>
      <pubDate>Tue, 16 Oct 2007 21:48:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087265#M309914</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-10-16T21:48:36Z</dc:date>
    </item>
    <item>
      <title>Re: error on dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087266#M309915</link>
      <description>i can't find any devices.&lt;BR /&gt;do you that's was the reason of this alarm?</description>
      <pubDate>Tue, 16 Oct 2007 22:07:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-on-dmesg/m-p/4087266#M309915</guid>
      <dc:creator>remer</dc:creator>
      <dc:date>2007-10-16T22:07:35Z</dc:date>
    </item>
  </channel>
</rss>

