Users Guide

improve write performance. For example, after the background initialization of a RAID 5 virtual disk completes, the parity information

is initialized. After the background initialization of a RAID 1 virtual disk completes, the physical disks are mirrored.

The background initialization process helps the controller identify and correct problems that may occur with the redundant data later.

In this regard, the background initialization process is similar to a check consistency.

The background initialization should be allowed to run to completion. If canceled, the background initialization automatically restarts

within 0 to 5 minutes. Some processes such as read and write operations are possible while the background initialization is running.

However, other processes such as creating a virtual disk, cannot be run concurrently with background initialization. These processes

cause the background initialization to cancel.

Related links

Canceling Background Initialization

Setting Background Initialization Rate

Non-RAID Controller Description

The non-RAID SCSI and SAS controllers are non-RAID controllers that support SCSI and SAS devices. Because these controllers are

non-RAID, they do not support virtual disks. You can manage these non-RAID controllers and their attached SCSI and SAS devices

with Storage Management.

NOTE: Supported features may vary from controller to controller.

Non-RAID SCSI Controllers

The Broadcom PCIe U320 non-RAID controllers use Small Computer System Interface (SCSI) technology.

Non-RAID SAS Controllers

The following non-RAID controllers use Serial Attached SCSI (SAS) technology:

• SAS 6 Gbps Host Bus Adapter (HBA)

• Broadcom SAS 9207-8e

• Broadcom SAS 9300-8e

• Broadcom SAS 9206-16e

• SAS 12 Gbps HBA

• HBA 330

NOTE: Storage Management only enumerates and provides the PCI slot information for Broadcom SAS 9207-8e and SAS

9300-8e controllers. As Storage Management does not monitor these non-RAID controllers, devices connected to these

controllers are not enumerated, alerts are not logged, and SNMP traps are not sent for these controllers.

NOTE: In Storage Management, the Broadcom SAS HBA controller page display properties such as: ID, Status, Name,

Slot ID, State, Driver Version, Storport Driver Version, Number of Connectors, and Controller Tasks.

NOTE: When a backplane without an expander (passive backplane) is connected to an HBA 330 controller, the

enumeration of the physical disks is split between Connector 0 and Connector 1. For example, if the passive backplane is

populated with a maximum of eight physical disks, the rst four physical disks are listed under Connector 0 and the

remaining four physical disks are listed under Connector 1. You will be able to view all the eight physical disks only if both

bays are connected. If one bay is connected, only the physical disks associated with that bay are displayed.

NOTE: For SAS 12 Gbps HBA and HBA 330 controller, the Available Reports that can be viewed are View Slot Occupancy

Report and View Physical Disk Firmware Version Report.

NOTE: At times, the connector ID for SAS 12 Gbps HBA may not be displayed correctly on Storage Management. This

occurs because of a rmware limitation in the SAS 12 Gbps HBA. However, this connector ID discrepancy does not cause

any functional limitation.