Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Linux
- 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
- VxVM boot disk recovery
- 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 interconnects
- 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 issues with systemd unit service files
- 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
Substituting a root mirror disk for a failed root disk
To substitute a root disk mirror for a failed root disk
- Use the vxplex command to remove the plex records that were on the failed disk:
# vxplex -g bootdg -o rm dis rootvol-01 swapvol-01
This example removes the plexes rootvol-01 and swapvol-01 that are configured on the failed root disk. You may need to modify the list of plexes according to your system configuration.
- Shut down the system, and then power it down.
- Remove the failed root disk (in this example, sda).
- Reconfigure the root disk mirror (in this example, sdb) to appear to the system as the original root disk (sda). This may require you to change settings on the drive itself, and to relocate the root disk mirror in the same physical slot as was occupied by the original root disk. Consult your system documentation for more information.
- Configure a disk of the same or larger capacity as the failed root disk as a replacement for the root mirror disk (sdb). It should occupy the same slot that was vacated if this is necessary for the system to see it as the same disk.
- Power up the system, and boot it from Linux installation CD number 1.
- On a Red Hat system, run the following command at the boot prompt to put the system in rescue mode:
boot: linux rescue
On a SUSE system, choose the "Rescue" option from the menu.
Log in as root, select your language and keyboard, and choose to skip finding your installation.
- Use the fdisk command to ensure that the new root disk (sda) and the replacement disk (sdb) have the same geometry:
# fdisk -l /dev/sda # fdisk -l /dev/sdb
See the fdisk(8) manual page for details.
- If the replacement disk already contains a VxVM private region, use the fdisk command to change the partition type for the private region partition to a value other than 7f.
# fdisk /dev/sdb
- Make a temporary mount point, /vxvm, and mount the root partition on it:
# mkdir /vxvm # mount -t ext3 /dev/sda1 /vxvm
In this example, the root partition is /dev/sda1, and the root file system type is ext3. You may need to modify this command according to your system configuration. For example, the root file system may be configured as a reiserfs file system.
- If the disk has a separate boot partition, mount this on /vxvm/boot:
# mount -t ext3 /dev/sda2 /vxvm/boot
In this example, the boot partition is /dev/sda2, and the boot file system type is ext3. You may need to modify this command according to your system configuration.
- Ensure that the device for the new root disk (in this example, sda) is defined correctly in the boot loader configuration file.
For the GRUB boot loader:
Check that the contents of the GRUB configuration file (/vxvm/boot/grub/menu.lst or /vxvm/etc/grub.conf as appropriate) are correct, and use the grub command to install the master boot record (MBR) in case it has been corrupted:
# /vxvm/sbin/grub grub> root (hd0,1) grub> setup (hd0) grub> quit
Here /boot is assumed to be on partition 2.
For the LILO boot loader:
Check that the contents of the /vxvm/etc/lilo.conf file are correct, and use the lilo command to recreate the master boot record (MBR) in case it has been corrupted:
# /vxvm/sbin/lilo -r /vxvm
In these examples, the MBR is written to /dev/sda. You may need to modify the command according to your system configuration.
- Unmount the partitions, run sync, and then exit the rescue shell:
# cd / # umount /vxvm/boot # umount /vxvm # sync # exit
- Shut down and power cycle the system. Enter the system's BIOS settings mode (this is usually achieved by pressing a key such as Esc, F2 or F12 on the console keyboard). Verify in the BIOS settings that the system is set to boot from the new root disk (in this example, sda). Otherwise the system may not be bootable.
- Reboot the system, selecting vxvm_root at the GRUB or LILO boot prompt as appropriate.
- Run the following command to mirror the volumes from the new root disk onto the replacement disk:
# /etc/vx/bin/vxrootmir sdb rootdisk
This example assumes that the disk media name of the replacement disk is sdb. You may need to modify this name according to your system configuration.