klionwhere.blogg.se

Failed root disk using veritas volume manager
Failed root disk using veritas volume manager






  1. #FAILED ROOT DISK USING VERITAS VOLUME MANAGER INSTALL#
  2. #FAILED ROOT DISK USING VERITAS VOLUME MANAGER SOFTWARE#

The disks disk02 and disk03 were not involved in the reinstallation and are recognized by VxVM and associated with their devices ( sdc and sdd). The display shows that the reinstalled root device, sdb, is not associated with a VM disk and is marked with a status of error. For example, for a reinstalled system with three disks and a reinstalled root disk, the output of the vxdisk list command is similar to this: This displays a list of system disk devices and the status of these devices.

failed root disk using veritas volume manager

If a complete copy of a volume's data is available, it can be repaired by the hot-relocation feature provided that this is enabled and there is sufficient spare disk space in the disk group.Įstablish which VM disks have been removed or reinstalled using the following command: Such volumes are invalid and must be removed, recreated, and restored from backup. After recovering the VxVM configuration, you must determine which volumes need to be restored from backup because a complete copy of their data is not present on the recovered disks.If a volume had only one plex contained on a disk that was reinstalled, removed, or replaced, then the data in that volume is lost and must be restored from backup.Īfter reinstalling VxVM, you must clean up the system configuration. If the root disk (and other disks containing critical file systems) was previously under VxVM control, any volumes or mirrors on that disk (or on other disks no longer attached to the system) are now inaccessible. If the root disk of your system and any other disks involved in the reinstallation were not under VxVM control at the time of failure and reinstallation, then the reconfiguration is complete at this point. The configuration of the preserved disks does not include the root disk as part of the VxVM configuration. As the root disk has been reinstalled, it does not appear to VxVM as a VM disk. The configuration preserved on the disks not involved with the reinstallation will now be recovered. Reattach the disks that were removed from the system.To recover the Veritas Volume Manager configuration

#FAILED ROOT DISK USING VERITAS VOLUME MANAGER SOFTWARE#

Once the Veritas Volume Manager packages have been loaded, and you have installed the software licenses, recover the Veritas Volume Manager configuration. Recovering the Veritas Volume Manager configuration

#FAILED ROOT DISK USING VERITAS VOLUME MANAGER INSTALL#

If required, use the vxlicinst command to install the Veritas Volume Manager license key.Warning: Do not use vxinstall to initialize VxVM. Reinstall the Veritas software from the installation disks.It is recommended that you keep the existing host name, as this is assumed by the procedures in the following sections. If anything is written on a disk other than the root disk, the Veritas Volume Manager configuration on that disk may be destroyed.ĭuring reinstallation, you can change the system's host name (or host ID). Install the operating system prior to installing any Veritas software.Įnsure that no disks other than the root disk are accessed in any way while the operating system installation is in progress. Once any failed or failing disks have been replaced and disks not involved with the reinstallation have been detached, reinstall the operating system as described in your operating system documentation. Removing the second disk ensures that the home file system remains intact. For example, if the operating system was originally installed with a home file system on the second disk, it can still be recoverable. Disconnect all other disks containing volumes from the system prior to reinstalling the operating system.ĭisconnecting the other disks ensures that they are unaffected by the reinstallation. Several of the automatic options for installation access disks other than the root disk without requiring confirmation from the administrator. To prevent the loss of data on disks not involved in the reinstallation, involve only the root disk in the reinstallation procedure. See "Cleaning up the system configuration" on page 53. Restore any information in volumes affected by the failure or reinstallation, and recreate system volumes ( rootvol, swapvol, usr, and other system volumes).See "Recovering the Veritas Volume Manager configuration" on page 52. Recover the Veritas Volume Manager configuration.See "Reinstalling Veritas Volume Manager" on page 52. Add the Volume Manager package, but do not execute the vxinstall command.See "Reinstalling the operating system" on page 52. Reinstall the base system and any other unrelated Volume Manager packages.See "Prepare the system for reinstallation" on page 51. Replace any failed disks or other hardware, and detach any disks not involved in the reinstallation.

failed root disk using veritas volume manager

To reinstall the system and recover the Veritas Volume Manager configuration, the following steps are required: Reinstalling the system and recovering VxVM








Failed root disk using veritas volume manager