VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Listing Unstartable Volumes

4 VERITAS Volume Manager Troubleshooting Guide

Listing Unstartable Volumes

An unstartable volume can be incorrectly conﬁgured 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:

# 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

Restarting a Disabled Volume

If a disk failure caused a volume to be disabled, you must restore the volume from a

backup afterreplacing the failed disk.Any volumes that arelisted as Unstartable must

be restarted using the vxvol command before restoring their contents from a backup. For

example, to restart the volume mkting so that it can be restored from backup, use the

following command:

# vxvol -o bg -f start mkting

The -f option forciblyrestarts thevolume, and the -o bg option resynchronizes plexes as

a background task.

Recovering a Mirrored Volume

A system crash or an I/O error can corrupt one or more plexes of a mirrored volume and

leave no plex CLEAN or ACTIVE. You can mark one of the plexes CLEAN and instruct the

system to use that plex as the source for reviving the others as follows:

1. Place the desired plex in the CLEAN state using the following command:

# vxmend fix clean plex

For example, to place the plex vol01-02 in the CLEAN state:

# vxmend fix clean vol01-02