Skip to content

Commit 116db4f

Browse files
authored
Update delete-s2d-storage-pool-reuse-disks.md
1 parent 6241e88 commit 116db4f

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

support/windows-server/backup-and-storage/delete-s2d-storage-pool-reuse-disks.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Delete a Storage Spaces Direct Storage Pool and Reset the Physical Sisks
2+
title: Delete a Storage Spaces Direct Storage Pool and Reset the Physical Disks
33
description: Explains how to gracefully delete an S2D storage pool so that you can reuse the disks elsewhere.
44
ms.date: 01/07/2026
55
manager: dcscontentpm
@@ -71,7 +71,7 @@ To use the procedures from this example, make sure that the following permission
7171
> [!NOTE]
7272
>
7373
> - If you don't specify a node when you run `Get-PhysicalDisk` on any node within an S2D cluster, the output includes all physical disks across all nodes in the cluster. This behavior is by design. Each node maintains awareness of the entire pool's disk inventory--not only the disks that are physically attached to it.
74-
> - In the command output, note that the **CanPool** property of the 64-GB disks (1002-1004 and 2002-2004) is **False**. This value means that the disks already belong to a storage pool.
74+
> - In the command output, the **CanPool** property of the 64-GB disks (1002-1004 and 2002-2004) is **False**. This value means that the disks already belong to a storage pool.
7575
7676
```output
7777
Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
@@ -205,7 +205,7 @@ To verify that the virtual disks, storage tiers, and the storage pool don't exis
205205
PS C:\Users\SQLVMADMIN> Get-StoragePool
206206
```
207207

208-
The output of this command resembles the following example. Note that the primordial storage pool is still present.
208+
The output of this command resembles the following example. Notice that the primordial storage pool is still present.
209209

210210
```output
211211
FriendlyName OperationalStatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize
@@ -240,7 +240,7 @@ After the script finishes, verify the disk status by running the following comma
240240
PS C:\Users\SQLVMADMIN> Get-PhysicalDisk
241241
```
242242

243-
The output of this command resembles the following example. Note that the **CanPool** property of each disk changed from "False" to "True." The disks don't belong to a storage pool anymore, but they're available to assign to a new storage pool.
243+
The output of this command resembles the following example. The **CanPool** property of each disk changed from "False" to "True." The disks don't belong to a storage pool anymore, but they're available to assign to a new storage pool.
244244

245245
```output
246246
Number FriendlyName SerialNumber MediaType CanPool OperationalStatus HealthStatus Usage Size
@@ -257,7 +257,7 @@ Number FriendlyName SerialNumber MediaType CanPool OperationalStatus Hea
257257

258258
## More information
259259

260-
If you remove a physical disk from the storage pool infrastructure without using the process that's detailed in this article, both the storage pool and the disk become unusable. For example, if you remove a disk from one node, the System log of that node generates Event ID 157:
260+
If you remove a physical disk from the storage pool infrastructure without using the process that this article provides, both the storage pool and the disk become unusable. For example, if you remove a disk from one node, the System log of that node generates Event ID 157:
261261

262262
```output
263263
Log Name: System

0 commit comments

Comments
 (0)