Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Solaris
- Introduction
- Section I. Troubleshooting Veritas File System
- Section II. Troubleshooting Veritas Volume Manager
- Recovering from hardware failure
- About recovery from hardware failure
- Listing unstartable volumes
- Displaying volume and plex states
- The plex state cycle
- Recovering an unstartable mirrored volume
- Recovering an unstartable volume with a disabled plex in the RECOVER state
- Forcibly restarting a disabled volume
- Clearing the failing flag on a disk
- Reattaching failed disks
- Recovering from a failed plex attach or synchronization operation
- Failures on RAID-5 volumes
- Recovering from an incomplete disk group move
- Restarting volumes after recovery when some nodes in the cluster become unavailable
- Recovery from failure of a DCO volume
- Recovering from instant snapshot failure
- Recovering from the failure of vxsnap prepare
- Recovering from the failure of vxsnap make for full-sized instant snapshots
- Recovering from the failure of vxsnap make for break-off instant snapshots
- Recovering from the failure of vxsnap make for space-optimized instant snapshots
- Recovering from the failure of vxsnap restore
- Recovering from the failure of vxsnap refresh
- Recovering from copy-on-write failure
- Recovering from I/O errors during resynchronization
- Recovering from I/O failure on a DCO volume
- Recovering from failure of vxsnap upgrade of instant snap data change objects (DCOs)
- Recovering from failed vxresize operation
- Recovering from boot disk failure
- VxVM and boot disk failure
- Possible root, swap, and usr configurations
- Booting from an alternate boot disk on Solaris SPARC systems
- The boot process on Solaris SPARC systems
- Hot-relocation and boot disk failure
- Recovery from boot failure
- Repair of root or /usr file systems on mirrored volumes
- Replacement of boot disks
- Recovery by reinstallation
- Managing commands, tasks, and transactions
- Backing up and restoring disk group configurations
- Troubleshooting issues with importing disk groups
- Recovering from CDS errors
- Logging and error messages
- Troubleshooting Veritas Volume Replicator
- Recovery from RLINK connect problems
- Recovery from configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- About recovery from a Primary-host crash
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL volume error at reboot
- Primary SRL volume overflow recovery
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- Secondary SRL volume error cleanup and recovery
- Secondary SRL header error cleanup and recovery
- Secondary SRL header error at reboot
- Troubleshooting issues in cloud deployments
- Recovering from hardware failure
- Section III. Troubleshooting Dynamic Multi-Pathing
- Section IV. Troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting Storage Foundation Cluster File System High Availability
- About troubleshooting Storage Foundation Cluster File System High Availability
- Troubleshooting CFS
- Troubleshooting fenced configurations
- Troubleshooting Cluster Volume Manager in Veritas InfoScale products clusters
- CVM group is not online after adding a node to the Veritas InfoScale products cluster
- Shared disk group cannot be imported in Veritas InfoScale products cluster
- Unable to start CVM in Veritas InfoScale products cluster
- Removing preexisting keys
- CVMVolDg not online even though CVMCluster is online in Veritas InfoScale products cluster
- Shared disks not visible in Veritas InfoScale products cluster
- Troubleshooting Storage Foundation Cluster File System High Availability
- Section V. Troubleshooting Cluster Server
- Troubleshooting and recovery for VCS
- VCS message logging
- Log unification of VCS agent's entry points
- Enhancing First Failure Data Capture (FFDC) to troubleshoot VCS resource's unexpected behavior
- GAB message logging
- Enabling debug logs for agents
- Enabling debug logs for IMF
- Enabling debug logs for the VCS engine
- About debug log tags usage
- Gathering VCS information for support analysis
- Gathering LLT and GAB information for support analysis
- Gathering IMF information for support analysis
- Message catalogs
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting Intelligent Monitoring Framework (IMF)
- Troubleshooting service groups
- VCS does not automatically start service group
- System is not in RUNNING state
- Service group not configured to run on the system
- Service group not configured to autostart
- Service group is frozen
- Failover service group is online on another system
- A critical resource faulted
- Service group autodisabled
- Service group is waiting for the resource to be brought online/taken offline
- Service group is waiting for a dependency to be met.
- Service group not fully probed.
- Service group does not fail over to the forecasted system
- Service group does not fail over to the BiggestAvailable system even if FailOverPolicy is set to BiggestAvailable
- Restoring metering database from backup taken by VCS
- Initialization of metering database fails
- Troubleshooting resources
- Troubleshooting I/O fencing
- Node is unable to join cluster while another node is being ejected
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Manually removing existing keys from SCSI-3 disks
- System panics to prevent potential data corruption
- Cluster ID on the I/O fencing key of coordinator disk does not match the local cluster's ID
- Fencing startup reports preexisting split-brain
- Registered keys are lost on the coordinator disks
- Replacing defective disks when the cluster is offline
- The vxfenswap utility exits if rcp or scp commands are not functional
- Troubleshooting CP server
- Troubleshooting server-based fencing on the Veritas InfoScale products cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting the steward process
- Troubleshooting licensing
- Validating license keys
- Licensing error messages
- [Licensing] Insufficient memory to perform operation
- [Licensing] No valid VCS license keys were found
- [Licensing] Unable to find a valid base VCS license key
- [Licensing] License key cannot be used on this OS platform
- [Licensing] VCS evaluation period has expired
- [Licensing] License key can not be used on this system
- [Licensing] Unable to initialize the licensing framework
- [Licensing] QuickStart is not supported in this release
- [Licensing] Your evaluation period for the feature has expired. This feature will not be enabled the next time VCS starts
- Verifying the metered or forecasted values for CPU, Mem, and Swap
- VCS message logging
- Troubleshooting and recovery for VCS
- Section VI. Troubleshooting SFDB
Recovering a root disk and root mirror from a backup
This procedure assumes that you have the following resources available:
A listing of the partition table for the original root disk before you encapsulated it.
A current full backup of all the file systems on the original root disk that was under Veritas Volume Manager control. If the root file system is of type ufs, you can back it up using the ufsdump command.
See the ufsdump(1M) manual page.
A new boot disk installed to replace the original failed boot disk if the original boot disk was physically damaged.
This procedure requires the reinstallation of the root disk. To prevent the loss of data on disks not involved in the reinstallation, only involve the root disk in the reinstallation procedure.
Several of the automatic options for installation access disks other than the root disk without requiring confirmation from the administrator. Therefore, disconnect all other disks containing volumes from the system prior to starting this procedure. This will ensure that these disks are unaffected by the reinstallation. Reconnect the disks after completing the procedure.
The procedure assumes the device name of the new root disk to be c0t0d0s2, and that you need to recover both the root (/) file system on partition s0, and the /usr file system on partition s6.
To recover a root disk and root mirror from a backup
- Boot the operating system into single-user mode from its installation CD-ROM using the following command at the boot prompt:
ok boot cdrom -s
- Use the format command to create partitions on the new root disk (c0t0d0s2). These should be identical in size to those on the original root disk before encapsulation unless you are using this procedure to change their sizes. If you change the size of the partitions, ensure that they are large enough to store the data that is restored to them.
See the format(1M) manual page.
A maximum of five partitions may be created for file systems or swap areas as encapsulation reserves two partitions for Veritas Volume Manager private and public regions.
- Use the mkfs command to make new file systems on the root and usr partitions. For example, to make a ufs file system on the root partition, enter:
# mkfs -F ufs /dev/rdsk/c0t0d0s0
See the mkfs(1M) manual page.
See the mkfs_ufs(1M) manual page.
- Mount/dev/dsk/c0t0d0s0 on a suitable mount point such as /a or /mnt:
# mount /dev/dsk/c0t0d0s0 /a
- Restore the root file system from tape into the /a directory hierarchy. For example, if you used ufsdump to back up the file system, use the ufsrestore command to restore it.
See the ufsrestore(1M) manual page.
- Use the installboot command to install a bootblock device on /a.
- If the /usr file system is separate from the root file system, use the mkdir command to create a suitable mount point, such as /a/usr/, and mount /dev/dsk/c0t0d0s6 on it:
# mkdir -p /a/usr # mount /dev/dsk/c0t0d0s6 /a/usr
- If the /usr file system is separate from the root file system, restore the /usr file system from tape into the /a/usr directory hierarchy.
- Disable startup of VxVM by modifying files in the restored root file system.
- Create the file /a/etc/vx/reconfig.d/state.d/install-db to prevent the configuration daemon, vxconfigd, from starting:
# touch /a/etc/vx/reconfig.d/state.d/install-db
- Copy /a/etc/system to a backup file such as /a/etc/system.old.
- Comment out the following lines from /a/etc/system by putting a * character in front of them:
set vxio:vol_rootdev_is_volume=1 rootdev:/pseudo/vxio@0:0
These lines should then read:
* set vxio:vol_rootdev_is_volume=1 * rootdev:/pseudo/vxio@0:0
- Copy /a/etc/vfstab to a backup file such as /a/etc/vfstab.old.
- Edit /a/etc/vfstab, and replace the volume device names (beginning with /dev/vx/dsk) for the / and /usr file system entries with their standard disk devices, /dev/dsk/c0t0d0s0 and /dev/dsk/c0t0d0s6. For example, replace the following lines:
/dev/vx/dsk/rootvol /dev/vx/rdsk/rootvol / ufs 1 no - /dev/vx/dsk/usrvol /dev/vx/rdsk/usrvol /usr ufs 1 yes -
with this line:
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no - /dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 yes -
- Remove /a/dev/vx/dsk/bootdg and /a/dev/vx/rdsk/bootdg:
# rm /a/dev/vx/dsk/bootdg # rm /a/dev/vx/rdsk/bootdg
- Shut down the system cleanly using the init 0 command, and reboot from the new root disk. The system comes up thinking that VxVM is not installed.
- If there are only root disk mirrors in the old boot disk group, remove any volumes that were associated with the encapsulated root disk (for example, rootvol, swapvol and usrvol) from the /dev/vx/dsk/bootdg and /dev/vx/rdsk/bootdg directories.
- If there are other disks in the old boot disk group that are not used as root disk mirrors, remove files involved with the installation that are no longer needed:
# rm -r /etc/vx/reconfig.d/state.d/install-db
Start the Veritas Volume Manager I/O daemons:
# vxiod set 10
Start the Veritas Volume Manager configuration daemon in disabled mode:
# vxconfigd -m disable
Initialize the volboot file:
# vxdctl init
Enable the old boot disk group excluding the root disk that VxVM interprets as failed::
# vxdctl enable
Use the vxedit command (or the Veritas Enterprise Administrator (VEA)) to remove the old root disk volumes and the root disk itself from Veritas Volume Manager control.
- Use the vxdiskadm command to encapsulate the new root disk and initialize any disks that are to serve as root disk mirrors. After the required reboot, mirror the root disk onto the root disk mirrors.