Storage Technologies

What you will be able to do

• Distinguish persistent storage, HDD and SSD media, and SATA and NVMe connection paths in a support case.
• Map a physical disk to its partitions and volumes, then interpret total capacity and remaining space correctly.
• Separate storage health evidence from backup and recovery protection.
• Choose a safe read-only inspection and verification sequence before changing storage state.

01

Build a Storage Support Map

Storage support starts with identity, not a replacement guess. Record the device, its media type, connection path, logical layout, capacity, and current condition before proposing a change.

These properties answer different questions. An SSD label describes media, SATA or NVMe describes communication, and a drive letter identifies a usable volume rather than the entire physical device.

A useful first pass is read-only. It preserves the starting state, reduces the chance of selecting the wrong disk, and creates evidence that another technician can review.

02

Persistent storage

Persistent storage retains the operating system, applications, and saved user data beyond the current powered session. This property should be recorded separately from the other layers in the storage map.

Identify which information must survive a restart, then separate that requirement from RAM capacity and current application activity. A useful read-only starting point is: compare memory and storage in task manager.

Keep this boundary in view: a second file on the same device is not a backup. The expected evidence is saved information remains available after restart.

03

HDD and SSD media

HDDs and SSDs can both provide persistent storage, but they use different physical media and should be identified before support work. This property should be recorded separately from the other layers in the storage map.

Record the model, reported media type, capacity, and device role instead of assuming performance or compatibility from appearance. A useful read-only starting point is: run `get-physicaldisk` to inspect reported media.

Keep this boundary in view: media type does not identify the connection path. The expected evidence is media type and device role are recorded separately.

04

Storage connection paths

A storage device's media type and its host connection are separate properties; SATA and NVMe describe different communication paths. This property should be recorded separately from the other layers in the storage map.

Match the documented device interface, host support, form factor, connector, and power requirements before proposing a replacement. A useful read-only starting point is: run `get-disk` and inspect the reported bus type.

Keep this boundary in view: a familiar connector shape is not full compatibility proof. The expected evidence is device media and connection path are distinguished.

05

Disks partitions volumes

Windows represents physical disks, partition layouts, and formatted volumes as related but distinct storage layers. This property should be recorded separately from the other layers in the storage map.

Map the physical disk to its partitions and volumes before changing a letter, format, size, or layout. A useful read-only starting point is: open disk management for a read-only layout view.

Keep this boundary in view: system and recovery partitions should not be modified casually. The expected evidence is the physical device and logical layout are mapped.

06

Health and backup boundary

Health information describes observed device condition, while a backup is a separate data copy used for recovery from loss or corruption. This property should be recorded separately from the other layers in the storage map.

Record capacity, free space, health, errors, temperature, and wear where available, then confirm important data has a separate recoverable copy. A useful read-only starting point is: use `get-storagereliabilitycounter` read-only.

Keep this boundary in view: a healthy status does not replace a tested backup. The expected evidence is condition evidence and recovery protection are separate.

07

Read Capacity and Free Space

Total capacity describes the size exposed by a disk or volume. Free space describes how much of a formatted volume remains available, so the two values should not be used interchangeably.

Windows can expose several volumes on one physical disk. Record the disk number, volume label, file system, total size, and remaining space before deciding where pressure exists.

Low free space is a logical-volume observation. It does not by itself identify failed media, prove that the physical disk is full, or authorize deleting files without a retention decision.

08

Use a Safe Storage Workflow

Begin with the ticket symptom and the exact device identity. Collect read-only disk, partition, volume, capacity, and health evidence before opening hardware or running a modifying storage command.

If a change could affect data, confirm the backup scope and a realistic restore path first. Health output describes observed condition, while a tested backup provides recovery protection.

Change only one layer at a time and verify the intended result. If the device identity, encryption state, recovery partition, or backup boundary remains unclear, stop and escalate instead of improvising.

09

Recap Before Practice and Prove

Persistent storage retains saved information beyond the current powered session. RAM supports active work but does not replace persistent storage.

HDD and SSD identify storage media. SATA and NVMe describe communication paths, so media type and interface must be recorded separately.

A physical disk can contain partitions that expose formatted volumes. A drive letter identifies a volume, not necessarily a separate physical device.

Capacity, free space, temperature, errors, wear, and health status are different observations. Each one answers a limited support question.

Health evidence is not a backup. Before a risky storage change, confirm a separate recoverable copy and preserve the original device identity and layout.