During the synchronization of a mirrored volume copy it was necessary to duplicate the record of a medium error onto the volume copy, creating a virtual medium error. Each managed disk has a table of virtual medium errors. The virtual medium error could not be created because the table is full. The volume copy is in an inconsistent state and has been taken offline.
Three different approaches can be taken to resolving this problem: 1) the source volume copy can be fixed so that it does not contain medium errors, 2) the number of virtual medium errors on the target managed disk can be reduced or 3) the target volume copy can be moved to a managed disk with more free virtual medium error entries.
The managed disk with a full medium error table can be determined from the data of the root event.
Approach 1) - This is the preferred procedure because it restores the source volume copy to a state where all of the data can be read. Use the normal service procedures for fixing a medium error (rewrite block or volume from backup or regenerate the data using local procedures).
Approach 2) - This method can be used if the majority of the virtual medium errors on the target managed disk do not relate to the volume copy. Determine where the virtual medium errors are using the event log events and re-write the block or volume from backup.
Approach 3) - Delete the offline volume copy and create a new one either forcing the use of different MDisks in the storage pool or using a completely different storage pool.
Follow your selection option(s) and then mark the error as "fixed".
Possible Cause-FRUs or other: