Storage & file system troubleshooting
Disk, volume, file-system and storage-health troubleshooting.
Distinguish file-system repair from physical disk health. Back up important data before high-impact repair when disk health is uncertain.
Hardware warnings, SMART/vendor diagnostic failures or disappearing drives should leave the file-system-only path.
Does firmware and Windows see the physical disk consistently?
Separate physical disk visibility from partition, volume and drive-letter state.
Use available health/reliability data as evidence, not as an absolute guarantee.
Use CHKDSK only when file-system/volume integrity is the actual branch.
Back up first and stop destructive repair when hardware failure or data loss is plausible.
Drive 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.
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.
File-system errors in Windows 11: start with CHKDSK scan before repair switches
Use CHKDSK for a volume/file-system integrity problem—not as a generic slow-PC command—and distinguish a scan from /f or /r repair operations.
Drive 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.
Storage Event ID 129 or 153 in Windows: treat timeouts and retries as storage-path evidence
Repeated Storport resets/retries can point to a stressed or unreliable storage path; correlate them with the affected disk, driver/controller, cabling and device health before file-system repair.
Error records in this system
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.
Open error record →Windows storage stackEvent ID 153Storage 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.
Open error record →Windows storage stackEvent ID 157Disk was surprise removed
Windows recorded that a disk disappeared unexpectedly; prioritize connection/power/controller/device stability and data protection before file-system repairs.
Open error record →Commands used in this system
CHKDSK
chkdsk C: /scanCheck a local file system/volume for errors. Repair switches such as /f or /r change the operation and can require downtime.
Low riskGet-Disk
Get-DiskList disks visible to the Windows Storage subsystem so physical disk detection/status can be separated from File Explorer or drive-letter problems.
Low riskGet-Volume
Get-VolumeList Windows volume objects, including drive letter, file system, health status and free/total size where available.
Low riskGet-PhysicalDisk
Get-PhysicalDiskList PhysicalDisk objects visible through Windows Storage providers, including operational and health status fields.
Low riskGet-StorageReliabilityCounter
Get-PhysicalDisk | Get-StorageReliabilityCounterRead reliability counters exposed by supported disks/providers, including fields such as temperature, errors, wear and time in use.
Low riskGet-WinEvent — storage timeout/retry events
Get-WinEvent -FilterHashtable @{LogName='System'; Id=129,153,157; StartTime=(Get-Date).AddDays(-7)}Read recent storage reset, I/O retry and surprise-removal events to establish whether a storage-path problem is repeating and when it occurs.