Clear, practical technology insights
TipsMake Learning
Explore TipsMake guides
Learning Library
Hardware Health ChecksLesson 13 of 18

Check drive health indicators

A slow or unstable PC can make the storage device look guilty, but storage symptoms come from several different layers. A nearly full system volume can slow updates and paging. File-system damage can cause read errors even when the physical device is healthy. A device can also report a reliability warning before Windows shows obvious corruption. The safe approach is to protect important files first, identify which layer the evidence points to, and use read-only checks before repair switches. The practical focus is to inspect capacity, Windows health status, error history and file-system state without treating one green badge or one command as proof that a drive is healthy.

16 min Beginner to intermediate Hardware Health ChecksReviewed 2026-07-30 00:00:00
Learning objectives

What you will learn

  • Distinguish low free space, file-system errors and device-health warnings.
  • Collect read-only storage evidence before running repair commands.
  • Use CHKDSK options conservatively and understand when downtime is required.
  • Recognize signs that require immediate backup and professional replacement planning.
Before you start

What you need

  • A verified backup of irreplaceable files before any repair operation.
  • Administrator access for advanced disk checks.
  • Reliable power and enough time for an offline scan if one becomes necessary.

Separate capacity, file-system and hardware questions

Begin by naming the actual symptom: low-space warning, slow file access, application errors, repeated file corruption, boot failure, unusual noises or a Windows storage-health notification. These are not interchangeable. A full volume can cause failures without hardware damage; a failing drive can still show plenty of free space.

Windows exposes critical storage warnings for supported NVMe solid-state drives when reliability is degraded, spare capacity is low or the device is placed in read-only mode. Microsoft also notes that not every drive or storage interface exposes the same health telemetry, so the absence of a warning is not proof of good hardware.

Drive health decision flow separating free space, file-system checks, device warnings and backup actions.
Storage diagnosis is layered: capacity, file system and device reliability require different evidence and different responses.

Record capacity and the affected device before scanning

Open Settings > System > Storage and record the free and used space on the Windows volume. If more than one physical drive is installed, identify which drive contains the affected files. Disk Management can show volume layout and device association, but do not initialize, format or change partitions during diagnosis.

Record the device model from Device Manager or the manufacturer utility. Note whether the symptom follows one folder, one volume or the entire system. A USB enclosure, cable or port can produce read errors that disappear when the same device is connected safely elsewhere, so include connection details in the baseline.

  1. 1

    Back up irreplaceable files to a separate device or trusted cloud location.

  2. 2

    Open Settings > System > Storage and record free space on every relevant volume.

  3. 3

    Open Disk Management only to identify volume letters, sizes and physical layout.

  4. 4

    Record the storage device model and connection type.

  5. 5

    Note the exact files, folders or workloads that fail and the time of failure.

  6. 6

    Check Windows Security > Device performance & health for storage-related messages when available.

Begin with read-only evidence and logs

The CHKDSK command checks a volume's file system and metadata. Without repair switches, it can report status; the /f switch fixes logical errors and may require the volume to be locked or checked at restart, while /r adds a sector-read scan and includes /f. Microsoft documents additional switches, but they are not generic performance tweaks.

Open an elevated Terminal and use chkdsk C: without repair switches when you need a preliminary file-system status for the Windows volume. Record the full result. Also inspect Event Viewer > Windows Logs > System around the symptom time for storage, disk, NTFS or volume-related events. One event is a lead, not a verdict; repeatability and matching timestamps matter.

  1. 1

    Open Windows Terminal as administrator.

  2. 2

    Run chkdsk C: without /f or /r for a preliminary status when appropriate.

  3. 3

    Copy the final summary into the incident record.

  4. 4

    Open Event Viewer and filter the System log around the symptom time.

  5. 5

    Record event source, ID, timestamp and message for relevant storage events.

  6. 6

    Compare the result with manufacturer diagnostics or service guidance for the exact model.

Choose repair only after data is protected

If the evidence shows logical file-system errors and the device is otherwise stable, schedule chkdsk /f during a maintenance window. The Windows volume normally requires a restart. Do not interrupt the check. Use /r only when the symptom and official support guidance justify a full readable-sector scan; it can take much longer and is not an SSD health test.

If Windows reports a critical storage warning, files become unreadable, errors increase, the drive disappears, the system freezes during backup, or a mechanical drive clicks or grinds, stop writing to the device. Prioritize data recovery and replacement over repeated repair passes. Repairing metadata does not reverse physical degradation.

Verification checklist
  • Important files exist on a separate verified destination.
  • The affected physical device and volume are identified correctly.
  • Read-only evidence was captured before any repair switch.
  • A repair command has a clear purpose, maintenance window and rollback or recovery plan.
  • Increasing errors trigger replacement or recovery rather than repeated scans.

Escalate when evidence points beyond Windows

Manufacturer diagnostics, firmware updates and warranty procedures are device-specific. Use the computer or drive manufacturer's support channel rather than generic firmware packages. On managed systems, preserve logs and involve IT before replacing storage or changing encryption configuration.

A clean CHKDSK result does not verify controller electronics, NAND endurance, cables, enclosure power or intermittent faults. If failures remain reproducible, continue with hardware diagnostics or professional service.

Hands-on practice

Create a storage evidence card

Document one volume without making a repair change.

  1. 1

    Record the symptom and exact timestamp.

  2. 2

    Verify a separate backup of one important file.

  3. 3

    Record volume free space and device model.

  4. 4

    Run a read-only CHKDSK status check when safe.

  5. 5

    Capture one relevant Event Viewer result or note that none matched.

  6. 6

    Write the condition that would justify /f, replacement or professional recovery.

Common mistakes to avoid

  • Running chkdsk /r as a routine speed optimization.
  • Assuming no Windows health warning means the drive is healthy.
  • Formatting or initializing an unfamiliar disk during diagnosis.
  • Repeating repairs while errors increase or files become unreadable.
Lesson recap

Key takeaways

  • Capacity, file-system integrity and physical health are separate questions.
  • Capture read-only evidence and protect data before repair.
  • Increasing errors or device warnings require recovery and replacement planning.

Frequently asked questions

Does CHKDSK test the physical health of an SSD?

It checks file-system and volume structures and can test readability with certain switches, but it is not a complete SSD wear or controller diagnostic. Use supported device-health data and manufacturer tools as additional evidence.

Should I use /f and /r together?

Only when the symptom and official guidance justify them. /r includes /f and can take substantially longer. Back up first and schedule downtime.

Evidence and updates

Sources and further reading

  1. What to do about a critical warning for a storage deviceMicrosoft Support
  2. chkdskMicrosoft Learn
  3. Device performance and health in the Windows Security appMicrosoft Support
Finish this lesson

Ready to continue?

Mark the lesson complete so your Learning Path progress stays current on this device.