Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

64 Error messages
Understanding messages
V-5-0-249
VxVM vxio WARNING V-5-0-249 RAID-5 volume entering degraded mode
operation
Description: An uncorrectable error has forced a subdisk to detach. At this
point, not all data disks exist to provide the data upon request. Instead,
parity regions are used to regenerate the data for each stripe in the array.
Consequently, access takes longer and involves reading from all drives in the
stripe.
Action: Check for other console error messages that indicate the cause of the
failure. Replace any failed disks as soon as possible.
V-5-0-251
VxVM vxio WARNING V-5-0-251 read error on object
object
of mirror
plex
in volume volume (start offset length length)
Description: An error was detected while reading from a mirror. This error
may lead to further action shown by later error messages.
Action: If the volume is mirrored, no further action is necessary since the
alternate mirrors contents will be written to the failing mirror; this is often
sufficient to correct media failures. If this error occurs often, but never leads
to a plex detach, there may be a marginally defective region on the disk at
the position indicated. It may eventually be necessary to remove data from
this disk (see the vxevac(1M) manual page) and then to reformat the drive.
If the volume is not mirrored, this message indicates that some data could
not be read. The file system or other application reading the data may
report an additional error, but in either event, data has been lost. The
volume can be partially salvaged and moved to another location if desired.
Note: This message may also appear during a plex detach operation in a
cluster. In this case, no action is required.
V-5-0-252
VxVM vxio NOTICE V-5-0-252 read error on object subdisk of mirror
plex in volume volume (start offset length length) corrected
Description: A read error occurred, which caused a read of an alternate
mirror and a writeback to the failing region. This writeback was successful
and the data was corrected on disk.