<?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: MSA20 RAID6 - Code 776 - Ready for Recovery in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/msa20-raid6-code-776-ready-for-recovery/m-p/4624631#M34892</link>
    <description>Hi Ross,&lt;BR /&gt;&lt;BR /&gt;Can you look at the physical layout and confirm the target selections in ACU?&lt;BR /&gt;&lt;BR /&gt;The map looks weird.&lt;BR /&gt;&lt;BR /&gt;However, it looks like there might have been 3 drives failing at some point, which may indicate a recreate/restore is needed. Drives 1:1 &amp;amp; 1:5 reported Hot-plug start failures. 1:3 is reporting hard read errors, but according to map layout 1:3 isn't part of the configuration, 3 of the target are on the MSA1500, and the MSA1500cs has wrong target status on several drives indicating a possible conflict.&lt;BR /&gt;&lt;BR /&gt;Unit Flags                      Status   &lt;BR /&gt;                                        ------------------------------- -------- &lt;BR /&gt;                                        Rebuild Aborted From Read Error Critical &lt;BR /&gt;&lt;BR /&gt;Physical Drives                      0x0005&lt;BR /&gt;   Assigned Drives                      0x0005&lt;BR /&gt;   Fault Tolerance Mode                 6 (0x0005)&lt;BR /&gt;   Drives Consumed For Fault Tolerance  0x0002&lt;BR /&gt;   Big Blocks In Logical Drive          0x00000000aea62030&lt;BR /&gt;   Block Size                           512 Bytes Per Block (0x0200)&lt;BR /&gt;   Number Of Parity Groups              0x00&lt;BR /&gt;   Drive Param Table                    Max Cylinders Max Heads Translation Signature Phys Sectors Per Track Pre Comp Cylinder Max ECC Burst Drive Control Max Physical Cylinders Max Physical Heads Landing Zone Sectors Per Track Checksum &lt;BR /&gt;                                        ------------- --------- --------------------- ---------------------- ----------------- ------------- ------------- ---------------------- ------------------ ------------ ----------------- -------- &lt;BR /&gt;                                        0xffff        0xff      0x00                  0x00                   0xffff            0x00          0x08          0x0000                 0x00               0xffff       0x20              0x9c     &lt;BR /&gt;&lt;BR /&gt;   Drive Assignment Map                 Device                Status        &lt;BR /&gt;                                        --------------------- ------------- &lt;BR /&gt;                                        Physical Drive 1:1    Informational &lt;BR /&gt;                                        Physical Drive 1:2    Informational &lt;BR /&gt;                                        Physical Drive 1I:1:6 Informational &lt;BR /&gt;                                        Physical Drive 1I:1:5 Informational &lt;BR /&gt;                                        Physical Drive 2I:1:4 Informational &lt;BR /&gt;&lt;BR /&gt;I think it lost the configuration or auto assigned drives that might have been flagged as hot spares?&lt;BR /&gt;&lt;BR /&gt;I think it should be this:&lt;BR /&gt;&lt;BR /&gt;1:1&lt;BR /&gt;1:2&lt;BR /&gt;1:3&lt;BR /&gt;1:4&lt;BR /&gt;1:5&lt;BR /&gt;&lt;BR /&gt;You might have to replace 1:3 due to the hard read errors.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;</description>
    <pubDate>Tue, 27 Apr 2010 19:13:26 GMT</pubDate>
    <dc:creator>cnb</dc:creator>
    <dc:date>2010-04-27T19:13:26Z</dc:date>
    <item>
      <title>MSA20 RAID6 - Code 776 - Ready for Recovery</title>
      <link>https://community.hpe.com/t5/disk-enclosures/msa20-raid6-code-776-ready-for-recovery/m-p/4624630#M34891</link>
      <description>We have a RAID6 array on our MSA20, containing a total of 5 500GB drives. Recently we had two of the drives fail from what appears to be a firmware issue. After upgrading the firmware on the SA6400 to 2.84 and the MSA20 to 2.08, the status on both drives changed from "MISSING" to "AVAILABLE". When we powered everything back on the Logical Drive showed a status of "(Ready for Recovery) Logical Drive 1 (1.4TB, RAID6 (ADG)) is queued for rebuilding." It has remained at this status for a couple hours now and shows no signs of actually rebuilding or recovering. I've attached the ADU report that we ran. If anyone has any ideas, please let us know.</description>
      <pubDate>Tue, 27 Apr 2010 13:14:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/msa20-raid6-code-776-ready-for-recovery/m-p/4624630#M34891</guid>
      <dc:creator>Ross Hathaway</dc:creator>
      <dc:date>2010-04-27T13:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: MSA20 RAID6 - Code 776 - Ready for Recovery</title>
      <link>https://community.hpe.com/t5/disk-enclosures/msa20-raid6-code-776-ready-for-recovery/m-p/4624631#M34892</link>
      <description>Hi Ross,&lt;BR /&gt;&lt;BR /&gt;Can you look at the physical layout and confirm the target selections in ACU?&lt;BR /&gt;&lt;BR /&gt;The map looks weird.&lt;BR /&gt;&lt;BR /&gt;However, it looks like there might have been 3 drives failing at some point, which may indicate a recreate/restore is needed. Drives 1:1 &amp;amp; 1:5 reported Hot-plug start failures. 1:3 is reporting hard read errors, but according to map layout 1:3 isn't part of the configuration, 3 of the target are on the MSA1500, and the MSA1500cs has wrong target status on several drives indicating a possible conflict.&lt;BR /&gt;&lt;BR /&gt;Unit Flags                      Status   &lt;BR /&gt;                                        ------------------------------- -------- &lt;BR /&gt;                                        Rebuild Aborted From Read Error Critical &lt;BR /&gt;&lt;BR /&gt;Physical Drives                      0x0005&lt;BR /&gt;   Assigned Drives                      0x0005&lt;BR /&gt;   Fault Tolerance Mode                 6 (0x0005)&lt;BR /&gt;   Drives Consumed For Fault Tolerance  0x0002&lt;BR /&gt;   Big Blocks In Logical Drive          0x00000000aea62030&lt;BR /&gt;   Block Size                           512 Bytes Per Block (0x0200)&lt;BR /&gt;   Number Of Parity Groups              0x00&lt;BR /&gt;   Drive Param Table                    Max Cylinders Max Heads Translation Signature Phys Sectors Per Track Pre Comp Cylinder Max ECC Burst Drive Control Max Physical Cylinders Max Physical Heads Landing Zone Sectors Per Track Checksum &lt;BR /&gt;                                        ------------- --------- --------------------- ---------------------- ----------------- ------------- ------------- ---------------------- ------------------ ------------ ----------------- -------- &lt;BR /&gt;                                        0xffff        0xff      0x00                  0x00                   0xffff            0x00          0x08          0x0000                 0x00               0xffff       0x20              0x9c     &lt;BR /&gt;&lt;BR /&gt;   Drive Assignment Map                 Device                Status        &lt;BR /&gt;                                        --------------------- ------------- &lt;BR /&gt;                                        Physical Drive 1:1    Informational &lt;BR /&gt;                                        Physical Drive 1:2    Informational &lt;BR /&gt;                                        Physical Drive 1I:1:6 Informational &lt;BR /&gt;                                        Physical Drive 1I:1:5 Informational &lt;BR /&gt;                                        Physical Drive 2I:1:4 Informational &lt;BR /&gt;&lt;BR /&gt;I think it lost the configuration or auto assigned drives that might have been flagged as hot spares?&lt;BR /&gt;&lt;BR /&gt;I think it should be this:&lt;BR /&gt;&lt;BR /&gt;1:1&lt;BR /&gt;1:2&lt;BR /&gt;1:3&lt;BR /&gt;1:4&lt;BR /&gt;1:5&lt;BR /&gt;&lt;BR /&gt;You might have to replace 1:3 due to the hard read errors.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Apr 2010 19:13:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/msa20-raid6-code-776-ready-for-recovery/m-p/4624631#M34892</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2010-04-27T19:13:26Z</dc:date>
    </item>
  </channel>
</rss>

