Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

If a volume has a disk I/O failure (for example, because the disk has an

uncorrectable error), VxVM can detach the plex involved in the failure. I/O stops

on that plex but continues on the remaining plexes of the volume.

If a disk fails completely, VxVM can detach the disk from its disk group. All plexes

on the disk are disabled. If there are any unmirrored volumes on a disk when it

is detached, those volumes are also disabled.

Note: Apparent disk failure may not be due to a fault in the physical disk media

or the disk controller, but may instead be caused by a fault in an intermediate or

ancillary component such as a cable, host bus adapter, or power supply.

The hot-relocation feature in VxVM automatically detects disk failures, and notifies

the system administrator and other nominated users of the failures by electronic

mail. Hot-relocation also attempts to use spare disks and free disk space to restore

redundancy and to preserve access to mirrored and RAID-5 volumes.

For more information about administering hot-relocation, see the Veritas Volume

Manager Administrator’s Guide.

Recovery from failures of the boot (root) disk requires the use of the special

procedures.

See “VxVM and boot disk failure” on page 41.

Listing unstartable volumes

An unstartable volume can be incorrectly configured or have other errors or

conditions that prevent it from being started. To display unstartable volumes,

use the vxinfo command. This displays information about the accessibility and

usability of volumes

To list unstartable volumes

◆

Type the following command:

# vxinfo [-g diskgroup] [volume ...]

The following example output shows one volume, mkting, as being unstartable:

home fsgen Started

mkting fsgen Unstartable

src fsgen Started

rootvol root Started

swapvol swap Started

Recovering from hardware failure

Listing unstartable volumes