<?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: Proliant DL 385 G5p array problem in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994921#M135147</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i titally agree with Ernsto,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;before doing anything else, start the server once WITHOUT disks, this will reset the cached info.&lt;/P&gt;&lt;P&gt;then use the ACU utility on the Smart Start 8.7 to repair the relation of the RAID .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sometimes i change the whole smart array, all you need to do is repair, and this is the great advantage of the HW RAID rather than the SW RAID&lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2013 07:53:27 GMT</pubDate>
    <dc:creator>Hazem Bahgat</dc:creator>
    <dc:date>2013-03-14T07:53:27Z</dc:date>
    <item>
      <title>Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5988379#M135027</link>
      <description>&lt;P&gt;The server in questions has a Smart Array P400 controller with 2 250GB SATA drives running a mirrored configuration.&amp;nbsp; There was a power outage that took out of the drives and now the slot the drive was is is no longer working.&amp;nbsp; The drive was replaced and put into a different slot, but there does not appear to be any way to rebuild the mirror with the drive in a different slot using the Array Configuration Utility.&amp;nbsp; Any insight on how to fix this issue would be appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2013 15:55:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5988379#M135027</guid>
      <dc:creator>jalbrecht-ts</dc:creator>
      <dc:date>2013-03-08T15:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994073#M135117</link>
      <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;a failed drive will be rebuilt ONLY in its original position.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if the slot does not work anymore there is no way to initialize a rebuild.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this is why you should never physically move an array with a failed drive.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sorry&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;ernesto (germany)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2013 16:52:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994073#M135117</guid>
      <dc:creator>ernst limbrunner</dc:creator>
      <dc:date>2013-03-13T16:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994083#M135119</link>
      <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;as you have only 2 drives you might try the following trick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;switch both sas cables&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this will turn position 5 into 1, 6 into 2, 7 into 3 and 8 into 4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;now put the surviving disk in its new corresponding position.&lt;/P&gt;&lt;P&gt;put the new drive into its corresponding position (but only after the OS has completely booted !!)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in a raid 1 configuration never put a replacement drive into the cage when the server is powered off.&lt;/P&gt;&lt;P&gt;always wait until the oS is up and running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;ernesto (germany)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2013 17:01:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994083#M135119</guid>
      <dc:creator>ernst limbrunner</dc:creator>
      <dc:date>2013-03-13T17:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994089#M135120</link>
      <description>&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;one more important thing&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;before doing anything else.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;start the server once WITHOUT disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this will reset the smart controller and the controller will read the config from the disks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;this little trick has helped many many times, when a controller or a disk was moved or replaced&lt;/P&gt;&lt;P&gt;and the array controller reported 0 logical drives.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;best regards&lt;/P&gt;&lt;P&gt;ernesto&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2013 17:08:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994089#M135120</guid>
      <dc:creator>ernst limbrunner</dc:creator>
      <dc:date>2013-03-13T17:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994345#M135125</link>
      <description>&lt;P&gt;Thanks for the response.&amp;nbsp; We will give this a try. The other thing to do I found out is replace the Backplane if the slot has gone bad.&amp;nbsp; Cost is about $150 online.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2013 21:42:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994345#M135125</guid>
      <dc:creator>jalbrecht-ts</dc:creator>
      <dc:date>2013-03-13T21:42:57Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant DL 385 G5p array problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994921#M135147</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i titally agree with Ernsto,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;before doing anything else, start the server once WITHOUT disks, this will reset the cached info.&lt;/P&gt;&lt;P&gt;then use the ACU utility on the Smart Start 8.7 to repair the relation of the RAID .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;sometimes i change the whole smart array, all you need to do is repair, and this is the great advantage of the HW RAID rather than the SW RAID&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2013 07:53:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-dl-385-g5p-array-problem/m-p/5994921#M135147</guid>
      <dc:creator>Hazem Bahgat</dc:creator>
      <dc:date>2013-03-14T07:53:27Z</dc:date>
    </item>
  </channel>
</rss>

