Disk vs Drive: Understanding the Difference

A physical disk is a single hardware storage device: one SSD module, one hard drive, one USB flash drive. It has a serial number, a firmware version, a physical connector, and a finite number of sectors. You can hold it in your hand. If it fails, all the data on it is at risk. Physical disks are what Macrium Reflect labels as "Disk 0," "Disk 1," and so on in its main interface.

A logical disk (or logical volume) is an abstraction created by the operating system or a storage controller. It represents a usable storage space that may span part of a physical disk (a partition), an entire physical disk, or even multiple physical disks (as in RAID, Storage Spaces, or LVM configurations). Logical disks are what Windows assigns drive letters to, and they are what applications interact with through the file system.

The distinction becomes critical in several scenarios. Disk cloning operates at the physical disk level: Macrium Reflect reads every partition from the source physical disk and writes them to the target physical disk. If you have a single physical disk with three partitions (EFI System Partition, C: Windows, and D: Data), a disk clone captures all three partitions and the partition table itself, producing a bootable replica. Partition imaging, by contrast, operates at the logical level: you select specific partitions (volumes) to capture, and the resulting image file contains only those selected partitions.

For bare-metal disaster recovery, capturing the entire physical disk is almost always the correct choice. A physical disk image or clone includes the boot loader, EFI System Partition, recovery partition, and all data partitions. Restoring a physical disk image to a new drive produces a fully bootable system with no additional configuration required. Capturing only the C: partition would omit the boot infrastructure, requiring manual repair of the boot process after restoration.

The single most common mistake in backup and cloning operations is confusing a logical drive (a partition with a drive letter) with a physical disk (the entire hardware device). This mistake can result in incomplete backups that fail to capture critical boot infrastructure, cloning operations that produce non-bootable target disks, or restore operations that overwrite the wrong disk entirely.

When you want to clone your system disk to a new SSD, you need to clone the entire physical disk, not just the C: partition. A typical Windows installation disk contains at least three partitions: the EFI System Partition (ESP, approximately 100-500 MB, containing the boot loader), the Microsoft Reserved Partition (MSR, 16 MB), and the Windows partition (C:). Some systems also have a recovery partition and an OEM diagnostics partition. Cloning only the C: partition would produce an SSD that contains your Windows files but cannot boot because the EFI boot loader is missing.

Macrium Reflect handles this correctly by default. When you initiate a disk clone, the software presents each physical disk and all of its partitions. Selecting the disk itself (the top-level entry) automatically includes all partitions. Macrium also handles the common scenario of cloning from a larger disk to a smaller one: it automatically resizes partitions proportionally to fit the target disk, preserving the partition layout and boot configuration. This is the most common use case when migrating from a 1 TB HDD to a 500 GB SSD.

For backup images, you have a choice: image the entire disk or image individual partitions. Imaging the entire disk is recommended for system drives because it captures everything needed for a bare-metal restore. Imaging individual partitions is useful for data-only volumes where boot infrastructure is not a concern. Macrium Reflect's interface clearly distinguishes between these options, showing the physical disk as a parent entry with individual partitions nested underneath.