1. Take volume off synchronous mode
– Pre-emptively avoid this error: “Failed to update the volume. Failed to update the volume: Operation is not permitted on volumes configured for synchronous replication.”
– Login to Nimble > click on Manage > Data Storage > click the target volume > Edit > Next to advance to the Space settings > Next to advance to the Protection Settings > select “No Volume Protection” > Save > select Okay to disassociate… > Make Edits to commit change
2. Expand volume size
– Click on Manage > Data Storage > click the target volume > Edit > Next to advance to the Space settings > type in a numerical value to represent the desired volume size (e.g. change from 2.4 TiB to 3.0 TiB) > Save > put a check mark next to Okay to resize volume > Make Edits
3. Resize volume in Windows
These commands are to be executed on the owner node of the target volume.
The quick method
# Resize volume to its available maximum
$driveLetter="V"
Update-HostStorageCache
$max=(Get-PartitionSupportedSize -DriveLetter $driveLetter).SizeMax
Resize-Partition -DriveLetter $driveLetter -Size $max
The struggles during troubleshooting
# View all partitions of disk 13
PS C:\Windows\system32> Get-Partition -DiskNumber 13
DiskPath: \\?\Disk{0a0816ef-54f0-2eae-ff8c-8edb05b53e72}
PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
1 17408 128 MB Reserved
2 V 135266304 2.38 TB Basic
# View specific partition of disk
PS C:\Windows\system32> Get-Partition -DiskNumber 13 -PartitionNumber 2
DiskPath: \\?\Disk{0a0816ef-54f0-2eae-ff8c-8edb05b53e72}
PartitionNumber DriveLetter Offset Size Type
--------------- ----------- ------ ---- ----
2 V 135266304 2.38 TB Basic
# collect partition sizes as a variable
$size = (Get-PartitionSupportedSize -DiskNumber 13 -PartitionNumber 2)
Get-PartitionSupportedSize -DiskNumber 13 -PartitionNumber 2)
0/2+ completed
[ ]
PS C:\Windows\system32> $size
SizeMin SizeMax
------- -------
2612375207936 2616702516736
# Demonstration of a failed attempt due to a bug in
Resize-Partition -DiskNumber 13 -PartitionNumber 2 -Size $size.SizeMax
Error:
PS C:\Windows\system32> Resize-Partition -DiskNumber 13 -PartitionNumber 2 -Size $size.SizeMax
Resize-Partition : Size Not Supported
Extended information:
The size of the extent is less than the minimum of 1MB.
Activity ID: {90e2f332-c11d-4df3-a056-a52a6970dcf0}
At line:1 char:1
+ Resize-Partition -DiskNumber 13 -PartitionNumber 2 -Size $size.SizeMa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (StorageWMI:ROOT/Microsoft/.../MSFT_Partition) [Resize-Partition], CimExce
ption
+ FullyQualifiedErrorId : StorageWMI 4097,Resize-Partition
$wrongSize = (Get-PartitionSupportedSize -DiskNumber 13 -PartitionNumber 2)
$correctSize = (Get-PartitionSupportedSize -DriveLetter $driveLetter)
PS C:\Windows\system32> $correctSize
SizeMin SizeMax
------- -------
2612374355968 2748643786240
PS C:\Windows\system32> $wrongSize
SizeMin SizeMax
------- -------
2612375207936 2616702516736
4. Turn synchronous mode back on
a. Delete orphanated copy
– Login to Nimble > click on Manage > Data Storage > put a check-mark next to the target volume’s previous replicated copy (should be shown as offline) > click on “X” or “Remove” button > verify that the volume to delete is the orphanated copy > Delete
b. Add volume back to protection group
– Click on Manage > Data Protection > click on the correct Volume Collection (also known as protection group) > Actions > Edit > highlight the target volume in the Available pool > Add > Save