Jeanette/Ken Nutsford wrote:
>
> We have a private volume RAID disk which sustained directory corruption
> resulting eventually in a systems failure on purging a file. Now when the
volume
> mount is initiated it reports an error mounting the volume and gives the
message
> "VOLUME WILL BE MOUNTED AS ERROR VOLUME."
>
> A dstat shows the volume with status ERROR_MOUNT but we are unable to
FORMATVOL
> unless the status is SCRATCH or UNKNOWN. How can the ERROR_MOUNT status be
> changed so that we can set up the private volume from the beginning?

I hope you already got some help in the meantime, but if not:

If your directory or in your case more probably a structure called
file label tabel got corrupted, so that a purge attempt (or even
PURGEFILE attempt in FSCHECK) results in a system abort (most likely
SA 55x or SA 2052), then the more immediate thing to do is to get
your hardware/disk checked first before you rebuild the volume set.

Once the hardware is sorted out or fixed, you need to
volutil: scratchvol <ldev>
all volumes in that volume set (maybe it is just this one disk array,
in your case) and then rebuild the set per
volutil: newset <setname>:<mastername> <ldev> 100 100
to setup the first disk/master and
volutil: newvol <setname>:<membername> ...
for all other disks in that set.

A formatvol is usually unnecessary.

Goetz.