Dynamic disk

On this page 7

A dynamic disk is a Windows disk type in which volumes are tracked by the Logical Disk Manager (LDM) database instead of a conventional partition table, which allows volumes to span, stripe or mirror across several physical disks. In Windows storage & file systems, it is the older software volume management layer that preceded Storage Spaces.

Microsoft has deprecated dynamic disks for most purposes except mirrored boot volumes, and recommends basic disks or Storage Spaces for new deployments. Dynamic disks still appear on older servers and workstations, so administrators need to understand how they work, how to read their volume types and how to convert them back safely.

How a dynamic disk stores volume information

A dynamic disk keeps a 1 MB LDM database at the end of the disk, and every dynamic disk in the same computer holds a replicated copy of that database. The database describes all dynamic volumes, the disks they occupy and the extents on each disk, so Windows can assemble a volume that is spread over several drives.

On MBR disks, the whole disk appears to other systems as a single partition of type 0x42, which hides the real layout from tools that do not understand LDM. On GPT disks, Windows creates an LDM metadata partition and an LDM data partition instead. In both cases the actual volume map lives only in the LDM database, which is why non-Windows systems and many older recovery tools cannot read dynamic volumes reliably.

The table below contrasts the core properties of the two Windows disk types.

PropertyBasic diskDynamic disk
Volume mapMBR or GPT partition tableLDM database replicated on all dynamic disks
Multi-disk volumesNot supported nativelySpanned, striped, mirrored and RAID-5
PortabilityReadable by most operating systemsMainly readable by Windows
Microsoft statusRecommended defaultDeprecated except for mirrored boot volumes
Basic disk compared with dynamic disk

Dynamic volume types and their trade-offs

Dynamic disks support five volume types, each with a different balance of capacity, speed and fault tolerance. Client editions of Windows have historically lacked RAID-5 volumes, which are available only on Windows Server.

Volume typeMinimum disksUsable capacityFault tolerance
Simple volume1Full size of the extentNone
Spanned volume2Sum of all extentsNone, one failed disk loses the volume
Striped volume2Sum of equal extentsNone, comparable to RAID 0
Mirrored volume2Half of the totalSurvives one disk failure, comparable to RAID 1
RAID-5 volume3Total minus one diskSurvives one disk failure, server only
Dynamic volume types

Spanned volumes are the most dangerous type because they concatenate disks without redundancy: the volume is lost when any member disk fails, so the risk grows with every disk added. Striped volumes raise throughput by writing in parallel but carry the same exposure.

Mirrored volumes are the only type that Microsoft still treats as a legitimate use of dynamic disks, mainly for mirroring the system and boot volume on servers without a hardware RAID controller. Even here, the mirror must be broken and re-created after a disk replacement, and resynchronization can take several hours on large disks.

Dynamic disks compared with Storage Spaces and hardware RAID

Dynamic disks were Windows’ first built-in software RAID, but newer mechanisms now cover the same needs with fewer constraints. The comparison below explains why most administrators choose a different approach for new systems.

TechnologyLayerStrengthsWeaknesses
Dynamic disksVolume manager in the operating systemSimple setup in Disk ManagementDeprecated, rigid layouts, weak portability
Storage SpacesStorage pool with virtual disksThin provisioning, mixed disk sizes, parityParity write speed can be low
Hardware RAIDDedicated controllerOffloaded parity, battery-backed cacheController-specific, extra cost
Options for combining disks in Windows

Storage Spaces replaces most dynamic disk scenarios because it pools disks of different sizes and lets virtual disks grow later. Hardware RAID remains common on servers where boot redundancy must not depend on the operating system.

Converting between basic and dynamic disks

Converting a basic disk to dynamic is non-destructive: Disk Management or the diskpart command convert dynamic keeps existing partitions and turns them into simple volumes. The reverse direction is the problem, because converting dynamic to basic officially requires deleting every volume on the disk first.

The usual decisions are summarized in the following table.

SituationRecommended actionReason
Single disk with simple volumesBack up, delete volumes, convert to basicRemoves deprecated metadata with no benefit lost
Mirrored boot volume on a serverKeep it or migrate to hardware RAIDStill a supported use of dynamic disks
Spanned or striped data volumeMigrate data to Storage SpacesRemoves the single point of failure
Disk moved from another computerImport foreign disk in Disk ManagementMerges its LDM database into the local one
Choosing a path for an existing dynamic disk

Third-party partition tools claim to convert dynamic disks to basic without data loss, and they often succeed for simple volumes. Such conversions edit low-level metadata directly, so a verified full backup is mandatory before any attempt.

Limitations and common mistakes

  • Dual-boot systems break when the disk is converted, because other operating systems cannot interpret the LDM layout.
  • Removable drives and most USB disks cannot be made dynamic, and laptops gain nothing from the conversion.
  • A disk that shows as Foreign or Missing after a move is not empty: importing it restores the volumes, while deleting it destroys them.
  • Treating a mirrored volume as a backup is a mistake, because deletions, ransomware and corruption are mirrored instantly to both disks.
  • Some imaging and recovery tools fail on dynamic volumes, which can block a restore when it is needed most.

The safest general rule is to use basic disks by default and reserve dynamic disks for legacy systems that already depend on them, while planning their eventual migration.

The idea in brief

A dynamic disk is an older way for Windows to treat several hard drives as a team. It can glue drives together into one big drive. It can split work between them for speed. It can also keep two identical copies, so one drive can fail without data loss.

Windows keeps a small hidden notebook on each drive. The notebook records how the team is arranged. Newer features now do the same job more flexibly. Today it is mainly found on older computers and is rarely chosen for new ones.

A practical scenario

An IT technician takes over a file server installed years ago with two 4 TB disks converted to dynamic and combined into a spanned volume of 8 TB. One disk starts reporting reallocated sectors in its health data. Because a spanned volume has no redundancy, a failure of that disk would make the whole 8 TB volume unreadable.

The technician adds three new 4 TB disks, creates a Storage Spaces pool with a parity virtual disk, and copies the data with robocopy over a weekend. After verifying the copy, he deletes the spanned volume and converts both old disks back to basic. The server now tolerates a single disk failure without data loss, and the deprecated dynamic configuration is gone.