Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Storage & file system · reviewed troubleshooting

Check storage health in Windows before running repair commands

Separate physical-disk health evidence from volume/file-system repair by checking what Windows Storage reports before using CHKDSK repair switches.

Applies to: Windows 11Change risk: LowReviewed: 2026-09-17
Do this first
  1. Back up important data first if the drive is disappearing, making abnormal noises or already reports health warnings.
  2. Run Get-PhysicalDisk and identify the correct device by model/size.
  3. For supported devices, query storage reliability counters and preserve any warning/error values.
  4. Check Get-Volume separately so a file-system/volume state is not confused with physical-disk health.

What this problem usually means

Windows Storage cmdlets distinguish physical disks from volumes. Get-PhysicalDisk can expose operational/health status, while Get-StorageReliabilityCounter can expose provider-supported counters such as temperature, errors, wear and power-on time. Availability varies by device/provider, so missing counters are not proof that a drive is healthy.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Inventory physical disk health without changing it

Low risk

Why this belongs here: Get-PhysicalDisk is read-oriented and shows disks visible to the Storage management provider.

  1. Open PowerShell.
  2. Run Get-PhysicalDisk.
  3. Match the disk by friendly name/model/size and record OperationalStatus and HealthStatus.
  4. Do not initialize, format or remove a disk based only on this inventory.
Get-PhysicalDisk
2

Read reliability counters when the device exposes them

Low risk

Why this belongs here: Microsoft documents reliability counters for temperature, errors, wear and time-in-use on supported storage devices.

  1. Pipe the identified PhysicalDisk object to Get-StorageReliabilityCounter.
  2. Record counters that are actually populated.
  3. Compare suspicious results with the SSD/HDD/PC manufacturer diagnostic before destructive repair.
Get-PhysicalDisk | Get-StorageReliabilityCounter
Stop condition

When this guide stops being the right path

If the disk reports Warning/Unhealthy, repeatedly disappears, cannot be detected reliably or contains irreplaceable data, stop nonessential write-heavy repair and prioritize backup/vendor or data-recovery assessment.

If the problem is still not fixed

Use the file-system/CHKDSK path only when the physical disk remains reliably detected and the evidence points to volume/file-system integrity.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideDrive randomly disconnects in Windows 11: separate cable, power, device detection and disk health

Repeated storage disconnects are not a reason to format the drive; preserve detection and health evidence before changing the file system.

CommandGet-StorageReliabilityCounter

Read reliability counters exposed by supported disks/providers, including fields such as temperature, errors, wear and time in use.

GuideDrive not showing in File Explorer: check Disk Management before formatting anything

Determine whether Windows sees the disk, whether a volume exists, and whether the problem is only a missing drive letter before destructive changes.

ErrorEvent ID 129 — Storport reset to device was issued

A storage request timed out at Storport and Windows reset the device path; correlate repeated resets with the affected disk/controller path and hardware/driver state.

ErrorEvent ID 153 — Storage I/O operation was retried

The storage miniport request timed out and Windows retried the I/O; repeated occurrences need path/load/driver/hardware correlation.

ErrorEvent ID 157 — Disk was surprise removed

Windows recorded that a disk disappeared unexpectedly; prioritize connection/power/controller/device stability and data protection before file-system repairs.