
NOTE: If the target OpenVMS I64 system disk has an
33 or more blocks. For example:
$ DUMP/HEADER/BLOCK=END=0 SYS$SYSDEVICE:[000000]GPT.SYS ...
Map area
Retrieval pointers:
Count: 36 LBN: 0
Count: | 36 | LBN: | 71132925 |
This example is from a disk with 71132960 blocks. The placement of the final extent is 71132924, which is calculated by subtracting 36 (the size of the last extent) from the disk capacity (71132960).
You may be able to temporarily recover from this condition and attempt to bootstrap the target OpenVMS I64 system disk by renaming GPT.SYS to GPT.BAD, and then entering the SET BOOTBLOCK command. To correctly recover from this condition, you must INITIALIZE the target disk and then reload the disk contents using a
To write the boot block structures onto an OpenVMS I64 system disk, enter the SET BOOTBLOCK command using the following format:
$ SET BOOTBLOCK [/PRESERVE=SIGNATURES] [/I64]
You can specify the file name for the boot partition
SYS$SYSDEVICE:[VMS$COMMON.SYS$LDR]SYS$EFI.SYS
The command also assumes the current architecture. To specify OpenVMS I64, include /I64 in the command line.
Use the /PRESERVE=SIGNATURES qualifier to preserve the existing GUID disk signature value and the associated root aliases. Note that using the OpenVMS Backup utility creates a new disk signature when restoring a bootable disk image.
If you reset the boot block structures, you might need to remove any EFI boot aliases that reference the disk, and then add them back again. You can use the EFI alias command to remove and add aliases; HP recommends using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) to maintain EFI console boot aliases.
NOTE: The boot partition file must be contiguous and movefile operations on the file must be disabled. If the file is not contiguous, use the DCL command COPY/CONTIGUOUS (or equivalent) to
Alternatively, you can write a boot block by entering the following command:
$ RUN SYS$SYSTEM:SYS$SETBOOT
The utility prompts you for the required input (in a way similar to the operation of the OpenVMS Alpha Writeboot utility).
A.5 Configuring and Managing OpenVMS Booting on Integrity Servers 171