<?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: Smart Array 3200 error in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986811#M8616</link>
    <description>ok just rebooted for the third time today and now 2nd hard drive has very bright failure light on front.  &lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;dennis</description>
    <pubDate>Tue, 24 Jun 2003 20:59:36 GMT</pubDate>
    <dc:creator>Dennis Stuart</dc:creator>
    <dc:date>2003-06-24T20:59:36Z</dc:date>
    <item>
      <title>Smart Array 3200 error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986808#M8613</link>
      <description>Our Proliant ML570 server (Win2K svr), when booting, pauses (and requires pressing F1 to continue) when checking the SmartArray 3200 controller.  At that time, it displays the error "1787 Interim recovery mode".  After pressing F1, no more errors come up, and the server boots/runs fine.  Any ideas?</description>
      <pubDate>Mon, 02 Jun 2003 19:14:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986808#M8613</guid>
      <dc:creator>Jason Krampien</dc:creator>
      <dc:date>2003-06-02T19:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Smart Array 3200 error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986809#M8614</link>
      <description>Hello:&lt;BR /&gt;&lt;BR /&gt;"1787 - Interim recovery mode" indicates you have a failed hard drive in your array which has not yet been replaced.&lt;BR /&gt;&lt;BR /&gt;The server will continue to stop at F1 until the condition is repaired, or by going into the BIOS to disable the F1 boot-up prompt.&lt;BR /&gt;&lt;BR /&gt;In this case, you should check your array for a failed hard drive.  Sounds like you might be running with no fault-tolerance right now.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Janine</description>
      <pubDate>Tue, 03 Jun 2003 13:16:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986809#M8614</guid>
      <dc:creator>Janine Bertolo</dc:creator>
      <dc:date>2003-06-03T13:16:12Z</dc:date>
    </item>
    <item>
      <title>Re: Smart Array 3200 error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986810#M8615</link>
      <description>I am getting the same message.  I started to  receive a message regarding device\scsiport0 did not respond within the timeout period first.  When I rebooted, I got the post error messages listed above.  It also shows in the event log that the drive in slot 2, port 1, bay four status has a new status of 3.  Another message lists another drive with a status of 7.  I do not have any indicator on the drives that they are failing.  Is this status supposed to tell me the health of the drive?</description>
      <pubDate>Tue, 24 Jun 2003 20:53:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986810#M8615</guid>
      <dc:creator>Dennis Stuart</dc:creator>
      <dc:date>2003-06-24T20:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Smart Array 3200 error</title>
      <link>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986811#M8616</link>
      <description>ok just rebooted for the third time today and now 2nd hard drive has very bright failure light on front.  &lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;dennis</description>
      <pubDate>Tue, 24 Jun 2003 20:59:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/smart-array-3200-error/m-p/2986811#M8616</guid>
      <dc:creator>Dennis Stuart</dc:creator>
      <dc:date>2003-06-24T20:59:36Z</dc:date>
    </item>
  </channel>
</rss>

