<?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 I/O error in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557884#M2387</link>
    <description>hi all..i have got a 12H disk array with two K-360 servers in a cluster.suddenly one volume showed I/O error when bdf is typed.then momentarily the node2 in the cluster gave the error"x controller failed" and it told couldnt access a disk at a specified address.here i have attached the dmesg output.this is an SOS.kindly suggest the possible problem.the dmesg output is of node 2.node1 dmesg output i didnt get.awaiting reply.&lt;BR /&gt;thanks in advance.&lt;BR /&gt;viks</description>
    <pubDate>Fri, 27 Jul 2001 09:11:22 GMT</pubDate>
    <dc:creator>viks</dc:creator>
    <dc:date>2001-07-27T09:11:22Z</dc:date>
    <item>
      <title>I/O error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557884#M2387</link>
      <description>hi all..i have got a 12H disk array with two K-360 servers in a cluster.suddenly one volume showed I/O error when bdf is typed.then momentarily the node2 in the cluster gave the error"x controller failed" and it told couldnt access a disk at a specified address.here i have attached the dmesg output.this is an SOS.kindly suggest the possible problem.the dmesg output is of node 2.node1 dmesg output i didnt get.awaiting reply.&lt;BR /&gt;thanks in advance.&lt;BR /&gt;viks</description>
      <pubDate>Fri, 27 Jul 2001 09:11:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557884#M2387</guid>
      <dc:creator>viks</dc:creator>
      <dc:date>2001-07-27T09:11:22Z</dc:date>
    </item>
    <item>
      <title>Re: I/O error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557885#M2388</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It looks as if one of the controllers of the autoraid failed. Because you have Alternate paths to your luns configured the kernel switches to that alternate patchs when the primary patch fails (that's why you see the switch messages). You can check the autoraid with the following commands:&lt;BR /&gt;/opt/hparray/bin/arraydsp -i&lt;BR /&gt;this will give the serial number which is needed with the next commands:&lt;BR /&gt;arraydsp -a [serialnr] # for all info&lt;BR /&gt;arraydsp -c [serialnr] # for controller info&lt;BR /&gt;&lt;BR /&gt;Check the status of the controllers. Also, if possible, check the display on the 12H itself.&lt;BR /&gt;If there are problems contact HP ...</description>
      <pubDate>Fri, 27 Jul 2001 10:50:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557885#M2388</guid>
      <dc:creator>Mark van Hassel</dc:creator>
      <dc:date>2001-07-27T10:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: I/O error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557886#M2389</link>
      <description>Did you take a look at the front panel on HP AutoRAID ?&lt;BR /&gt;Did it show nothing ?&lt;BR /&gt;&lt;BR /&gt;"Dmesg output" explained that there is a failure in the hardware path for /dev/dsk/c2t1d5 so the ownership of the LUN automatically switches to the alternate path for /dev/dsk/c3t0d5 because alternate links are configured.&lt;BR /&gt;&lt;BR /&gt;For some reason, the problem has been disappeared naturally so the ownership of the LUN for /dev/dsk/c3t0d5 switches to the primary path again.&lt;BR /&gt;&lt;BR /&gt;Dmesg shows this procedure over and over which means that there must be something wrong on AutoRAID.&lt;BR /&gt;&lt;BR /&gt;Check out controller and host bus adaptor !&lt;BR /&gt;It's a good idea to issue ARM (Array Management) commands to get a clue as follows:&lt;BR /&gt;&lt;BR /&gt;# arraydsp -i ( To get a serial number )&lt;BR /&gt;# arraydsp -a &lt;SERIAL number=""&gt;&lt;BR /&gt;# logprint -a &lt;SERIAL number=""&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;/SERIAL&gt;&lt;/SERIAL&gt;</description>
      <pubDate>Fri, 27 Jul 2001 11:22:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/i-o-error/m-p/2557886#M2389</guid>
      <dc:creator>Insu Kim</dc:creator>
      <dc:date>2001-07-27T11:22:06Z</dc:date>
    </item>
  </channel>
</rss>

