disk partitioning. This informational message applies to the configuration of the volume or of the partition that was mounted. User Action: This particular message is informational. 2 PARTITION the target volume is partitioned Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates that the target volume is partitioned. User Action: This message can be associated with another message, usually BADPARTVAL or MOUNTED. If associated with an error status, resolve the associated and underlying error. 2 PARTNOTAVAIL the specified partition is not available Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A valid partition was selected and a valid partition header was found, but the selected partition does not exist on this volume. User Action: Select a partition that exists on the target volume. If the partition header is valid and the selected partition actually does exist on the target volume, please contact the customer support center for assistance. 2 PERILCLUS cluster count within 16 clusters of required FAT format cut-over Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified FAT volume has a valid format, though the count of clusters is within 16 clusters of a required cut- over to the next larger or next smaller FAT format. Per EFI FAT specifications, this condition can cause instability when this volume is accessed from certain erronously-coded FAT utilities. All FAT12 volumes must have fewer than 4085 clusters, all FAT16 volumes must have between 4085 and 65524 clusters inclusive, and all FAT32 volumes must have at least 65525 clusters. This volume is perilously close to one of these cluster count cut-overs. User Action: While no action is specifically required, the EFI FAT specifications do recommend reinitializing the volume with a new cluster size, and specifically with a cluster size calculated to avoid a cluster count in proximity to one of the FAT format cut-overs. 2 RENAMERR rename error Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: cannot rename the specified object User Action: resolve the problems cited with the messages that accompany this one. 2 RSVDCLUS Reserved cluster Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an attempt to operate on a reserved storage cluster has occured. This can indicate a volume structure error, or a volume structure corruption, or an internal error. User Action: If this condition is not a result of a corrupted FAT volume structure or media error and can be reproduced, please contact the support center. 2 SBDEF default: defname Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This is the default specification for a particular command. This specification is combined with the file specification to produce the target specification. User Action: This message is typically a secondary error and associated with a primary error message. This message is intended to provide additional information useful in the resolution of the primary error. 2 SBTRG seeking: filename Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This is the name of the target filename or of the target device for a particular command. User Action: This message is typically a secondary error and associated with a primary error message. This message is intended to provide additional information useful in the resolution of the primary error. 2 SECTORBYTES expected sector size is bytes bytes Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports the expected sector size. This message can be caused by a volume that does not have the required sector size, or by a corrupted volume, or by an unsupported or unrecognized volume format. User Action: this message is informational, normally accompanying another message. 2 SEEKBPB searching for BIOS Parameter Block Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates the status of the processing. User Action: This particular message is informational. 2 SEEKBPBNG invalid BIOS Parameter Block detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume does not utilize a recognized BIOS Parameter Block structure. User Action: Check the target volume for structural validity. 2 SEEKBPBOK valid BIOS Parameter Block detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates the status of the processing. User Action: This particular message is informational. 2 SEEKMBR searching for Master Boot Record Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates the status of the processing. User Action: This particular message is informational. 2 SEEKMBROK valid Master Boot Record detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates the status of the processing. User Action: This particular message is informational. 2 SETUNRARCH cannot write unrecognized or unsupported architecture Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This application does not support writing a bootblock for the specified architecture; the specified architecture is not recognized or not supported. User Action: Please select a supported architecture. If the architecture is supported, please confirm the minimum necessary software revision of OpenVMS is present for the particular architecture. 2 SFNAMDEPTH permissible short filename directory depth exceeded Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Too many subdirectories have been specified in the file path. User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 SKIPPING skipping command processing Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This condition code is used within the utility, and flags processing specific to the IF, ELSE and ENDIF commands. User Action: This condition is used within the utility, and is not expected to be displayed to the user; this is an internal informational message. 2 SUCCESS success Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: normal successful completion User Action: if you had intended to cause this operation to fail, please try harder next time. 2 SYNTAX input command syntax error Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized command or command option was specified. User Action: Please verify the command syntax, and re-enter the specified command. 2 SYSDIAGSYS SYS$DIAGNOSTICS.SYS Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This message displays the name of the OpenVMS I64 diagnostics partition file, and often accompanies another message. User Action: In isolation, this message is entirely informational. If there is another error message, please resolve that issue. 2 SYSEFISYS SYS$EFI.SYS Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This message displays the name of the OpenVMS I64 bootstrap partition file, and often accompanies another message. User Action: In isolation, this message is entirely informational. If there is another error message, please resolve that issue. 2 TARGETREQ target device specification required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The target device or device and primary bootstrap file specification is required. User Action: You must specify the target for the SETBOOT operation. 2 TPAEXIT successful tparse transition Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal state transition match has succeeded within the parsing logic; the attempted transition matches the input data. User Action: this status is internal to the FAT filename parsing, and should not be generally visible outside the application. This message indicates a state transition match, and this status has little direct meaning outside of its use within the lib$table_ parse processing. 2 TPAFAIL lib$table_parse parse state transition failed Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal state transition match has failed within the parsing logic; the attempted transition does not match the input data. User Action: this status is internal to the FAT filename parsing, and should not be generally visible outside the application. This message indicates a state transition failure, and this status has little direct meaning outside of its use within the lib$table_ parse processing. 2 TRYFIXFAT trying to recover from a severe disk corruption Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message is usually reported in conjunction with other messages, and is typically displayed when there are errors reading the File Allocation Table (FAT). These errors are ominous. User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 TRYMBR only MBR-only boot block operations possible; invalid GPT Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Consider requesting an MBR-only boot block initialization. User Action: This message is typically a secondary error and associated with a primary error message. This message is intended to provide additional information useful in one potential resolution for the primary error. 2 UNEXPCOND unexpected internal condition value detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: An internal operation should have returned a particular status condition value and did not. This tends to indicate an internal error or data corruption. User Action: An internal error has apparently been detected. Please contact support. If this error can be reproduced with a specific command or a specific command sequence, please provide the reproducer. 2 UNKFATTYP FAT type type is not supported Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target FAT disk does not use a recognized format, or the FAT format used is not one supported by this utility. User Action: the format of the specified FAT disk is incompatible, and cannot be accessed. 2 UNKGPT unknown, unsupported or unrecognized GPT partitioning Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume does not utilize a recognized GPT disk partitioning scheme. User Action: Check the target volume for structural validity. 2 UNKIOFUNC unknown, unrecognized or corrupted I/O function code Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal error has been detected, and an I/O function code is unrecognized, unsupported, or corrupted. User Action: An internal error has been detected. Please contact support. If this error can be reproduced with a specific command or a specific command sequence, please provide the reproducer. 2 UNKIOTARG unknown or unrecognized I/O target Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal error has been detected, and the type of target for an I/O operation cannot be determined. User Action: An internal error has been detected. Please contact support. If this error can be reproduced with a specific command or a specific command sequence, please provide the reproducer. 2 UNKMPFMT unknown file header mapping pointer format detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A mapping pointer in the file header is using an unrecognized or unsupported mapping pointer format. User Action: There is no particular recovery for this error, if this is the most current version of this tool. This version of the tool is incompatible with the OpenVMS file header format, or there is a corruption within the file header, or other similar error. 2 UNKPART unknown, unsupported or unrecognized partitioning Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume does not utilize a recognized disk partitioning scheme. User Action: Check the target volume for structural validity. 2 UNKRMSORG unknown RMS organization FAB$B_ORG org detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal error has been detected; an RMS file organization is unrecognized, unsupported, or corrupted. User Action: An internal error has been detected. Please check the integrity of all RMS files involved with the current operation. If all files are valid and consistent, please contact support. If this error can be reproduced with a specific command or a specific command sequence, please provide the reproducer. 2 UNRECRX unrecognized FAT12 floppy disk volume geometry detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: One or more of the FAT12 volume structure checks has detected a volume geometry that is not recognized, as EFI$CP supports only a subset of the available FAT12 floppy disk devices. User Action: FAT12 volumes have predesignated geometries, and this FAT12 volume has an unrecognized geometry. Repair or reinitialize the target volume appropriately, or transfer the contents of the FAT volume onto one of the recognized and supported FAT volume formats (and the associated geometry). The 2HD 1.44 megabyte RX26 floppy disk drive is the most common floppy disk typically found on OpenVMS systems. 2 UNRGPTVERS target volume contains an unrecognized GPT version Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume appears to contain a GPT, but the embedded version number is unexpected and unsupported. User Action: The command or request cannot operate as requested. If the target volume contains GPT structures, then the volume is apparently corrupted, or can contain data structures that could differ from the expected structures. 2 UNSUPBPB unsupported or corrupt target BIOS Parameter Block detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: One or more of the volume structure checks has detected a volume format that is recognized, but that is not supported. User Action: Repair or reinitialize the target volume appropriately, or transfer the contents of the FAT volume to one of the recognized and supported FAT volume formats. 2 UNSUPVOL unsupported volume format Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: One or more of the volume structure checks has detected a volume format that is recognized, but that is not supported. User Action: Repair or reinitialize the target volume appropriately, or transfer the contents of the FAT volume to one of the recognized and supported FAT volume formats. 2 VALPARTITION valid partition values must be between 0 and 3, inclusive Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates the range of valid partition values. User Action: This message is always associated with another error, usually BADPARTVAL. Resolve the associated and underlying error. 2 VOLINIT FAT volume volume has been initialized Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified FAT-format volume has been initialized. User Action: The FAT-format storage volume has been initialized, typically at user request. This particular message is informational. 2 VOLLABEL FAT volume has label label Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The volume has the specified label. User Action: Verify that the correct volume is mounted; verify the label entered. If this is not the label you expected, please dismount this volume and find and mount the volume with the expected label. 2 WRITELOCK target volume is write-locked Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an operation writing write access failed, as the target volume is currently mounted read-only. User Action: evaluate if the target volume should be dismounted and mounted writable, or if the operation is appropriate for the specified volume.