Veritas, solaris. "UX:vxfs fsck: ERROR: V-3-20003: /dev/vx/rdsk/xxx:Cannot open /dev/vx/rdsk/xxx: No such device or address"

При возникновении ошибки V-3-20003 с описанием "No such device or address"
vxinfo -g <disk group>
(<disk group> можно посмотреть vxdg list)
показывала некоторые volume в состоянии Unstartable, при этом
vxprint -g <disk group> -hvt <unstartable volume>
показывала plex(ы) в состоянии DISABLED RECOVER.

Реанимация производилась по
Veritas Volume Manager Troubleshooting Guide
Recovering an unstartable volume with a disabled plex in the RECOVER state

A plex is shown in the RECOVER state if its contents are out-of-date with respect
to the volume. This can happen if a disk containing one or more of the plex’s
subdisks has been replaced or reattached. If a plex is shown as being in this
state, it can be recovered as follows:
Use the following command to force the plex into the OFFLINE state:
# vxmend [-g diskgroup] -o force off plex
Place the plex into the STALE state using this command:
# vxmend [-g diskgroup] on plex
If there are other ACTIVE or CLEAN plexes in the volume, use the following
command to reattach the plex to the volume:
# vxplex [-g diskgroup] att plex volume
If the volume is already enabled, resynchronization of the plex is started
If there are no other clean plexes in the volume, use this command to make
the plex DISABLED and CLEAN:
# vxmend [-g diskgroup] fix clean plex
If the volume is not already enabled, use the following command to start it,
and preform any resynchronization of the plexes in the background:
# vxvol [-g diskgroup] -o bg start volume

Note: If the data in the plex was corrupted, and the volume has no ACTIVE
or CLEAN redundant plexes from which its contents can be resynchronized,
it must be restored from a backup or from a snapshot image.

полезные команды veritas volume manager