Skip to content

Commit d93f194

Browse files
v-tappelgatev-tappelgate
authored
Merge pull request #10407 from v-tappelgate/AB#8618-Data-corruption-and-storage-replication-failures
AB#8618: Data corruption and storage replication failures in Windows …
2 parents ae295f2 + 3fe9677 commit d93f194

2 files changed

Lines changed: 125 additions & 0 deletions

File tree

‎support/windows-server/backup-and-storage/troubleshoot-data-corruption-storage-replication-failures-ws2025.md‎

Lines changed: 123 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,123 @@
1+
---
2+
title: Troubleshoot Data Corruption and Storage Replication Failures in Windows Server 2025
3+
description: Discusses how to identify, troubleshoot, and resolve issues that relate to data corruption, disk errors, and storage replication failures in Windows Server 2025.
4+
ms.date: 12/19/2025
5+
author: kaushika-msft
6+
ms.author: kaushika
7+
manager: dcscontentpm
8+
audience: itpro
9+
ms.topic: troubleshooting
10+
ms.reviewer: kaushika, simonw
11+
ai.usage: ai-assisted
12+
ms.custom:
13+
- sap:backup,recovery,disk,and storage\data corruption and disk errors
14+
- pcy:WinComm Storage High Avail
15+
appliesto:
16+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
17+
---
18+
# Troubleshoot data corruption and storage replication failures in Windows Server 2025
19+
20+
This article discusses how to identify, troubleshoot, and resolve issues that relate to data corruption, disk errors, and storage replication failures in Windows Server 2025. These issues can affect storage performance, data integrity, and replication reliability in your environment.
21+
22+
## Symptoms
23+
24+
You might experience one or more of the following symptoms in Windows Server 2025:
25+
26+
- The event logs list disk, storage, and replication-related errors. These errors might include the following events:
27+
- Event ID 7 (device error)
28+
- Event ID 11 (controller error)
29+
- Event ID 153 (disk timeout)
30+
- Event ID 1112 (Storage Replica replication error)
31+
32+
- Files or databases appear to be corrupted, or application storage appears to be corrupted.
33+
- Storage Replica experiences replication failures.
34+
- Storage monitoring tools generate warnings or alerts that indicate degraded performance or reliability.
35+
36+
## Cause
37+
38+
The following factors can cause these issues:
39+
40+
- Physical disk failures, such as bad sectors or mechanical defects
41+
- Data corruption within the storage subsystem
42+
- Underlying storage hardware issues that interfere with replication processes
43+
- Misconfigured storage replication settings, such as inadequate log sizes or incorrect replication mode
44+
- Disk configuration issues that reduce system resilience
45+
46+
## Resolution
47+
48+
> [!IMPORTANT]
49+
> Before you start troubleshooting storage issues, make sure that you have current backups of all critical data.
50+
51+
To resolve data corruption and storage replication failures in Windows Server 2025, follow these steps.
52+
53+
1. To inspect hardware for failing disks, open a Windows PowerShell command prompt, and then run the following cmdlets:
54+
55+
```powershell
56+
Get-PhysicalDisk | Format-Table -AutoSize
57+
Get-PhysicalDisk | Get-StorageReliabilityCounter
58+
```
59+
60+
If a disk or controller is defective, replace it promptly to prevent further corruption or replication errors.
61+
62+
1. Make sure that all storage arrays, RAID configurations, and storage area networks (SANs) or network attached storage (NAS) devices are functioning correctly, and use tools such as Performance Monitor (Perfmon) to verify their performance.
63+
64+
1. Make sure that firmware is up to date on all storage controllers.
65+
66+
1. To fix bad disk sectors and recover as much data as possible, open a Windows Command Prompt window, and then run the following command:
67+
68+
```console
69+
chkdsk <Drive>: /F /R
70+
```
71+
72+
> [!NOTE]
73+
> In this command, \<Drive> represents the drive to be fixed.
74+
75+
1. If `chkdsk` doesn't recover some part of the data, restore that data from your backup.
76+
77+
1. Review your disk and Storage Replica configuration, and make sure that your system follows best practices. Closely review the following settings:
78+
79+
- Allocate sufficient space for log files (production workloads should have at least 8 GB available for log files).
80+
- Allocate sufficient network bandwidth for replication traffic.
81+
- Verify the volume alignment and cluster size settings.
82+
- Verify that the replication mode (synchronous or asynchronous) matches your requirements.
83+
- Make sure that all replication nodes are running Windows Server Datacenter edition.
84+
85+
1. To verify that you restored data consistency and transfer reliability, test storage replication. At a PowerShell command prompt, run the following cmdlets:
86+
87+
```powershell
88+
Get-SRGroup | Format-List *
89+
Get-SRPartnership | Format-List *
90+
Test-SRTopology -SourceComputerName Server1 -SourceVolumeName D: -DestinationComputerName Server2 -DestinationVolumeName D:
91+
```
92+
93+
1. To verify that your system is stable, monitor the replication status for at least 24 hours.
94+
95+
1. For more troubleshooting information, including specialized troubleshooting for Event ID 153, see [Data corruption and disk errors troubleshooting guidance](troubleshoot-data-corruption-and-disk-errors.md).
96+
97+
1. If issues persist, consider contacting Microsoft Support. To learn about helpful information that you can add to your support request, review [Data collection](#data-collection).
98+
99+
## Data collection
100+
101+
Before you contact Microsoft Support for assistance, gather the following information from your Windows Server 2025 environment:
102+
103+
- Event Viewer logs for disk, storage, and replication errors (System, Application, and Microsoft-Windows-StorageReplica/Admin logs).
104+
- Output from PowerShell cmdlets, such as the following cmdlets:
105+
106+
```powershell
107+
Get-PhysicalDisk | Format-Table -AutoSize
108+
Get-SRGroup
109+
Get-SRPartnership
110+
Get-EventLog -LogName System -Newest 100 | Where-Object {$_.Source -like "*disk*" -or $_.Source -like "*storage*"}
111+
```
112+
113+
- Details of your storage configuration, including RAID levels, disk models, firmware versions, and storage controller information.
114+
- Screenshots or exports from monitoring tools that show error codes and performance metrics.
115+
- The steps that you already took to troubleshoot the issue.
116+
117+
## References
118+
119+
- [Check disk for errors in Windows Server](/windows-server/administration/windows-commands/chkdsk)
120+
- [Storage Replica overview in Windows Server](/windows-server/storage/storage-replica/storage-replica-overview)
121+
- [Troubleshoot Storage Spaces issues](/windows-server/storage/storage-spaces/troubleshooting-storage-spaces)
122+
- [Storage Replica known issues](/windows-server/storage/storage-replica/storage-replica-known-issues)
123+
- [Data corruption and disk errors troubleshooting guidance](troubleshoot-data-corruption-and-disk-errors.md)

‎support/windows-server/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -768,6 +768,8 @@ items:
768768
items:
769769
- name: Troubleshoot Windows Server Storage Replica
770770
href: ./backup-and-storage/troubleshoot-windows-server-storage-replica.md
771+
- name: Troubleshoot data corruption and storage replication failures in Windows Server 2025
772+
href: ./backup-and-storage/troubleshoot-data-corruption-storage-replication-failures-ws2025.md
771773
- name: Storage Sense
772774
items:
773775
- name: Troubleshoot Windows Server Storage Sense

0 commit comments

Comments
 (0)