metadb errors

Hi All.
Been out of Unix admin work for about 10 years and I just took over a new position...

seeing the 'use metadb to delete databases which are broken message' on reboot. The system comes up but I'm not sure what's on this disk that's failing...

metadb -i shows:

 
excalibur# metadb -i
        flags           first blk       block count
     a m  pc luo        16              1034            /dev/dsk/c0t2d0s3
    M     pc            unknown         unknown         /dev/dsk/c3t0d0s3
     a    pc luo        16              1034            /dev/dsk/c0t1d0s3
 o - replica active prior to last mddb configuration change
 u - replica is up to date
 l - locator for this replica was read successfully
 c - replica's location was in /etc/lvm/mddb.cf
 p - replica's location was patched in kernel
 m - replica is master, this is replica selected as input
 W - replica has device write errors
 a - replica is active, commits are occurring to this replica
 M - replica had problem with master blocks
 D - replica had problem with data blocks
 F - replica had format problems
 S - replica is too small to hold current data base
 R - replica had device read errors
 

Can I just delete it and re-attach (metadb -d and -a options)?
Just need some assistance on determining if this necessary or being used at all.

Thanks in advance to all replies.

Disksuite needs a minimum of 3 metastate databases therefore when setting thing up I run something like:

# metadb -a -f -c 3 c0t0d0s7 c0t1d0s3 c1t0d0s7

This makes 3 copies of the metastate database in each slice so that I have a few to spare and even with only one out of the three disks working DiskSuite still works.

If you have another disk with some free space then make a small slice on it (the minimum last time I tried was about 40MB, plenty of room) add another metastate database (3 copies!) onto it, then remove the problematic one, newfs(1) the slice that had the erroneous metastate database in it to wipe it and then try recreating it again.