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
- Failures on RAID-5 volumes
- Recovery from failure of a DCO volume
- Recovering from instant snapshot failure
- Recovering from failed vxresize operation
- Recovering from boot disk failure
- 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 configuration errors
- Errors during an RLINK attach
- Errors during modification of an RVG
- Recovery on the Primary or Secondary
- Recovering from Primary data volume error
- Primary SRL volume error cleanup and restart
- Primary SRL header error cleanup and recovery
- Secondary data volume error cleanup and recovery
- 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
- Troubleshooting CFS
- Troubleshooting fenced configurations
- Troubleshooting Cluster Volume Manager in Veritas InfoScale products clusters
- Troubleshooting Storage Foundation Cluster File System High Availability
- Section V. Troubleshooting Cluster Server
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting I/O fencing
- System panics to prevent potential data corruption
- Fencing startup reports preexisting split-brain
- 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 licensing
- Licensing error messages
- VCS message logging
- Troubleshooting and recovery for VCS
- Section VI. Troubleshooting SFDB
Shared disks not visible in Veritas InfoScale products cluster
If the shared disks in /dev/rdsk are not visible, perform the following tasks:
Make sure that all shared LUNs are discovered by the HBA and SCSI layer. This can be verified by running the ls -ltr command on any of the disks under /dev/rdsk/*.
For example:
# ls -ltr /dev/rdsk/disk_name lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d4s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,4:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d3s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,3:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d2s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,2:c,raw lrwxrwxrwx 1 root root 81 Aug 18 11:58 c2t5006016141E02D28d1s2 -> ../../devices/pci@7c0/pci@0/pci@8/SUNW,qlc@0/fp@0, 0/ssd@w5006016141e02d28,1:c,raw
If all LUNs are not discovered by SCSI, the problem might be corrected by specifying dev_flags or default_dev_flags and max_luns parameters for the SCSI driver.
If the LUNs are not visible in /dev/rdsk/* files, it may indicate a problem with SAN configuration or zoning.
Perform the following additional steps:
Check the file
/kernel/drv/sd.conf
to see if the new LUNs were added.Check the format to see if the LUNs have been labeled in the server.
Check to see is the disk is seen, using the following command:
# prtvtoc /dev/rdsk/disk_name