<?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: I/O Error in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753130#M835406</link>
    <description>&lt;BR /&gt;Youve had a hardware/SCSI error to some remote disk or tape device. Its nothing too serious - unless youre getting more of them logged all the time ?&lt;BR /&gt;&lt;BR /&gt;Anyway, its very difficult from your output to find the device which probably caused it. The best tool to use is LOGTOOL which you run from xstm (OnlineDiag diagnostic software - which you should have installed). Run xstm then go to tool -&amp;gt; utility -&amp;gt; logtool  and from logtool display the formatted log or raw log and this will show all errors and which devices logged them which should uncover your troublesome device. Diagnosing hardware problems like this is a specialist task, you should probably get HP to dialin to view the logs (if possible) or save the raw log from logtool above and email it to HP (response centre) to get an expert to analyse for you.&lt;BR /&gt;</description>
    <pubDate>Thu, 27 Jun 2002 08:15:17 GMT</pubDate>
    <dc:creator>Stefan Farrelly</dc:creator>
    <dc:date>2002-06-27T08:15:17Z</dc:date>
    <item>
      <title>I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753129#M835405</link>
      <description>HI!&lt;BR /&gt;what is it mean?&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix: SCSI: Unhandled interrupt -- lbolt: 35117, dev: cb&lt;BR /&gt;010000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:           lbp-&amp;gt;state: a0&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:           lbp-&amp;gt;offset: ffffffff&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:           lbp-&amp;gt;uPhysScript: 480000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:   From most recent interrupt:&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:           ISTAT: 0a, SIST0: 81, SIST1: 00, DSTAT:&lt;BR /&gt;80, DSPS: 00680b80&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:   NCR chip register access history (most recent la&lt;BR /&gt;st): 183 accesses&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, DCMDDBC: 0f000001&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, SBCL: a2&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, DFIFO: 01&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, SSTAT1: 00&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, SSTAT2: 02&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  3, DSP&amp;lt;-00480058&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                 18, ISTAT: 09&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  2, DSTAT: 84&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  2, DSPS: 00000001&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  1, SCRATCH: ff001000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  2, DSP&amp;lt;-00480080&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:               3413, ISTAT: 0a&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:                  2, SSTAT0: 81&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    04:  SOCL:     01    SODL:     00    SXFER:&lt;BR /&gt;08    SCID:     80&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    08:  SBCL:     a3    SBDL:     00    SIDL:&lt;BR /&gt;08    SFBR:     00&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    0c:  SSTAT2:   03    SSTAT1:   01    SSTAT0:&lt;BR /&gt;00    DSTAT:    80&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    10:  DSA:      00000000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    14:  CTEST3:   02    CTEST2:   21    CTEST1:&lt;BR /&gt;f0    CTEST0:   51&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    18:  CTEST7:   00    CTEST6:   3c    CTEST5:&lt;BR /&gt;00    CTEST4:   00&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    1c:  TEMP:     00400000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    20:  LCRC:     53    CTEST8:   20    ISTAT:&lt;BR /&gt;0a    DFIFO:    55&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    24:  DCMDDBC:  09000055&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    28:  DNAD:     00680bab&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    2c:  DSP:      00500008&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    30:  DSPS:     00680b80&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    34:  SCRATCH:  ff001000&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    38:  DCNTL:    01    DWT:      00    DIEN:&lt;BR /&gt;7f    DMODE:    c0&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:    3c:  ADDER:    00b80b88&lt;BR /&gt;Jun 26 22:02:22 haksa vmunix:&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:   NCR chip register access history (most recent la&lt;BR /&gt;st): 130 accesses&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, SBCL: a2&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, DFIFO: 01&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, SSTAT1: 00&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, SSTAT2: 02&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  9, DSP&amp;lt;-00480058&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                 19, ISTAT: 09&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  3, DSTAT: 84&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  2, DSPS: 00000001&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, SCRATCH: ff001020&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  4, DSP&amp;lt;-00480080&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                 17, ISTAT&amp;lt;-20&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:               3387, ISTAT: 2a&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  2, SSTAT0: 01&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  3, DSTAT: 80&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  1, DSPS: 07f80f00&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:                  2, SCRATCH: ff001020&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:   lsp: 2759000&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:           bp-&amp;gt;b_dev: cb011000&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:           scb-&amp;gt;io_id: 10000e0&lt;BR /&gt;Jun 26 22:04:22 haksa vmunix:           scb-&amp;gt;cdb: 12 00 00 00 80 00&lt;BR /&gt;&lt;BR /&gt;I'm serious...&lt;BR /&gt;Please... I wait your answer&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Jun 2002 08:05:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753129#M835405</guid>
      <dc:creator>Kwang-cheong , Seo</dc:creator>
      <dc:date>2002-06-27T08:05:32Z</dc:date>
    </item>
    <item>
      <title>Re: I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753130#M835406</link>
      <description>&lt;BR /&gt;Youve had a hardware/SCSI error to some remote disk or tape device. Its nothing too serious - unless youre getting more of them logged all the time ?&lt;BR /&gt;&lt;BR /&gt;Anyway, its very difficult from your output to find the device which probably caused it. The best tool to use is LOGTOOL which you run from xstm (OnlineDiag diagnostic software - which you should have installed). Run xstm then go to tool -&amp;gt; utility -&amp;gt; logtool  and from logtool display the formatted log or raw log and this will show all errors and which devices logged them which should uncover your troublesome device. Diagnosing hardware problems like this is a specialist task, you should probably get HP to dialin to view the logs (if possible) or save the raw log from logtool above and email it to HP (response centre) to get an expert to analyse for you.&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Jun 2002 08:15:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753130#M835406</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2002-06-27T08:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753131#M835407</link>
      <description>Hi, you might have a look at the latest patches for your OS.&lt;BR /&gt;Secondly, read &lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xbfdffef4d250d611abdb0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xbfdffef4d250d611abdb0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt; of Stephen, who had a similar problem, i think..&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ceesjan</description>
      <pubDate>Thu, 27 Jun 2002 10:38:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753131#M835407</guid>
      <dc:creator>Ceesjan van Hattum</dc:creator>
      <dc:date>2002-06-27T10:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753132#M835408</link>
      <description>I agree about it being a timeout on a disk.  Looking at dev=cb010000 it looks like the disk at /dev/dsk/c1t0d0 caused the lbolt.  I would try the following:&lt;BR /&gt;1: Do a diskinfo on the disk to make sure it is reporting size and firmware revision correctly.&lt;BR /&gt;2: Change the timeout on the disk to 180 using pvchange -t 180&lt;BR /&gt;3: Verify termination on the path.&lt;BR /&gt;4: If the problem doesn't change check the disk and controller for bus 1 (c1) for errors in logtool through the utilities in mstm.  If there are many you may have a failing disk or controller and will want to call for service.&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Jun 2002 13:33:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753132#M835408</guid>
      <dc:creator>barrett cooper</dc:creator>
      <dc:date>2002-06-28T13:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753133#M835409</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Looks like a scsi disk problem,&lt;BR /&gt;&lt;BR /&gt;dev cb010000 --&amp;gt; c1t0d0&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Jun 2002 14:01:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753133#M835409</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-06-28T14:01:18Z</dc:date>
    </item>
    <item>
      <title>Re: I/O Error</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753134#M835410</link>
      <description>Thanks your answer.&lt;BR /&gt;This problem is Terminator.&lt;BR /&gt;&lt;BR /&gt;Thank you.</description>
      <pubDate>Mon, 01 Jul 2002 11:57:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/i-o-error/m-p/2753134#M835410</guid>
      <dc:creator>Kwang-cheong , Seo</dc:creator>
      <dc:date>2002-07-01T11:57:34Z</dc:date>
    </item>
  </channel>
</rss>

