Skip to content

Commit a42fe76

Browse files
authored
Update troubleshoot-data-corruption-and-disk-errors.md
1 parent fa10d31 commit a42fe76

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ To fix this issue, you have to relieve the overload. Follow these steps:
121121
1. Make sure that you have enough controllers to handle the system load. If you have multiple high-load drives that share a controller, consider splitting the drives among different controllers.
122122
1. Check the controller configurations, especially any throttling configurations (such as for VMware Storage I/O Control).
123123
1. If the system traffic doesn't flow as expected, check for the following issues:
124-
- iSCSI configuration issues, such as damaged cables, damaged network adapters, or network adapters that handle non-storage traffic and storage traffic.
124+
- iSCSI configuration issues, such as damaged cables, damaged network adapters, or network adapters that handle nonstorage traffic and storage traffic.
125125
- MPIO configuration issues, such as insufficient or incorrectly configured multipaths.
126126
1. If the previous steps don't fix the timeout issue, contact your hardware vendor for information about your specific driver timeouts.
127127

@@ -141,7 +141,7 @@ To fix this issue, follow these steps:
141141

142142
### Event ID 157: Disk 2 has been surprise removed
143143

144-
This event indicates that the *Classpnp.sys* driver received a surprise removal request from the plug and play (PNP) manager for a non-removable disk.
144+
This event indicates that the *Classpnp.sys* driver received a surprise removal request from the plug and play (PNP) manager for a nonremovable disk.
145145

146146
This issue most often occurs when something disrupts communication between the system and a disk. For example, any of the following incidents can generate this event:
147147

0 commit comments

Comments
 (0)