<?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: MSA1500 CS - Code 271 - Failed Logical Drives in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208896#M58538</link>
    <description>I was able to get around the locked state at the CLI level by issuing command "Override ACULock On".  This allowed me to run a Show Tech_Support command.  Attached is a copy of the Tech_Support report.  Is the problem, I need to assign/correct the Profile Names?</description>
    <pubDate>Wed, 18 Nov 2009 18:15:21 GMT</pubDate>
    <dc:creator>Borg8472</dc:creator>
    <dc:date>2009-11-18T18:15:21Z</dc:date>
    <item>
      <title>MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208887#M58529</link>
      <description>&lt;!--!*#--&gt;Powered-On my disk arrays and MSA1500 CS properly but ESX host servers halt loading "vsd-mount".  Upon review of attached storage via ACU, I found that 9 out of 12 logical drives failed with error "Logical drive 3 (410.2 GB, RAID5) has failed and cannot be used. All data on this logical drive has been lost. Configuration changes to this logical drive are not allowed until this problem is corrected. also, if your controller supports Expansion, Extension, or migration, these ...".  See attached snapshot.&lt;BR /&gt;&lt;BR /&gt;I do care about data on the logical drives and do not have a valid backup.  Is it possible to recovery from this error without losing data?  If Yes, how?&lt;BR /&gt;&lt;BR /&gt;I would like to call HP Technical Support on this but the MSA1500 CS is no longer under warranty.</description>
      <pubDate>Wed, 11 Nov 2009 17:16:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208887#M58529</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-11T17:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208888#M58530</link>
      <description>What do have in common the Arrays C, D, E, F, I, J, K, L and M?&lt;BR /&gt;&lt;BR /&gt;The logical unit is RAID 5 so you must have at least 2 disks failed.&lt;BR /&gt;&lt;BR /&gt;Maybe you have an MSA20 or MSA30 disconnected or failed and there are lot of disks missing.</description>
      <pubDate>Wed, 11 Nov 2009 18:04:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208888#M58530</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2009-11-11T18:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208889#M58531</link>
      <description>Looks like the only commonality amongst the logical drives is the FC SAN Switch, a (StorageWorks SAN Switch 2/4V).  All 4 MSA60 storage arrays are present, online and all disks and MSA controller reporting no failures.  All drives and disk arrays have green LEDs, no reds and no failures on MSA1500 CS Controller display.</description>
      <pubDate>Wed, 11 Nov 2009 18:32:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208889#M58531</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-11T18:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208890#M58532</link>
      <description>&lt;!--!*#--&gt;Upon further review I did find the logical drive failure notifications in the MSA1500 CS display panel by scrolling through the messages/notifications.&lt;BR /&gt;&lt;BR /&gt;I still need to retain the content of the failed logical drives if at all possible.&lt;BR /&gt;&lt;BR /&gt;Any help is greatly appreciated!&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Wed, 11 Nov 2009 18:54:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208890#M58532</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-11T18:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208891#M58533</link>
      <description>I re-seated the MSA controllers, power supplies, I/O modules and SFP Optical Transceivers.  This allowed ESX servers to boot up all the way and have access to non-failed logical drives.  The failed logical drives are still not accessible.&lt;BR /&gt;&lt;BR /&gt;The problem now is that HP ACU can no longer communicate with the MSA, it just times out.&lt;BR /&gt;&lt;BR /&gt;I reinstalled PSP, plus uninstalled and reinstalled ACU, plus ACU CLI.  I have reset HBA QLA2312F back to factory default settings and gather that the latest QLA2312f HBA Windows driver comes from the PSP, which is up-to-date.&lt;BR /&gt;&lt;BR /&gt;I just want ACU to re-gain access to the failed logical drives, so that I can accept the failure and re-enable the failed drives to move forward.</description>
      <pubDate>Fri, 13 Nov 2009 21:35:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208891#M58533</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-13T21:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208892#M58534</link>
      <description>hi there,&lt;BR /&gt;&lt;BR /&gt;you can give me the error message when you checking the msa through ACU.&lt;BR /&gt;&lt;BR /&gt;Or &lt;BR /&gt;&lt;BR /&gt;You can use CLI port and use the command.&lt;BR /&gt;accept units.&lt;BR /&gt;accept unit (unit no)&lt;BR /&gt;This is as good as ACU &lt;BR /&gt;&lt;BR /&gt;Prashant S.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Nov 2009 04:52:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208892#M58534</guid>
      <dc:creator>Prashant (I am Back)</dc:creator>
      <dc:date>2009-11-16T04:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208893#M58535</link>
      <description>My attached server (DL360 G4) took over 1.5 hrs to boot while being connected to SAN/Switch/MSA.  I disconnect FC cable in order to allow the server to complete its boot process.  The error in EventViewer is "The driver detected a controller error on \Device\Harddisk2".  &lt;BR /&gt;&lt;BR /&gt;I am looking into seeing what I can do at the ACU CLI level to try to resolve.  &lt;BR /&gt;&lt;BR /&gt;Thanks for the suggestion!</description>
      <pubDate>Mon, 16 Nov 2009 19:41:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208893#M58535</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-16T19:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208894#M58536</link>
      <description>Yes, the Accept Units command helped.  This command looks like it re-enable 4 out of the 8 logical drives.  Upon issuing the Show Eventlog command, there are still issues with the last 4 logical drives.  I am willing to just delete and re-create them if I can re-gain access to them via CLI command prompt.  When the MSA boots all the way up, it says Scanning for Devices, then goes away after 10 minutes and does not give me a CLI command prompt.  Pressing the &amp;lt; or &amp;gt; buttons on the display does not display any messages.  I have re-seated MSA components again, but it had no effect.&lt;BR /&gt;&lt;BR /&gt;Suggests are welcome!</description>
      <pubDate>Tue, 17 Nov 2009 00:56:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208894#M58536</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-17T00:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208895#M58537</link>
      <description>I was able to re-gain access to ACU CLI by disconnecting the SCSI I/O modules.  The MSA is currently in a locked state, such that no matter what command I issue, it pops the below message "ACU Lock state is currently Active.  Locked by WWN xxx".  Attached is a snap-shot of the error message.  Researching how to get out of this locked state.</description>
      <pubDate>Wed, 18 Nov 2009 17:43:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208895#M58537</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-18T17:43:08Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208896#M58538</link>
      <description>I was able to get around the locked state at the CLI level by issuing command "Override ACULock On".  This allowed me to run a Show Tech_Support command.  Attached is a copy of the Tech_Support report.  Is the problem, I need to assign/correct the Profile Names?</description>
      <pubDate>Wed, 18 Nov 2009 18:15:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208896#M58538</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-18T18:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1500 CS - Code 271 - Failed Logical Drives</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208897#M58539</link>
      <description>The information to resolve this known issue/problem is on HP's website:  &lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=415598&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=415598&amp;amp;objectID=c01204574" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&amp;amp;cc=us&amp;amp;taskId=110&amp;amp;prodSeriesId=415598&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=415598&amp;amp;objectID=c01204574&lt;/A&gt;</description>
      <pubDate>Thu, 19 Nov 2009 18:00:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1500-cs-code-271-failed-logical-drives/m-p/5208897#M58539</guid>
      <dc:creator>Borg8472</dc:creator>
      <dc:date>2009-11-19T18:00:54Z</dc:date>
    </item>
  </channel>
</rss>

