FreeDOS VOL and LABEL: Identify Volumes Without Trusting a Drive Letter

In FreeDOS, VOL displays a volume label and serial number when they exist, while LABEL creates, changes, or deletes a label. These commands are helpful when several removable disks or partitions appear under familiar drive letters. Their output is still filesystem metadata, not a guarantee that the letter points to the same physical device tomorrow.

The key operational distinction is between a drive letter, a human-readable volume label, and a volume serial value. A drive letter is the current DOS namespace assignment. A label is a mutable name intended to help people recognize a volume. A serial value is reported by VOL, but FreeDOS’s user-facing command does not claim that it is a manufacturer serial number, unique identity, or cryptographic proof. Treat them as corroborating clues, then verify expected files and device configuration before any write operation.

Inspect before changing a label

Start with an explicit drive:

VOL C:
LABEL C:
DIR C:\

VOL is an internal FreeCOM command. LABEL is an executable distributed with FreeDOS. LABEL with a drive but no new name displays the current label and asks whether to create a replacement, according to the command reference. Do not press through a prompt until you have confirmed the volume is the intended target. In scripts, always specify the drive rather than relying on the current drive.

Record the result along with the machine or virtual-machine configuration, the current drive mapping, and a known marker file. If the volume is removable, confirm which physical medium is inserted. If the system has USBASPI, a network redirector, a RAM disk, or substituted/joined paths, the letter may not correspond to the physical device an operator expects.

LABEL accepts a name as an argument or prompts when one is omitted. FreeDOS help specifies an 11-character maximum and says that network drives and ASSIGNed, JOINed, SUBSTed, or SWSUBSTed drives cannot be labeled. A command failure under one of those conditions is not evidence that the volume is damaged. Identify the namespace layer first and do not bypass a restriction by guessing at a lower-level disk write.

Separate label, serial value, filesystem, and partition

A volume label is not a partition name and does not change the partition table or filesystem type. The FreeDOS VOL reference gives FORMAT drive /V:LABEL as another way to assign a label, but FORMAT is a much broader and destructive operation; never use it merely to fix a name. LABEL is the narrow operation for changing the label on a supported volume.

The volume serial shown by VOL is also not the same as a drive letter or the physical disk’s hardware serial. The command interface reports a value associated with the mounted filesystem; it does not expose a device-enclosure identity or prove uniqueness across cloned images. If two byte-for-byte copies of a disk are attached, an identical filesystem label and serial are not surprising. If a volume is reformatted or cloned, naming metadata may be reused or changed independently of the storage device.

Do not use labels as access control. Labels are visible metadata and can often be changed. They are not passwords, ownership lists, encryption settings, or a tamper-evident identifier. For evidence handling, record the volume metadata as one observation and acquire or hash the contents through a suitable tool. Preserve the original medium before any modification.

Likewise, do not treat the serial string alone as a definitive forensic marker. The official FreeDOS VOL help promises to display the volume label and serial number if they exist, but it does not describe a hardware serial or global uniqueness guarantee. The safe inference is limited: the command provides useful comparison data for the currently mounted volume. Combine it with a device inventory, partition information, known marker paths, and hashes appropriate to the case.

Change labels with a reviewed plan

If a label change is intended, write down the old value, the desired value, and the exact drive before invoking the mutation. A direct invocation can set the value:

LABEL D: ARCHIVE-2026
VOL D:
DIR D:\

Choose a fresh, recognizable label within the documented limit, using characters accepted by the actual utility and filesystem. Then query it again with VOL and inspect the root directory. The displayed result verifies the command’s visible effect; it does not validate every metadata copy or prove that a different operating system will display the same capitalization.

Do not use a generic label such as DATA on many removable media if operators rely on it to distinguish one copy from another. Labels need not be unique. A better operational scheme combines a human name with a controlled inventory record, for example a project code plus an acquisition date, while respecting the filesystem’s character and length limits. Maintain a separate mapping from inventory record to device and image checksum.

If you are renaming a volume that contains active applications, consider whether scripts, backup utilities, or users depend on the old label. The drive letter may remain unchanged, but media-selection prompts and human workflows can change. Search configuration files for the old label, update only the intended references, and test the boot and application paths before returning the disk to routine use.

Use labels in removable-media workflows

Labels were valuable when a task used several floppy disks or removable volumes. A command prompt can display a label to help a person select the intended disk, and an operator can compare that name against a written manifest. The label is strongest as a human-facing check when paired with contents that are expected on that disk.

For a multi-disk backup, create a manifest outside the media that records disk order, label, reported volume serial, file list, checksums, and date of acquisition. On restore, check every inserted disk before copying. Do not assume A: or D: still identifies the same media after a reboot or after loading another storage driver. Verify a marker file and the required subdirectory before allowing a script to write.

For USB storage, DOS driver stacks can assign letters according to detected devices and configuration. Confirm the actual contents and metadata instead of assuming the last letter is the USB drive. Keep the source read-only where possible while collecting evidence. If you need to change a label after confirming the volume, capture the old state first and test the updated label with the program that consumes it.

Diagnose missing or confusing VOL output

If VOL does not show an expected label or serial, first check that the drive letter exists and can be read. Confirm that it points to the intended volume and that the filesystem driver mounted it. A command that queries a nonexistent, disconnected, redirected, or substituted path may fail for reasons unrelated to the media contents.

Compare VOL with DIR and, where appropriate, FDISK’s read-only partition report. FreeDOS help says DIR and LABEL can also show the serial number; if output differs, record the command versions and the exact path. Do not repair or format a volume just because its label is absent. A label is optional. The existence of files and a valid mounted filesystem matter separately.

If LABEL reports that the volume cannot be labeled, check the documented exclusions for networked and logical path-mapping drives, permissions or write protection supplied by the device, and the exact target. Keep the original volume unchanged during diagnosis. Test a label change on a disposable image before using the procedure on a unique disk.

Acceptance checks

A sound volume-identification procedure records the current DOS drive mapping, queries VOL with an explicit letter, inspects the label and serial together with expected files, and verifies the backing device or image through an independent inventory. If a label must change, preserve the old value and content manifest, invoke LABEL only after confirming the target, then query VOL and DIR again.

The result should be described accurately: “FreeDOS reported label X and volume serial Y for drive D: during this boot” is stronger and safer than “disk D is device Y.” Keep the label useful for humans, the serial as corroborating filesystem metadata, and the device record as the source of physical identity. This prevents a familiar name from becoming a destructive assumption.

Related:

Sources: