<?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: HostRAID - Drive upgrade problem in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332443#M29671</link>
    <description>&amp;gt; the block address translation for 80GB has to be maintained &lt;BR /&gt;Maybe true on this embedded controller which is low end/limited functionality. What you did is normal and works transparently with smartarray cotrollers and larger array systems. &lt;BR /&gt;&lt;BR /&gt;Have you rebooted the server (and power off) since the drive replacement? These embeded controllers have ROM based (BIOS) configuration interfaces and may rebooting (with power off) might help.&lt;BR /&gt;&lt;BR /&gt;Otherwise you need to blow away the small LUN and create new larger one.</description>
    <pubDate>Wed, 07 Jan 2009 14:32:28 GMT</pubDate>
    <dc:creator>TTr</dc:creator>
    <dc:date>2009-01-07T14:32:28Z</dc:date>
    <item>
      <title>HostRAID - Drive upgrade problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332441#M29669</link>
      <description>We have an ML110 G3 server, originally installed with 2 x 80GB SATA drives in a RAID 1 configuration.&lt;BR /&gt;Drive on Port 0 was replaced with a 250GB drive and the mirror was rebuilt.&lt;BR /&gt;Drive on Port 1 was replaced with a 250GB drive and the mirror was rebuilt.&lt;BR /&gt;HP Storage manager now sees the array as follows:&lt;BR /&gt;&lt;BR /&gt;__Physical Devices &lt;BR /&gt;____Direct Attached Devices&lt;BR /&gt;______Port 0 - Optimal (232.83GB)&lt;BR /&gt;______Port 1 - Optimal (232.83GB)&lt;BR /&gt;&lt;BR /&gt;__Logical Devices &lt;BR /&gt;____Logical Drives (1)&lt;BR /&gt;______Array 1 - Optimal (74.38GB)&lt;BR /&gt;&lt;BR /&gt;The "Create logical drive" option is disabled for the controller. Is there any way we can either extend the Logical drive to use all the pace on the physical drives, or create a second logical drive, without losing the existing contents of the array?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Jan 2009 12:31:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332441#M29669</guid>
      <dc:creator>MSD</dc:creator>
      <dc:date>2009-01-06T12:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: HostRAID - Drive upgrade problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332442#M29670</link>
      <description>Hi, the problem you have is that by rebuilding an 80GB mirror to a 250GB drive the block address translation for 80GB has to be maintained so the rest of the capacity becomes inaccessible. your best option is to back up the data and create a new 250GB mirror to restore to, the addressing will then be created for the full disk capacity.</description>
      <pubDate>Wed, 07 Jan 2009 11:32:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332442#M29670</guid>
      <dc:creator>Greybeard</dc:creator>
      <dc:date>2009-01-07T11:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: HostRAID - Drive upgrade problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332443#M29671</link>
      <description>&amp;gt; the block address translation for 80GB has to be maintained &lt;BR /&gt;Maybe true on this embedded controller which is low end/limited functionality. What you did is normal and works transparently with smartarray cotrollers and larger array systems. &lt;BR /&gt;&lt;BR /&gt;Have you rebooted the server (and power off) since the drive replacement? These embeded controllers have ROM based (BIOS) configuration interfaces and may rebooting (with power off) might help.&lt;BR /&gt;&lt;BR /&gt;Otherwise you need to blow away the small LUN and create new larger one.</description>
      <pubDate>Wed, 07 Jan 2009 14:32:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332443#M29671</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2009-01-07T14:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: HostRAID - Drive upgrade problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332444#M29672</link>
      <description>Hi TTr, I think he used all of the 80GB for the LUN on the old array, the LUNs are created within the block / striped area and as the larger drive was a mirror of the smaller one there will be no addressable blocks on the rest of the drive so nowhere to put another / extended LUN.  So yes, blow it away and start again.</description>
      <pubDate>Thu, 08 Jan 2009 09:24:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332444#M29672</guid>
      <dc:creator>Greybeard</dc:creator>
      <dc:date>2009-01-08T09:24:45Z</dc:date>
    </item>
    <item>
      <title>Re: HostRAID - Drive upgrade problem</title>
      <link>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332445#M29673</link>
      <description>Thanks to you both. &lt;BR /&gt;&lt;BR /&gt;I guess you confirmed my fears that there was no easy solution to the problem. I was clutching at straws.&lt;BR /&gt;&lt;BR /&gt;The Back-up, resize, restore option has been complicated for me due to limited resources and lost media. - My problem and not one for here.</description>
      <pubDate>Thu, 08 Jan 2009 10:58:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/hostraid-drive-upgrade-problem/m-p/4332445#M29673</guid>
      <dc:creator>MSD</dc:creator>
      <dc:date>2009-01-08T10:58:43Z</dc:date>
    </item>
  </channel>
</rss>

