Back to Contents Page

Controllers

Dell OpenManage™ Array Manager User's Guide Version 3.6

  Understanding Read, Write, and Cache Policy

  Understanding Hot Spares

  PERC Subsystem 1 Controllers

  PERC Subsystem 2 Controllers

  SCSI Subsystem Controllers

  Controller Menu Commands

This section applies to all controllers supported by Array Manager.

Most operating systems (OS) do not read and write data directly from the disks, but instead send read and write instructions to a controller. The controller (or adapter) is the hardware in your system that interacts directly with the disks to write and retrieve data. A system can have more than one controller, with each controller attached to its own set of disks.

RAID controllers can span the boundaries of the disks so as to create an extended amount of storage space -- or a virtual disk -- using the capacity of more than one disk. The operating system views these virtual disks as if they are a single, large disk or drive.

The PERC Subsystem 1 and PERC Subsystem 2 controllers are RAID controllers. They have features for creating virtual disks. The SCSI Subsystem controllers are non-RAID SCSI controllers. They are not capable of creating virtual disks, but they do provide tape and CDROM management.

For information on the PV660F Subsystem, see "The Dell PowerVault 660F Storage System."

To view the controllers attached to your system:

  1. Expand the Arrays object in the Array Manager tree view hierarchy.

  2. Expand the subsystem object. This action displays the controllers included in the subsystem. Depending on which types of controllers your system has, there may be more than one subsystem object in the tree view.

Note Different controllers support different features. For this reason, the controller pop-up menu options and the storage objects displayed under a controller in the tree view can vary.

Understanding Read, Write, and Cache Policy

This section applies to 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, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

When creating a virtual disk, you specify the read, write, and cache policies for the virtual disk. The following describes how each of these policies functions.

Read Policy

The read policies indicate whether or not the controller should read sequential sectors of the logical drive when seeking data. The read policies are as follows.

Read policy 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, and CERC ATA100/4ch controllers
Read policy for PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers
Write Policy

The write policies specify whether the controller sends a write-request completion signal as soon as the data is in the cache or after it has been written to disk. The write policies are as follows.

Write policy 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, and CERC ATA100/4ch controllers
Note The Write-Back Caching option is not available for controllers that do not have a battery.
Note Write-through caching is the default write policy setting when cluster mode is enabled. In cluster mode, the PERC 3/DC, 4/DC, and 4e/DC controllers only allow write-through caching.
Write policy for PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers
Cache Policy

The Direct I/O and Cache I/O cache policies apply to reads on a specific logical drive. These settings do not affect the read-ahead policy. The cache policies are as follows.

Cache policies apply to 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.

Understanding Hot Spares

This section applies to 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, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

A hot spare is an unused backup array disk that can be used to rebuild data from a redundant virtual disk. Hot spares remain in standby mode. When an array disk that is used in a redundant virtual disk fails, the assigned hot spare is activated to replace the failed array disk without interrupting the system or requiring your intervention. If a virtual disk using the failed array disk is not redundant, then the data is permanently lost without any method (unless you have a backup) to restore the data.

Hot spare implementation is somewhat different for controllers in PERC Subsystem 1 and PERC Subsystem 2.

The following sections provide more information regarding hot spare considerations for PERC Subsystem 1 and PERC Subsystem 2 controllers:

The following sections describe procedures for assigning a hot spare:

Considerations for Hot Spares (PERC Subsystem 1)

This section applies to 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

When creating a virtual disk, the array disks included in the virtual disk can be different sizes. When assigning a hot spare on a PERC Subsystem 1 controller, the hot spare only needs to be the same size (or larger) as the smallest array disk included in the virtual disk.

This is because when using a PERC Subsystem 1 controller, you can assign array disks of different sizes to a virtual disk. Once you have fully consumed a smaller array disk with a virtual disk, however, any portion of larger array disks that are not consumed by the virtual disk become unusable. Therefore, there is no data on the unused portion of a larger disk that needs to be rebuilt. A redundant virtual disk will also be either striped or mirrored in equal portions across its member array disks. The amount of data requiring a rebuild will therefore not be larger than the smallest array disk.

A dedicated hot spare can only be assigned to a single virtual disk. A global hot spare is assigned to all redundant virtual disks on the controller. A global hot spare must be the same size (or larger) as the smallest array disk included in the largest virtual disk on the controller.

Once you have assigned a global hot spare, any new virtual disks created on the controller will not be protected by the hot spare if the partition size of the disk is larger than the global hot spare. In this case, you can unassign the global hot spare after creating a new virtual disk and then assign a new and larger hot spare to cover all redundant virtual disks on the controller.

Note The Configure Dedicated Hot Spare command is not available on the PERC 2/SC and PERC 2/DC controllers.
Dedicated Hot Spare Considerations for RAID 10 and RAID 50 on PERC Subsystem 1 Controllers

If you have created a RAID 10 or RAID 50 virtual disk that does not fully consume its member array disks, then you will not be able to assign a dedicated hot spare to the RAID 10 or RAID 50 virtual disk. Array Manager does not allow you to create RAID 10 and RAID 50 virtual disks from partial array disks. You will therefore not encounter this situation if you are using Array Manager to create your virtual disks. If you use the controller BIOS, however, you may be able to create a RAID 10 or RAID 50 virtual disk that uses partial array disks. In this situation, you will not be able to assign a dedicated hot spare to these RAID 10 or RAID 50 virtual disks.

Array Disk State, Event Messages and Hot Spares on PERC Subsystem 1 Controllers

If you have a hot spare assigned to a virtual disk and an array disk in the virtual disk fails, the failed array disk may change from Online state to Ready state without displaying a Failed state. This occurs when the hot spare is activated before the array disk is able to report the Failed state. Because the Failed state is not reported, the "array disk failed" event 500 is not generated.

Once the hot spare is activated it changes to the Rebuilding state. If you review the event log and identify a "rebuilding" event such as 526 or 527, you can assume that an array disk has failed.

Considerations for Hot Spares (PERC Subsystem 2)

This section applies to PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

A dedicated hot spare on PERC Subsystem 2 controllers rebuilds the portion of a redundant virtual disk that resides on the failed array disk. On PERC Subsystem 2 controllers, individual array disks may be included in more than one virtual disk. (Assigning a portion of an array disk to a virtual disk does not preclude the remaining portion of the array disk from being used by other virtual disks.)

You can assign the same dedicated hot spare to more than one virtual disk. In this case, the hot spare attempts to rebuild all portions of redundant virtual disks that reside on a failed array disk. To increase the likelihood that the hot spare is able to rebuild all virtual disks, you should do the following:

  1. Create virtual disks that share the same set of array disks.

  2. Only assign dedicated hot spares to those virtual disks that share the same set of array disks.

  3. Assign a hot spare that is big enough to rebuild the total size of all virtual disks to which the hot spare is assigned. For example, if you have a 20 MB, a 30 MB, and a 50 MB virtual disk all sharing the same set of array disks, then the hot spare needs to be 100 MB or larger.

Once the hot spare is activated to rebuild a particular virtual disk, it is no longer available for rebuilding other virtual disks should an additional array disk fail. For this reason, when a hot spare is activated it is automatically unassigned from the remaining virtual disks. To maintain data protection, you will need to add a new hot spare and assign it to the other virtual disks.

Note The Configure Dedicated Hot Spare command is not available on the CERC SATA1.5/2s controller.

PERC Subsystem 1 Controllers

Description of PERC Subsystem 1 Controllers

This section applies to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers

The PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC 4/Di, 4e/Si, 4e/Di, and controllers are high-performance intelligent PCI-to-SCSI host adapters with RAID control capabilities. The PERC 4e/DC (dual channel) controller provides PCI-express architecture.

The CERC ATA100/4ch controller is a PCI-to-IDE host adapter with RAID control capabilities. Each channel on the CERC ATA100/4ch supports 100 MB data transfer. Each channel on this controller supports a single device.

Each channel on the PERC 2/SC and PERC 2/DC controllers supports SCSI data transfer rates of up to 80 MB per second per channel and up to 160 MB per second per channel for the PERC 3/SC, 3/DCL, 3/DC, and 3/QC controllers. The channels on these controllers also support up to 15 devices.

Each channel on the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, controllers supports SCSI data transfer rates of up to 320 MB.

The PERC 4/IM controller supports SCSI data transfer rates of up to 320 MB per second. Using the PERC 4/IM controller BIOS, you can create an integrated mirror. See "Integrated Mirroring and the PERC 4/IM Controller" for more information.

For more information about specific controller features, refer to the hardware manual that came with the controller.

The following features are available on 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.

Note Supported features may vary from controller to controller.
Note The PERC 4/IM controller provides integrated mirroring. The ability to create an integrated mirror with Array Manager is not supported. You can, however, create the integrated mirror using the controller BIOS. If you do so, the integrated mirror will be displayed as a virtual disk in the Array Manager console. See "Integrated Mirroring and the PERC 4/IM Controller" for more information.

Supported RAID Levels (PERC Subsystem 1)

This section applies to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers

The following table indicates the RAID levels supported by the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch Controllers. Refer to the "comments" column for information on how a controller implements a particular RAID level.

For information on controller features and virtual disks, see "Number of Array Disks per Virtual Disk" and "Maximum Virtual Disks per Controller."

Supported RAID Levels for PERC Subsystem 1 Controllers

Concatenation or RAID Level

Controllers

Comments

RAID-0

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

RAID-1

PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4/IM, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch

RAID-5

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

RAID 10

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, PERC 2, 2/Si, 3/Si, 3/Di, and CERC SATA1.5/6ch

RAID 50

PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di

RAID 50 support on the PERC 4/Di, 4e/Si, and 4e/Di controllers is implemented as striping across multiple RAID 5 volumes.

Cluster Support

This section applies to 3/DC, 4/DC, and 4e/DC controllers

Array Manager supports PERC 3/DC, 4/DC, and 4e/DC controllers that have Microsoft Cluster Server (MSCS) enabled.

Note Array Manager does not set resource ownership in a Microsoft Windows cluster configuration.
Note Dell does not provide cluster support on NetWare 6.x.

Updated Information

This section applies to 3/DC, 4/DC, and 4e/DC controllers

After a failover of cluster resources, it is necessary to perform a rescan operation in order for Array Manager to display the most up-to-date information about shared resources. You can specify that a rescan automatically be performed when the Array Manager console is launched by selecting the Rescan at startup check box on the Quick Access window.

If a failover occurs while the Array Manager console is displayed, you can perform a rescan by selecting Rescan from the View pull-down menu or using the Rescan button on the Array Manager toolbar.

Creating and Deleting Virtual Disks on Cluster-enabled Controllers

This section applies to 3/DC, 4/DC, and 4e/DC controllers

If you are using a PERC 3/DC, 4/DC, or 4e/DC controller in a cluster configuration, you must shut down and power off the other systems in the cluster before creating or deleting the virtual disk. The following procedure describes the sequence of actions required to create or delete a virtual disk from a cluster-enabled controller. For the purposes of this procedure, the system on which you are deleting the virtual disk is identified as "system A" and the other system in the cluster is identified as "system B."

  1. Stop the clustering services on system B.

  2. Shut down and power off system B.

  3. Create or delete the virtual disk on system A using the procedure described in the "To Create a Virtual Disk"section or the "Deleting Virtual Disks"section. If you are creating a virtual disk on a cluster-enabled controller, you should review the "Virtual Disk Considerations for PERC Subsystem 1 Controllers" section before continuing.

  4. Reboot system A.

  5. Restart system B.

Automatic Rescan

This section applies to 3/DC, 4/DC and 4e/DC controllers

There is a Rescan at startup check box at the bottom of the Quick Access window that is designed for use with cluster-enabled controllers. When the Rescan at startup check box is selected, Array Manager automatically performs a rescan when the Array Manager console is launched. It is recommended that this check box be selected on a system with a cluster-enabled PERC 3/DC, 4/DC, 4e/DC controller.

You can display the Quick Access Window by selecting Quick Access Window from the View pull-down menu.

Downloading Firmware and Cluster Controllers

This section applies to 3/DC, 4/DC, and 4e/DC controllers

When downloading firmware on a clustered controller, it is recommended that you shut down the other systems in the cluster first. When restarted, the other systems in the cluster should be able to see the firmware updates that you have applied.

If, however, you have downloaded firmware on a controller without first shutting down the other systems in the cluster, you may find that the other systems cannot see the firmware update until you restart the disk management service on those systems. For example, if you download firmware onto system A, and system B cannot see the firmware update, then restart the disk management service on system B.

Note If you downloaded firmware using an application other than Array Manager, rescan the controller to see the updated firmware version in the Array Manager console.

Integrated Mirroring and the PERC 4/IM Controller

This section applies to PERC 4/IM controller

The PERC 4/IM controller enables you to mirror a disk drive that resides internally in the server. This feature can be used to mirror a system's boot drive, ensuring that the system remains running in the event of a boot drive failure. The PERC 4/IM controller firmware maintains the mirrored data on both drives so that the system's CPU is not burdened with the extra processing required to maintain the mirrored data.

When implementing mirroring on a PERC 4/IM controller, you use the controller BIOS to create a virtual disk from hard disks. A hard disk is a physical disk that is directly visible to the operating system. Unlike creating a virtual disk on other controllers, the PERC 4/IM controller is able to implement a mirror for a hard disk that already contains data. The data is then copied to the mirror. Any data previously residing on the mirror is overwritten.

Once you have created the integrated mirror using the controller BIOS, the operating system sees the mirror as a virtual disk and a virtual disk object for the mirror is displayed in the Array Manager tree view. Expanding the virtual disks object displays the disks included in the mirror. These disks are now labeled "array disks" since they are part of a virtual disk and no longer individually visible to the operating system.

Background Initialization on PERC Subsystem 1 Controllers

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 a redundant virtual disk begins automatically within 0 to 5 minutes after the virtual disk is created. The background initialization of a redundant virtual disk prepares the virtual disk to maintain redundant data and improves write performance. For example, after the background initialization of a RAID 5 virtual disk completes, the parity information has been initialized. After the background initialization of a RAID 1 virtual disk completes, the array disks are mirrored.

The background initialization process helps the controller identify and correct problems that may occur with the redundant data at a later time. In this regard, the background initialization process is similar to a check consistency.

The background initialization should be allowed to run to completion. If cancelled, the background initialization will automatically restart within 0 to 5 minutes. Other processes such as read and write operations are possible while the background initialization is running. Other processes, such as creating a virtual disk, cannot be run concurrently with a background initialization. These processes cause the background initialization to cancel.

FlexRAID Virtual Sizing

This section applies to PERC 2/SC and 2/DC controllers

FlexRAID virtual sizing is a feature of PERC 2/SC and PERC 2/DC controllers. When enabled, the operating system sees your virtual disk as an arbitrarily large disk, typically 1024 GB, instead of its actual size. This lets you add and remove array disks of different sizes to your configuration without having to reboot the system.

Note This feature is not recommended for use on a Windows 2000 or Windows Server 2003 server.

This section on FlexRAID virtual sizing has the following topics:

Enabling FlexRAID Virtual Sizing

This section applies to PERC 2/SC and 2/DC controllers

This feature is specific to each virtual disk. You create the virtual disk first in Array Manager. Then you must exit Array Manager, reboot the system to bring up the PERC 2/SC or PERC 2/DC controller BIOS utility, and then enable virtual sizing on that virtual disk through a command in the utility.

To Enable FlexRAID Virtual Sizing
  1. After booting the system, when you see "PowerEdge Expandable RAID Controller" displayed in the BIOS, press Ctrl+M to enter the BIOS configuration utility.

  2. Select Objects.

  3. Select Logical Drives.

  4. Select any logical drive, such as Logical Drive 0. Logical drives and virtual disks are the same.

  5. Select View/Update Parameters.

  6. Go to FlexRAID Virtual Sizing = ... and select Enabled.

  7. Exit the BIOS configuration utility and reboot.

Retained FlexRAID Virtual Sizing Characteristics

This section applies to PERC 2/SC and 2/DC controllers

In Array Manager, if you delete a virtual disk with FlexRAID virtual sizing enabled and then create another virtual disk in its place, that disk will retain the deleted disk's FlexRAID virtual sizing characteristics. For example, if you just deleted six virtual disks with virtual sizing enabled on them and create eight new ones, you should still see virtual sizing on the first six of them, but not on the last two. To avoid having retained virtual sizing characteristics from deleted virtual disks, reboot before creating new virtual disks.

FlexRAID and Dynamic Volumes

This section applies to PERC 2/SC and 2/DC controllers

FlexRAID virtual sizing does not work with dynamic volumes. On Windows 2000, you will not be able to upgrade a basic disk to dynamic if FlexRAID virtual sizing is enabled. You do not need FlexRAID virtual sizing on a Windows 2000 machine because you can add storage and create and modify dynamic volumes without having to reboot.

Controller Rebuild Rate

This section applies to 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

During a rebuild, the complete contents of an array disk are reconstructed. The rebuild rate, configurable between 0% and 100%, represents the percentage of the system resources dedicated to rebuilding failed array disks. At 0%, the rebuild will have the lowest priority for the controller, will take the most time to complete, and will be the setting with the least impact to system performance. At 100%, the rebuild will be at the highest priority for the controller, will minimize the rebuild time, and will be the setting with the most impact to system performance.

The setting can be modified while a rebuild is already in progress.

Drive Status Changes

This section applies to 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

Because of hardware restrictions, 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 will not detect a drive status change until I/O is attempted. For example, when an unconfigured drive is removed, the controller will not detect the change until a manual rescan is done or other I/O operations are attempted.

S.M.A.R.T. Alerts

This section applies to 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

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 will not report S.M.A.R.T. alerts for unassigned or hot spare drives.

PERC Subsystem 1 Controller Issues

This section applies to 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

This section on controller issues covers the following topics:

Array Manager and PERC Console Compatibility Issues

This section applies to 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

Both Array Manager and PERC Console programs can be installed on the same server. However, only one program can be used to configure 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 at any given time. To maintain the integrity of storage device configuration, simultaneous use of Array Manager and PERC Console is not supported. It is strongly recommended that Array Manager and PERC Console not be used at the same time on the same server.


PERC Subsystem 2 Controllers

The following controllers are supported by the PERC subsystem 2:

Description of PERC Subsystem 2 Controllers

This section applies to PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

The PERC 2 RAID controller contains four channels. PERC 2/Si and PERC 3/Si are single integrated channel controllers. The PERC 3/Di is a dual integrated channel controller. The CERC SATA1.5/6ch and CERC SATA1.5/2s controllers are PCI RAID controllers with Serial Advanced Technology Attachment.

Supported RAID Levels (PERC Subsystem 2)

This section applies to PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

The PERC 2, PERC 2/Si, PERC 3/Si, and PERC 3/Di controllers support the following RAID levels:

The CERC SATA1.5/2s controller supports the following RAID levels:

For RAID support information on the CERC SATA/6ch controller, see RAID Support on the CERC SATA1.5/6ch.

For more information on storage concepts used in this section, see "What Is RAID?" and "Choosing RAID Levels and Concatenation."

For information on controller features and virtual disks, see "Number of Array Disks per Virtual Disk" and "Maximum Virtual Disks per Controller."

RAID Support on the CERC SATA1.5/6ch

The CERC SATA1.5/6ch controller supports the following RAID levels:

The CERC SATA1.5/6ch controller does not support a concatenated virtual disk using more than a single array disk or a RAID 1-concatenated virtual disk. If you have a virtual disk using an unsupported RAID level on this controller, you should do the following:

  1. Back up the virtual disk's data to tape.

  2. Delete the unsupported virtual disk.

  3. Create a virtual disk using a supported RAID level.

  4. Restore the data from backup.

Managing the Controller Battery

This section applies to PERC 2 and 3/Di controllers

The battery of the PERC 2 controller preserves the contents of its nonvolatile cache memory in the event of power loss. The battery provides a minimum of 72 hours protection for DIMMs up to 64 MB and 48 hours protection for 128-MB DIMMs. However, the duration of protection, or holdover time, depends on the battery's charge level. This section has two topics:

Note The PERC 2/Si and PERC 3/Si RAID controllers do not contain a battery and therefore do not support battery management.

Battery Recharging

This section applies to PERC 2 and 3/Di controllers

The battery is fully discharged when you first install the controller. The controller detects this condition and automatically begins charging the battery. This charging process takes approximately three hours. The controller can be used during this time; however, the battery is unable to meet the specified holdover time until it is fully charged. The battery is still able to handle brief power losses during the initial charge cycle.

Battery Reconditioning

This section applies to PERC 2 and 3/Di controllers

After you have installed the controller, it notifies you every six months that a battery reconditioning cycle is required. This reconditioning cycle requires a full discharge and recharge of the battery. It ensures that the battery's capacity is being measured correctly and that the battery's full holdover time is maintained.

To Recondition the Battery
  1. Right-click a controller.

  2. Click Properties.

  3. Click the Recondition button.

The reconditioning cycle takes approximately 8 to 10 hours. During this time, the battery's holdover time is reduced to zero (during discharge) and then restored (during full charge). To ensure that no data is lost from nonvolatile cache memory, the controller automatically disables cache (both read and write) during a reconditioning cycle. When the cache is disabled, performance is degraded for the reconditioning period. Once the reconditioning cycle is complete, the cache is restored to its original settings.

It is highly recommended that battery reconditioning be done during off-peak times.

Note On some servers, the PERC 3/Di controller has a lithium ion battery which does not require reconditioning. In this case, the Recondition button is inactive (greyed out). There are other situations that cause the Recondition button to be inactive. For example, if the battery is currently in a recondition cycle or is not installed or otherwise missing, the Recondition button is inactive.

Array Manager and FAST Compatibility Issues

This section applies to PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

Array Manager and FAST cannot both be installed on the same machine. If the Array Manager installation process detects that FAST is already installed, the Array Manager installation will not complete.


SCSI Subsystem Controllers

The following controllers are supported by the SCSI subsystem:

Description of SCSI Subsystem Controllers

This section applies to Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, and LSI 1030 controllers

The SCSI subsystem controllers are non-RAID controllers that support SCSI devices. Because these controllers are non-RAID, they do not support virtual disks. You can manage these non-RAID controllers and their attached SCSI devices with Array Manager.

The Ultra SCSI controllers supported by Array Manager are a high voltage differential (HVD) SCSI drop-in controller that fits in a PCI slot on the server or is embedded in the server. This controller can be used to attach HVD devices such as an HVD tape drive.

The Ultra2 SCSI and Ultra160 SCSI controllers are low voltage differential (LVD) drop-in controllers that fit in a PCI slot on the server or are embedded in the controller. These controllers can be used to attach external enclosures and other LVD SCSI devices.

The LSI 1020 and LSI 1030 controllers provide Ultra320 SCSI capability. The LSI 1020 is a PCI-X to Single Channel Ultra320 SCSI controller. The LSI 1030 is a PCI-X to Dual Channel Ultra320 SCSI controller.

Array Manager also supports RAID controllers on which you can create virtual disks. For information on these controllers, see the following:


Controller Menu Commands

This section applies to 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, 4/IM, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, CERC SATA1.5/2s, Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, and LSI 1030 controllers

The following sections describe pop-up menu commands for the PERC Subsystem 1, PERC Subsystem 2, and SCSI Subsystem controllers. For information on the PV660F controller commands, see "The Dell PowerVault 660F Storage System."

Right-click a controller in the Array Manager tree view to display its pop-up menu commands. Because the features for each controller can vary, your controller's pop-up menu may not display all of these commands.

Rescan Controller

This section applies to 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, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, CERC SATA1.5/2s, Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, and LSI 1030 controllers

The Rescan command scans the controller channels to verify the currently connected devices or to recognize new devices that have been added to the channels. When you do a rescan on a controller object, all channels or backplanes attached to the controller are rescanned. If you want to rescan only a single channel or backplane, then do the rescan on the channel or backplane object.

Use this command to display new objects in the Array Manager tree view and status changes.

The following are examples of common situations where you may need to rescan the controller:

To Rescan a Controller, Channel, or Backplane
  1. Right-click a controller, channel, or backplane.

  2. Click Rescan.

After the rescan is finished, the console is refreshed and any configuration changes appear under the Array Group object and under the channel or backplane object.

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, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

The removal of an array disk within a virtual disk is reflected immediately in the console, whereas adding an array disk to a virtual disk is reflected only by performing a rescan. Array disks that are not part of virtual disks will not be polled for status changes.

Note On 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, displaying a status change of a virtual disk or one of its member array disks requires that you do I/O on the controller on which the virtual disk resides.

Enable Alarm

This section applies to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/DC, 4e/DC, and CERC ATA100/4ch controllers

Use this function to enable the controller alarm setting. When enabled, the alarm sounds in the event of a device failure.

To Enable Alarm
  1. Right-click a controller.

  2. Click Enable Alarm.

Disable Alarm

This section applies to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/DC, 4e/DC, and CERC ATA100/4ch controllers

Use this function to disable the alarm. If disabled, the alarm does not sound in the event of a device failure.

To Disable Alarm
  1. Right-click a controller.

  2. Click Disable Alarm.

Quiet Alarm

This section applies to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/DC, 4e/DC, and CERC ATA100/4ch controllers

Use this function to quiet the alarm once it is sounding. Once quieted, the alarm is still enabled in the event of a future device failure.

To Quiet Alarm
  1. Right-click a controller.

  2. Click Quiet Alarm.

Rebuild Rate

This section applies to 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

Use this command to change the rebuild rate setting. The rebuild rate refers to how much of the system's resources are dedicated to rebuilding a failed array disk when a rebuild is necessary. A rebuild rate of 100% means that the system resources are completely dedicated to rebuilding the failed array disk. You can improve system performance during a rebuild by lowering the rebuild rate. This means that the rebuild will take longer to complete, however.

To Rebuild a Failed Array Disk
  1. Right-click a controller.

  2. Click Rebuild Rate. This action displays the Rebuild Rate dialog.

  3. Adjust the setting on the Rebuild Rate dialog as appropriate.

Initialize Array Disks

This section applies to PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

Use this function to initialize one or more array disks simultaneously. Array disks must be initialized before they can be used by Array Manager.

To Initialize Array Disks
  1. Right-click a controller.

  2. Click Initialize Array Disks.

  3. Click OK after selecting which array disks you want to initialize.

Export Log File

This section applies to PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, CERC ATA100/4ch, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

This command extracts a log from the controller(s) and places it in the Array Manager installation directory. When you export the log file from the controller, the controller's event information is cleared. The log gives detailed information on the controller activities and can be useful for troubleshooting. The log's file name is the word "log" and the month and day, such as "log0921" or "log_0921" for a log created on September 21.

To Export the Log File from the Controller
  1. Right-click a controller.

  2. Click Export Log File.

Note CERC SATA1.5/2s does not support the Export Log Files function on NetWare.

Controller Properties

This section applies to 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, 4/IM, PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, CERC SATA1.5/2s, Ultra SCSI, Ultra2 SCSI, Ultra160 SCSI, LSI 1020, and LSI 1030 controllers

To display the controller properties, do the following:

  1. Right-click the controller object in the Array Manager tree view.

  2. Select Properties from the pop-up menu.

The controller properties can vary depending on the model of the controller. Controller properties may include:

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, and CERC ATA100/4ch controllers

The battery has a recharge limit of 1100. Once this limit is reached, the battery status changes to Needs Replacement.

For PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers

Properties for each of the PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers appear differently. When a controller is opened in read-only mode, the console displays Read only in the name that appears in the left pane. If the controller is already in use, it can be opened only in read-only mode.

Note A PERC 2, 2/Si, 3/Si, 3/Di, CERC SATA1.5/6ch, or CERC SATA1.5/2s controller will be opened in Read Only mode if it is already in use.


Back to Contents Page