![]() 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.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.Use the installboot command to install a bootblock device on /a.For example, if you used ufsdump to back up the file system, use the ufsrestore command to restore it. Restore the root file system from tape into the /a directory hierarchy.Mount /dev/dsk/c0t0d0s0 on a suitable mount point such as /a or /mnt: # mount /dev/dsk/c0t0d0s0 /a.For example, to make a ufs file system on the root partition, enter: # mkfs -F ufs /dev/rdsk/c0t0d0s0 Use the mkfs command to make new file systems on the root and usr partitions.If you change the size of the partitions, ensure that they are large enough to store the data that is restored to them.Ī 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. 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. Use the format command to create partitions on the new root disk ( c0t0d0s2).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.To recover a root disk and root mirror from a backup 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. Reconnect the disks after completing the procedure. This will ensure that these disks are unaffected by the reinstallation. Therefore, disconnect all other disks containing volumes from the system prior to starting this procedure. 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, only involve the root disk in the reinstallation procedure. This procedure requires the reinstallation of the root disk. If the root file system is of type ufs, you can back it up using the ufsdump command.Ī new boot disk installed to replace the original failed boot disk if the original boot disk was physically damaged. Volume Manager for UNIX/Linux 3.This procedure assumes that you have the following resources available:Ī listing of the partition table for the original root disk before you encapsulated it.Ī current full backup of all the file systems on the original root disk that was under Veritas Volume Manager control. # rm /etc/vx/reconfig.d/state.d/install-db Remove the install-db file so that VxVM, which was disabled in Step 3, can be re-enabled: Halt the machine and do a boot -a, then select the /etc/system.rsv:ġ1. Edit system.rsv and remove the following vxio:vol_rootdev_is_volume=1Ħ. Make a copy of /a/etc/system to boot from that system file temporarily:ĥ. # touch /a/etc/vx/reconfig.d/state.d/install-dbĤ. Mount the root partition (in this example the root partition is c0t0d0s0): Boot the machine into single user mode from CD:Ģ. NOTE : Break the mirror if the root disk is mirrored, before continuing with the following procedure.ġ. ![]() The steps below explain how to recreate the corrupt /etc/vx/volboot file in a VxVM root disk encapsulated environment. Vxvm:vxconfigd: ERROR: enable failed: volboot file not loadedĪ corrupt volboot file can make the system non-bootable in a VERITAS Volume Manager (VxVM) encapsulated root disk environment. Setting default IPv4 interface for multicast: add net 224.0/4: gateway sunhost VxVM starting special volumes ( swapvol ).Ĭonfiguring the /dev directory (compatibility devices) When you get to the following prompt enter / physical name of root device <<<<- Enter this (this comes from /etc/system). The /etc/path_to_inst on your system does not exist or is empty.ĭo you want to rebuild this file ? yes <<<<-–type yes When the system asks about rebuilding the path_to_inst, type yes SunOS Release 5.8 Version Generic_108528-15 64-bitĬopyright 1983-2001 Sun Microsystems, Inc. At the following prompts, just hit enter:Įnter filename : << -–Hit enterĮnter default directory for modules : This value is not the same as the default offered during the boot, use the value specified for rootdev in the /etc/system file.Ģ. Under VERITAS Volume Manager ™ rootdisk encapsulation, the administrator must take an extra step to ensure the path_to_inst file is created and populated. Note : This will only work if the rootdisk is encapsulated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |