VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

vxconfigd Warning Messages

60 VERITAS Volume Manager Troubleshooting Guide

◆ Description: This error only happens for volumes that are started automatically by

vxconfigd at system startup. The plex is being detached as a result of I/O failure,

disk failure during startup or prior to the last system shutdown or crash, or disk

removal prior to the last system shutdown or crash.

◆ Action: To ensure that the ﬁle system retains the same number of active mirrors,

removethegiven plexand adda new mirrorusing the vxassist mirror operation.

Also consider replacing any bad disks before running this command.

vxvm:vxconfigd: WARNING: Disk disk in group group flagged as shared;

Disk skipped

◆ Description: The given disk is listed as shared, but the running version of VxVM does

not support shared disk groups.

◆ Action: This message can usually be ignored. If you want to use the disk on this

system, use vxdiskadd to add the disk. Do not do this if the disk really is shared

with other systems.

vxvm:vxconfigd: WARNING: Disk disk in group group locked by host hostid

Disk skipped

◆ Description: The given disk is listed as locked by the host with the VERITAS Volume

Manager host ID (usually the same as the system hostname).

◆ Action: This message can usually be ignored. If you want to use the disk on this

system, use vxdiskadd to add the disk. Do not do this if the disk really is shared

with other systems.

vxvm:vxconfigd: WARNING: Disk disk in group group: Disk device not found

◆ Description: No physical disk can be found that matches the named disk in the given

disk group. This is equivalent to failure of that disk. (Physical disks are located by

matching the disk IDs in the disk group conﬁguration records against the disk IDs

stored in the VERITAS Volume Manager header on the physical disks.) This error

message is displayed for any disk IDs in the conﬁguration that are not located in the

disk header of any physical disk. This may result from a transient failure such as a

poorly-attached cable, or from a disk that failsto spinup fast enough. Alternately, this

may happen as a result ofa disk beingphysically removedfrom thesystem, or from a

disk that has become unusable due to a head crash or electronics failure.

Any RAID-5 plexes, DRL log plexes, RAID-5 subdisks or mirrored plexes containing

subdisks on this disk are unusable. Such disk failures (particularly on multiple disks)

may cause one or more volumes to become unusable.

◆ Action: If hot-relocation is enabled, VERITAS Volume Manager objects affected by the

disk failure are taken care of automatically. Mail is sent to root indicating what

actions were taken by VxVM and what further actions the administrator should take.

vxvm:vxconfigd: WARNING: Disk disk in kernel is not a recognized type