vxbootsetup - set up system boot information on a Veritas Volume Manager disk

/etc/vx/bin/vxbootsetup [-g diskgroup] [-R rootpath] [-ACDHQVYfhnv] [medianame...]

The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a disk, create mirrors on that disk of the root file system volumes, such as the root (/), swap, /usr, /home, /opt, and /var volumes (if they exist). These mirrors should be restricted mirrors of the volume. The vxbootsetup utility configures a disk by writing a boot track at the beginning of the disk and by creating physical disk partitions in the UNIX VTOC that match the mirrors of the root file system volumes.

With no medianame arguments, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to be bootable. If medianame arguments are specified, only the named disks are configured.

vxbootsetup requires that the root volume is named rootvol and has a usage type of root. The swap volume is required to be named swapvol and to have a usage type of swap. The volumes containing /usr and /var (if any) are expected to be named usr and var, respectively.

Root, swap, /usr and /var volumes are created when the original system boot disk is encapsulated with the vxencap utility or when Veritas Volume Manager (VxVM) is first set up on the system. (/usr and /var are only encapsulated if they existed on the system; see the Symantec Storage Foundation Administrator’s Guide and the vxencap(1M) man page for details on encapsulating the boot disk.)

See the chapter on recovery in the Veritas InfoScale™ 7.0 Troubleshooting Guide for detailed information on how the system boots and how VxVM impacts the system boot process.

The following utilities call vxbootsetup automatically: vxmirror, vxunroot, vxrootadm, and vxencap. If you use vxassist or vxmake and vxplex to create mirrors of the root volume on a disk, you must call vxbootsetup directly to make that disk bootable.

-A	Removes stale vx-<dmname> eeprom devaliases. Use the -A option to avoid conflicts with existing devaliases.
-C	Clears miscellaneous partitions. VxVM assigns the partition tag 0x0 to disk partitions that contain non-root file systems (data volumes). Use the -C option to remove stale data partitions in case of a conflict. This option requires overwriting the existing partitions, so you must also specify the -f option.
-D	Displays debugging output.
-H	Displays the usage message (Help).
-Q	Specifies that the command quits immediately when an error is detected.
-R rootpath
	Specifies an alternate root path.
-V	Displays the commands which the vxbootsetup operaton will call, without executing them.
-Y	Specifies that the vxbootsetup operation displays prompts for default values. If the -Y option is not specified, the vxbootsetup operation runs without user interaction, and uses default values.
-f	Allows overwriting the existing partitions (force).
-g diskgroup
	Specifies the disk group for the operation, either by disk group ID or by disk group name. If this option is not specified, the default disk group is determined using the rules given in the vxdg(1M) manual page.
-h	Displays the usage message (Help).
-n	The default behavior of vxbootsetup is to create partitions for non-system volumes on a disk device. This option prevents such partitions from being created.
-v	Displays the commands that the vxbootsetup operation calls and executes the commands.

EFI disks cannot be set up as system boot disks.

vxdisksetup(1M), vxedvtoc(1M), vxassist(1M), vxdg(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M)

Symantec Storage Foundation Administrator’s Guide
Veritas InfoScale™ 7.0 Troubleshooting Guide