Users Guide

RAID 60. If you have selected RAID 10 and if the controller supports uneven RAID 10, then the span count value is not
displayed. The controller automatically sets the appropriate value. For RAID 50 and RAID 60, this field is not displayed
when minimum number of disks are used to create RAID. It can be changed if more disks are used.
3. In the Select Physical Disks section, select the number of physical disks.
For more information about the fields, see the iDRAC Online Help
4. From the Apply Operation Mode drop-down menu, select when you want to apply the settings.
5. Click Create Virtual Disk.
Based on the selected Apply Operation Mode, the settings are applied.
NOTE: You can use alphanumeric characters, spaces, dashes, and underscores in the disk name.
Any other special characters that you enter are removed and replaced by space while creating the virtual disk.
Creating virtual disks using RACADM
Use the racadm storage createvd command.
For more information, see the iDRAC RACADM CLI Guide available at https://www.dell.com/idracmanuals.
NOTE: Disk slicing or configuring partial VDs is not supported using RACADM on the drives managed by S140 controller.
Editing virtual disk cache policies
You can change the read, write, or disk cache policy of a virtual disk.
NOTE:
Some of the controllers do not support all read or write policies. Therefore, when a policy is applied, an error
message is displayed.
The read policies indicate whether the controller must read sequential sectors of the virtual disk searching for data:
● Adaptive Read Ahead — The controller initiates read ahead only if the two most recent reads requests accessed sequential
sectors of the disk. If subsequent read requests access random sectors of the disk, the controller reverts to no read ahead
policy. The controller continues to evaluate whether read requests are accessing sequential sectors of the disk, and initiates
read ahead if necessary.
● Read Ahead — The controller reads sequential sectors of the virtual disk when seeking data. Read ahead policy may
improve system performance if the data is written to the sequential sectors of the virtual disk.
● No Read Ahead — Selecting no read ahead policy indicates that the controller should not use read ahead policy.
The write policies specify if the controller sends a write-request completion signal when the data is in the cache or after it has
been written to the disk.
● Write Through — The controller sends a write-request completion signal only after the data is written to the disk.
Write-through caching provides better data security than write-back caching, since the system assumes that the data is
available only after it has been safely written to the disk.
● Write Back — The controller sends a write-request completion signal as soon as the data is in the controller cache but has
not yet been written to disk. Write back caching may provide improved performance since subsequent read requests can
retrieve data quickly from the cache then from the disk. However, data loss may occur in the event of a system failure which
prevents that data from being written on a disk. Other applications may also experience problems when actions assume that
the data is available on the disk.
● Force Write Back — The write cache is enabled regardless of whether the controller has a battery. If the controller does
not have a battery and force write-back caching is used, data loss may occur in the event of a power failure.
The Disk Cache policy applies to readings on a specific virtual disk. These settings do not affect the read-ahead policy.
NOTE:
● Controller non-volatile cache and battery backup of controller cache affects the read-policy or the write policy that a
controller can support. All PERCs do not have battery and cache.
● Read ahead and write back requires cache. Therefore, if the controller does not have cache, it does not allow you to set
the policy value.
Similarly, if the PERC has cache but not battery and the policy is set that requires accessing cache, then data loss may
occur if base of power off. So few PERCs may not allow that policy.
Managing storage devices 243