Solaris 8 : Solstice DiskSuite / All mirrors are in all “Needs maintenance”

[Dantares]

Hello to all,

On Solaris 8 with Solstice DiskSuite, I used a soft partitions built
directly on slices on the disk.

I encounter a problem because DiskSuite indicates that the mirrors are
in all “Needs maintenance”.

The file system is good but how can I solve the problem without risk of
data loss.

Searching on internet I found the following command :

metarecover c1t0d0s6 -d –p

Is it good?

Here are the details of my problem

root#metastat d50
d50: Mirror
Submirror 0: d51
State: Needs maintenance
Submirror 1: d52
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 31454016 blocks

d51: Submirror of d50
State: Needs maintenance
Invoke: metareplace d50 d53 <new device>
Size: 31454016 blocks
Stripe 0:
Devic Start Block Dbase State Hot Spare
d53 0 No Maintenance
Stripe 1:
Devic Start Block Dbase State Hot Spare
d55 0 No Okay

d53: Soft Partition
Component: c1t0d0s6
State: Okay
Size: 25165824 blocks
Extent Start Block Block count
0 44101648 25165824

d55: Soft Partition
Component: c1t1d0s6
State: Okay
Size: 6291456 blocks
Extent Start Block Block count
0 60878863 6291456

d52: Submirror of d50
State: Needs maintenance
Invoke: after replacing "Maintenance" components:
metareplace d50 d54 <new device>
Size: 31454016 blocks
Stripe 0:
Devic Start Block Dbase State Hot Spare
d54 0 No Last Erred
Stripe 1:
Devic Start Block Dbase State Hot Spare
d56 0 No Maintenance

d54: Soft Partition
Component: c1t1d0s6
State: Okay
Size: 25165824 blocks
Extent Start Block Block count
0 35713038 25165824

d56: Soft Partition
Component: c1t0d0s6
State: Okay
Size: 6291456 blocks
Extent Start Block Block count
0 27324429 6291456

root#metarecover -n c1t1d0s6 -p
c1t1d0s6: Soft Partition metadb configuration is valid
c1t1d0s6: Soft Partition metadb matches extent header configuration

root#metarecover -n c1t0d0s6 -p
c1t0d0s6: Soft Partition metadb configuration is valid
c1t0d0s6: Soft Partition metadb matches extent header configuration

root#metadb
flags first blk block count
a m p luo 16 1034 /dev/dsk/c1t0d0s7
a p luo 1050 1034 /dev/dsk/c1t0d0s7
a p luo 2084 1034 /dev/dsk/c1t0d0s7
a p luo 16 1034 /dev/dsk/c1t1d0s7
a p luo 1050 1034 /dev/dsk/c1t1d0s7
a p luo 2084 1034 /dev/dsk/c1t1d0s7

Thank you very much for your help. excuse my English but I do not speak
very well.