<?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: Controller battery failure in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735069#M4979</link>
    <description>Hi Viks,&lt;BR /&gt;&lt;BR /&gt;The autoraid will never perform a true non-interupted failover.  you will get application hangs, for the duration of the pvchange switchover, should be set to around 90secs for the autoraid.&lt;BR /&gt;&lt;BR /&gt;However, if your applications behave well, pulling a controller will not cause a problem.&lt;BR /&gt;&lt;BR /&gt;Changing the X and Y physical position will make no difference to the operation of the autoraid.  Being in either slot X or Y has no bearing on the functionality of either controller.  &lt;BR /&gt;&lt;BR /&gt;You can pull the X controller and the array will run fine off the Y controller.. without moving it anywhere.&lt;BR /&gt;&lt;BR /&gt;It will work fine in slot Y, once you have verified that the alternate links are good.&lt;BR /&gt;ie the Y controller will be used on X removal.  There is nothing more that you need to do other than removing the failed controller.&lt;BR /&gt;&lt;BR /&gt;(At least test that once you've identified it is certainly not a battery failure by swopping battery positions in the controller)&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
    <pubDate>Wed, 19 Jun 2002 07:56:38 GMT</pubDate>
    <dc:creator>Bill McNAMARA_1</dc:creator>
    <dc:date>2002-06-19T07:56:38Z</dc:date>
    <item>
      <title>Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735061#M4971</link>
      <description>Hi All,i got an AR12H with two controllers.sometimeback i changed the second battery on X controller.but after a few days it showed bad.so again i replaced the both the batteries of the X controller with a good set.again the same battery #2 is failing.if started on monday till wednesday there is no problem but later "replace x battery" is displayed.i did a small preventive maintenance also.but no use.how to approach this.any help wud be highly helpful.&lt;BR /&gt;thanks in advance&lt;BR /&gt;</description>
      <pubDate>Fri, 31 May 2002 04:12:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735061#M4971</guid>
      <dc:creator>viks</dc:creator>
      <dc:date>2002-05-31T04:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735062#M4972</link>
      <description>I tried to avoid this question, but seeing as nobody has replied, will give you what I believe is bad news: Controller Failure... and a very stupid type of failure..&lt;BR /&gt;&lt;BR /&gt;Again change the 2 batteries, to known good, fully charged ones, and see if Battery 2 still fails.  If so, get the ouptut of the logprint command for the arrayid and send it to your hp rc engineer.&lt;BR /&gt;&lt;BR /&gt;There is a risk of data failure and performance is going to be poor because of disabled caching.&lt;BR /&gt;&lt;BR /&gt;The data failure will come if there is a power fail or incorrect shutdown and you are using a strange controller map resiliancy.&lt;BR /&gt;&lt;BR /&gt;Post up your arraydsp -a of the array.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;Bill</description>
      <pubDate>Fri, 31 May 2002 12:32:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735062#M4972</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-05-31T12:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735063#M4973</link>
      <description>Dear Bill ... sorry for the extreme delay.thanks for ur response.but again i was observing this week.two days continuously it works fine but the third day it tells battery failure.i got one more question.can i just swap the X and Y controllers so that i will be sure that my  system doesnt goes down at any point of time.now i am not very sure if X fails i Y will take care or not.theoritically it shud.but if it fails then i am in a soup.right.reply me at the earliest.&lt;BR /&gt;regards&lt;BR /&gt;Viks&lt;BR /&gt;</description>
      <pubDate>Wed, 12 Jun 2002 02:25:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735063#M4973</guid>
      <dc:creator>viks</dc:creator>
      <dc:date>2002-06-12T02:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735064#M4974</link>
      <description>Hi again,&lt;BR /&gt;&lt;BR /&gt;I'll look into your attachment in a minute, but just to reply to the failover case of the controller first..&lt;BR /&gt;&lt;BR /&gt;The system should not go down on any failure in the autoraid, unless you have your boot disk/swap fs there.&lt;BR /&gt;&lt;BR /&gt;BUT, certain filesystems on the autoraid are potentially at risk if you haven't configured LVM to respond correctly to "failed hardware"&lt;BR /&gt;&lt;BR /&gt;ie, &lt;BR /&gt;Lets imaging you have the following configuration&lt;BR /&gt;&lt;BR /&gt;Controller X SCSI ID 1&lt;BR /&gt;Controller Y SCSI ID 2&lt;BR /&gt;&lt;BR /&gt;LUN0 LUN1&lt;BR /&gt;&lt;BR /&gt;Controller X connected to host directly.&lt;BR /&gt;&lt;BR /&gt;Controller Y connected to host directly (not the same bus as Controller X)&lt;BR /&gt;&lt;BR /&gt;See diagram attached&lt;BR /&gt;&lt;BR /&gt;Make sure that LVM has been configured for switchover, via vgdisplay All_VGs_on_12H and look for Alternate Paths to the luns, if you don't have an alternate path defined, there will be no switch over and your filesystems /vg on the 12H will go down brutally.&lt;BR /&gt;&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 12 Jun 2002 09:09:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735064#M4974</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-06-12T09:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735065#M4975</link>
      <description>&lt;BR /&gt;1 battery in controller X has for sure failed:&lt;BR /&gt;Battery #1 state = DEAD   &lt;BR /&gt;Battery #2 is okay.&lt;BR /&gt;&lt;BR /&gt;I'd swap position of the two batteried around just to verify that it is either the controller that is damaged or if it is the battery itself.&lt;BR /&gt;Run the same arraydsp command.&lt;BR /&gt;&lt;BR /&gt;If you see&lt;BR /&gt;Battery #1 state = DEAD   &lt;BR /&gt;Battery #2 state = GOOD&lt;BR /&gt;&lt;BR /&gt;Then your controller has failed, or if you see&lt;BR /&gt;&lt;BR /&gt;Battery #1 state = GOOD   &lt;BR /&gt;Battery #2 state = DEAD&lt;BR /&gt;&lt;BR /&gt;after swopping the X controller battery positions around then the Battery (and not the controller) is a dud.&lt;BR /&gt;&lt;BR /&gt;I can't exactly recall which is battery #1 and #2, but recommend to change BOTH at the same time, (don't want a weaker battery that the other)&lt;BR /&gt;&lt;BR /&gt;Try to get a thin pliers to remove/intert the battery connector, because you can a&amp;gt; hurt your fingers! and b&amp;gt; pull out wires from the battery connector.&lt;BR /&gt;&lt;BR /&gt;On the brighter side, your array looks in good health, &lt;BR /&gt;(There is f/w upgrade available, however, I wouln't recomment upgrading just for the sake of it.)&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 12 Jun 2002 09:18:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735065#M4975</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-06-12T09:18:42Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735066#M4976</link>
      <description>viks,&lt;BR /&gt;&lt;BR /&gt;Plus,read this: &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x96b70bce6f33d6118fff0090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x96b70bce6f33d6118fff0090279cd0f9,00.html&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;live free or die &lt;BR /&gt;harry  &lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Wed, 12 Jun 2002 11:21:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735066#M4976</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-06-12T11:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735067#M4977</link>
      <description>I guess point are out of the question for my lovely art! ;P&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Fri, 14 Jun 2002 10:39:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735067#M4977</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-06-14T10:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735068#M4978</link>
      <description>Dear Bill , tell me onething.i am sure my raid box wont go down as all the vg's have got alternate paths.but what i want to avoid is failure of X controller because of battery dead condition.so i thought i can interchange X and Y controller positions and run the show for sometime till i get a replacement controller.can i do this.&lt;BR /&gt;regards&lt;BR /&gt;Viks</description>
      <pubDate>Wed, 19 Jun 2002 07:12:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735068#M4978</guid>
      <dc:creator>viks</dc:creator>
      <dc:date>2002-06-19T07:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Controller battery failure</title>
      <link>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735069#M4979</link>
      <description>Hi Viks,&lt;BR /&gt;&lt;BR /&gt;The autoraid will never perform a true non-interupted failover.  you will get application hangs, for the duration of the pvchange switchover, should be set to around 90secs for the autoraid.&lt;BR /&gt;&lt;BR /&gt;However, if your applications behave well, pulling a controller will not cause a problem.&lt;BR /&gt;&lt;BR /&gt;Changing the X and Y physical position will make no difference to the operation of the autoraid.  Being in either slot X or Y has no bearing on the functionality of either controller.  &lt;BR /&gt;&lt;BR /&gt;You can pull the X controller and the array will run fine off the Y controller.. without moving it anywhere.&lt;BR /&gt;&lt;BR /&gt;It will work fine in slot Y, once you have verified that the alternate links are good.&lt;BR /&gt;ie the Y controller will be used on X removal.  There is nothing more that you need to do other than removing the failed controller.&lt;BR /&gt;&lt;BR /&gt;(At least test that once you've identified it is certainly not a battery failure by swopping battery positions in the controller)&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Wed, 19 Jun 2002 07:56:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/controller-battery-failure/m-p/2735069#M4979</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-06-19T07:56:38Z</dc:date>
    </item>
  </channel>
</rss>

