Summary
This article helps you identify and fix severe performance issues on a Windows Server failover cluster that hosts a SQL Server instance. You might experience these issues during server startup or after signing in. Use this article to diagnose the root cause, apply a resolution, and collect diagnostic data if you have to escalate your issue to your storage vendor or Microsoft Support.
Symptoms
In a failover cluster environment that runs Microsoft SQL Server, you encounter the following symptoms:
- After a restart, the servers start slowly.
- The Windows desktop and applications load slowly or experience delays.
- Windows File Explorer and Windows PowerShell perform sluggishly.
- The servers fail or shut down unexpectedly.
- When you open a system tool such as Task Manager, you experience a long delay before the tool starts.
- User productivity decreases significantly.
Additionally, the event log contains a large number of disk error warnings and disk timeout events, such as the following examples:
- Event ID 153:
The IO operation at logical block address 123456 for Disk 2 was retried - Event ID 154:
The IO Operation failed due to a hardware error - Status code
0xC0000185:The Boot Configuration Data for your PC is missing or contains errors.
Cause
These performance issues typically indicate a storage subsystem issue, such as one or more of the following issues:
- Disk hardware, firmware, or controller issues:
- A disk is corrupted, or hardware fails.
- A storage controller isn't functioning correctly.
- Storage firmware isn't compatible with either the hardware or the storage controllers.
- Configuration or processing issues:
- The storage cache is saturated. This condition increases latency in storage operations.
- The logging level is too verbose. This condition floods the event log and increases the processing load.
- A bottleneck restricts storage operations. This condition slows the storage system response time.
Resolution
To resolve this issue, follow these steps:
- Update firmware and drivers to the latest versions that your hardware and operating system support.
- Engage the storage vendor to conduct a full diagnostic review of the storage system.
- If any diagnostics detect issues such as faulty storage hardware, replace the affected hardware.
- Inspect the storage controllers and cache to identify failures, health issues, or degradation.
- Review Windows Server and SQL Server storage best practices, and reconfigure storage settings to optimize performance.
- Track disk errors and verify performance improvements by monitoring system and event logs.
- If the issues persist, eliminate hardware-related failures by replacing storage components.
Data collection
Before you engage your storage vendor or Microsoft Support, collect the following information:
- Event data that covers the period when the issue occurred. You can export this information from Event Viewer.
- Hardware diagnostic reports from the storage vendor's tools.
- Version information for the storage controller firmware and drivers.
- Error and cluster logs from SQL Server.
- Performance data that focuses on disk I/O and latency. To collect this information, use tools such as Performance Monitor (PerfMon).
- Details of recent configuration changes in the failover cluster or storage environment.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
