Update troubleshoot-data-corruption-and-disk-errors.md

Edit review per CI 8340

Author: przlplx

support/windows-server/backup-and-storage/troubleshoot-data-corruption-and-disk-errors.md

@@ -1,5 +1,5 @@
 ---
-title: Guidance for troubleshooting data corruption and disk errors
+title: Guidance for Troubleshooting Data Corruption and Disk Errors
 description: Provides guidance to help troubleshoot data corruption and disk errors in Windows.
 ms.date: 01/15/2025
 author: kaushika-msft
@@ -16,7 +16,7 @@ appliesto:
 ---
 # Data corruption and disk errors troubleshooting guidance
 
-Disk, file system, and storage issues in Windows Server environments can cause inaccessible drives, file or folder corruption, unexpected drive state changes, and application or backup failures. If not resolved promptly, these issues can compromise data integrity, disrupt service availability, and lead to downtime or data loss.
+Disk, file system, and storage issues in Windows Server environments can cause inaccessible drives, file or folder corruption, unexpected drive state changes, and application or backup failures. If they're not resolved promptly, these issues can compromise data integrity, disrupt service availability, and cause downtime or data loss.
 
 This article provides guidance to help you identify, diagnose, and repair data corruption and disk errors effectively.
 
@@ -25,18 +25,18 @@ This article provides guidance to help you identify, diagnose, and repair data c
 - Before you perform any repairs or modify any disks, back up all critical data.
 - Make sure that you have administrative permissions on the affected devices.
 - Familiarize yourself with storage subsystem architecture and event log monitoring.
-- Make sure that you use modern volume management tools. Avoid deprecated features such as dynamic disks
+- Make sure that you use modern volume management tools. Avoid deprecated features, such as dynamic disks
 
 > [!NOTE]
-> This article describes commands you have to run at an administrative Windows command prompt or an administrative Windows PowerShell command prompt.
+> This article discusses commands that you have to run at an administrative Windows command prompt or an administrative Windows PowerShell command prompt.
 
 ## Troubleshooting checklist
 
 Use this checklist for systematic troubleshooting.
 
 **Check drivers and firmware**
 
-Make sure that the storage-related drivers and firmware are up to date. Consult your hardware vendor for the latest drivers and diagnostic tools, if necessary. This step includes drivers for components such as:
+Make sure that the storage-related drivers and firmware are up to date. Consult your hardware vendor for the latest drivers and diagnostic tools, if it's necessary. This step includes drivers for components such as:
 
 - iSCSI port
 - RAID controller
@@ -46,15 +46,15 @@ Make sure that the storage-related drivers and firmware are up to date. Consult
 
 **Scan the health of the storage system**
 
-Use `chkdsk` in scan mode to look for potential storage system issues without making changes. Open a Windows Command Prompt window as an administrator, and then run the following command:
+Run `chkdsk` in scan mode to look for potential storage system issues without making changes. Open a Windows Command Prompt window as an administrator, and then run the following command:
 
 ```
 console chkdsk /scan
 ```
 
 **Review the event log for relevant events**
 
-The following Event IDs indicate that there's data corruption or a disk error:
+The following event IDs indicate data corruption or a disk error:
 
 - Event ID 55, `The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume.`
 - Event ID 98, `Volume C: (\Device\HarddiskVolume3) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line or run "REPAIR-VOLUME \<drive:>" locally or remotely via PowerShell.`
@@ -65,7 +65,7 @@ The following Event IDs indicate that there's data corruption or a disk error:
 **Scan and repair NTFS volumes**
 
 > [!NOTE]  
-> Resilient file system (ReFS) volumes can automatically fix corruption issues. You can still run `chkdsk` to scan them.
+> Resilient file system (ReFS) volumes can automatically fix corruption issues. You can still run `chkdsk` if you want to scan the volumes.
 
 1. To get detailed information about a volume, run the following command at a Windows command prompt:
 
@@ -76,7 +76,7 @@ The following Event IDs indicate that there's data corruption or a disk error:
    > [!NOTE]
    > In this command, \<RootPath> represents the drive letter of the drive root.
 
-1. To verify if the volume is dirty, run the following command at a Windows command prompt:
+1. To check whether the volume is dirty, run the following command at a Windows command prompt:
 
    ```console
    fsutil dirty query <VolumePath>:
@@ -85,7 +85,7 @@ The following Event IDs indicate that there's data corruption or a disk error:
    > [!NOTE]
    > In this command, \<VolumePath> represents the drive letter.
 
-1. If the result of the previous step indicates that the volume is dirty, schedule a maintenance window for the volume. The disk isn't accessible during the repair process. During the maintenance window, run the following command at the Windows command prompt:
+1. If the results of the previous step indicate that the volume is dirty, schedule a maintenance window for the volume. The disk isn't accessible during the repair process. During the maintenance window, run the following command at the Windows command prompt:
 
    ```console
    chkdsk /f /r
@@ -96,19 +96,24 @@ The following Event IDs indicate that there's data corruption or a disk error:
 
 **Advanced troubleshooting**
 
-If errors persist, follow these steps to further test the system and isolate the issue:
+If errors persist, further test the system to isolate the issue. Follow these steps:
 
 1. Uninstall any third-party disk management software, such as Diskeeper.
 1. Remove or update filter drivers.
 1. Switch to different types of drivers. For example, RAID controller drivers or monolithic drivers.
 1. Check the multipath I/O configuration. For more information, see [Multipath I/O (MPIO) troubleshooting guidance](windows-server-mpio-troubleshooting.md).
-1. To isolate an issue to specific hardware, remove individual disks from the cluster and then test the system.
+1. To isolate an issue to specific hardware, remove individual disks from the cluster, and then test the system.
 
 ## Common issues and solutions
 
 ### Event ID 153: The IO operation at logical block address 123456 for Disk 2 was retried
 
-Event ID 153 indicates that the storage subsystem is overloaded, which is causing requests to time out. Event ID 153 is similar to Event ID 129, but the difference is that Event ID 153 is logged when the Storport miniport driver (sometimes known as an adapter or HBA driver) times out a request, while Event ID 129 is logged when the Storport driver (*Storport.sys*) times out a request to the disk. Because of the way the Storport miniport driver and the Storport driver interact, Event ID 153 might not be accompanied by an error.
+Event ID 153 indicates that the storage subsystem is overloaded. This condition causes requests to time out. Event ID 153 is similar to Event ID 129. The events differ as follows:
+
+- Event ID 153 is logged when the Storport miniport driver (sometimes known as an adapter or HBA driver) times out a request.
+- Event ID 129 is logged when the Storport driver (*Storport.sys*) times out a request to the disk.
+
+Because of the manner in which the Storport miniport driver and the Storport driver interact, Event ID 153 might not be accompanied by an error message.
 
 To fix this issue, you have to relieve the overload. Follow these steps:
 
@@ -118,16 +123,16 @@ To fix this issue, you have to relieve the overload. Follow these steps:
 1. If the system traffic doesn't flow as expected, check for the following issues:
    - iSCSI configuration issues, such as damaged cables, damaged network adapters, or network adapters that handle non-storage traffic and storage traffic.
    - MPIO configuration issues, such as insufficient or incorrectly configured multipaths.
-1. If the previous steps can't fix the timeout issue, contact your hardware vendor for information about your specific driver timeouts.
+1. If the previous steps don't fix the timeout issue, contact your hardware vendor for information about your specific driver timeouts.
 
 ### Event ID 129: Reset to device, \Device\RaidPort1, was issued
 
-Similar to Event ID 153, Event ID 129 indicates that the storage subsystem is overloaded, which is causing requests to time out. Event ID 129 is logged when the Storport driver (*Storport.sys*) times out a request to the disk. The event information includes the name of the storage adapter (HBA) driver (also known as the miniport driver) that's associated with the affected Storport driver.
+Similar to Event ID 153, Event ID 129 indicates that the storage subsystem is overloaded. This condition causes requests to time out. Event ID 129 is logged when the Storport driver (*Storport.sys*) times out a request to the disk. The event information includes the name of the storage adapter (HBA) driver (also known as the miniport driver) that's associated with the affected Storport driver.
 
 The following issues can cause this behavior:
 
 - LUNs aren't responding.
-- Hardware issues such as faulty SAN routers are causing request drops.
+- Hardware issues such as faulty SAN routers cause request drops.
 
 To fix this issue, follow these steps:
 
@@ -142,13 +147,14 @@ This issue most often occurs when something disrupts communication between the s
 
 - A SAN fabric error
 - A SCSI bus issue
-- A disk that fails
-- A user unplugs a disk while the system is running.
+- A disk failure
+- A user unplugging a disk while the system is running
 
 To fix this issue, follow these steps:
 
 1. Verify that the disk subsystem is healthy.
-1. Check the state of the disk hardware, and check storage connections for disruptions.
+1. Check the state of the disk hardware.
+2. Check storage connections for disruptions.
 
 ### Event ID 55 and Event ID 98: Please run the chkdsk utility
 
@@ -158,7 +164,7 @@ NTFS events such as Event ID 55, 50, 140, and 98 indicate file system corruption
 - I/O requests that the file system sends to the disk subsystem aren't completed successfully.
 
 > [!NOTE]  
-> Because NTFS couldn't write data to the transaction log, this issue could affect the ability of NTFS to stop or roll back the operations in which the transaction data couldn't be written.
+> Because NTFS can't write data to the transaction log, this issue could affect the ability of NTFS to stop or roll back the operations in which the transaction data couldn't be written.
 
 To fix these issues, follow these steps:
 
@@ -178,6 +184,6 @@ To fix these issues, follow these steps:
 
 1. Update third-party storage drivers or firmware.
 
-1. If the issue persists, try switching to different types of drivers. For example, RAID controller drivers or monolithic drivers, or try rearranging hardware into various combinations.
+1. If the issue persists, try switching to different kinds of drivers. For example, RAID controller drivers or monolithic drivers, or try rearranging hardware into various combinations.
 
 [!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]