Technical White Paper

Nonconformance to the following restrictions may result in the error message below.
Virtual disk (VD) referenced (dedicated hot spare) is RAID-0, which cannot have hot spares
Physical disk (PD) is too small for the virtual disk referenced (dedicated hot spare)
Physical disk is wrong type for the virtual disk (i.e. SATA PD to be used as hot spare for SAS VD)
Similar conditions when no VD referenced, which is the global hot-spare attempted
assignment
ERROR MESSAGE:
<n1: AssignSpare_OUTPUT
<n1:Message>Physical disk FQDD did not identify a
valid physical disk for the operation</n1:Message>
<n1:MessageID>STOR009</n1:MessageID>
<n1:ReturnValue>2</n1:ReturnValue>
</n1:AssignSpare_OUTPUT>
16.16.3 Unassigning the Hot Spare-UnassignSpare()
The UnassignSpare() method is used to unassign a physical disk. The physical disk may be used as a
dedicated hot spare to a virtual disk, or as a global hot-spare. After running the method successfully,
the physical disk drive is no longer a hot-spare.
Invoke UnassignSpare() with the following parameters and syntax:
TARGET: This parameter is the FQDD of the DCIM_PhysicalDiskView
EXAMPLE:
wsman invoke -a UnassignSpare http://schemas.dmtf.org/wbem/wscim/1/cimschema/
2/root/dcim/DCIM_RAIDService
?SystemCreationClassName=DCIM_ComputerSystem,
CreationClassName=DCIM_RAIDService,SystemName=DCIM:ComputerSystem,
Name=DCIM:RAIDService -h $IPADDRESS -V -v -c dummy.cert -P 443
-u $USERNAME -p $PASSWORD -J UnassignSpare.xml -j utf-8 -y basic
The input file UnassignSpare.xml is shown below:
<p:UnassignSpare_INPUT xmlns:p="http://schemas.dmtf.org/wbem/wscim/1/cim-
schema/2/root/dcim/DCIM_RAIDService">
<p:Target>Disk.Bay.3:Enclosure.Internal.0-0:RAID.Integrated.1-
1</p:Target>
</p:UnassignSpare_INPUT>
OUTPUT:
<n1:UnassignSpare_OUTPUT>
<n1:RebootRequired>YES</n1:RebootRequired>
<n1:ReturnValue>0</n1:ReturnValue>
</n1:UnassignSpare_OUTPUT>
16.17 Managing Keys for Self Encrypting Drives
NOTE: The Dell Key Manager feature is not available at this time.