<?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: VA7400 disk failure in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968105#M8364</link>
    <description>Please attach 'armdsp -a' output and I will be able to explain you in details.&lt;BR /&gt;In your case rebuild has been completed and there's enough space for this rebuild to complete successfully and space for active hot spare. If you do not see any warnings like 'redundancy lost' then there's enough space for next rebuild. But of course, you should replace failed component ASAP to keep redundancy at initial level&lt;BR /&gt;Eugeny</description>
    <pubDate>Thu, 08 May 2003 04:13:03 GMT</pubDate>
    <dc:creator>Eugeny Brychkov</dc:creator>
    <dc:date>2003-05-08T04:13:03Z</dc:date>
    <item>
      <title>VA7400 disk failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968104#M8363</link>
      <description>Recently we had one disk failure on VA7400. Array has recovered data from redundancy, BUT - SDM gui still shows, that there are hot spares for each redundancy group. WTF ? What action is needed to allocate hot spare for failed disk ? Our VA is in autoraid mode, and using RAID0+1 right now. &lt;BR /&gt;Of course we will get new disk ASAP, but I'm worrying about the data and possible downtime ... &lt;BR /&gt;&lt;BR /&gt;Saulius</description>
      <pubDate>Thu, 08 May 2003 04:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968104#M8363</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2003-05-08T04:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 disk failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968105#M8364</link>
      <description>Please attach 'armdsp -a' output and I will be able to explain you in details.&lt;BR /&gt;In your case rebuild has been completed and there's enough space for this rebuild to complete successfully and space for active hot spare. If you do not see any warnings like 'redundancy lost' then there's enough space for next rebuild. But of course, you should replace failed component ASAP to keep redundancy at initial level&lt;BR /&gt;Eugeny</description>
      <pubDate>Thu, 08 May 2003 04:13:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968105#M8364</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-05-08T04:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 disk failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968106#M8365</link>
      <description>Actually I suspect that VA firmware reallocated data, and "made" new hot spare. Because I see in the armdsp output:&lt;BR /&gt;&lt;BR /&gt;CAPACITY USAGE&lt;BR /&gt;&lt;BR /&gt;  Total Disk Enclosures:________________2&lt;BR /&gt;&lt;BR /&gt;  Redundancy Group:_____________________1&lt;BR /&gt;    Total Disks:________________________11&lt;BR /&gt;    Total Physical Size:________________734,329 GB&lt;BR /&gt;    Allocated to Regular LUNs:__________232,1 GB&lt;BR /&gt;    Allocated as Business Copies:_______0 bytes&lt;BR /&gt;    Used as Active Hot Spare:___________66,753 GB&lt;BR /&gt;    Used for Redundancy:________________169,704 GB&lt;BR /&gt;    Unallocated (Available for LUNs):___265,77 GB&lt;BR /&gt;&lt;BR /&gt;  Redundancy Group:_____________________2&lt;BR /&gt;    Total Disks:________________________8&lt;BR /&gt;    Total Physical Size:________________534,057 GB&lt;BR /&gt;    Allocated to Regular LUNs:__________147 GB&lt;BR /&gt;    Allocated as Business Copies:_______0 bytes&lt;BR /&gt;    Used as Active Hot Spare:___________66,753 GB&lt;BR /&gt;    Used for Redundancy:________________147,86 GB&lt;BR /&gt;    Unallocated (Available for LUNs):___172,443 GB&lt;BR /&gt;&lt;BR /&gt;  Used by Non-Included Disks:___________66,757 GB</description>
      <pubDate>Thu, 08 May 2003 05:57:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968106#M8365</guid>
      <dc:creator>Saulius_1</dc:creator>
      <dc:date>2003-05-08T05:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: VA7400 disk failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968107#M8366</link>
      <description>Yes, I believe it should be this way. When disk fails, VA does rebuild, after rebuild it checks if there's a still space for active hot spare (checks unallocated space) and if there's a space, it 'eats' active hotspare space from unallocated area&lt;BR /&gt;Eugeny</description>
      <pubDate>Thu, 08 May 2003 09:59:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7400-disk-failure/m-p/2968107#M8366</guid>
      <dc:creator>Eugeny Brychkov</dc:creator>
      <dc:date>2003-05-08T09:59:17Z</dc:date>
    </item>
  </channel>
</rss>

