Reference Guide

IOPSRead : 0 /S
IOPSTotal : 1 /S
IOPSWrite : 1 /S
IOThroughputRead : 0 B/S
IOThroughputTotal : 11.98 KB/S
IOThroughputWrite : 11.98 KB/S
MemoryAvailable : 472.87 GB
MemoryTotal : 768 GB
After all available disks are claimed in the storage pool, the CapacityPhysicalUnpooled is 0 B.
The storage rebalance job might take a few minutes. You can monitor the process by using the Get-StorageJob cmdlet.
Extending volumes
You can resize volumes that are created in Spaces Direct storage pools by using the Resize-VirtualDisk cmdlet. For more
information, see https://technet.microsoft.com/windows-server-docs/storage/storage-spaces/resize-volumes.
Performing AX node recovery
If a cluster node fails, perform node operating system recovery in a systematic manner to ensure that the node is brought up with the
configuration that is consistent with other cluster nodes.
The following sections provide details about operating system recovery and post-recovery configuration that is required to bring the node
into an existing Azure Stack HCI cluster.
NOTE: To perform node recovery, ensure that the operating system is reinstalled.
Configuring RAID for operating system drives
Prerequisites
The Dell EMC PowerEdge servers offer the Boot Optimized Storage Solution (BOSS) S-1 controller as an efficient and economical way to
segregate operating system and data on the internal storage of the server. The BOSS S-1 solution in the latest generation of PowerEdge
servers uses one or two BOSS M.2 SATA devices to provide RAID 1 capability for the operating system drive.
NOTE:
All Dell EMC Solutions for Azure Stack HCI are configured with hardware RAID 1 for the operating system drives
on BOSS M.2 SATA SSD devices. The steps in this section are required only when recovering a failed cluster node.
Before creating a new RAID, the existing or failed RAID must be deleted.
About this task
This procedure describes the process of creating operating system volumes.
Steps
1. Log in to the iDRAC web interface.
2. Go to Storage > Controllers.
Figure 21. View controllers
Day 0 Operations
29