Dell OpenManage Array Manager User's Guide Version 3.6
Protecting Data with a Hot Spare
Channel Redundant Virtual Disks
Reconfiguring/Migrating Virtual Disks
In order to implement RAID functions, RAID controllers must create a virtual disk. A virtual disk refers to storage created by a RAID controller from one or more array disks. Although a virtual disk may be created from several array disks, it is seen by the operating system as a single disk. Depending on the RAID level used, the virtual disk may retain redundant data in case of a disk failure or have particular performance attributes. See "Understanding Storage Concepts" for more information.
In the Array Manager tree view, a virtual disk object can be expanded to display the array disks included in the virtual disk.
To view virtual disks, expand the Arrays, subsystem, controller, and Array Groups objects in the tree view.
![]() |
Note Virtual disks can only be created on a RAID controller. |
When you create a redundant virtual disk using a RAID controller, you have the opportunity to maintain system operations even when a disk fails. To do so, you would assign a hot spare to the virtual disk. When a disk fails, the redundant data is rebuilt onto the hot spare without interrupting system operations. More information regarding hot spares and the procedures for implementing them is included in the controller chapter. See the following for more information:
When creating a virtual disk, it is possible to use disks attached to different channels to implement channel redundancy. This configuration might be used for disks that reside in enclosures subject to thermal shutdown. See the following for more information:
![]() |
Note Channel redundancy only applies to controllers that have more than one channel and that attach to an external disk enclosure. |
In order to implement RAID functions, you need to create a virtual disk. A virtual disk refers to storage created by a RAID controller from one or more array disks. Although a virtual disk may be created from several array disks, it is seen by the operating system as a single disk. See "What Is RAID?" for more information.
Depending on your controller, refer to the following sections:
You may also wish to refer to the following related sections:
In addition to the considerations described in this section, you should also be aware of the controller limitations described in "Number of Array Disks per Virtual Disk."
Be aware that the following considerations apply when creating virtual disks:
In addition to the considerations described in this section, you should also be aware of the controller limitations described in "Number of Array Disks per Virtual Disk."
Be aware that the following considerations apply when creating virtual disks:
There are limitations on the number of array disks that can be included in the virtual disk. These limitations depend on the controller. When creating a virtual disk, controllers support a certain number of stripes and spans (methods for combining the storage on array disks). Because the number of total stripes and spans is limited, the number of array disks that can be used is also limited. The limitations on stripes and spans affect the possibilities for concatenation and RAID levels as follows:
In the case of RAID 50, you can use a greater number of array disks than is possible for the other RAID levels. The number of channels on the controller, however, imposes limitations on how many array disks can be included in a virtual disk when using RAID 50. This is because only a limited number of array disks can be physically attached to the controller.
The following table describes the specific limitations for the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers.
The following table describes the specific limitations for the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers.
For more information on storage concepts used in this section, see "What Is RAID?" and "Choosing RAID Levels and Concatenation."
![]() |
Note In addition to this online help, you should review the hardware documentation that is provided with the controllers. Reviewing the hardware documentation along with this online help may provide a fuller understanding of the controller limitations. |
Controllers have limitations on the number of virtual disks that they can support.
You can create a maximum of 8 virtual disks on one PERC 2/SC or PERC 2/DC controller and a maximum of 40 virtual disks on one CERC ATA100/4ch controller. On the PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di, controllers, you can create a maximum of 40 virtual disks.
You can create a maximum of 24 virtual disks on a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller.
The Create Virtual Disk Wizard - Express Mode
Express Mode calculates an appropriate virtual disk layout based on the available space and controller considerations. Using Express Mode, you can quickly create a virtual disk using recommended selections.
Create Virtual Disk Express Mode
The Create Virtual Disk Wizard - Advanced Mode
Advanced Mode allows you to specify the read, write, and cache policy for the virtual disk. You can also select the array disks and the controller channel to be used. You need a good knowledge of RAID levels and hardware to use this mode.
Create Virtual Disk Advanced Mode. The Read, Write, and Cache Policy options vary depending on the controller.
![]() |
Note When creating a concatenated virtual disk on the CERC SATA1.5/2s controller, you cannot specify the virtual disk name. |
![]() |
Note This note applies to PERC 2/SC, PERC 2/DC, PERC 3/SC, PERC 3/DC, PERC 3/DCL, PERC 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers. When you create a RAID 10 or RAID 50 virtual disk, the size option is redundant, as the maximum size will be created. When you click Finish, the Size text box displays the maximum size. |
Read policy for PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers
Write policy for PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers
![]() |
Note Write-through caching is the default write policy setting when cluster mode is enabled. In cluster mode, the PERC 3/DC controllers only allow write-through caching. |
When using Express Mode, the wizard selects disks for you depending on the RAID level you selected and on the controller. When using Advanced Mode, the wizard displays the disks that you selected from the Available Disks section of Advanced Mode. Use the Blink and Unblink buttons to identify which disks are selected by blinking their LED display.
When using Advanced Mode, you can select the disks to be used from the Available Disks tabs. These tabs indicate the disks attached to each controller channel that are available depending on the RAID level you selected and the controller.
If the newly created virtual disk does not appear under Disks in the tree view, then perform a rescan by selecting Rescan from the View pull-down menu. Rescan forces the Array Manager software to locate and query all the objects in the system. This can take several minutes if there are numerous disks on the system.
When initializing is complete, the virtual disk appears in the tree view of the Array Manager console. Each virtual disk is automatically mapped to a Windows disk. For example, if Virtual disk 0 is mapped to Windows Disk 0, the Array Manager console will display Virtual disk 0 as "Virtual Disk 0 (Disk 0)," and the Windows disk 0 as "Disk 0 (Virtual Disk 0)."
If a virtual disk is not mapped to a Windows disk, reboot the system.
![]() |
Note On the PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, initialization begins automatically after you have created a redundant virtual disk. |
When you create a virtual disk, a write signature is not automatically written to the disk. Windows requires a write signature on virtual disks. For instructions on writing a disk signature, see the section "Write a Disk Signature" in the "Disks" chapter.
You can reconfigure or migrate a virtual disk in order to increase the disk's capacity or change its RAID level. The procedure for reconfiguring a virtual disk varies depending on which controller you have.
The PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers have pop-up menu commands that enable you to expand the virtual disk, change the RAID level, and change the cache policy. Use the following commands to accomplish these tasks.
Use the Virtual Disk Reconfiguration wizard to change attributes of a virtual disk on a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller. You can:
Use this procedure to reconfigure a virtual disk on a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller:
The following sections describe pop-up menu commands for the PERC Subsystem 1 and PERC Subsystem 2 virtual disks. For information on the PV660F virtual disk commands, see "The Dell PowerVault 660F Storage System."
Right-click a virtual disk in the Array Manager tree view to display its pop-up menu commands. Because the features for each virtual disk can vary, the virtual disk pop-up menu may not display all of these commands.
Use this function to add array disks to a virtual disk. You can also change the virtual disk's RAID level.
![]() |
Note If you add a member to a virtual disk that shares array disk storage with another virtual disk, you may not be able to create or delete virtual disks on the controller. Whenever you create a virtual disk that you plan to expand later with the Add Member command, it is recommended that you use the entire capacity of its member array disks. |
![]() |
Note The Add Member command is only available for RAID 0, RAID 1, and RAID 5. |
Add Member shows progress information in the right pane. To view the progress, click the parent of the virtual disk. The status of the virtual disk will be Reconstructing, and progress information will display until the Add Member operation is finished. At the end of the operation, the Type category shows the changed RAID level, if the RAID level was changed.
Use the Transform Type function to change the RAID level or stripe size of a virtual disk without adding or removing disks. The following is a list of supported RAID level migrations:
Deleting a virtual disk permanently deletes all information contained within all volumes residing on that virtual disk.
|
Caution All data (including file systems, volumes, Windows disks) on the virtual disk is lost when the disk is deleted. |
Because of PERC 2/SC and 2/DC controller hardware constraints, virtual disks must be deleted in the reverse order of their creation on these controllers. In other words, the last disk that you created must be deleted first.
There are particular considerations for deleting a virtual disk from a cluster-enabled PERC 3/DC controller. Review the "Creating and Deleting Virtual Disks on Cluster-enabled Controllers" section before attempting to delete the virtual disk.
If the disk you are deleting was not the last one created, a message may display that asks you to delete the most recently created virtual disk first.
![]() |
Note If you delete a virtual disk and immediately create a new virtual disk with all the same characteristics as the one that was deleted, the controller will recognize the data as if the first virtual disk were never deleted. In this situation, if you don't want the old data after recreating a new virtual disk, reinitialize the virtual disk. |
Use this function to change the read or cache policies of a virtual disk.
![]() |
Note In cluster mode, the PERC 3/DC controller only allows write-through caching. |
If you wish to verify your changes, right-click the virtual disk, select Properties, and check the virtual disk properties.
Use this command to rename a virtual disk. Renaming a virtual disk enables you to change the virtual disk name displayed in the Array Manager tree view. The numbering format for the virtual disk remains unchanged.
Depending on the controller you have, there are different considerations regarding the controller BIOS:
![]() |
Note The Rename command is not available for concatenated virtual disks on a CERC SATA1.5/2s controller. |
On PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, background initialization of redundant virtual disks begins automatically after the virtual disk is created.
It is important that the background initialization be allowed to run to completion. You can, however, cancel the background initialization. When you do so, the controller will restart the background initialization within 0 to 5 minutes. See "Background Initialization on PERC Subsystem 1 Controllers" for more information.
To cancel background initialization, right-click the redundant virtual disk and select Cancel Background Initialization.
Use this command to assign and configure a dedicated hot spare for a redundant virtual disk. If one of the array disks belonging to a redundant virtual disk fails or is removed, then the virtual disk becomes degraded. A degraded virtual disk that has a properly configured hot spare automatically rebuilds onto that hot spare.
You can configure a dedicated hot spare for redundant virtual disks using RAID 1, 10, 5, 50, and RAID-1 concatenated.
Hot spares created with the Configure Dedicated Hot Spare command are dedicated to a virtual disk. They will only be used if an array disk in the virtual disk fails. When you dedicate a hot spare for a virtual disk, you may notice that other virtual disks are also assigned the same hot spare. This is because the dedicated hot spare applies to all virtual disks that use the same array disks as the virtual disk for which you are configuring the hot spare. The hot spare will rebuild the data for all redundant virtual disks that are using the failed array disk.
To remove the dedicated hot spare and return the array disk to its normal status, use the Remove a Dedicated Hot Spare procedure.
For more information on hot spares including size requirements, see "Understanding Hot Spares." For considerations regarding RAID 10 and RAID 50 virtual disks created using the controller BIOS, see "Dedicated Hot Spare Considerations for RAID 10 and RAID 50 on PERC Subsystem 1 Controllers."
![]() |
Note Configuring a dedicated hot spare for a virtual disk is highly recommended. |
![]() |
Note The Configure Dedicated Hot Spare command is not available on the PERC 2/SC, PERC 2/DC, and CERC SATA1.5/2s controllers. |
Use this operation to remove a dedicated hot spare from a virtual disk. This operation returns an array disk that was previously configured as a dedicated hot spare to its normal status.
![]() |
Note When removing a hot spare that was created with the Configure Dedicated Hot Spare menu option, be aware that multiple virtual disks may be using the hot spare. This is because the hot spare applies to all virtual disks that use the same array disks as the virtual disk for which the hot spare was created. Removing a dedicated hot spare removes the hot spare from all of these virtual disks. |
This operation verifies the accuracy of the redundant data in the virtual disk and rebuilds parity if necessary. You also use this function if your disk is in a degraded state. Running Check Consistency may be able to restore your disk to Ready status.
You cannot check the consistency of a non-redundant RAID type.
![]() |
Note On PERC 2, 2/Si, 3/Si, 3/Di, and CERC SATA1.5/6ch controllers, you can pause the consistency check once it is in progress with the Pause Consistency Check option. |
If you have initiated a consistency check using the Check Consistency option, you can suspend or pause the consistency check with the Pause Consistency Check option. Once paused, you can later resume the consistency check by using the Resume Consistency Check option. A paused consistency check will also automatically resume when the system is rebooted.
After having suspended a consistency check by using the Pause Consistency Check option, you can resume the consistency check with the Resume Consistency Check option.
For PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, CERC ATA100/4ch, you can cancel a consistency check that you initiate.
On PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di and CERC SATA1.5/6ch controllers, a consistency check will be auto-initiated when you create a redundant virtual disk. If you cancel that initial consistency check, then the virtual disk is not considered "redundant". To assure the virtual disk is redundant, you must let a consistency check run to completion.
The CERC SATA1.5/2s controllers do not have a pausing feature. You must allow the consistency check to complete or cancel the consistency check.
Use this procedure on any virtual disk on a PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controller system. The virtual disk will be formatted by this operation. Note that you need to initialize before using any virtual disk.
|
Caution Initializing a virtual disk destroys any data that is on the disk. |
![]() |
Note If you initialize a virtual disk and then notice that volume information has not been erased, reboot the server. |
You can cancel the virtual disk initialization while it is in progress.
Use this procedure to format a virtual disk on a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controller. This operation erases the files and removes the file systems on virtual disks but keeps the virtual disk configuration intact.
|
Caution On a NetWare system, Array Manager does not have the ability to detect whether the SYS volume or the boot partition reside on the virtual disk. Formatting a virtual disk that contains the SYS volume or boot partition will damage the system. |
Formatting a virtual disk on the PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers removes the Windows disk object and any associated drive mapping. After the format is complete, the disk object is restored, but it may not be mapped to a drive. To restore the drive mapping, either do a global rescan or stop and restart the Disk Management Service.
![]() |
Note If you format a virtual disk that has been upgraded to dynamic, the disk functions may become inactive or the status of the disk may change to "foreign" or "offline." You can view a disk's status by selecting the disk's General tab. When using a PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller, you can resolve these problems by doing a global rescan. |
This command recovers the disk space occupied by an orphan or dead disk segment. An orphan disk segment is part of a multipartition virtual disk that cannot access another disk segment within the same virtual disk. A dead disk segment is either no longer needed by the virtual disk or is physically damaged. This operation can be performed only on failed virtual disks of redundant RAID types.
![]() |
Note You can restore only segments of a redundant RAID type. |
![]() |
Note This operation is not supported in NetWare. |
Use the Split Mirror command to separate mirrored data originally configured as a RAID 1 or RAID 10 virtual disk. Splitting a RAID 1 mirror creates two concatenated non-redundant virtual disks. Splitting a RAID 10 mirror creates two RAID 0 (striped) non-redundant virtual disks. Data is not lost during this operation.
![]() |
Note This operation is not supported in NetWare. It is also not supported when using a dynamic virtual disk with a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di or CERC SATA1.5/6ch, or CERC SATA1.5/2s controller. |
|
Caution Your virtual disk will no longer be redundant after performing a Split Mirror operation. |
Use the Unmirror command to separate mirrored data and restore one half of the mirror to free space. Unmirroring a RAID 1 virtual disk results in a single, non-redundant concatenated virtual disk. Unmirroring a RAID 10 virtual disk results in a single, non-redundant RAID 0 (striped) virtual disk. Data is not lost during this operation.
![]() |
Note This operation is not supported in NetWare. It is also not supported when using a dynamic virtual disk with a PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, or, CERC SATA1.5/2s controller. |
|
Caution Your virtual disk will no longer be redundant. |
The Blink Virtual Disk command allows you to locate the array disks included in a virtual disk by blinking the light-emitting diodes (LEDs) on the array disks. The LEDs could blink from 30 seconds to indefinitely.
This procedure is only supported for hotswap array disks (disks that reside in a carrier).
![]() |
Note This procedure is not supported on the CERC ATA100/4ch or PERC 4/IM controllers. |
The Unblink Virtual Disk command allows you to cancel the Blink Virtual Disk command.
This procedure is only supported for hotswap array disks (disks that reside in a carrier).
![]() |
Note This procedure is not supported on the CERC ATA100/4ch or PERC 4/IM controllers. |
A rebuild menu option is available for RAID 1 virtual disks on the CERC SATA1.5/2s controller. The Rebuild option on this controller is only enabled when one array disk in the RAID 1 contains data that is not consistent with the data on the other array disk. This may occur if one of the array disks is removed or the cable is disconnected and the other array disk continues to update its data. See Rebuilding a Virtual Disk on the CERC SATA1.5/2s Controller for more information.
This command enables you to display the virtual disk properties.
To display the virtual disk properties:
The Virtual Disk Properties dialog has tabs for displaying the properties of the virtual disk. These properties include the read, write, and cache policies of the disk, its status, and its capacity.