You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-server/backup-and-storage/iscsi-storage-connectivity-troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ SAN-based and iSCSI storage environments in Windows Server (2025, 2022, 2019, an
23
23
24
24
### After you restart Windows Server 2022, the list of favorite target IPs for the iSCSI configuration is incorrect
25
25
26
-
This is a display issue that might occur even if the backend configuration is correct. Microsoft is aware of the issue.
26
+
This issue is a display issue that might occur even if the back-end configuration is correct. Microsoft is aware of the issue.
27
27
28
28
### Backups become unresponsive on Windows Server 2025 ReFS drives
29
29
@@ -238,7 +238,7 @@ To check for and fix volume issues, follow these steps:
238
238
1. Review the quorum configuration. If it's necessary, reassign the quorum.
239
239
1. Review the certificates and certificate store.
240
240
- Check the certificate store's access control list. The SYSTEM account and the ADMINISTRATORS group must have full control on the C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder.
241
-
- If it's necessary, re-import required certificates by running commands that resemble the following example at a Windows command prompt:
241
+
- If it's necessary, import the required certificates again by running commands that resemble the following example at a Windows command prompt:
242
242
243
243
```console
244
244
certutil -store -service clussvc\my
@@ -285,8 +285,8 @@ If iSCSI or Storage PowerShell commands aren't working, you might have an issue
285
285
- Disk fragmentation on HDDs, or lack of TRIM on SSDs.
286
286
- Network or switch misconfiguration or packet loss.
287
287
- Disks that go offline (because they run out of available disk space).
288
-
- Excessively long disk queues, accumulated shadow copies (more than 4,000 copies), or storport driver issues. These can increase latency.
289
-
- Nonoptimized commands or insufficient available threads. These can slow down backup or file copy operations.
288
+
- Excessively long disk queues, accumulated shadow copies (more than 4,000 copies), or storport driver issues. These conditions can increase latency.
289
+
- Nonoptimized commands or insufficient available threads. These conditions can slow down backup or file copy operations.
0 commit comments