<?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: dmesg errors and disks in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665707#M49472</link>
    <description>Hi Craig,&lt;BR /&gt;&lt;BR /&gt;I'm sorry i didn't answer your question fully. I don't see any reason why a cdrom mounted should interfere with the bdf command. I have not seen something like that.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;Sanjay&lt;BR /&gt;</description>
    <pubDate>Fri, 15 Feb 2002 18:14:56 GMT</pubDate>
    <dc:creator>Sanjay_6</dc:creator>
    <dc:date>2002-02-15T18:14:56Z</dc:date>
    <item>
      <title>dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665698#M49463</link>
      <description>9000/750&lt;BR /&gt;HP-UX 10.20&lt;BR /&gt;&lt;BR /&gt;I was doing a bdf, very, very slow, I actually killed the process as it took too long...... So I did a quick dmesg and got the below mesage. I am not sure of the disk setup, if it's mirrored, etc, just took over the system. It seems like the disks are not set using lvm....... Any things I can start to check to investigate a possible bad disk?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;DIAGNOSTIC SYSTEM WARNING:&lt;BR /&gt;   The diagnostic logging facility has started receiving excessive&lt;BR /&gt;   errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;   until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;   If the DEMLOG daemon is not active, use the DIAGSYSTEM command&lt;BR /&gt;   in SYSDIAG to start it.&lt;BR /&gt;   If the DEMLOG daemon is active, use the LOGTOOL utility in SYSDIAG&lt;BR /&gt;   to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;&lt;BR /&gt;SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192,&lt;BR /&gt;        blkno: 32, sectno: 64, offset: 32768, bcount: 8192.&lt;BR /&gt;&lt;BR /&gt;SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192,&lt;BR /&gt;        blkno: 32, sectno: 64, offset: 32768, bcount: 8192.&lt;BR /&gt;4/0/3.2 tgt&lt;BR /&gt;4/0/3.2.0 sdis</description>
      <pubDate>Fri, 15 Feb 2002 15:58:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665698#M49463</guid>
      <dc:creator>Mike_21</dc:creator>
      <dc:date>2002-02-15T15:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665699#M49464</link>
      <description>Mike,&lt;BR /&gt;&lt;BR /&gt;Check /var/adm/syslog/syslog.log, see if any specific errors are appearing there as well as 'dmesg'.&lt;BR /&gt;&lt;BR /&gt;if so, look for possible 'lbolt' errors, which can be resolved to a Disk Device Name /dev/dsk/c1t2d3. Resolve this device to a SCSI address using 'ioscan -fn'.&lt;BR /&gt;&lt;BR /&gt;Multiple failures can indicate a bad SCSI Card (as I just found out today).&lt;BR /&gt;&lt;BR /&gt;Share and Enjoy! Ian Dennison</description>
      <pubDate>Fri, 15 Feb 2002 16:02:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665699#M49464</guid>
      <dc:creator>Ian Dennison_1</dc:creator>
      <dc:date>2002-02-15T16:02:05Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665700#M49465</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There are some hardware errors. Use STM for checking all your hardwares.&lt;BR /&gt;&lt;BR /&gt;See this for help:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_qik.pdf" target="_blank"&gt;http://www.docs.hp.com/hpux/onlinedocs/diag/stm/stm_qik.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Shiju&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Feb 2002 16:09:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665700#M49465</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-02-15T16:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665701#M49466</link>
      <description>Hi Mike,&lt;BR /&gt;&lt;BR /&gt;Check your disk at /dev/dsk/c2t2d0. Seems like this might be giving problem.&lt;BR /&gt;&lt;BR /&gt;hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Feb 2002 16:12:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665701#M49466</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-02-15T16:12:56Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665702#M49467</link>
      <description>Sanjay,&lt;BR /&gt;Usually /dev/dsk/c2t2d0 is the cdrom, do you think that could cause a slow bdf? Possibly if it was mounted at the time...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;C</description>
      <pubDate>Fri, 15 Feb 2002 16:20:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665702#M49467</guid>
      <dc:creator>Craig Rants</dc:creator>
      <dc:date>2002-02-15T16:20:23Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665703#M49468</link>
      <description>HI Mike&lt;BR /&gt;Sanjay has it -- you have a disk with problems.&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Fri, 15 Feb 2002 16:21:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665703#M49468</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2002-02-15T16:21:18Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665704#M49469</link>
      <description>Hi Craig,&lt;BR /&gt;&lt;BR /&gt;I just decoded the device that is giving problem,&lt;BR /&gt;&lt;BR /&gt;SCSI: Async write error -- dev: b 31 0x022000, errno: 16, resid: 8192, &lt;BR /&gt;&lt;BR /&gt;0x -&amp;gt; Major No.&lt;BR /&gt;02 -&amp;gt; Controller / bus&lt;BR /&gt;2 --&amp;gt; Target device&lt;BR /&gt;0 --&amp;gt; Lun No.  &lt;BR /&gt;00 -&amp;gt; Flags&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Feb 2002 17:59:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665704#M49469</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-02-15T17:59:05Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665705#M49470</link>
      <description>Sanjay,&lt;BR /&gt;I know how you decoded it, I am just bring up the issue of a possible cdrom and will it cause the same problems as a hard disk. Seeing as most disks are on different controllers and buses than a cdrom, what would the implications be?&lt;BR /&gt;&lt;BR /&gt;C</description>
      <pubDate>Fri, 15 Feb 2002 18:07:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665705#M49470</guid>
      <dc:creator>Craig Rants</dc:creator>
      <dc:date>2002-02-15T18:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665706#M49471</link>
      <description>hi Craig,&lt;BR /&gt;&lt;BR /&gt;I cannot say anything about cdrom being at that address. I have a system where my cdrom is at c7t2d0. We can say anything about cdrom being at that place with certainity only after looking at the ioscan output. &lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sanjay&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Feb 2002 18:12:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665706#M49471</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-02-15T18:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg errors and disks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665707#M49472</link>
      <description>Hi Craig,&lt;BR /&gt;&lt;BR /&gt;I'm sorry i didn't answer your question fully. I don't see any reason why a cdrom mounted should interfere with the bdf command. I have not seen something like that.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;Sanjay&lt;BR /&gt;</description>
      <pubDate>Fri, 15 Feb 2002 18:14:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-errors-and-disks/m-p/2665707#M49472</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-02-15T18:14:56Z</dc:date>
    </item>
  </channel>
</rss>

