<?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: RAID 1+0 in MSA1500 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/raid-1-0-in-msa1500/m-p/4591626#M43100</link>
    <description>All logical drives appear in OK status, no failures. No errors on disks for years.&lt;BR /&gt;&lt;BR /&gt;The only hardware issue are the batteries on the MSA20:&lt;BR /&gt;&lt;BR /&gt;Array accelerator status:&lt;BR /&gt;Temporarily disabled&lt;BR /&gt;Batteries are not fully charged&lt;BR /&gt;Battery pack 1 not fully charged&lt;BR /&gt;Battery pack 2 not fully charged&lt;BR /&gt;&lt;BR /&gt;The fact that you can mount the LUN and see directories means that there's a filesystem on it. There's no way any hardware failure can alter a LUN in a way that it only deletes files and not directories.&lt;BR /&gt;&lt;BR /&gt;I don't know what filesystem is being used on that LUN, and the MSA1500 does not know either and does not care. Try with a file recovery utility because probably the files alre already on the disks, but filesystem has been corrupted.</description>
    <pubDate>Mon, 01 Mar 2010 10:08:09 GMT</pubDate>
    <dc:creator>Víctor Cespón</dc:creator>
    <dc:date>2010-03-01T10:08:09Z</dc:date>
    <item>
      <title>RAID 1+0 in MSA1500</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/raid-1-0-in-msa1500/m-p/4591625#M43099</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a MSA1500 with 3 RAID 5 and one RAID 1+0 logical drives. Yesterday we had some kind of electrical power glitch that affected it; drives remained mounted but any access was impossible (I/O error).&lt;BR /&gt;&lt;BR /&gt;We rebooted the node and rebooted MSA1500. Everything seems OK (all DSA20 disks are green as the MSA LEDs).&lt;BR /&gt;&lt;BR /&gt;RAID 5 ones work fine. RAID 1+0 can be mounted and we are able to see the former directories but we have no info in them.&lt;BR /&gt;&lt;BR /&gt;I append the ADU output where some errors can be seen. &lt;BR /&gt;&lt;BR /&gt;Are those errors only logic? I mean Â¿Can it be solved just recreating the volumen/logical drive?&lt;BR /&gt;&lt;BR /&gt;Is there a way to recover the stored information?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Feb 2010 13:32:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/raid-1-0-in-msa1500/m-p/4591625#M43099</guid>
      <dc:creator>Ángel Gutiérrez Rodrígu</dc:creator>
      <dc:date>2010-02-26T13:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: RAID 1+0 in MSA1500</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/raid-1-0-in-msa1500/m-p/4591626#M43100</link>
      <description>All logical drives appear in OK status, no failures. No errors on disks for years.&lt;BR /&gt;&lt;BR /&gt;The only hardware issue are the batteries on the MSA20:&lt;BR /&gt;&lt;BR /&gt;Array accelerator status:&lt;BR /&gt;Temporarily disabled&lt;BR /&gt;Batteries are not fully charged&lt;BR /&gt;Battery pack 1 not fully charged&lt;BR /&gt;Battery pack 2 not fully charged&lt;BR /&gt;&lt;BR /&gt;The fact that you can mount the LUN and see directories means that there's a filesystem on it. There's no way any hardware failure can alter a LUN in a way that it only deletes files and not directories.&lt;BR /&gt;&lt;BR /&gt;I don't know what filesystem is being used on that LUN, and the MSA1500 does not know either and does not care. Try with a file recovery utility because probably the files alre already on the disks, but filesystem has been corrupted.</description>
      <pubDate>Mon, 01 Mar 2010 10:08:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/raid-1-0-in-msa1500/m-p/4591626#M43100</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2010-03-01T10:08:09Z</dc:date>
    </item>
  </channel>
</rss>

