<?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: HHBA1500 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/hhba1500/m-p/3046641#M9451</link>
    <description>Hi James,&lt;BR /&gt;&lt;BR /&gt;the ID=9 SCSI timeout in the NT systemlog can be due to different reasons like :&lt;BR /&gt;&lt;BR /&gt;- high disk I/O and at a certain time the reply from the array came to slow, so the driver reports a timeout. This is no real issue if it does not occur frequently.&lt;BR /&gt;&lt;BR /&gt;- a H/W problem in the HBA, GBIC (electrical to optical converter), fibre cable , fibre hub or the RS12FC controller itself.&lt;BR /&gt;&lt;BR /&gt;Check the log back till the oldest entry and see if this issue occured before.&lt;BR /&gt;GBIC's i.e. when becoming older might have a problem with the laser power becoming to low and this can result in such an error.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For what you noticed after the reboot, if all s/w and utilities (fc array assistant and toptools agents) are installed you should have seen entries in the Windows eventlog about failed drives prior to that reboot (unless the disk failure happened to occured at the power off/on of the array)&lt;BR /&gt;&lt;BR /&gt;You could check the fc array log file which is a text file named fa1cl.log to see what happened in the RS12FC.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;regards, Kris&lt;BR /&gt;</description>
    <pubDate>Tue, 12 Aug 2003 15:06:30 GMT</pubDate>
    <dc:creator>kris rombauts</dc:creator>
    <dc:date>2003-08-12T15:06:30Z</dc:date>
    <item>
      <title>HHBA1500</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hhba1500/m-p/3046640#M9450</link>
      <description>The device \Device\ScsiPort4 did not respond&lt;BR /&gt;within the timeout period&lt;BR /&gt;Event ID: 9&lt;BR /&gt;Source HHBA5100&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Have a FC Rack Storage 12 -Fiber&lt;BR /&gt;The above caused problems on the system. Rebooted the system after powering it down. Next it looked like it started to rebuild on the spare drive but there was not indication of drive failure.  Now another drive looks like&lt;BR /&gt;it has failed.  Any ideas about what the problem may be with the fiber array?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Mon, 11 Aug 2003 18:45:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hhba1500/m-p/3046640#M9450</guid>
      <dc:creator>james gould</dc:creator>
      <dc:date>2003-08-11T18:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: HHBA1500</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hhba1500/m-p/3046641#M9451</link>
      <description>Hi James,&lt;BR /&gt;&lt;BR /&gt;the ID=9 SCSI timeout in the NT systemlog can be due to different reasons like :&lt;BR /&gt;&lt;BR /&gt;- high disk I/O and at a certain time the reply from the array came to slow, so the driver reports a timeout. This is no real issue if it does not occur frequently.&lt;BR /&gt;&lt;BR /&gt;- a H/W problem in the HBA, GBIC (electrical to optical converter), fibre cable , fibre hub or the RS12FC controller itself.&lt;BR /&gt;&lt;BR /&gt;Check the log back till the oldest entry and see if this issue occured before.&lt;BR /&gt;GBIC's i.e. when becoming older might have a problem with the laser power becoming to low and this can result in such an error.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;For what you noticed after the reboot, if all s/w and utilities (fc array assistant and toptools agents) are installed you should have seen entries in the Windows eventlog about failed drives prior to that reboot (unless the disk failure happened to occured at the power off/on of the array)&lt;BR /&gt;&lt;BR /&gt;You could check the fc array log file which is a text file named fa1cl.log to see what happened in the RS12FC.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;regards, Kris&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Aug 2003 15:06:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hhba1500/m-p/3046641#M9451</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2003-08-12T15:06:30Z</dc:date>
    </item>
  </channel>
</rss>

