<?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 messages in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604091#M34830</link>
    <description>a few days ago, the following messages started appearing in the /var/adm/messages file.  The last four lines are repetative through today.&lt;BR /&gt;The system configuration, as far as disks are concerned is four physical 9GB disks in two volume groups (vg0 and vg1), mirrored.  What is the key to breaking down the message to determine the erroring device.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Oct 24 07:25                                                                   &lt;BR /&gt;                scb-&amp;gt;cdb: 2a 00 00 36 a5 50 00 00 10 00                        &lt;BR /&gt;SCSI: Abort abandoned -- lbolt: 69314221, dev: 1f005000, io_id: a85511, status:&lt;BR /&gt;200                                                                            &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Async write error -- dev: b 31 0x005000, errno: 126, resid: 8192,        &lt;BR /&gt;        blkno: 992504, sectno: 1985008, offset: 1016324096, bcount: 8192.      &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Read error -- dev: b 31 0x005000, errno: 126, resid: 2048,               &lt;BR /&gt;blkno: 8, sectno: 16, offset: 8192, bcount: 2048.                      &lt;BR /&gt;LVM: vg[0]: pvnum=0 (dev_t=0x1f005000) is POWERFAILED                          &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Write error -- dev: b 31 0x005000, errno: 126, resid: 10240,             &lt;BR /&gt;        blkno: 2310, sectno: 4620, offset: 2365440, bcount: 10240.             &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Read error -- dev: b 31 0x005000, errno: 126, resid: 2048,               &lt;BR /&gt;        blkno: 8, sectno: 16, offset: 8192, bcount: 2048.                      &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 30 Oct 2001 16:11:03 GMT</pubDate>
    <dc:creator>Louis McCurry</dc:creator>
    <dc:date>2001-10-30T16:11:03Z</dc:date>
    <item>
      <title>error messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604091#M34830</link>
      <description>a few days ago, the following messages started appearing in the /var/adm/messages file.  The last four lines are repetative through today.&lt;BR /&gt;The system configuration, as far as disks are concerned is four physical 9GB disks in two volume groups (vg0 and vg1), mirrored.  What is the key to breaking down the message to determine the erroring device.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Oct 24 07:25                                                                   &lt;BR /&gt;                scb-&amp;gt;cdb: 2a 00 00 36 a5 50 00 00 10 00                        &lt;BR /&gt;SCSI: Abort abandoned -- lbolt: 69314221, dev: 1f005000, io_id: a85511, status:&lt;BR /&gt;200                                                                            &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Async write error -- dev: b 31 0x005000, errno: 126, resid: 8192,        &lt;BR /&gt;        blkno: 992504, sectno: 1985008, offset: 1016324096, bcount: 8192.      &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Read error -- dev: b 31 0x005000, errno: 126, resid: 2048,               &lt;BR /&gt;blkno: 8, sectno: 16, offset: 8192, bcount: 2048.                      &lt;BR /&gt;LVM: vg[0]: pvnum=0 (dev_t=0x1f005000) is POWERFAILED                          &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Write error -- dev: b 31 0x005000, errno: 126, resid: 10240,             &lt;BR /&gt;        blkno: 2310, sectno: 4620, offset: 2365440, bcount: 10240.             &lt;BR /&gt;                                                                               &lt;BR /&gt;SCSI: Read error -- dev: b 31 0x005000, errno: 126, resid: 2048,               &lt;BR /&gt;        blkno: 8, sectno: 16, offset: 8192, bcount: 2048.                      &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Oct 2001 16:11:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604091#M34830</guid>
      <dc:creator>Louis McCurry</dc:creator>
      <dc:date>2001-10-30T16:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: error messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604092#M34831</link>
      <description>I looks like the device with the problem is&lt;BR /&gt;b 31 0x005000&lt;BR /&gt;Look under /dev/dsk and grep for 0x0050000.&lt;BR /&gt;It will give you the device number&lt;BR /&gt;Hope this help.&lt;BR /&gt;&lt;BR /&gt;nancy</description>
      <pubDate>Tue, 30 Oct 2001 16:19:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604092#M34831</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2001-10-30T16:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: error messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604093#M34832</link>
      <description>Hi Louis:&lt;BR /&gt;&lt;BR /&gt;Knowledge Base document #KBRC00000668 provides the answer.  The disk device can be determined by the using the dev_t value. For example: &lt;BR /&gt;&lt;BR /&gt;dev_t value of 0x1c045000 is associated with c4t5d0 &lt;BR /&gt;&lt;BR /&gt;04 = instance number&lt;BR /&gt; 5 = SCSI address number&lt;BR /&gt; 0 = LUN number&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 30 Oct 2001 16:20:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604093#M34832</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-10-30T16:20:21Z</dc:date>
    </item>
    <item>
      <title>Re: error messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604094#M34833</link>
      <description>The easiest way is to do an ll of /dev/dsk&lt;BR /&gt;and match the last 4 or 5 digits.&lt;BR /&gt;This is the explanation:&lt;BR /&gt;Within the syslog.log file and the dmesg output there can be an entry when scsi errors are occurring.  The complaints could be pertaining to SCSI Bus Resets, Parity Errors, Lbolt errors.  Along with these errors will come a hex device address.  An example of this address would be 0x1f000100 and can be referred to as the dev_t number.&lt;BR /&gt;     &lt;BR /&gt;     The following is the information needed to understand the translation:&lt;BR /&gt;     &lt;BR /&gt;     - the 0x signifies a hex number&lt;BR /&gt;     - the first 2 digits represent the major number in hex - convert these &lt;BR /&gt;     2 digits to a decimal number&lt;BR /&gt;     - the remaining digits represent the minor number in hex&lt;BR /&gt;     - then perform an ll on the /dev/dsk directory to match the major and &lt;BR /&gt;     minor numbers to an actual device&lt;BR /&gt;     &lt;BR /&gt;     The following is an example of the process:&lt;BR /&gt;     &lt;BR /&gt;     eg.   0x1f000100 &lt;BR /&gt;     1f = 31 decimal (which is the major number) 000100 already in hex &lt;BR /&gt;     (which is the minor number)&lt;BR /&gt;     &lt;BR /&gt;     ll /dev/dsk, you should see a device file with a major number of 31 &lt;BR /&gt;     and minor number of 000100, this is the device complaining in syslog &lt;BR /&gt;     or dmesg etc.&lt;BR /&gt;     &lt;BR /&gt;Eileen&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Oct 2001 16:21:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604094#M34833</guid>
      <dc:creator>Eileen Millen</dc:creator>
      <dc:date>2001-10-30T16:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: error messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604095#M34834</link>
      <description>Hi Louis,&lt;BR /&gt;&lt;BR /&gt;If you "ll /dev/dsk" and look for&lt;BR /&gt;&lt;BR /&gt;major=31&lt;BR /&gt;minor=0x005000&lt;BR /&gt;&lt;BR /&gt;that will identify the disk in question.  It looks like c0t5d0.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin.</description>
      <pubDate>Tue, 30 Oct 2001 16:22:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-messages/m-p/2604095#M34834</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2001-10-30T16:22:50Z</dc:date>
    </item>
  </channel>
</rss>

