<?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: 431 extension/expansion workaround? in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/431-extension-expansion-workaround/m-p/2527212#M1871</link>
    <description>I have the same situation. I tried the workaround you described. Don't worry, failing and replacing on line the drive is a safe job. But when I tried to expand the array, ACU is still saying that it cannot expand it because it was made with a different controller!! ARGH. &lt;BR /&gt;Now I'm gonna call Compaq support...</description>
    <pubDate>Sun, 20 May 2001 23:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2001-05-20T23:00:00Z</dc:date>
    <item>
      <title>431 extension/expansion workaround?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/431-extension-expansion-workaround/m-p/2527211#M1870</link>
      <description>I have a Proliant 1600 Server 384 meg ram.  Presently running a 221 raid controller.  All upgraded with SS 4.80  &lt;BR /&gt;Raid 5 array, 3 drives.  wideultra 2. &lt;BR /&gt; &lt;BR /&gt;On advice from tech support we purchased a 431 controller as an upgrade as it supported both array expansion and logical drive extension.  &lt;BR /&gt;We have since come to find out that the initial array must have been created on the 431 raid controller to allow these features.  &lt;BR /&gt;In speaking with some support people, we have a proposed work around for this type of situation.  &lt;BR /&gt;Backups should be done as advised by Compaq.  &lt;BR /&gt;1. install the 431 controller and drivers.  &lt;BR /&gt;2. remove the 221 controller.  &lt;BR /&gt;3. attach the raid array from the 221 controller to the 431 controller.  &lt;BR /&gt;4. fail one of the drives in the array.  &lt;BR /&gt;    This is the proposed part  &lt;BR /&gt;5. insert new drive, the 431 will rebuild it as a 431 raid array would have been built on a new array, not as a 221 controller (the old controller)  &lt;BR /&gt;  &lt;BR /&gt;Since it cannot have only one drive with this configuration, all the drives in the array will be updated to have an additional 5 meg each reserved for the Raid controller.  This is made possible because the new drive has enough room to get the ball rolling for the configurations.  I am told the controller is smart enough to do the job and modify the rest of the drives to allow the configuration to be complete and theroretically error free.  &lt;BR /&gt;  &lt;BR /&gt;Please, if anyone has any information or tried this procedure, let me know.  &lt;BR /&gt;  &lt;BR /&gt;John</description>
      <pubDate>Thu, 10 May 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/431-extension-expansion-workaround/m-p/2527211#M1870</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-05-10T23:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: 431 extension/expansion workaround?</title>
      <link>https://community.hpe.com/t5/disk-enclosures/431-extension-expansion-workaround/m-p/2527212#M1871</link>
      <description>I have the same situation. I tried the workaround you described. Don't worry, failing and replacing on line the drive is a safe job. But when I tried to expand the array, ACU is still saying that it cannot expand it because it was made with a different controller!! ARGH. &lt;BR /&gt;Now I'm gonna call Compaq support...</description>
      <pubDate>Sun, 20 May 2001 23:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/431-extension-expansion-workaround/m-p/2527212#M1871</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-05-20T23:00:00Z</dc:date>
    </item>
  </channel>
</rss>

