1 Error_Messages This section describes the various error messages that can be reported by the components of the EFI$CP package. 2 4GIGABYTES FAT32 limits the maximum native file size to four gigabytes Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified data file size is larger than the largest native file size permissible within the Microsoft FAT32 version 1.03 specification. User Action: Persuade Microsoft to extend FAT and Intel to support and to use the newer format, or persuade Intel to support an additional disk volume structure for use within the Intel Itanium EFI environment, or persuade HP to design and provide FAT extensions specific to the HP OpenVMS FAT support and HP systems based on Intel Itanium. Alternatively, consider the use of multiple smaller files for the data storage, and also consider the applicability of data compression. Only the use of smaller files should be assumed to be compatible and transportable across platforms supporting FAT32 version 1.03 volumes. 2 ALREXISTS specified file or directory already exists Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified object already exists. User Action: specify a file or directory name that is not present. 2 ALRMOUNTED volume volume already mounted Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume is already mounted. User Action: The particular command or operation is incompatible with a volume that is already mounted, or an incorrect volume was specified. Specify the correct target device for the command, or DISMOUNT the specified device and then re-issue the command. 2 AMBPARTYP ambiguous partition type; multiple matching types present Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: you have specified a particular partition type, and there are several matching partitions present. The first such match has been selected. User Action: At present, there is no way to access subsequent matching partitions. No way short of patching the type code field of the Master Boot Record (MBR), that is. 2 ASSUME internal assumption failure Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: An internal assumption necessary for correct operation has failed. 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 BADBLK bad block Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: bad FAT disk storage block encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADBPB invalid or corrupt target BIOS Parameter Block detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A series of verification operations is performed to detect faulty or corrupted BIOS Parameter Block (BPB) structure. (The BPB is a critical system data structure for the FAT volume structure.) This message indicates that one or more of the verifications has failed, and that the target FAT partition is apparently corrupted, or that the target partition structure is not a valid FAT partition. User Action: Verify that the target volume or target partition is consistent and uncorrupted, and particularly that the FAT partition is correct using the SHOW BPB command or another volume structure verification utility. If the volume partition is valid, please contact the customer support center. Consider restoration from archives or a data recovery service, and reinitialization of the FAT volume or FAT partition. 2 BADCOPSYN invalid COPY syntax Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: both parameters are F11 file specifications, or both are FAT file specifications. The COPY command presently supports only copies from or copies to a FAT volume, and not F11-to-F11 or FAT-to-FAT copies. User Action: Respecify the command, with corrected parameters. 2 BADDATE bad date detected; specified date value is illegal Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A bad or a null date value has been detected, and assumed to indicate a FAT volume corruption. The particular operation that detected the corruption has been terminated. This message is the error variant of the BADDATE2 informational, and is used when MOUNT/IGNORE=CORRUPTIONS is not requested. User Action: locate and correct the source of the bad date, Indy 2 BADDATE2 null date detected; date value reset to 1-Jan-1980 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A null date value has been detected, is considered illegal, and has been repaired. The Windows epoch date 1-Jan-1980 has been substituted. This message is the non-fatal version of the BADDATE error, and is used when MOUNT/IGNORE=CORRUPTIONS is requested. User Action: The FAT volume is providing a null date value. Short of contacting the vendor and/or reworking the software that created the FAT volume data structure(s) involved, there are comparatively few options available. 2 BADDBGDEV invalid or unexpected debugging device detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A DECwindows call used within debugging code returned an unexpected device name, or no debugging device was available. 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 BADDEVALIAS bad device alias specified Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports the specified device alias name is invalid. User Action: Specify a valid device-like name (with colon) as the device alias. 2 BADDIRSPEC invalid directory specification Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized directory specification has been encountered User Action: Please respecify the command, using the expected syntax. 2 BADF11NAM invalid OpenVMS filename Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized filename has been encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADF12SIZE specified volume partition size is too small for FAT12 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified partition volume creation size request is too small to be for a FAT12 volume. User Action: Specify a valid partition file size. For FAT12, the volume size is typically either 1440 or (more commonly) 2880. 2 BADF16SIZE specified volume partition size is too large for FAT16 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified partition volume creation size request is too large to be for a FAT16 volume. User Action: Specify a valid partition file size. For FAT16, the volume size must be less than or equal to 4194304 blocks. 2 BADFAT FAT sector unavailable, synthesizing a FAT sector of EOC entries Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports a device error reading the File Allocation Table (FAT), and the generation of a block of End Of Cluster Chain (EOC) end of file entries in the FAT table; all files involving FAT entries within the failed FAT sector are effectively truncated. User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 BADFATNAM invalid FAT filename Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized filename has been encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADFATSPEC invalid FAT file or directory specification Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized FAT file or directory specification has been encountered User Action: Please respecify the command, using the expected syntax. 2 BADFILSPEC invalid file specification Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized directory specification has been encountered User Action: Please respecify the command, using the expected syntax. 2 BADGPTOPT select MBR-only operations, or re-INITIALIZE this disk Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: GPT.SYS is present but apparently ill-formed or ill-sized. User Action: Use the DCL commands DIRECTORY and DUMP to determine if the file is present, if the file is writable, and if storage is allocated to all blocks of the file. In particular, try to DUMP/BLOCK=START=lastblock the last block of the file. (If this dump of the last block fails, you cannot use GPT bootstrap structures with this disk, and you must either select and use MBR-only operations or you must reinitialize the entire disk with a valid GPT and reload the files.) 2 BADGPTSYS [000000]GPT.SYS incorrectly placed on target disk Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The GPT.SYS file is not correctly located on the target disk. When present, this file must have at least two extents, with the lowest extent covering the first 33 blocks rounded up to the disk cluster factor, and the last extent must occupy the last 33 logical blocks, rounded up to the disk cluster factor. User Action: The specified disk structure is not compatible with GPT-based bootstraps, and must either use the traditional MBR bootstrap or must be reinitialized with the GPT option specified. There is no mechanism available that can retrofit the GPT.SYS file onto an existing disk without requiring reinitialization. 2 BADINDEXF INDEXF.SYS file incorrectly placed on target disk Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The INDEXF.SYS file is not correctly located on the target disk. User Action: The specified disk volume structure appears corrupt. 2 BADLFDEPTH permissible long 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 BADLFNAM invalid or unsupported long filename syntax Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized long filename has been encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADPARAM bad parameter Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal argument-passing error has occured, and the specified operation or internal call cannot be completed. User Action: If the problem can be reproduced, please contact the support center for assistance. 2 BADPARTITION invalid or corrupt target volume partition record Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates that the target volume is not partitioned, or that the partition header has been corrupted. User Action: Verify that the target volume is consistent and uncorrupted, and particularly that the partition record is correct using SHOW MBR or another verification utility. If the volume partition record is valid, please contact the customer support center. 2 BADPARTVAL partition specification invalid Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified partition value is not valid. This typically means that the specified value is outside the permissible range of values for the particular type of partition. User Action: The partition specification is not compatible with the volume format. Usually, the specification is outside the range that is valid for the target volume. Respecify within the valid range. Additional messages will typically indicate the range for the specified volume structure. 2 BADPATH path component dir is missing or invalid Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A component of a syntactically valid file path specification is not valid. Most commonly, the path component does not match an existing directory. This is not permitted. User Action: Please respecify the path. 2 BADPOOL an internal memory corruption has been detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: integrity checks associated with a memory allocation or a deallocation operation have detected an application memory pool corruption. User Action: an internal application memory management error has been detected. If you are an engineer supporting this application, this error can also be easily triggered by a change to a core data structure that has not been followed by a full source rebuild. If you are a user of this application, you will want to contact the support center, and you will likely need to restart the application, as this error indicates a fatal problem within the application run-time environment. If this error can be reproduced, please provide details of this process. 2 BADROOTDIR invalid root directory Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized root directory has been encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADSFNAM invalid or unsupported short filename syntax Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid or unrecognized short filename has been encountered User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 BADVBNMAP VBN scatter-gather map is corrupt Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This indicates an internal error within the processing, and particularly that a core mapping data structure has been found to be corrupted. User Action: If the condition can be reproduced, please contact support. 2 BADWILDCARD invalid wildcard use in FAT file or directory specification Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid use of wildcards was used. The only valid uses currently are for the filename portion - they cannot be used in the path - and only the simple forms of wildcards can be used - that is the name or extension cannot be partially wildcarded but must fully be wildcarded. User Action: Please respecify the command, using the expected syntax. 2 CLNSHUT volume reports improper dismount Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume was not properly dismounted, and may not be in a consistent state. User Action: Check the target volume for structural validity. 2 CLUSALLO successful storage allocation Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: allocation operation succeeded User Action: consider the acquisition of additional disk storage, as certain of the available storage has just been utilized. 2 COPIED copied srcfile to dstfile Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This informational message is displayed as requested, and indicates the specified source file was copied to the specified target file. User Action: Informational. No user action is required. 2 CREATERR creation error Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: cannot create the specified object User Action: resolve the problems cited with the messages that accompany this one. 2 CREERR Creation failure Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: An error was detected within the FAT volume structure volume processing during FAT file or FAT directory creation, and the associated command operation has failed. User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 DELETED deleted deleted Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the FAT file or directory has been deleted. User Action: informational output for /LOG 2 DELETERR deletion error Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: cannot delete the specified object User Action: resolve the problems cited with the messages that accompany this one. 2 DEVNOTALL device is not allocatable Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume does not appear to be capable of being allocated; the device is either already allocated by another user, or the device is mounted shareable. User Action: Check the target device name specified, and ensure the device is appropriate for the requested operation. 2 DEVNOTFOD device is not a files-oriented device Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume does not appear to be capable of file storage, and is apparently unsuitable for the specified operation. User Action: Check the target device name specified, and ensure the device is appropriate for the requested operation. 2 DEVNOTRDY device not ready, not mounted, or unavailable Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target device is not ready, not mounted, not available or otherwise inaccessable. User Action: Please check the device specification used and check the status of the target device, and resolve the error. 2 DEVTOOSMALL specified target FAT volume is too small Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target device is too small to be a FAT device, or an internal error has been detected. User Action: If the volume is large enough to be a FAT device, please contact support for assistance. 2 DFUDEFLBN files can be aligned with DFU DEFRAGMENT /LBN=lbn Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This message provides a command which can align a disk file onto a particular disk logical block number (LBN). User Action: This message is normally associated with another error. Please resolve the primary error. The DFU utility installation kit is available on various OpenVMS Freeware distributions. 2 DIRFULL directory file is full Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the directory file has insufficient room for the requested additional file(s), and cannot be extended. User Action: delete some files, or use shorter filenames. 2 DIRNOTEMT specified directory is not empty Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified directory object contains files, and thus cannot be deleted. User Action: delete the files first, then delete the directory. 2 DIRNOTFOU cannot locate specified directory Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target directory is not found, not available or otherwise inaccessable. User Action: Please check the file specification used and check the contents of the target device, and resolve the error. 2 DISMOUNT volume volume dismounted Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume was dismounted, and is no longer accessable. User Action: when you next wish to access the contents of the now-dismounted volume, you will want to first remount it using the MOUNT command. 2 DRVERR drive error error reading FAT sector sector Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports a device error reading the File Allocation Table (FAT). If multiple copies of the FAT are present, similar errors are being reported across all copies. User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 DRVERRETRY drive error reading FAT sector sector, attempting retry Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports a device error reading the File Allocation Table (FAT). This is ominous. If multiple copies of the FAT are present, there will be an attempt to read the required FAT data from the same sector within an another copy of the FAT. User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 DRVERRSEC attempting to read FAT table table sector sector 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. If multiple copies of the FAT are present, there will be an attempt to read the required FAT data from the same sector within an another copy of the FAT. (The FAT table display is zero-based, and the sector display is the relative sector within the FAT.) User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 DRVERRSTS drive error error reading FAT Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message reports a device error reading the File Allocation Table (FAT). This is ominous. If multiple copies of the FAT are present, there will be an attempt to read the required FAT data from the same sector within an another copy of the FAT. User Action: Attempt to copy all user data off the FAT volume, as it appears the FAT volume is failing. 2 DUPLTAIL unable to generate unique numeric tail for filename Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: There are too many files of similar long file names on the FAT volume, and the associated unique 8.3 filename cannot be generated as required. User Action: Use additional and unique long file names, or use additional FAT volumes. The short name is generated from the first one to up to six characters of the long filename, and it is the numbers of duplicate strings within this portion of all long filenames presently in use that is triggering this error. Use of filenames that are not unique within the first one to up to six characters will inherently reduce the performance of various FAT volume operations, as well. 2 EOF end of file Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an end of file condition has been detected User Action: resolve messages associated with this one. 2 ERRALIAS invalid specification of /DEVICE_ALIAS Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specification of /DEVICE_ALIAS is incorrect in this context. User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRCREATE partition creation error error detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the partition creation has failed with the specified error User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRCRESIZ specification of partition size required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: specification of the size of the created partition is required. User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRDEVICE specification of a device or of a partition is required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: specification of either the device or of the partition is required. User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRIVDEV invalid specification of device or partition Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an invalid specification of either the device or of the partition was detected. User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRLABEL specification of volume label required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specification of the volume label is required User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 ERRLABOVR specification of volume label or of label override is required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: specification of either the volume label or of the appropriate volume label override is required. User Action: This message is expected to be associated with a command syntax error. Please verify the command syntax, and re- enter the specified command. 2 F12RSCNOT1 invalid FAT12 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, the FAT12 volume can have any reserved sector count greater than zero, but the value is usually 1. Specifications allege other values can cause incompatibilities in certain circumstances. User Action: No action is required. The valid is valid, and the volume will be correctly processed by this utility. 2 F16RSCNOT1 invalid FAT16 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, the FAT16 volume can have any reserved sector count greater than zero, but the value is usually 1. Specifications allege other values can cause incompatibilities in certain circumstances. User Action: No action is required. The valid is valid, and the volume will be correctly processed by this utility. 2 F32RSCNOT32 valid but unexpected FAT32 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, the FAT32 volume can have any reserved sector count greater than zero, but the value is usually 32. Specifications allege other values can cause incompatibilities in certain circumstances. User Action: No action is required. The valid is valid, and the volume will be correctly processed by this utility. 2 FAT12MAX Cluster count too large for FAT12 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: FAT12 has a capacity limit on the numbers of storage allocation units (clusters), and this limit has been reached. User Action: You must specify or utilize volumes with smaller cluster counts, or switch to a FAT structure that permits the required number of clusters. 2 FAT16MAX Cluster count too large for FAT16 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: FAT16 has a capacity limit on the numbers of storage allocation units (clusters), and this limit has been reached. User Action: You must specify or utilize volumes with smaller cluster counts, or switch to a FAT structure that permits the required number of clusters. 2 FAT32MAX Cluster count too large for FAT32 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: FAT32 has a capacity limit on the numbers of storage allocation units (clusters), and this limit has been reached. User Action: You must specify or utilize volumes with a smaller cluster required number of clusters; the attempted volume structure is beyond the upper limits of FAT32. 2 FAT32MIN Cluster count too small for FAT32 Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: FAT32 has a capacity limit on the numbers of storage allocation units (clusters), and this limit has been reached. User Action: You must specify or utilize volumes with a larger cluster count, or switch to a FAT structure that permits the required number of clusters; the attempted volume structure is beyond the lower limits of FAT32. 2 FATNYI FAT volume structure not recognized or not yet implemented Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The FAT volume structure that was detected is either not a recognized FAT volume structure, or is a FAT volume structure that is not yet implemented within this tool. User Action: Use a FAT volume structure supported by this tool, or formally request an enhancement to the tool. 2 FATOVF FAT value value overflows supported limit value Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: internal FAT data structure corruption 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 FATTYP FAT structure type code Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This message normally accompanies one or more additional messages, and provides addititional information. Resolve the condition(s) associated with the accompanying message(s). User Action: This particular message is informational. 2 FATTYPERR corrupted FAT volume structure type code detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: An internal consistency check has detected an unsupported or an invalid FAT type code. This error is generally fatal, as a correct determination of the particular flavor of FAT for the current volume is central to correct operations. User Action: If this is a supported FAT volume structure, an internal error has been detected. Please contact support. If this error can be reproduced with a specific command or a specific command sequence and particularly using a FAT version supported by this tool, please provide the reproducer. 2 FILNOTALI file is not aligned to specified sector boundary Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target file is not aligned with the specified sector boundary. This most commonly arises when the input volume cluster factor is not a multiple of the specified output disk sector size; when the input file is not aligned on a 2048-byte (four block) sector boundary. (Given that files involved are expected to be marked /NOMOVE, the tool will not attempt to perform a MOVEFILE or similar low-level operation; the tool will not attempt to correct the positioning error.) User Action: Either relocate the file to a sector boundary, or reinitialize the input volume to use a multiple of four as the volume cluster factor. The DFU command DEFRAGMENT/LBN=lbn can be used to locate a file onto a specific LBN. 2 FILNOTFOU cannot locate specified file Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the target file is not found, not available or otherwise inaccessable. User Action: Please check the file specification used and check the contents of the target device, and resolve the error. 2 FIXEDDATE fixed date date selected for regression test processing Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This informational is displayed only when diagnostics are enabled, and when an actual date and time value is being replaced with a value intended solely for easing processing for regression tests. User Action: Informational. No user action is required. This message should never be displayed in normal operations, only appearing when user diagnostics and regression testing mechanisms are both explicitly requested. 2 FLUSHFAT flushing FAT volume caches out to the FAT volume Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The preceding operation has caused a requirement for the FAT file system caches to be flushed out to the FAT disk. User Action: Informational. No user action is required. 2 GETUNRARCH unrecognized or unsupported architecture detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This application has detected an unrecognized or an unsupported architecture. User Action: Confirm that the target target system device is a valid and bootable system disk. 2 GPTIOERR attempt to write to or to erase [000000]GPT.SYS failed Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: GPT.SYS is present, but is apparently ill-formed or ill-sized. User Action: Use the DCL commands DIRECTORY and DUMP to determine if the file is present, if the file is writable, and if storage is allocated to all blocks of the file. In particular, use DUMP/BLOCK=START=lastblock to dump the last allocated block of the file. (If this dump of the last block fails, the GPT.SYS file likely overhangs the end of the disk, and you cannot use GPT bootstrap structures with this disk. You must either select and use MBR-only operations or you must reinitialize the entire disk with a valid GPT and reload the files.) 2 GPTVERS GPT version vers detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This message displays the version of the GPT structure, 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 HIGHERVERS unexpected GPT bootblock data structure version detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified bootblock contains what appear to be GPT data structures, but the data structure version code is not one that was expected. User Action: The command or request may not be able to operate as requested. If the target volume contains valid GPT structures, then the version of this tool is apparently incompatible with that of the target structures. Depending on the context, the utility may attempt to continue processing. 2 HRDERR volume reports a hard error Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume reports a structural error, and may not be in a consistent state. User Action: Check the target volume for structural validity. 2 ICFNEST indirect command file nesting exceeds max level limit Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the number of indirect command file levels has exceeded the hardcoded limits within the application. User Action: specify fewer levels of nesting, or contact support and request that the hardcoded maximim permissible number of indirect command file nestings be increased. 2 ILLIOFUNC illegal 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 illegal, 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 INCOMPATFAT record organization or file structure not supported by FAT Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The target file has an RMS record format or file structure that is not supported by FAT, nor by operating systems or environments or applications typically accessing files on FAT volumes. As a result, the file contents are unlikely to be easily accessable within these environments, and may or may not be viewable by or by accessable these applications. It is unlikely that the record attributes and file structures will restored correctly should the file be subsequently copied back onto an OpenVMS disk, as well; the record attributes and details of the file structure may or will be lost. While most any modern platform does support one or more sequential file formats, there can be and often are record-level differences within the bytes associated with a particular sequential file storage format on a particular platform. The file record format for the specified file is expected to be unique to OpenVMS. Files using block formats, or files of Stream or Stream Linefeed record formats are generally the most compatible formats across the most platforms. This message is only generated when copying file(s) from an OpenVMS volume structure onto a FAT volume structure. User Action: No particular user action is required, though the conversion to and the use of a record format supported more directly by applications using FAT would certainly be recommended. You can protect OpenVMS structures using a zip archive to protect the attributes, or you can potentially restore the attributes by using either CONVERT/FDL or SET FILE/ATTRIBUTES to restore lost record attributes on any files imported back into OpenVMS. 2 INCOMPMOUNT incompatibly-mounted target volume; mounted private or foreign Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The target volume for the operation is mounted privately or is mounted foreign, and only a subset of bootblock operations are available on such volumes. The current operation is not one of the operations permitted on such volumes-file contiguity checks and file size checks are not permitted on foreign-mounted volumes, for instance. User Action: This message is typically associated with another error. 2 INCVOLLABEL incorrect volume label Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The label specified does not match the label on the volume. User Action: Verify that the correct volume is mounted; verify the label entered. Repeat the request, specifying the correct volume label or specifying /OVERRIDE=ID. 2 INSFMEM insufficient free memory Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: there is insufficient memory available for an allocation request, either due to insufficiently-configured process address space or (far less likely) due to a corruption of the process memory pool. User Action: configure additional process memory, log out and back in, and restart the application. 2 INTIL3OVF internal itemlist overflow Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: An internal consistency check has detected an itemlist overflow, and the size of the particular itemlist data structure involved is hard-coded. 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 INVCACHE invalid or mismatched file cache detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the contents of the file cache do not reflect the current file User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 INVCHAIN invalid cluster chain detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the contents of the file cluster chain are corrupted. User Action: If this error can be reproduced and is not a result of invalid data input, please contact support. 2 INVF12CF invalid FAT12 volume cluster factor Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT12 volume can offer more than 4084 clusters, and this volume erroneously offers more. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT12 volume with a larger cluster factor, or reinitialize the volume using FAT16 or FAT32. 2 INVF12RSC invalid FAT12 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT12 volume can have a reserved sector count of zero. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT12 volume. 2 INVF16CF invalid FAT16 volume cluster factor Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT16 volume can offer less than 4085 clusters nor more than 65524 clusters, and this volume is outside the valid range. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT16 volume with a cluster size that will produce a cluster factor in the required range, or reinitialize the volume using FAT12 or FAT32. 2 INVF16RSC invalid FAT16 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT16 volume can have a reserved sector count of zero. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT12 volume. 2 INVF32CF invalid FAT32 volume cluster factor Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT32 volume can offer less than 65525 clusters, and this volume is outside the valid range. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT32 volume with a smaller cluster size; with a cluster factor within the required range, or reinitialize the volume using FAT12 or FAT16. 2 INVF32RSC invalid FAT32 reserved sector count Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Per EFI FAT specifications, no FAT32 volume can have a reserved sector count of zero. The FAT volume is apparently corrupted. User Action: Reinitialize the FAT12 volume. 2 INVLBN invalid logical block number Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified logical block number is invalid. This generally points to an internal error, or to an error in the volume structure. User Action: Retry. Dismount and remote the volume, and retry. If the problemc persists, reinitialize the entire volume. If the condition can be reproduced, please contact support. 2 INVVBN invalid virtual block number Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified virtual block number is invalid. This generally points to an internal error, or to an error in the volume structure. User Action: Retry. Dismount and remote the volume, and retry. If the problemc persists, reinitialize the entire volume. If the condition can be reproduced, please contact support. 2 INVVOL Invalid volume format Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: One or more of the volume structure checks has failed. Failures normally indicate that the specified target disk is not a recognized or supported format, or the target disk volume is corrupted. 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 ISDIR target is a directory Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified target file is a directory. User Action: This particular message is informational, and is normally associated with another message. 2 ISMFD target is master file directory Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified file is the volume MFD. User Action: This particular message is informational, and is normally associated with another message. 2 LBLOCKED logical block I/O operations to target device are blocked Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: All logical block read and write operations targeting the specified device are disabled User Action: An internal safety interlock has been triggered. Please contact support. If this error can be reproduced with a specific command or a specific command sequence, please provide the reproducer. 2 LOWERVERS Bad GPT bootblock data structure version detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified bootblock contains what appear to be GPT data structures, but the data structure version code is too old. User Action: The command or request may not be able to operate as requested. If the target volume contains valid GPT structures, then the version of this tool is apparently incompatible with that of the target structures. Depending on the context, the utility may attempt to continue processing. 2 LOWVER specified software version is too low Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the software version does not meet minimal requirements. User Action: Check that the specified software version meets minimal requirements, and upgrade the software as needed. 2 MBRPART valid Master Boot Record partitioning detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume has MBR disk partitioning User Action: This particular message is informational. 2 MCMLXXX_MMCVII Year year exceeds FAT architectural limits for the date Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified date is outside of the FAT year limits, and most likely the date has exceeded the Year 2107 (MCMLXXX) expiration date. This condition can also arise when the specified year is prior to 1980 (MMCVII); when the year specified precedes the earliest year permitted within the FAT architecture. User Action: exchange the current FAT disk volume structure for a new file system or for an updated FAT file system (if available), or set the system time to a date between 1980 and 2107, inclusive. For additional information, consult any available Y2K archives. 2 MFDFULL master file directory is full Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the master file directory file has insufficient room for the requested additional file or directory, and the master file directory cannot be extended on FAT12 and FAT16 volumes. User Action: delete some files, or use shorter filenames. 2 MNTCOMMENT please load the FAT volume into the drive Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: we here ask the operator nicely, seeking to have the FAT volume loaded into the specified disk drive. User Action: this message is intended to be displayed to the system operators upon problems mounting the specified FAT volume. 2 MOUNTED FAT volume volume has been mounted Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified FAT-format volume has been mounted. User Action: The FAT-format storage volume has been mounted, typically at user request. 2 MOVEABLE file is erronously marked as moveable Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The file attributes erroneously permit the relocation of the bootfile by a disk defragmentation tool, and the target volume is thus vulnerable to corruptions. User Action: Use the DCL command SET FILE/NOMOVE to prevent the file from being relocated. Failure to mark the bootfile as NOMOVE can lead to stale information stored in the boot block and to corresponding problems with subsequent bootstraps. Should the bootfile actually be relocated, you will have to bootstrap from another OpenVMS system disk or from an OpenVMS distribution kit, and update the contents of the bootblock. 2 MUSTBEDIR specification must be a directory for TREE or SUBDIR Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the user provided a filename when only a path name can be specified. The /SUBDIR command can use a wildcarded filename but not a fully specificed name. User Action: Please respecify the command, using the expected syntax. 2 NESTED nested partitions are incompatible with some EFI firmware Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: Certain versions of EFI firmware and all current versions of SETBOOT are intolerant of any attempts to nest MBRs. User Action: Do not nest MBRs. 2 NEWALIAS new EFI console boot alias will be required Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A request to preserve existing signatures has been made, but no existing signatures have been found. New signatures have been generated, and any existing EFI console boot aliases will have to be recreated or new aliases created. This typically indicates there were no existing EFI GPT structures, or the structures were found to be corrupted. User Action: The requested operation completed and the EFI bootstrap structures written to the disk are valud, though there are new disk signatures and any existing EFI console boot aliases referencing existing signatures could not be preserved. Use the EFI console to delete the old boot aliases, and then to add the new boot alias associated with the new signature. 2 NOBOOACC no bootblock access is available Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: attempts to access the bootblock data structures stored in LBN0 via virtual I/O and the GPT.SYS or INDEXF.SYS files and via direct logical I/O read access for LBN0 have failed. This prevents the determination of the target bootblock architecture, and any other similar derivative information. User Action: Please target a disk with accessable GPT.SYS or INDEXF.SYS structures, or please operate from within a process context possessing LOG_IO privilege or other necessary privileges. 2 NOBTBALPHA target volume does not contain the Alpha VAX BTB bootblock Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target does not contain the BTB structures associated with an OpenVMS Alpha bootstrap. User Action: The command or request cannot operate as requested. If the target volume contains BTB structures, then the volume is apparently corrupted. 2 NOBTBVAX target volume does not contain the VAX BTB bootblock Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target does not contain the BTB structures associated with an OpenVMS VAX bootstrap. User Action: The command or request cannot operate as requested. If the target volume contains BTB structures, then the volume is apparently corrupted. 2 NOCLUSFREE no clusters available for allocation Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: There are no storage units available for the requested operation; the disk is too full to process the request. User Action: There is insufficient storage for the requested operation. Release some storage, delete some files, or move the contents of this disk to a larger disk volume. 2 NOCOLON ensure the device alias specification includes a colon Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message is usually associated with a report that the specified device alias name is invalid. User Action: Specify a valid device-like name (with colon) as the device alias. 2 NODISKSIG no valid disk signature found Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A request to preserve existing disk signatures has been made, but no existing signatures have been found. New signatures have been generated, and any existing EFI console boot aliases will have to be recreated or new aliases created. This typically indicates there were no existing EFI GPT structures, or the structures were found to be corrupted. User Action: The requested operation completed and the EFI bootstrap structures written to the disk are valud, though there are new disk signatures and any existing EFI console boot aliases referencing existing signatures could not be preserved. Use the EFI console to delete the old boot aliases, and then to add the new boot alias associated with the new signature. 2 NODISMOUNT cannot dismount volume volume Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume is not mounted. User Action: The particular command or operation is incompatible with a volume that is already mounted. Specify the correct target device for the command, or DISMOUNT the specified device and then re-issue the command. 2 NOEFIBOOT target volume does not contain an MBR or GPT EFI partition Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target does not contain the structures associated with an OpenVMS EFI MBR or EFI GPT bootstrap. User Action: The command or request cannot operate as requested. If the target volume contains MBR structures, then the volume is apparently corrupted. 2 NOEFISIZ unable to determine size for SYS$EFI.SYS file Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The software is not able to determine the size of the SYS$EFI.SYS file, and no size has been provided. This condition most commonly arises when the target volume is mounted foreign. User Action: If using the callable interface with a foreign- mounted volume, please specify the size. If using the command interface, please remount the target volume native. 2 NOFATCACHE FAT cache not allocated Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This indicates an internal error within the processing, and particularly that a core cache data structure has been found to be unallocated and uninitialized. User Action: If the condition can be reproduced, please contact support. 2 NOFATDEV no FAT device is mounted Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: there is no FAT device known to the utility User Action: You must issue the MOUNT command within the utility, and you can then re-issue the failing command. 2 NOFATVER FAT partition version information is not available Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the FAT partition was not built with the EFI$CP tool, and compatibility with OpenVMS cannot be assumed. User Action: Initialize the FAT partition with the appropriate OpenVMS tools, and retry the operation. 2 NOFILES no matching files were found Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified directory is empty, or the specified file was not found. User Action: This can be entirely normal. If the directory should have files or the file should exist, the volume and/or the directory is corrupt. Restore from BACKUP. 2 NOGPT specified target volume does not contain a GPT Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume does not contain the structures associated with an OpenVMS GPT. User Action: The command or request cannot operate as requested. If the target volume contains GPT structures, then the volume is apparently corrupted. If the target volume does not contain GPT structures, then the command cannot operate as requested. 2 NOMBR target volume does not contain a MBR Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume does not contain the structures associated with an OpenVMS MBR. User Action: The command or request cannot operate as requested. If the target volume contains MBR structures, then the volume is apparently corrupted. If the target volume does not contain MBR structures, then the command cannot operate as requested. 2 NOMBRPART selected Master Boot Record partition not available Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the requested partition was not detected on the target volume. User Action: Re-enter the command with no partition specified, or with a partition specification valid for the target volume. 2 NONCONTIG file must be marked as contiguous Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The file is comprised of two or more ranges of blocks, or could otherwise become fragmented. User Action: Use COPY/CONTIGUOUS or similar command to ensure that the file is contiguous, and retry the command. 2 NONCONTIGDIAG diagnostic partition must be marked as contiguous Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The SYS$DIAGNOSTICS hardware diagnostic partition is comprised of two or more ranges of blocks, or could otherwise become fragmented. User Action: Use COPY/CONTIGUOUS or similar command to ensure that the diagnostic partition is contiguous, and retry the command. 2 NONFAT target does not reside on a known FAT device Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the device specified for a FAT operation is not a recognized FAT device specification. The target is either not a FAT device, or not a FAT device that has been mounted within the current utility environment. This is incompatible with the command requirements. User Action: Respecify the command, with a corrected FAT device name or with a corrected FAT file specification parameter, or mount the target FAT device within the current utility environment. 2 NONSECTORIAL sector size bytes is not supported Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the expected and sole supported sector size is 512 bytes. The target FAT disk is using a different sector size. User Action: the format of the specified FAT disk is incompatible, and cannot be accessed. 2 NOPARTITION the target volume is not partitioned Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: this message indicates that the target volume is not partitioned. User Action: This message can be associated with another message, usually BADPARTVAL. If so, Resolve the associated and underlying error. 2 NOSUREFIX recovery from corruption may or may not be possible 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 NOTACHAN specified channel is invalid Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an attempt was made to perform an I/O operation on an invalid channel. 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 NOTCONTIG file is not contiguous Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified file must be comprised of a contiguous series of disk blocks, and the file has been found non- contiguous. User Action: Use the DCL command COPY/CONTIGUOUS to create a contiguous file from the current non-contigous file, and reissue the failing command. If there is insufficient contiguous free space on the target disk, you may have to delete or relocate existing files, defragment the disk using a tool such as BACKUP/IMAGE, or both. 2 NOTFOUND specified file or directory was not found Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: absent or not, the heart does not grow fonder. User Action: specify a file or directory name that is present. 2 NOTMOUNTED target volume is not mounted or not ready Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The specified target volume must be mounted. User Action: Use the DCL commands SHOW DEVICE and MOUNT to determine the device status, and to mount the specified volume on the target device. 2 NOVBNMAP VBN scatter-gather map not allocated Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: This indicates an internal error within the processing, and particularly that a core mapping data structure has been found to be unallocated and uninitialized. User Action: If the condition can be reproduced, please contact support. 2 NULLNAM part or all of a path or file specification is null Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: parsing has found in invalid or incorrect file specification. User Action: Respecify the pathname or filename after checking the syntax. 2 NULLTARG specified target is null Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: an internal search target is null, and should not be. 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 NYI Feature not yet implemented Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The requested feature or requested operation is not available. User Action: You will not be able to perform the requested operation. 2 ODDITY internal structural oddity detected Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: A fatal internal processing error or other unexpected internal condition has been detected. 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 OFFLINE environment offline, unavailable and/or unsupported Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: The particular command or requested operation is not available, is explicitly disabled, or is presently unsupported within the current run-time context. User Action: The particular command or operation is not available. 2 ONEPART single-partition volume; no Master Boot Record partitioning Facility: EFI$CP, The OpenVMS EFI Partition Control Program Explanation: the specified volume has does not utilize MBR 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.