HP OpenVMS System Manager's Manual, Volume 1:... |
Starting Up and Shutting Down the System |
|
|
| |
Writing a New Boot Block on the System Disk
On VAX systems, the primary bootstrap image is VMB.EXE.
On Alpha systems, the primary bootstrap image is APB.EXE.
On I64 systems, the primary bootstrap image is IPB.EXE.
Certain processors must read the boot block to obtain the location of the primary bootstrap image. Processors that read a boot block include the following ones:
To determine if your system reads the boot block, check one of the following manuals:
If you suspect that the boot block on the system disk is invalid, you can write a new boot block using the Writeboot utility (WRITEBOOT). The following actions might cause a boot block to become invalid:
| Instructions for using the WRITEBOOT utility are somewhat
different on VAX and Alpha systems. Instructions for performing
this task on VAX and Alpha systems follow. You must have LOG_IO
privilege to use WRITEBOOT. On I64 systems, you use SETBOOT to write a boot block. Instructions for performing this task are also in this section. |
On VAX systems, follow these steps to use the Writeboot utility:
$RUN SYS$SYSTEM:WRITEBOOT
Target system device (and boot file if not VMB.EXE):?On VAX systems, VMB.EXE is the default bootstrap image. Enter
a response in the following format:device:[VMS$COMMON.SYSEXE]VMB.EXE; Use the device name format described in the upgrade and installation
documentation for your processor. If you want to boot using a bootstrap
image other than the default, you must specify the full file specification
of the image, including device and directory. Enter VBN of boot file code (default is one): Ordinarily, the boot code is located at virtual block number
(VBN) 1 of the bootstrap image. Press Return to accept the default
value of 1. Enter load address of primary bootstrap in HEX (default is 200): The load address is the location in
memory (specified in hexadecimal notation) to which the system loads
the bootstrap image. Ordinarily you copy the bootstrap image to
address 200. Press Return to accept the default value of 200. On VAX systems, the Writeboot utility might display one or more of the following error messages:
$COPY/CONTIGUOUS device:[VMS$COMMON.SYSEXE]VMB.EXE; -_$device:[VMS$COMMON.SYSEXE]
Example:
On VAX systems, the following example writes a boot block on a system disk:
How to Perform This Task on Alpha Systems$RUN SYS$SYSTEM:WRITEBOOTTarget system device (and boot file if not VMB.EXE):?DUA0:[VMS$COMMON.SYSEXE]VMB.EXEEnter VBN of boot file code (default is one):[Return]Enter load address of primary bootstrap in HEX (default is 200):[Return]
On Alpha systems, follow these steps to use the Writeboot utility:
The procedure asks you whether you want to write the VAX portion of the boot block:$RUN SYS$SYSTEM:WRITEBOOT
Update VAX portion of boot block (default is Y):
Update Alpha portion of boot block (default is Y):Press Return to accept the default value of Y.
Enter Alpha boot file:On Alpha systems, APB.EXE is the default bootstrap image. Enter a response in the following format:device:[VMS$COMMON.SYSEXE]APB.EXE; where device specifies the device name of the system disk.
On Alpha systems, the Writeboot utility might display one or more of the following error messages:
$COPY/CONTIGUOUS device:[VMS$COMMON.SYSEXE]APB.EXE; -_$device:[VMS$COMMON.SYSEXE]
Example:
On Alpha systems, the following example writes a boot block on a system disk:
How to Perform This Task on I64 Systems$RUN SYS$SYSTEM:WRITEBOOTUpdate VAX portion of boot block (default is Y):NUpdate Alpha portion of boot block (default is Y):[Return]Enter Alpha boot file:DUA0:[VMS$COMMON.SYSEXE]APB.EXE;
To
write a boot block for OpenVMS I64 systems, HP provides the DCL
SET BOOTBLOCK command, which functions similarly to the Writeboot
utility (WRITEBOOT.EXE) used on OpenVMS Alpha systems. (Do not use
the Writeboot utility on OpenVMS I64 systems.)
SET
BOOTBLOCK allows you to create a bootable OpenVMS Alpha system disk
from one that was originally created by one of the following methods:
The SET BOOTBLOCK command also allows you to rewrite the boot block of an OpenVMS I64 system disk to point to a new version of the OpenVMS I64 primary bootstrap file (SYS$EFI.SYS) that you have previously copied to the disk. (Note that the file must be contiguous.)
To write a boot block onto a disk, enter the following command:
You can specify a boot file with the command. By default, the command creates the bootfile SYS$SYSDEVICE:[VMS$COMMON.SYS$LDR]SYS$EFI.SYS. The boot file must be contiguous. If it is not contiguous, use the DCL COPY/CONTIGUOUS command or similar to recreate a contiguous version of the boot file. In addition, the boot file must also be marked NOMOVE (use the DCL SET FILE/NOMOVE command) to avoid bootstrap failures that could otherwise arise from the normal and expected operations of disk defragmentation tools.$SET BOOTBLOCK
Alternatively, you can write a boot block by entering the following command:
The utility prompts you for the required input (as does the OpenVMS Alpha Writeboot utility).$RUN SYS$SYSTEM:SYS$SETBOOT
|
|