Event ID 11 with a disk controller error points to a problem on the I/O path. The number alone does not prove that a disk needs replacement: first read the provider, full message and device path.
Identify the event and device
Open the System log in Event Viewer and record the source, time, device path and event data. Another provider can use the same ID for an unrelated event. This query reads existing events; it does not repair storage.
Get-WinEvent -FilterHashtable @{
LogName = 'System'
Id = 11
StartTime = (Get-Date).AddDays(-7)
} -MaxEvents 30 |
Select-Object TimeCreated, ProviderName, Id, Message |
Format-ListCheck the storage path
Compare the time with slow I/O, missing volumes, failed backups and events 129 or 153. For SAN or iSCSI storage, also inspect MPIO paths, interfaces and array logs. For a VM, continue the investigation on the hypervisor and host storage.
Get-Disk |
Select-Object Number, FriendlyName, SerialNumber,
OperationalStatus, HealthStatusThis inventory describes disks visible to Windows. A RAID controller can expose a logical disk without showing every physical drive’s condition. Confirm identity in the vendor console; a disk number alone is insufficient for a replacement decision and can change.
Apply and verify a targeted correction
- Preserve logs and confirm that a usable backup exists before intervening on storage.
- Locate the affected path or component: connection, controller, network path, driver, firmware or device.
- Confirm the appropriate action against vendor guidance and schedule it around the workload.
- Repeat the operation that failed and watch events over a period comparable to the original incident.
A single Healthy status does not exclude an intermittent fault. Escalate recurring errors or inaccessible data with timestamps, provider details, serial number and storage logs. A file-system repair is not a universal fix for a controller error.