Diagnose Disk and NTFS Volume Errors Before Running CHKDSK Repair

Before you begin

Applicable to supported Windows Server/client environments where the named role or feature is installed. Run read-only checks first from an elevated PowerShell or Command Prompt as appropriate. Replace example hostnames, domain names, addresses, ports and paths with values from the affected environment. Record the exact error, timestamp, OS build and scope of impact.

Production safety: obtain change approval and a verified backup before modifying AD DS, DNS, DHCP, firewall, IIS, storage or Hyper-V configuration. Ensure console/out-of-band access before network or remote-access changes.

Symptoms and likely root cause

A server volume reports file-system warnings, disk latency, bad sectors or unexpected read-only behaviour.

Physical media/RAID/SAN/HBA driver, storage path, free space or NTFS corruption.

Diagnostic commands

Get-Disk | Format-Table Number,FriendlyName,SerialNumber,OperationalStatus,HealthStatus,IsOffline,IsReadOnly
Get-PhysicalDisk | Format-Table FriendlyName,HealthStatus,OperationalStatus,MediaType
Get-Volume
Get-WinEvent -LogName System -MaxEvents 200 | Where-Object ProviderName -Match 'disk|Ntfs|stor|stornvme' | Select TimeCreated,Id,ProviderName,Message
chkdsk D: /scan

Run the commands in order and save the complete output. The commands above are intended to establish the failing layer before a configuration change is attempted.

How to interpret the results

Correlate Windows disk number to RAID controller/LUN using vendor tools; Windows may not expose all hardware faults. /scan checks online file-system status without scheduling repair. Record storage events and latency before repair.

Practical correction

If corruption is confirmed and backup is verified, schedule chkdsk D: /f during maintenance. /r includes bad-sector recovery and can take a long time; do not run it as first response on failing/degraded media. Check RAID/SAN/HBA firmware and path stability.

Make one change at a time. Re-run the failed diagnostic after each change so the cause-and-effect relationship is clear.

Fallback and recovery

If physical media/RAID is degraded and data is critical, stabilise hardware or image the disk before write repairs; engage recovery specialist if needed. Restore test files from backup after repair.

Verification checklist

Success: storage hardware reports healthy, scan is clean or repair completed, event errors stop and application data is validated.

• Repeat the original failing operation from the affected client/user or service.
• Test from a second approved endpoint or subnet where relevant.
• Review the relevant event log/IIS log after the fix.
• Record the change, actual result and any remaining limitation.

Frequently asked question

Should I run chkdsk /r immediately? No. Check hardware health and verified backups first.

Official technical reference

Microsoft Learn — troubleshoot data corruption and disk errors

Use the official documentation for exact version support, prerequisites and any procedure that differs between Windows Server releases.

Technician field note

This runbook describes a controlled diagnostic path; it is not a universal guarantee that every environment has the same cause. If evidence does not match the expected result, stop and investigate rather than applying unrelated fixes. Do not mark the incident resolved until the original symptom is verified as cleared.