Skip to main content

What is a Logical Drive?

In one sentence

A Logical Drive is a disk that the operating system sees, but behind the scenes, this disk can be made up of one or more physical disks.

Definition

If there are several hard drives or SSDs inside a server, the RAID controller can combine them and present the result as a "new disk" to the operating system.
This new disk is the Logical Drive.

A Logical Drive is a logical Block Device created by a RAID Controller from one or more Physical Disk(s), which the operating system recognizes as an independent disk.
In many Vendors, this concept is also known as Virtual Disk.

Note

In servers that use Hardware RAID, the operating system usually does not see the physical disks directly; rather, it sees the output of the RAID controller, which is the same Logical Drive(s).

Logical Drive Formation Path

The general structure is as follows:

HDD / SSDPhysical DisksHDD / SSDHardware RAIDRAID ControllerHardware RAIDVirtual DiskLogical DriveVirtual DiskLinux / WindowsOperating SystemLinux / Windowsext4 / xfs / NTFSPartitions & File Systemext4 / xfs / NTFS

In this structure:

LayerDescription
Physical DisksActual disks inside the server, such as HDD or SSD
RAID ControllerThe component or controller that manages disks based on RAID
Logical DriveThe logical output of RAID presented to the Operating System
Operating SystemThe OS that sees the Logical Drive as a disk
Partition / File SystemStructures created by the OS on that disk

Why use a Logical Drive?

Using a Logical Drive isn't just for "showing one disk"; it is part of correct storage design in a server.

BenefitSimple ExplanationTechnical Note
Simpler ManagementInstead of multiple disks, the OS works with one or more defined disksStorage management, Booting, and Provisioning become simpler
Increased StabilityIn some RAIDs, if a disk fails, the service does not go downThere is redundancy in RAIDs like RAID 1 / 5 / 6 / 10
Performance ImprovementData can be read or written fasterDepending on RAID Level, Cache Policy, and Stripe Size, performance improves
Separation of UsesSeparate spaces can be had for the OS, data, and backupWorkload Separation and Lifecycle management become simpler
Attention

Not all RAIDs increase stability.
For example, RAID 0 may improve performance, but has no redundancy for data protection.

A Simple Example

Assume a server has 4 x 1TB SSDs.

If these disks are configured as RAID 10, the RAID controller can create one Logical Drive with a usable capacity of approximately 2TB.

In this case:

  • The operating system does not see 4 separate SSDs
  • It only sees one approximately 2TB disk
  • This disk is the Logical Drive

What does the OS actually see?

  • In Linux, this Logical Drive might be seen as /dev/sda or /dev/sdb
  • In Windows, it might be displayed as Disk 0 or Disk 1

Can Multiple Logical Drives be Created?

Yes. Depending on the capabilities of the RAID controller, multiple Logical Drives can be defined on a single controller.

For example:

Logical Drive NameUsage
OSInstalling the Operating System
VARKeeping Logs and Variable data
DATAStoring main data, Virtual Machines, or Volumes
BACKUPBackup files

This task has several important benefits:

  • Better separation of system data and work data
  • Easier Backup and Recovery
  • Easier capacity management
  • Reducing the risk of simultaneous disruption of all parts in operational scenarios
Important Note for Experts

If multiple Logical Drives are created on the same set of shared physical disks, this separation is primarily managerial and not necessarily complete functional separation.
For true I/O isolation, it is better to use separate Disk Group / Arrays.

Difference Between Logical Drive and Partition

One of the most common mistakes is equating Logical Drive with Partition; whereas these two reside in two different layers.

  • Logical Drive is built by the RAID Controller
  • Partition is built by the Operating System on the Logical Drive

That is, the correct order is usually as follows:

HDD / SSDPhysical DiskHDD / SSDRAID ControllerRAIDRAID ControllerVirtual DiskLogical DriveVirtual DiskDisk PartitionPartitionDisk Partitionext4 / XFS / NTFSFile Systemext4 / XFS / NTFS

Quick Comparison

ConceptBuilt By Which Component?Which Layer?
Physical DiskHardwarePhysical Layer
Logical DriveRAID ControllerStorage Layer
PartitionOperating SystemDisk Layer
File SystemOperating SystemFile Layer
Clarification

In this document, Logical Drive refers to the concept created by the RAID Controller.
This term should not be confused with the following:

  • Logical Drive in the old MBR / Extended Partition structure
  • Logical Volume in LVM
For Linux

In many professional Linux installations, first the Logical Drive is presented to the OS, then on it:

  1. Partition or LVM PV
  2. VG / LV
  3. File System

are created.

Role of Logical Drive in Plaivid

In the Plaivid architecture, it is usually recommended to create several separate Logical Drives for better management and appropriate performance.

Common suggested structure:

Logical DriveUsage
OSInstalling the OS and system files
VAR/var partition and system variable data
DATAStorage space for virtual machines, containers, and other Workloads

This design results in:

  • OS load being separated from virtual machine workload
  • Data growth is managed better
  • Backup and Recovery operations are performed more simply
  • During troubleshooting, the location of each data type is clearer
  • Future infrastructure development is more predictable

Design Tips for IT Experts

If you are designing or implementing infrastructure, these points are very important:

  • Choose RAID Level based on Workload
    RAID 10 is generally more suitable for heavy I/O and VMs than RAID 5.

  • Do not confuse usable capacity with raw capacity
    The final capacity of the Logical Drive depends on the RAID Level.

  • Multiple Logical Drives do not mean multiplied performance
    If they are all on the same set of shared disks, I/O contention still exists.

  • Check RAID Controller Cache and Battery/FBWC status
    This part can have a direct effect on Performance and Data Safety.

  • Don't forget Physical Disk Monitoring
    Even if the OS only sees the Logical Drive, real health is determined at the Physical Disk level.

  • Finalize storage design before installation
    In many servers, changing the structure of Logical Drives after services start is costly and risky.

Conclusion

A Logical Drive is the bridge between physical disks and the operating system.

If we want to put it very simply:

  • Physical Disk = What physically sits in the server
  • Logical Drive = What the RAID shows to the operating system
  • Partition = The part that the operating system creates on that disk

Consequently, when designing storage infrastructure, having correct knowledge of Logical Drive is one of the most fundamental concepts for installing the operating system, separating data, improving performance, and increasing reliability.