Dynamic Volumes Are Not Displayed Accurately in Text-Mode Setup or Recovery Console
This article was previously published under Q227364
This article has been archived. It is offered "as is" and will no longer be updated.
While you are using the Recovery console to repair an unbootable Windows 2000 system, or during the text-mode portion of Windows 2000 Setup, dynamic disks may not display accurate information about the correct sizes or the complete list of volumes contained on the dynamic disk(s). There is also no visible designation as to whether a disk is a basic or dynamic disk.
NOTE: Deleting or reformatting any dynamic disk volume using the Recovery console's DISKPART or FORMAT command, or during Windows 2000 text-mode Setup, could result in permanent data loss.
Windows 2000 does not fully support pure dynamic disk volumes during Setup. Setup only understands dynamic disk partitions that are hard-linked. Hard-linked dynamic partitions are created when you upgrade a basic disk to dynamic and the basic disk had pre-existing primary and/or logical drives configured. Each of the pre-existing partitions retains a legacy-style partition table entry (type 42 for primary and type 05 for extended), even after upgrading the disk to dynamic. These special hard-linked partition table entries allows Setup to recognize them as valid partitions for installation.
Pure dynamic disks (those not containing any hard-linked partitions) have only a single partition table entry (type 42) to define the entire disk. Dynamic disks store their volume configuration in a database located in a 1-MB private region at the end of each dynamic disk. Volumes contained on a pure dynamic disk are soft-linked, and drive letters for them are not displayed until Setup is complete. Setup displays a single drive letter for the whole drive (usually the drive letter assigned to the first soft-linked partition) even if it has multiple volumes configured. You cannot install a fresh installation to this type of dynamic disk without destroying underlying volumes.
Keep a record of all dynamic disks and the volumes they contain, noting which volumes are hard-linked. Uniquely name your volumes so they can be identified during a repair operation or during text-mode Setup. Do not delete any of the dynamic volumes unless you are going to delete all of them from text-mode Setup.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The following examples demonstrate some of the misleading information you may see in text-mode Setup when you have existing dynamic volumes:
- Dynamic disk with multiple dynamic volumes created after the disk is upgraded from basic:
Only the first volume is displayed. Its size equals the full size of the disk it is on. Deleting that single volume deletes all dynamic volumes on the disk.
- System/boot disk is dynamic:
The system and/or boot volume is displayed as the correct size, but deleting or reinstalling to any volume on this disk may cause the disk to be "dynamic unreadable."
- Dynamic disk with one volume created before upgrading to dynamic and additional volumes created after the upgrade:
The first volume appears in text-mode Setup with the correct size. A second volume is displayed as using the rest of the disk, although it may not be that large. Any additional dynamic volumes are not displayed and can be unknowingly removed if the second volume is deleted. Any volumes deleted from any dynamic disk may result in data loss in other volumes.
- Member of a dynamic mirrored, striped, spanned, or RAID-5 volume:
These volumes may have the same drive letter as the other members of the volume but are not designated as being a member of one of these types of volumes. Deleting one member may make the other members unusable, depending on the type of volume. The individual members are displayed in the same way as described in the first three examples.
For additional information about how Windows 2000 displays and assigns drive letters during Setup, please see the following article in the Microsoft Knowledge Base:
234048 How Windows 2000 Assigns, Reserves, and Stores Drive Letters
ldm veritas integration
Article ID: 227364 - Last Review: 01/11/2015 02:37:08 - Revision: 3.2
Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows 2000 Datacenter Server
- kbnosurvey kbarchive kbdiskmemory kbenv kbprb kbsetup KB227364