SUMMARY: Disksuite 4.2 Mirror Errors

Sorry for the delay in writing a Summary for my question, but I didn't get to
try any of the advice I received until this morning.

I received many great replies, namely from:
Joe-sunixadm
Jon Andrews
Mike-mps
ssethi
and a special thanks to Sampath Kari.

The solution was to run the following:

/root mirror
metareplace -e d10 c0t0d0s0  (d11 submirror which is in Needs Maintenance mode)
keep running metastat until status changes to Okay
metareplace -e d10  c1t4d0s0 (d12 submirror which is in Last Erred Status)
keep running metastat until status changes to Okay
/usr mirror
metareplace -e d20 c1t4d0s1 (d22 submirror which is in Needs Maintenance mode)
keep running metastat until status changes to Okay
metareplace -e d20 c0t0d0s1 (d21 submirror which is in Last Erred Status)
keep running metastat until status changes to Okay

Again thank you all for your prompt and excellent advice.


Original Questions:
I was brought in on a problem server today of which I have no previous history
with.  I will do my best to summarize the current symptoms so that an accurate
solution can be reached.  I have a two hour window later this week in order to
try and fix the errors.

The machine is an E3500 running Solaris 7 and two volumes, /root and /usr, are
mirrored using SDS 4.2.  From what I could gather, this machine had a power
failure and on the ensuing boot up, it would not boot with the currently active
boot disk.  A Sun Engineer was called out and he brought the system up by
booting from the mirrored root disk.  I cannot find any reports that any of the
disks are bad.  Within the Solstice admin tool, if I evaluate each set of
Mirrors and Submirrors, everything is working correctly.  But the status of the
disks are in Maintenance mode.  Here are the retyped results of running
metastat:

/root mirror:
d10: Mirror
  Submirror 0: d11
     State:    Needs maintenance
  Submirror 1: d12
     State:    Needs maintenance
  Pass: 1
  Read option: roundrobin
  Write option:     parallel
  size:   6413526 blocks

d11: Submirror of d10
     State:    Needs maintenance
  Invoke: metareplace d10 c0t0d0s0 <new device>
  Size:   6413526
  Stripe 0:
    Device     Start Blk Dbase     Status          Hot Spare
c0t0d0s0     0      No   Maintenance

d12: Submirror of d10
     State:    Needs maintenance
  Invoke: after replacing "Maintenance" components:
          metareplace d10 c140d0s0 <new device>
  Size:   6413526
  Stripe 0:
    Device     Start Blk Dbase     Status          Hot Spare
c1t4d0s0     0      No   Last Erred

----------------------------------------------------------------------------------------------------------
/usr mirror:
d20: Mirror
  Submirror 0: d21
     State:    needs maintenance
  Submirror 1: d22
     State:    Needs maintenance
  Pass: 1
  Read option: roundrobin
  Write option:     parallel
  size:   3073896 blks

d21: Submirror of d20
     State:    Needs maintenance
  Invoke: after replacing "Maintenance" components:
     metareplace d20 c0t0d0s1 <new device>
  Size:   3073896 blks
Stripe 0:
  Device  Start Blk Dbase     Status          Hot Spare
 c0t0d0s1   0       No   Last Erred

d22: Submirror of d20
     State:    Needs maintenance
  Invoke: metareplace d20 c1t4d0s1 <new device>
  Size:   3073896 blks
  Stripe 0:
     Device    Start Blk Dbase     Status          Hot Spare
  c1t4d0s1       0       No   Maintenance

In running metadb -i, all the databases were intact and healthy.

This may be as simple as the disks being out of synch, but I didn't want to run
metasync -r and risk causing more damage.

Could anyone who has run into these symptoms please provide some guidance on how
to handle this situation?  This is a production SAP machine and I have a limited
window of 2 hours later this week to clear this up.

Thank you for your help in advance.


*******************Internet Email Confidentiality Footer*******************


Privileged/Confidential Information may be contained in this message.  If you
are not the addressee indicated in this message (or responsible for delivery of
the message to such person), you may not copy or deliver this message to anyone.
In such case, you should destroy this message and kindly notify the sender by
reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind.  Opinions, conclusions and other
information in this message that do not relate to the official business of my
firm shall be understood as neither given nor endorsed by it.


_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers