VxVM no longer maintains entries for tunables in
/etc/system as was the case for VxVM 3.2 and earlier releases. All entries for Veritas Volume Manager device driver tunables are now contained in files named
/kernel/drv/vx*.conf, such as
See the Veritas Volume Manager Administrator's Guide.
/etc/system, make a copy of the file in the
root file system before editing it.
If the system configuration file is damaged, the system can be booted if the file is restored from a saved copy.
To restore a copy of the system configuration file
ok boot -a
Enter filename [/kernel/unix]:
/etc/system is damaged or missing, and a saved copy of this file is not available on the root disk, the system cannot be booted with the Veritas Volume Manager rootability feature turned on.
The following procedure assumes the device name of the root disk to be
c0t0d0s2, and that the
/) file system is on partition
To boot the system without Veritas Volume Manager rootability and restore the configuration files
boot cdrom -s
/dev/dsk/c0t0d0s0 on a suitable mount point such as
mount /dev/dsk/c0t0d0s0 /a
/etc/system is available, restore this as the file
/a/etc/system. If a backup copy is not available, create a new
/a/etc/system file. Ensure that /a/
etc/system contains the following entries that are required by VxVM:
Lines of the form
root mirror disks. Example driver names are
ide. To find out the names of the drivers, use the
ls command to obtain a long listing of the special files that correspond to the devices used for the root disk, for example:
ls -al /dev/dsk/c0t0d0s2
This produces output similar to the following (with irrelevant detail removed):
lrwxrwxrwx ... /dev/dsk/c0t0d0s2 ->
This example would require lines to force load both the
pci and the
root partition on which the configuration files were restored.