<?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: problem rebuilding failed drive in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466153#M440</link>
    <description>Yes I have seen this problem!! I just resolved this on a proliant 5500 and resolution is not what you want to here. You are going to wipe the array and reconfigure it. So I would suggest creating a recent backup and then restore it after it have been fixed.</description>
    <pubDate>Thu, 21 Dec 2000 00:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2000-12-21T00:00:00Z</dc:date>
    <item>
      <title>problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466149#M436</link>
      <description>the server in question is a 5500. Drive 0 in the array failed and it was replaced. &lt;BR /&gt;the server has 4 hard drives configured in RAID 5 and two logical drives are configured in the array. &lt;BR /&gt;After the drive was replaced it would start to rebuild the first logical drive and stop at 5% and would rebuilt the second logical drive. If yoou use ADU it report thet the drive is QUEUED for rebuilt but after 2 days nothing.  &lt;BR /&gt;Ran the array config. utility and reports the same. I even replaced the drive again and it did the same thing.  &lt;BR /&gt;Replaced the controller with another one and still it refuses to rebuilt the first logical drive. &lt;BR /&gt; &lt;BR /&gt;Have anyone seen anything like it?</description>
      <pubDate>Tue, 21 Nov 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466149#M436</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-11-21T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466150#M437</link>
      <description>which controller are you using? Does it have the latest firmware (4.44 I blieve)? what is the cache policy set for? what is your rebuild priority set to on the controller?  &lt;BR /&gt;  &lt;BR /&gt;Todd Hayward MCSE, ASE</description>
      <pubDate>Wed, 22 Nov 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466150#M437</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-11-22T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466151#M438</link>
      <description>Smart-2/p Version 4.32 &lt;BR /&gt;Also tried upgrading to a newer controller Smart 2DH &lt;BR /&gt;Tried all 3 setting for rebuild and no difference.</description>
      <pubDate>Wed, 22 Nov 2000 00:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466151#M438</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-11-22T00:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466152#M439</link>
      <description>Try  upgrading  the firmware on the other drives in the Array .</description>
      <pubDate>Wed, 20 Dec 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466152#M439</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-12-20T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466153#M440</link>
      <description>Yes I have seen this problem!! I just resolved this on a proliant 5500 and resolution is not what you want to here. You are going to wipe the array and reconfigure it. So I would suggest creating a recent backup and then restore it after it have been fixed.</description>
      <pubDate>Thu, 21 Dec 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466153#M440</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-12-21T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem rebuilding failed drive</title>
      <link>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466154#M441</link>
      <description>Another thing. This is caused by other drives in the array having logged hard errors on them. If you check the ADU or CIM you will find this out.   &lt;BR /&gt;  &lt;BR /&gt;This is to Compaq. Roger I a compaq eng. and I have been seeing this often in the support forum am if I were you I would have this escalated to your eng. department. The firmware on the controllers needs to be either less or more inteligent and should still be able to rebuild thies raidsets.   &lt;BR /&gt;Thanks   &lt;BR /&gt;Mike</description>
      <pubDate>Thu, 21 Dec 2000 00:00:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/problem-rebuilding-failed-drive/m-p/2466154#M441</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-12-21T00:00:01Z</dc:date>
    </item>
  </channel>
</rss>

