Hardware family

Storage & data paths

Storage connects persistent media to the files applications read and write. Explore the differences among a physical device, its controller, a logical…

Studio render of an M.2 SSD, a 3.5-inch hard drive with its top cover removed and an aluminium external enclosure arranged on a graphite plinth
Reading map: Storage & data pathsFirst 2 topics in reading order: Understanding this family; A useful place to begin. Each topic links to its section or page.INSIDE THIS PAGEStorage & data paths1Understanding thisfamily2 paragraphs2A useful place to begin1 paragraph

Start with this article

Reading a disk layout without changes

Disk Management shows physical disks, partitions and volumes in views that can look similar at first. Reading the wrong layer can lead to a mistaken…

Read the article

What this section covers

Storage connects persistent media to the files applications read and write. Explore the differences among a physical device, its controller, a logical volume, and the file system that organizes stored information.

Understanding this family

An application normally requests files rather than issuing raw commands to a disk. The operating system maps those requests through a file system, logical storage layers, and a controller interface. The physical medium then performs the underlying work. These boundaries explain why one device can contain several volumes and why one logical arrangement can involve more than one device.

Storage terminology also mixes physical packaging with communication standards. A small module's shape does not establish the protocol it uses, and a familiar connection label does not guarantee a particular workload's performance. Controllers, bridges, queueing, caches, and the storage medium all contribute to the observed path.

A useful place to begin

The interface topics describe how requests reach equipment; the data-layout topics explain how storage is represented above that boundary. No procedure here formats, partitions, or erases media. For model-specific controller software or firmware instructions, consult the computer or device maker's manufacturer documentation, especially where startup or existing data may be affected.

Field notes

Storage at a glance

Storage: Reading and writing data

  1. File systemfiles and folders
  2. Storage stackvolumes and partitions
  3. Controller driverNVMe, AHCI or RAID
  4. Controlleron the board or a card
  5. DriveSSD or HDD
Conceptual schematic of a selected path, not every request. Shown in one direction; the reverse direction uses related layers. Real systems add services, filter drivers and firmware not shown. Highlighted: the layer a driver change affects.

Write these down first

  • A current backup before any change
  • Controller mode in firmware: AHCI, RAID or NVMe
  • Storage controller driver name and version
  • Drive health shown by the maker's own diagnostics

Clues, not a diagnosis

Might involve the driver: A drive visible in firmware but missing during installation, or slower transfers after a controller driver change.

Check these too: Loose or faulty cables, insufficient power, a changed controller mode, a full drive, or a failing disk. Clicking noises or rising error counts in health readouts call for a backup first.

Where updates usually come from

Built-in NVMe and AHCI drivers suit many systems; RAID setups usually need the controller or motherboard maker's driver.

Practical articles

Topic

Storage interfaces and controllers

Storage interfaces define how a host expresses commands and receives results. The protocol, controller, physical packaging, and persistent medium are…

Topic

Disks, volumes and file systems

The storage space visible to an application is organized through several layers above the physical medium. A disk, a partition, a volume, and a mounted file…

Prefer a walkthrough

Step-by-step guides use the tools already on your computer

Each guide is tied to manufacturer documentation and keeps every change reversible.

Browse the guides