Makes the specified FAT disk volume or the specified FAT
partition file accessable. To mount a FAT partition file, you
must specify the /DEVICE_ALIAS qualifier.
EFI$CP is presently limited to a maximum of one mounted FAT
device at any one time.
Format
MOUNT target label-name log-name
1 – Parameter
target
Specifies the disk device that is to be made accessable to the
EFI$CP environment, or the FAT partition file specification when
used in conjunction with /DEVICE_ALIAS.
The FAT12 volume structure does not permit arbitrary capacities.
Disks and partitions with fewer than 4085 clusters are always
FAT12, and must match one of the predefined devices.
For operations on disk devices or partitions with capacities
within the FAT12 capacity range, the disk capacity must match
that of a recognized floppy device. Most commonly, this is
either the 1.44 megabyte (2880 blocks) or the 2.88 megabyte (5760
blocks) floppy disk, or an LD partition of a matching size, or a
partition file of a matching size.
For read-only operations or operations involving partition
files located on DVD or other read-only media, /NOWRITE must
be specified.
For additional related information, please see the EFI$_UNRECRX
error.
label-name
Specifies the volume label for the target volue.
If the label value contains spaces or other reserved characters,
the label string must be quoted.
The label specification match operation is both case-blind and
space-filled. In particular, if the length of the label string
specified is less than the length of the volume label, the short
of the two specifications is assumed to be space-padded.
If the target volume label is not known, you can can consider the
use of /OVERRIDE=IDENTIFICATION to override the volume label, and
mount the volume.
The volume label is used to create an OpenVMS logical name of
the format EFI$DISK$vollab. Whitespace and other characters
not permissible within typical OpenVMS logical names will be
replaced with underscores within the resulting logical name. This
logical name can be used to reference the target device within
the remainder of the EFI$CP session.
This logical name is particularly useful if you choose to
sequentially activate or to nest command procedure calls (see
@), with one procedure used to initialize and mount the target
device, and one or more subsequent procedures to perform a series
of operations-without specific regard to the target physical
device name used by the initial procedure.
log-name
Specifies a logical name to be created. If specified, the
translation of this logical name will contain the device
specification.
If the label-name parameter value is to be overridden (using
/OVERRIDE=IDENTIFICATION), the label-name parameter must be
specified (as a null string) if this log-name parameter is also
to be specified. With /OVERRIDE=IDENTIFICATION, the null string
specified within the label-name parameter is ignored.
2 – Description
This command causes EFI$CP to access and to read in data
structures needed for processing the FAT disk volume.
For EFI partition files such as SYS$LOADABLE_IMAGES:SYS$EFI.SYS
and SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS, you can use software
such as the OpenVMS LD component to render the partition file
accessable as a (usually foreign-mounted) disk device.
If the volume FAT data is found corrupted, MOUNT will attempt
to read the FAT data from a shadow copy of the FAT sector. Most
FAT volumes have two copies of FAT data present, and MOUNT will
attempt to use all available copies upon receipt of FAT I/O
failures within the FAT data.
MOUNT does not compare the FAT data across copies of the FAT upon
successful I/O operations. Comparison is not attempted as with
typically only two copies of FAT data present, and as there is no
checksumming and no ECC within FAT, there is no way to determine
which copy of the FAT is correct. EFI$CP does write modified data
to all copies of the FAT present
Should MOUNT detect sector read I/O errors in all copies of a
FAT sector, MOUNT will synthesize a block of FAT EOC (End of
Cluster Chain) markers to replace the missing FAT data, and will
continue with the MOUNT attempt. This EOC sector will effectively
truncate any files using cluster chain data stored within the bad
FAT sector, but may allow access to other files and to parts of
any files that reference (valid) cluster chain data prior to that
stored within the failed sector. Should this recovery processing
be triggered, you will obviously want to immediate relocate all
remaining data onto other media.
Mount can also check the integrity of the files when /CHECK
or /REPAIR are specified in the command. If the volume was
not cleanly dismounted, the check will be done unless the user
explicitly uses /NOCHECK. Some older versions of EFI$CP may have
created files with incorrect lengths which show up as errors in
EFICHK (a utility in the VMS UTILITIES area that can be run from
the EFI command shell). If EFI$CP detects that the FAT volume was
created with an old version of EFI$CP, it will automatically
check and repair the volume (unless /NOWRITE or /NOCHECK is
specified) and update the volume information to the current
version of EFI$CP.
3 – Qualifiers
3.1 /CACHE
/CACHE
/NOCACHE (default)
This qualifier causes EFI$CP to cache critical volume data data
in memory, rather than writing the data and the changes out to
the partition or the disk volume after each EFI$CP command.
Selecting /CACHE provides better performance (and particularly
with slow devices, such as floppy disk volumes), though there is
an increased risk of exposure to inconsistent or incomplete data
should an application or a system problem arise before the caches
are flushed; should the application exit unexpectedly prior to a
DISMOUNT operation.
If you choose MOUNT/CACHE, you will want to specify the DISMOUNT
command to dismount the device or the partition; to effect the
necessary cache flush. Failure to cleanly flush the volume cache
can result in volume corruptions and/or data loss.
3.2 /DEVICE_ALIAS
/DEVICE_ALIAS=alias
/NODEVICE_ALIAS (default)
This qualifier selects the device name alias to be used for
references to a directly-accessed partition file; for direct
access to a partition file. The specified string will be the
device name for subsequent accesses.
The permissible character set for this string is that of devices;
the same symbol character set used for logical names. Like a
logical name, there is no requirement to mimic the OpenVMS device
name fields.
The specified alias must include a trailing colon.
3.3 /DIAGNOSTICS
/DIAGNOSTICS
/NODIAGNOSTICS (default)
This qualifier is subject to change without notice, reserved for
use during HP regression testing, and should be specified only
under the direction of the HP Customer Support Center.
This command causes additional messages to be displayed.
3.4 /LOG
/LOG (default)
/NOLOG
Displays status-related and informational messages resulting from
the MOUNT request.
When not specified, some operations will still be logged - such
as problems found by the /CHECK qualifier. By specifying /NOLOG -
absolutly no logging will be done.
3.5 /OVERRIDE
/OVERRIDE=keyword
When used with the keyword IDENTIFICATION, this overrides the
requirement to specify a volume label.
If the label-name parameter is to be overridden (using
/OVERRIDE=IDENTIFICATION), then the label-name parameter must
be specified (as a null string) if the log-name parameter is also
to be specified. With /OVERRIDE=IDENTIFICATION, the null string
specified within the label-name parameter is ignored.
When used with the keyword GEOMETRY, this operation overrides
the FAT12 disk volume geometry requirement check. So long as
the FAT12 volume matches the FAT12 volume size requirements, the
volume can be mounted.
The geometry reported by the target device will not be altered.
When used with the keyword CORRUPTIONS, this operation
overrides various FAT volume structure checks inherent in volume
processing, and to thus permit continued operations with certain
questionable or potentially corrupt FAT volume structures.
Thus mechanism can bypass isolated, specific and very limited
corruptions found within the FAT volume structure. This does
not provide a generic mechanism for repairing or recovering from
arbitrary FAT volume structure corruptions.
Use of the /OVERRIDE=CORRUPTIONS mechanism is not recommended.
This mechanism should be used only under explicit directions of
the HP Customer Support Center.
3.6 /REGRESSION_TESTING
/REGRESSION_TESTING
/NOREGRESSION_TESTING (default)
This qualifier is subject to change without notice, reserved for
use during HP regression testing, and should be specified only
under the direction of the HP Customer Support Center.
This qualifier alters command output and particularly alters
the date and time values displayed, explicitly and only for use
during EFI$CP regression-testing operations.
3.7 /SYSTEM_ALIAS
/SYSTEM_ALIAS=alias
/NOSYSTEM_ALIAS (default)
This qualifier selects the device name alias to be used for
references to a directly-accessed partition file, and sets
the partition name to SYS$LOADABLE_IMAGES:SYS$EFI.SYS or
SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS.
When this qualifier is specified, the device name parameter is
ignored.
This qualifier is otherwise similar to /DEVICE_ALIAS.
3.8 /WRITE
/WRITE (default)
/NOWRITE
The target volume is mounted read- and write-accessable by
default. Specification of /NOWRITE permits the target to be
marked as read-only storage, thus preventing any unintentional
modifications to the volume.
When mounting a partition file located on DVD media,
specification of /NOWRITE is required.
3.9 /CHECK
Forces the FAT file structure to be validated. It is implicitly
done if the version of EFI$CP used to create the volume is out-
of-date. Unless the /NOCHECK qualifier is used - which will
prevent all checking. Older versions of EFI$CP got the file
lengths wrong. It also screwed up the RENAME operation on files
(leaving a stale file with 0 length). The /CHECK option does
essentially what EFICHK will do from the EFI shell.
Use /NOCHECK or /WRITELOCK if you are concerned about changing
the contents.
3.10 /REPAIR
/REPAIR (default)
/NOREPAIR
When the volume is CHECKED (see above) the /REPAIR option will
fix prolems that can be solved.
Older versions of EFI$CP got the file lengths wrong. It also
screwed up RENAME. The /CHECK option does essentially what EFICHK
-F will do from the EFI shell.
Use /NOCHECK or /WRITELOCK if you are concerned about changing
the contents.
EFI$CP> mount/log dva0:/override=identification
%EFI-I-SEEKMBR, searching for Master Boot Record
%EFI-I-ONEPART, single-partition volume; no Master Boot Record partitioning
%EFI-I-SEEKBPB, searching for BIOS Parameter Block
%EFI-I-SEEKBPBOK, valid BIOS Parameter Block detected
%EFI-I-MOUNTED, FAT volume NO NAME has been mounted
-EFI-I-NOPARTITION, the target volume is not partitioned
EFI$CP>
EFI$CP> mount/log lda251: "NO NAME"
%EFI-I-SEEKMBR, searching for Master Boot Record
%EFI-I-ONEPART, single-partition volume; no Master Boot Record partitioning
%EFI-I-SEEKBPB, searching for BIOS Parameter Block
%EFI-I-SEEKBPBOK, valid BIOS Parameter Block detected
%EFI-I-MOUNTED, FAT volume NO NAME has been mounted
-EFI-I-NOPARTITION, the target volume is not partitioned
EFI$CP>
EFI$CP> mount/log/override=id sys$loadable_images:sys$efi.sys -
3.11 /device_alias=foo:
%EFI-I-SEEKMBR, searching for Master Boot Record
%EFI-I-ONEPART, single-partition volume; no Master Boot Record partitioning
%EFI-I-SEEKBPB, searching for BIOS Parameter Block
%EFI-I-SEEKBPBOK, valid BIOS Parameter Block detected
%EFI-I-MOUNTED, FAT volume SYS$EFI has been mounted
-EFI-I-NOPARTITION, the target volume is not partitioned
EFI$CP> directory foo:\
This shows the results of mounting the EFI partition from an OpenVMS V8.2 system. Note that despite the
dire warnings, the contents of the files turns out to be OK. The older version of EFI$CP got the file
size wrong, but copied the contents OK.
EFI$CP> mou/repair/over=id/dev=efi: sys$loafable_images:sys$efi.sys
%MOUNT-I-NODISM, volume was not cleanly dismounted. Check in progress.
%EFICP-W-BADCCNT, EFI:\efi\vms\tools\biosutil.efi actual cluster count of 104 does not match the file allocation of 105.
Filesize of 213504 bytes, requires 420 blocks (rounded to the cluster factor of 4)
420 blocks shown allocated, but 104 actual clusters (416 blocks) counted in file
The disk storage (212992 bytes) is smaller than the file size (213504 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\tools\efichk.efi actual cluster count of 463 does not match the file allocation of 464.
Filesize of 949248 bytes, requires 1856 blocks (rounded to the cluster factor of 4)
1856 blocks shown allocated, but 463 actual clusters (1852 blocks) counted in file
The disk storage (948224 bytes) is smaller than the file size (949248 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\tools\ftpd.efi actual cluster count of 470 does not match the file allocation of 471.
Filesize of 963072 bytes, requires 1884 blocks (rounded to the cluster factor of 4)
1884 blocks shown allocated, but 470 actual clusters (1880 blocks) counted in file
The disk storage (962560 bytes) is smaller than the file size (963072 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\tools\tcpipv4.efi actual cluster count of 650 does not match the file allocation of 651.
Filesize of 1331712 bytes, requires 2604 blocks (rounded to the cluster factor of 4)
2604 blocks shown allocated, but 650 actual clusters (2600 blocks) counted in file
The disk storage (1331200 bytes) is smaller than the file size (1331712 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\vms_bcfg.efi actual cluster count of 123 does not match the file allocation of 138.
Filesize of 282624 bytes, requires 552 blocks (rounded to the cluster factor of 4)
552 blocks shown allocated, but 123 actual clusters (492 blocks) counted in file
The disk storage (251904 bytes) is smaller than the file size (282624 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\vms_set.efi actual cluster count of 111 does not match the file allocation of 121.
Filesize of 247296 bytes, requires 484 blocks (rounded to the cluster factor of 4)
484 blocks shown allocated, but 111 actual clusters (444 blocks) counted in file
The disk storage (227328 bytes) is smaller than the file size (247296 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-W-BADCCNT, EFI:\efi\vms\vms_show.efi actual cluster count of 110 does not match the file allocation of 121.
Filesize of 247296 bytes, requires 484 blocks (rounded to the cluster factor of 4)
484 blocks shown allocated, but 110 actual clusters (440 blocks) counted in file
The disk storage (225280 bytes) is smaller than the file size (247296 bytes)
Truncating file! ***CHECK CONTENTS FOR VALIDITY***
%EFICP-I-FATCHECK, 7 errors found, 7 fixed. 14 files in 3 folders checked, 11510462 total bytes in 5623 clusters
EFI$CP>