Dell™ OpenManage™ Server Administrator Storage Management User's Guide Overview Getting Started Understanding RAID Concepts Quick Access to Storage Status and Tasks Storage Information and Global Tasks Setting Hot Spare Protection Policy Controllers RAID Controller Batteries Connectors Enclosures and Backplanes Physical Disks Virtual Disks Protecting Your Virtual Disk with a Hot Spare Alert Messages Command Line Interface Moving Physical and Virtual Disks from One System to Another BIOS Terminology Trouble
Back to Contents Page Supported Features Dell™ OpenManage™ Server Administrator Storage Management User's Guide Supported Features on the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4e/Si, 4e/Di, 4e/DC, CERC ATA100/4ch, and 4/IM Controllers Supported Features on the PERC 3/Si, 3/Di, CERC SATA1.5/2s, and CERC SATA1.
Import Foreign Configuration No No No No No No No No No No No No No No No No No No No No No No No No No Yes Yes Yes Yes Yes Yes No No Start Patrol Read No No No No No No No No No No No Stop Patrol Read No No No No No No No No No No No Import/Recover Foreign Configuration Set Patrol Read Mode NOTE: For PERC 4 controllers, (Manual mode is not available). Battery Tasks Table A-2.
Virtual Disk Tasks Table A-5.
Maximum Number of Physical Disks in a RAID 10 16 16 16 16 16 16 16 16 16 16 NA Maximum Number of Physical Disks in a RAID 50 256 256 256 256 256 256 256 256 256 NA NA Minimum Number of Physical Disks that Can Be Concatenated 2 2 2 2 2 2 2 2 2 2 NA Minimum Number of Physical Disks in a RAID 0 1 1 1 1 1 1 1 1 1 1 NA Minimum Number of Physical Disks in a RAID 1 2 2 2 2 2 2 2 2 2 2 2 Minimum Number of Physical Disks in a RAID 5 3 3 3 3 3 3 3 3
Direct I/O Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Enclosure Support Table A-9. Enclosure Support on the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4/Di, 4e/Si, 4e/Di, 4e/DC, CERC ATA100/4ch, and 4/IM Controllers Enclosure Support Can an enclosure be attached to this controller? PERC 3/SC PERC 3/DC PERC 3/QC PERC 4/SC PERC 4/DC PERC 4/DI Yes Yes Yes Yes Yes Yes PERC 4e/SI Yes PERC 4e/DI Yes PERC 4e/DC Yes CERC ATA 100/4ch No Supported Features on the PERC 3/Si, 3/Di, CERC SATA1.
Battery Tasks Table A-11. Battery Tasks Supported by the PERC 3/Si, 3/Di, CERC SATA1.5/2s, and CERC SATA1.5/6ch Controllers Battery Task Name PERC 3/Si PERC 3/Di CERC SATA 1.5/2s CERC SATA 1.5/6ch Recondition Battery Yes Yes No No Start Learn Cycle No No No No Delay Learn Cycle No No No No Connector Tasks Table A-12. Connector Tasks Supported by the PERC 3/Si, 3/Di, CERC SATA1.5/2s, and CERC SATA1.
Delete (any) Virtual Disk Yes Yes No Yes Check Consistency Yes Yes Yes Yes Cancel Check Consistency Yes Yes Yes Yes Pause Check Consistency Yes Yes No Yes Resume Check Consistency Yes Yes No Yes Cancel Background Initialization (BGI) No No No No Format Virtual Disk Yes Yes No Yes Cancel Format Virtual Disk No No No No Restore Dead Disk Segments Yes Yes No Yes Initialize Virtual Disk No No No No Fast Initialize Virtual Disk No No No No Slow Initialize Vi
RAID 6 No No No No RAID 60 No No No No Read, Write, and Disk Cache Policy Table A-17. Read, Write, and Cache Policy Supported by the PERC 3/Si, 3/Di, CERC SATA1.5/2s, and CERC SATA1.
Table A-19.
Physical Disk Tasks Table A-22.
Table A-24.
Write Policy Yes Yes Yes Yes Yes Yes Write Back (Enabled) Yes Yes Yes Yes Yes Yes Write Through (Disabled) Yes Yes Yes Yes Yes Yes Force Write Back (Enabled Always) Yes Yes Yes Yes Yes Yes Write Cache Enabled Protected No No No No No No Cache Policy No No No No No No Disk Cache Policy Yes Yes Yes Yes Yes No Cache I/O No No No No No No Direct I/O No No No No No No Enclosure Support Table A-27.
Import Foreign Configuration No No Import/Recover Foreign Configuration No No Set Patrol Read Mode No No Start Patrol Read No No Stop Patrol Read No No Battery Tasks Table A-29. Battery Tasks Supported on the SAS 5/iR and SAS 6/iR Controller Battery Task Name SAS 5/iR SAS 6/iR Recondition Battery No No Start Learn Cycle No No Delay Learn Cycle No No Connector Tasks Table A-30.
Create Virtual Disk No Yes Create Virtual Disk Advanced Wizard No Yes Create Virtual Disk Express Wizard No No Rename No No Blink/Unblink Yes Yes Reconfigure No No Change Policy No No Split Mirror No No Unmirror No No Delete Last Virtual Disk No Yes Delete (any) Virtual Disk No Yes Check Consistency No No Cancel Check Consistency No No Pause Check Consistency No No Resume Check Consistency No No Cancel Background Initialization (BGI) No No Format Virtual Disk
Minimum Number of Physical Disks in a RAID 10 NA NA Minimum Number of Physical Disks in a RAID 50 NA NA Maximum number of physical disks in a RAID 6 NA NA Maximum number of physical disks in a RAID 60 NA NA Minimum number of physical disks in a RAID 6 NA NA Minimum number of physical disks in a RAID 60 NA NA Read, Write, Cache and Disk Cache Policy Table A-35.
Table A-37.
Cancel Clear No No Virtual Disk Tasks Table A-41.
l "Supported Features on the SAS 5/iR and SAS 6/iR Controllers" l "Supported Features on the Non-RAID Controllers" Enclosure and Backplane Tasks Table A-43.
Back to Contents Page Determining the Health Status for Storage Components Dell™ OpenManage™ Server Administrator Storage Management User's Guide Health Status Rollup: Battery is Charging or Dead Health Status Rollup: Enclosure Power Supply Failed or Power Connection Removed Health Status Rollup: Physical Disks in a Virtual Disk are Failed or Removed Health Status Rollup: One Enclosure Fan is Failed Health Status Rollup: Physical Disks in a Virtual Disk are Unsupported, Partially or Permanently Degrade
Storage Subsystem Controller Battery Connector Physical Disk(s) Firmware/ Virtual Disk(s) Driver Component Status Health Rollup Health Status Rollup: All Physical Disks in a Virtual Disk are in Foreign State Table B-4.
Health Rollup Health Status Rollup: Unsupported Firmware Version Table B-8. Health Status Rollup: Unsupported Firmware Version (Enclosures Not Included) Storage Subsystem Controller Battery Connector Physical Disk(s) Firmware/Driver Virtual Disk(s) Component Status Health Rollup Health Status Rollup: Enclosure Power Supply Failed or Power Connection Removed Table B-9.
Table B-12. Health Status Rollup: One Enclosure Temperature Probe is Failed Storage Subsystem Controller Connector Enclosure Enclosure Temperature Probe Virtual Disks Physical Disks Component Status Health Rollup NA Health Status Rollup: Lost Both Power Connections to the Enclosure Table B-13.
Back to Contents Page Physical Disks Dell™ OpenManage™ Server Administrator Storage Management User's Guide Add a New Disk to Your System How to Avoid Removing the Wrong Disk Replacing a Physical Disk Receiving SMART Alerts Other Disk Procedures Physical Disk Properties and Tasks Assign and Unassign Global Hot Spare Online and Offline Clear Physical Disk and Cancel Clear Revertible Hot Spare Physical disks reside within an enclosure or are attached to the controller.
Replacing a Physical Disk Receiving SMART Alerts SMART alerts are messages predicting that a disk may fail in the near future. If a physical disk is receiving SMART alerts, you should replace the disk. Use the following procedures to replace a disk receiving SMART alerts. If the disk is part of a redundant virtual disk: 1. Select the redundant virtual disk that includes the physical disk that is receiving SMART alerts and perform the Check Consistency task. See "Check Consistency" for more information.
The following table describes properties that may be displayed for physical disks depending on the controller. Property Status Definition These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal See "Storage Component Severity" for more information. Name This property displays the name of the physical disk. The name is comprised of the connector number followed by the disk number.
"2094" "2106" "2107" "2108" "2109" "2110" "2111" Progress This property displays how close to completion an operation is that is being performed on the physical disk. For example, if the physical disk is being rebuilt, then a value of 52% indicates that the rebuild is 52% complete. This property is only displayed when an operation is being performed on the physical disk. Bus Protocol This property displays the technology that the physical disk is using.
NOTE: Different controllers support different features. For this reason, the tasks displayed on the Tasks drop-down menu can vary depending on which controller is selected in the tree view. If no tasks can be performed because of controller or system configuration limitations, then the Tasks drop-down menu displays No Task Available.
This task causes the lights on the disk to blink. You can safely remove the disk under the following conditions: l Wait for about 30 seconds to allow the disk to spin down. l Wait until you notice the initial blink pattern has changed into a different pattern or the lights have stopped blinking. A physical disk is no longer in Ready state after doing a Prepare to Remove.
Does my controller support this feature? See "Supported Features." A global hot spare is an unused backup disk that is part of the disk group. Hot spares remain in standby mode. When a physical disk that is used in a virtual disk fails, the assigned hot spare is activated to replace the failed physical disk without interrupting the system or requiring your intervention. When a hot spare is activated, it rebuilds the data for all redundant virtual disks that were using the failed physical disk.
5. Select the Physical Disks object. 6. Select Online or Offline from the Available Tasks drop-down menu of the physical disk you want to make online or offline. 7. Click Execute. Clear Physical Disk and Cancel Clear Does my controller support this feature? See "Supported Features." Use the clear physical disk task to erase data residing on a physical disk. The Clear task applies to physical disks that are in Ready state and that contain data or that are in Clear state.
To enable Revertible Hot Spare: 1. On the Change Controller Properties page, enable Revertible Hot Spare and Auto replace on predictive failure. 2. Click Apply Changes. To locate this task in Storage Management: 1. Expand the Storage tree object to display the controller objects. 2. Select a controller object on which you want to enable the revertible hot spare task and select the Information/Configuration tab. 3.
Back to Contents Page RAID Controller Batteries Dell™ OpenManage™ Server Administrator Storage Management User's Guide Battery Properties and Tasks Some RAID controllers have batteries. If the controller has a battery, Storage Management displays the battery under the controller object in the tree view. In the event of a power outage, the controller battery preserves data that is in the nonvolatile cache memory (NVRAM) but not yet written to disk.
Property Status Definition These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal See "Storage Component Severity" for more information. Name This property displays the name of the battery. State This property displays the current status of the battery. Possible values are: Ready — The battery is functioning normally. Degraded — The battery needs to be reconditioned. Reconditioning — The battery is being reconditioned.
Do the following to execute a drop-down menu battery task: 1. Expand the Storage tree object to display the controller objects. 2. Expand a controller object. 3. Select the Battery object. 4. Select a task from the Available Tasks drop-down menu. 5. Click Execute. Drop-down Menu Battery Tasks: l "Recondition Battery" l "Start Learn Cycle" l "Battery Delay Learn Cycle" Recondition Battery Does my controller support this feature? See "Supported Features.
The battery Learn cycle discharges and then fully charges the controller battery. The Learn cycle recalibrates the battery integrated circuit so that the controller can determine whether the battery can maintain the controller cache for the prescribed period of time in the event of a power loss. For example, some controller batteries are required to maintain the controller cache for 72 hours. While the Learn cycle is in progress, the battery may not be able to maintain the cache during a power loss.
Back to Contents Page BIOS Terminology Dell™ OpenManage™ Server Administrator Storage Management User's Guide BIOS Terms and the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch Controllers BIOS Terms and the PERC 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s Controllers The terminology used by Storage Management can be different from the terminology used in the controller BIOS. The following sections show some of these differences.
Back to Contents Page Connectors Dell™ OpenManage™ Server Administrator Storage Management User's Guide Channel Redundancy and Thermal Shutdown Channel Redundancy on PERC 3/DC, 3/QC, 4/DC, 4e/DC, 4/Di, and 4e/Di Controllers Creating a Channel-redundant Virtual Disk Connector Health Connector Properties and Tasks Logical Connector Properties and Tasks A controller contains one or more connectors (channels or ports) to which you can attach disks.
NOTE: Channel redundancy only applies to controllers that have more than one channel and that attach to an external disk enclosure. 1. Launch the Create Virtual Disk Advanced Wizard by doing the following: a. 2. Locate the controller on which you are creating a channel-redundant virtual disk Expand the controller object until the Virtual Disks object is displayed. b. Select the Virtual Disks object and click Go To Create Virtual Disk Wizard. c. Click Virtual Disk Advanced Wizard.
c. d. Repeat "step b" until you have selected the desired number of disks. You must select the same number of physical disks on each channel that you use. Click Continue. Connector Health This screen displays the status of the connector and the components attached to the connector. Connector Status Component status is indicated by the severity. A component with a Warning or Critical/Failure status requires immediate attention to avoid data loss if possible.
Property Definition These icons represent the severity or health of the storage component. See "Storage Component Severity" for more information. A Warning or Critical severity may indicate that the connector is unable to communicate with attached devices such as an enclosure. Check the status of attached devices. See "Cables Attached Correctly" and "Isolate Hardware Problems" for more information. Name This property displays the connector number.
Logical Connector Properties and Tasks Use this window to view information about the logical connector (connector in redundant path mode) and to execute connector tasks. Logical Connector Properties The connector properties can vary depending on the model of the controller. Connector properties may include: Property Definition These icons represent the severity or health of the storage component. See "Storage Component Severity" for more information.
l "Enclosure and Backplane Properties and Tasks" Back to Contents Page
Back to Contents Page Command Line Interface Dell™ OpenManage™ Server Administrator Storage Management User's Guide CLI Command Syntax Syntax for Required, Optional, and Variable Command Elements User Privileges for omreport storage and omconfig storage omreport Command omconfig Virtual Disk Commands omconfig Physical Disk Commands omconfig Battery Commands omconfig Connector Commands omconfig Global Commands omconfig Enclosure Commands omconfig Controller Commands Storage Management has a fully-featu
omconfig name=value Pairs Following the command levels, the omreport and omconfig command syntax may require one or more name=value pairs. The name=value pairs specify exact objects (such as a specific physical disk) or options (such as blink or unblink) that the command will implement.
omconfig storage pdisk action=blink controller=1 pdisk=2:1 enclosure= Parameter The omconfig syntax for specifying an enclosure includes the enclosure= parameter followed by the variable. How you specify the variable depends on whether the controller is using SCSI, SATA, ATA, or SAS technology. enclosure= Parameter on SAS Controllers On a SAS controller, the enclosure= parameter is specified as follows.
omconfig storage pdisk action=blink controller=1 pdisk=2:3:1,2:3:2, 2:3:3 See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses. Syntax for Required, Optional, and Variable Command Elements The omreport and omconfig commands have multiple name=value pairs. These name=value pairs may include required, optional, and variable parameters. The following table describes the syntax used to indicate these parameters.
omreport Storage Help Table 17-2. omreport Storage Help Commands Required Command Levels (1, 2, 3) Use omreport storage -? Displays a list of storage components for which omreport commands are available. omreport storage pdisk -? Displays a list of the omreport storage pdisk parameters for displaying physical disk information. See "omreport Physical Disk Status" for more information.
omreport Connector Status Table 17-6. omreport Connector Commands Required Command Levels (1, 2, 3) and name=value Pair omreport storage connector controller=id Use Displays all connectors on the specified controller. where id is the controller number. For example: controller=0 omreport storage connector controller=id connector=id where id is the controller number. For example: controller=0 Displays information for the specified connector on the controller.
information on specifying enclosures. where id is the controller number and is the enclosure ID. Example for SCSI controllers: controller=0 enclosure=2 info=fans. Example for SAS controllers: controller=0 enclosure=1:2 info=fans. controller=id enclosure= info=fans index=n where id is the controller number and is the enclosure ID and n is the number of a fan. Example for SCSI controllers: controller=0 enclosure=2 info=fans index=1.
displayed as Replacing. See "Revertible Hot Spare" for more information. connector=id Displays all physical disks attached to the specified connector on the controller. where id is the connector number. For example: connector=1 vdisk=id Displays all physical disks included in the specified virtual disk on the controller. where id is the virtual disk number. For example: vdisk=1 pdisk=connector:targetID Displays the specified physical disk on the specified connector on a SCSI, SATA, or ATA controller.
Shutdown" for more information. Use the following omconfig command syntax to enable smart thermal shutdown. Complete Syntax omconfig storage globalinfo action=enablests Example Syntax The omconfig command syntax for enabling thermal shutdown does not require that you specify a controller or enclosure ID.
Use the following omconfig command syntax to rescan all controllers on the system. See "Rescan Controller" and "Rescan to Update Storage Configuration Changes" for more information about using this command. Complete Syntax omconfig storage globalinfo action=globalrescan Example Syntax The omconfig command syntax for rescanning all controllers on the system does not require that you specify a controller ID.
To set the Dedicated Hot Spare Protection Policy for RAID 10 with severity level=warning if the threshold level of 2 hot spares is exceeded, enter the following: omconfig storage globalinfo action= setprotectionpolicies type=dhs raid=r1 hscount=2 warnlevel=2 omconfig Controller Commands The following sections provide the omconfig command syntax required to execute controller tasks. Table 17-15.
omconfig storage vdisk action=replacememberdisk controller=id vdisk=id source= destination= "omconfig Storage Virtual Disk" omconfig Rescan Controller Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to rescan a controller. See "Rescan Controller" and "Rescan to Update Storage Configuration Changes" for more information about using this command.
omconfig Disable Controller Alarm Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to disable the controller alarm. See "Disable Alarm (Controller)" for more information. Complete Syntax omconfig storage controller action=disablealarm controller=id where id is the controller ID as reported by the omreport storage controller command.
(Controller)" for more information. Complete Syntax omconfig storage controller action=testalarm controller=id where id is the controller ID as reported by the omreport storage controller command. Example Syntax For example, to test the alarm on controller 1, you would enter: omconfig storage controller action=testalarm controller=1 omconfig Reset Controller Configuration Does my controller support this feature? See "Supported Features.
Does my controller support this feature? See "Supported Features." Before creating a virtual disk, you should be familiar with the information in "Considerations Before Creating Virtual Disks." The omconfig syntax for creating a virtual disk has several parameters.
Specify the controller ID as reported by the omreport storage controller command. For example: controller=2 raid= Parameter (Required) Use the raid= parameter to specify concatenation or a RAID level for a virtual disk. Different controllers support different RAID levels. See "Controller-supported RAID Levels" for information on which RAID levels a controller supports.
[stripesize=< 2kb| 4kb| 8kb| 16kb| 32kb| 64kb| 128kb>] Parameter (Optional) Different controllers support different stripe sizes. See "Controller-supported Stripe Sizes" for information on which stripe sizes are supported for a controller. All stripe sizes are specified in kilobytes. For example, when specifying 128KB as the stripe size, you would enter: stripesize=128kb [cachepolicy=] Parameter (Optional) Different controllers support different cache policies.
No write cache writepolicy=nwc Force write back writepolicy=fwb [name=] Parameter (Optional) Use this parameter to specify a name for the virtual disk. For example: name=VirtualDisk1 NOTE: The CERC SATA1.5/2s controller does not allow you to specify a virtual disk name. The virtual disk will be created with a default name.
See "pdisk= Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Example Syntax For example, to set the background initialization rate on controller 1 to 50, you would enter: omconfig storage controller action=setbgirate controller=1 rate=50 omconfig Set Reconstruct Rate Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to set the reconstruct rate. See "Set Reconstruct Rate" for more information.
omconfig storage controller action= setcheckconsistency controller=1 rate=50 omconfig Export the Controller Log Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to export the controller log to a text file. For more information about the exported log file, see "Export Log." Complete Syntax omconfig storage controller action=exportlog controller=id where id is the controller ID as reported by the omreport storage controller command.
omconfig storage controller action= importforeignconfig controller=1 omconfig Import/Recover Foreign Configuration Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to import and recover all virtual disks that reside on physical disks newly attached to the controller. See "Foreign Configuration Operations" for more information.
omconfig Set Patrol Read Mode Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to set the patrol read mode for the controller. See "Set Patrol Read Mode" for more information. Complete Syntax omconfig storage controller action=setpatrolreadmode controller=id mode=manual|auto|disable where id is the controller ID as reported by the omreport storage controller command.
Use the following omconfig command syntax to stop the patrol read task on the controller. See "Start and Stop Patrol Read" for more information. Complete Syntax omconfig storage controller action=stoppatrolread controller=id where id is the controller ID as reported by the omreport storage controller command.
where PDISKID is specified as either: pdisk=connector:enclosureID:portID Example Syntax For example, to replace physical disk (PD1) with another physical disk (PD2), you would enter: omconfig storage vdisk action=replacememberdisk controller=0 vdisk=1 source=PD1 destination=PD2 omconfig Storage Controller Does my controller support this feature? See "Supported Features." Use the following omconfig storage command syntax to discard the preserved cache on the controller.
action=cancelcheckconsistency controller=id vdisk=id "omconfig Cancel Check Consistency" action=pausecheckconsistency controller=id vdisk=id "omconfig Pause Check Consistency" action=resumecheckconsistency controller=id vdisk=id "omconfig Resume Check Consistency" action=blink controller=id vdisk=id "omconfig Blink Virtual Disk" action=unblink controller=id vdisk=id "omconfig Unblink Virtual Disk" action=initialize controller=id vdisk=id "omconfig Initialize Virtual Disk" action=fastinit control
Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to unblink the physical disks included in a virtual disk. Complete Syntax omconfig storage vdisk action=unblink controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command.
Complete Syntax omconfig storage vdisk action=fastinit controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
For example, to restore segments on virtual disk 4 on controller 1, you would enter: omconfig storage vdisk action=restoresegments controller=1 vdisk=4 omconfig Split Mirror Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to separate mirrored data originally configured as a RAID 1, RAID 1-concatenated, or RAID 10 virtual disk. Splitting a RAID 1 or RAID 1-concatenated mirror creates two concatenated nonredundant virtual disks.
omconfig storage vdisk action=unmirror controller=1 vdisk=4 omconfig Assign Dedicated Hot Spare Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to assign one or more physical disks to a virtual disk as a dedicated hot spare. For more information on hot spares including size requirements, see "Protecting Your Virtual Disk with a Hot Spare.
omconfig Unassign Dedicated Hot Spare Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to unassign one or more physical disks that were previously assigned as a hot spare to a virtual disk. Complete Syntax omconfig storage vdisk action=assigndedicatedhotspare controller=id vdisk=id pdisk= assign=no where id is the controller ID and virtual disk ID. The variable specifies the physical disk.
Use the following omconfig command syntax to initiate a check consistency on a virtual disk. The check consistency task verifies the virtual disk's redundant data. Complete Syntax omconfig storage vdisk action=checkconsistency controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command.
omconfig storage vdisk action=pausecheckconsistency controller=id vdisk=id where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller.
where id is the controller ID and virtual disk ID as reported by the omreport command. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage vdisk controller=ID to display the IDs for the virtual disks attached to the controller. In some circumstances, you may receive a warning message if you attempt to delete a virtual disk containing the system or boot partition. You can override this warning by using the [force=yes] parameter.
omconfig storage vdisk action=reconfigure controller= id vdisk=id raid= size= pdisk= See "Parameter Specification for Create and Reconfigure Virtual Disk" for information on specifying the parameters. See "pdisk= Parameter" and "Multiple Targets" for more information on specifying physical disks. Example Syntax For example, you want to reconfigure virtual disk 4 to a size of 800MB.
information on how to specify these parameters using the omconfig command, see the following: l "[readpolicy=] Parameter (Optional)" l "[writepolicy=] Parameter (Optional)" l "[cachepolicy=] Parameter (Optional)" l "[diskcachepolicy=] Parameter (Optional)" Example Syntax For example, to change the read policy of virtual disk 4 on controller 1 to no-read-ahead, you would enter: omconfig storage vdisk action=changepolicy controller=1 v
action=remove controller=id pdisk= "omconfig Prepare to Remove Physical Disk" action=initialize controller=id pdisk= "omconfig Initialize Physical Disk" action=offline controller=id pdisk= "omconfig Offline Physical Disk" action=online controller=id pdisk= "omconfig Online Physical Disk" action=assignglobalhotspare controller=id pdisk= assign= "omconfig Assign Global Hot Spare" and "omconfig Unassign Global Hot Spare" action=rebuild controller=i
To blink the physical disk described in this example, you would enter: omconfig storage pdisk action=blink controller=1 pdisk=0:2:2 See "pdisk= Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology. omconfig Unblink Physical Disk Does my controller support this feature? See "Supported Features.
omconfig Prepare to Remove Physical Disk Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to prepare a physical disk for removal. See "Prepare to Remove" for more information. Complete Syntax omconfig storage pdisk action=remove controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. See "pdisk= Parameter" for more information.
Complete Syntax omconfig storage pdisk action=initialize controller= id pdisk= where id is the controller ID. The variable specifies the physical disk. See "pdisk= Parameter" for more information. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller. Example Syntax In this example, you want to offline physical disk 3 on connector 0 of controller 1. On a SAS controller, the physical disk resides in enclosure 2.
Example for SCSI, SATA, and ATA Controllers: To online the physical disk described in this example, you would enter: omconfig storage pdisk action=online controller=1 pdisk=0:3 See "pdisk= Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
To assign the physical disk described in this example as a global hot spare, you would enter: omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:3 assign=yes See "pdisk= Parameter on SCSI, SATA, and ATA Controllers" and "Multiple Targets" for more information on physical disk specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
Example for SAS Controllers: To unassign the physical disk described in this example as a global hot spare, you would enter: omconfig storage pdisk action=assignglobalhotspare controller=1 pdisk=0:2:3 assign=no See "pdisk= Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology.
See "pdisk= Parameter on SAS Controllers" and "Multiple Targets" for more information on physical disk specification. See "SAS RAID Controllers" to identify which controllers use SAS technology. omconfig Cancel Rebuild Physical Disk Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to cancel a rebuild that is in progress. If you cancel a rebuild, the virtual disk remains in a degraded state. For more information, see "Cancel Rebuild.
Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to recover unusable disk space. See "Remove Dead Segments" for more information. Complete Syntax omconfig storage pdisk action=removedeadsegments controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. See "pdisk= Parameter" for more information.
omconfig storage pdisk action=clear controller=id pdisk= where id is the controller ID. The variable specifies the physical disk. See "pdisk= Parameter" for more information. To obtain these values, you would enter omreport storage controller to display the controller IDs and then enter omreport storage pdisk controller=ID to display the IDs for the physical disks attached to the controller.
Does my controller support this feature? See "Supported Features." Use the following omconfig command syntax to cancel a replace member operation. Complete Syntax action=cancelreplacemember controller=id pdisk= where id is the physical disk IDs as reported by the omreport command.
For example, to recondition battery 0 on controller 1, you would enter: omconfig storage battery action=recondition controller=1 battery=0 omconfig Start Battery Learn Cycle Does my controller support this feature? See "Supported Features." Use the following omconfig command to start the battery learn cycle. Complete Syntax omconfig storage battery action=startlearn controller=id battery=id where id is the controller ID and battery ID as reported by the omreport command.
omconfig storage battery action=delaylearn controller=1 battery=0 days=3 hours=12 omconfig Connector Commands The following sections provide the omconfig command syntax required to execute connector tasks. Table 17-19.
action=settempprobes controller=id enclosure= index=id minwarn=n maxwarn=n action=resettempprobes controller=id enclosure= index=id action=setalltempprobes controller=id enclosure= minwarn=n maxwarn=n action=resetalltempprobes controller=id enclosure= action=blink controller=id enclosure= "omconfig Set Temperature Probe Thresholds" "omconfig Reset Temperature Probe Thresholds" "omconfig Set All Temperature Probe Thresholds" "omconfig Reset Al
Complete Syntax omconfig storage enclosure action=disablealarm controller=id enclosure= where id is the controller ID. The variable specifies the enclosure. See "enclosure= Parameter" for more information.
omconfig storage enclosure action=setassettag controller=1 enclosure=2 assettag=encl20 See "enclosure= Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses.
See "enclosure= Parameter on SAS Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses. omconfig Set Temperature Probe Thresholds Does my enclosure support this feature? See "Supported Features." Use the following omconfig command syntax to set the minimum and maximum warning temperature thresholds for a specified temperature probe.
omconfig storage enclosure action=resettempprobes controller=1 enclosure=2 index=3 See "enclosure= Parameter on SCSI, SATA, and ATA Controllers" for more information on enclosure specification. See "RAID Controller Technology: SCSI, SATA, ATA, and SAS" to identify which technology a controller uses. omconfig Set All Temperature Probe Thresholds Does my enclosure support this feature? See "Supported Features.
For example, you may want to reset the thresholds for all temperature probes in enclosure 2 on controller 1. Example for SAS Controllers: In this example, the temperature probes reside in enclosure 3 attached to connector 0 on controller 1. To reset the thresholds for all temperature probes, you would enter: omconfig storage enclosure action=resetalltempprobes controller=1 enclosure=0:3 See "enclosure= Parameter on SAS Controllers" for more information on enclosure specification.
Back to Contents Page Controllers Dell™ OpenManage™ Server Administrator Storage Management User's Guide What is a Controller? RAID Controller Technology: SCSI, SATA, ATA, and SAS RAID Controller Features Controller-supported RAID Levels Controller-supported Stripe Sizes RAID Controller Read, Write, Cache, and Disk Cache Policy Cluster-enabled RAID Controllers Creating and Deleting Virtual Disks on Cluster-enabled Controllers Integrated Mirroring and the PERC 4/IM Controller Background Initialization on PE
CERC SATA RAID Controllers The following Cost Effective RAID Controller (CERC) controllers use Serial Advanced Technology Attachment (SATA) technology. l CERC SATA1.5/6ch l CERC SATA1.5/2s CERC ATA RAID Controllers The following Cost Effective RAID Controller (CERC) controllers use Advanced Technology Attachment (ATA) technology. l CERC ATA100/4ch l CERC 6/I controller family SAS RAID Controllers The following RAID controllers use Serial Attached SCSI (SAS) technology.
information. l Disk migration or foreign configurations. Some controllers enable you to move physical disks that contain one or more virtual disks to another controller. The receiving controller is able to recognize and import the foreign configuration (virtual disks). See "Foreign Configuration Operations" for more information. Controller-supported RAID Levels RAID controllers may support different RAID levels.
NOTE: Storage Management does not allow you to select the Write-Back policy for controllers that do not have a battery. This restriction protects a controller without a battery from the data loss that may occur in the event of a power failure. On some controllers, the Write-Back policy may be available in the controller BIOS even though it is not available in Storage Management. l Force Write Back.
This section applies to 3/DC, 4/DC, and 4e/DC controllers Storage Management supports PERC 3/DC, 4/DC, and 4e/DC controllers that have Microsoft Cluster Server (MSCS) enabled. A cluster refers to two or more servers that are connected so that their resources can be shared and accessed as if the clustered servers were a single machine.
Integrated Mirroring and the PERC 4/IM Controller The PERC 4/IM controller enables you to mirror a physical disk that resides internally in the server. This feature can be used to mirror the system's boot drive from one physical disk to another, ensuring that the system remains running in the event that one of the physical disks fails.
Firmware/Driver Versions Use this window to view information about the controller firmware and drivers. For more information on firmware and drivers, see "Installation Considerations for Storage Management." Firmware/Driver Properties The firmware and driver properties can vary depending on the model of the controller. On some controllers, Storage Management may not be able to obtain the driver or firmware version. In this case, Storage Management displays Not Applicable.
Critical/Failure/Error. The component has either failed or failure is imminent. The component requires immediate attention and may need to be replaced. Data loss may have occurred.
Firmware Version This property displays the version of the firmware that is currently installed on the controller. NOTE: On some controllers, Storage Management may not be able to obtain the firmware version. In this case, Storage Management displays Not Applicable. Minimum Required Firmware Version This property displays the minimum firmware version that is required by Storage Management. This property is only displayed if the controller firmware does not meet the minimum requirement.
In cluster mode, the value is 6 or 7. The SCSI ID is not displayed on the PERC 4/IM, PERC 3/Si, and 3/Di controllers. Use the BIOS on these controllers to identify the SCSI ID. Controller Tasks Enables you to configure and manage the controller. For more information, see "Controller Tasks:." Controller Tasks Do the following to execute a controller task: 1. Expand the Storage tree object to display the controller objects. 2. Select a controller object. 3. Select the Information/Configuration subtab.
To rescan a controller: 1. Expand the tree view to display the controller object. 2. Select the Controller object. 3. Click the Configuration/Information subtab. 4. Select Rescan from the Controller Tasks drop-down menu. 5. Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see "Change Controller Properties.
Does my controller support this feature? See "Supported Features." Use the Set Rebuild Rate task to change the rebuild rate. See "Set Rebuild Rate" for more information. Export Log File Does my controller support this feature? See "Supported Features." Use this task to export the controller log to a text file. See "Export Log" for more information.
l Full Initialization (A BIOS setting determines whether a full or fast initialization occurs. See "Format and Initialize; Slow and Fast Initialize.") l Reconfigure (see "Virtual Disk Task: Reconfigure (Step 1 of 3)") To change the controller's rebuild rate: 1. Type a numerical value in the New Rebuild Rate text box. The value must be within the 0 – 100 range. 2. Click Apply Changes. If you want to exit and cancel your changes, click Go Back to Previous Page.
Export Log Does my controller support this feature? See "Supported Features." The Export Log task exports the controller log to a text file. The log gives detailed information on the controller activities and can be useful for troubleshooting. On a Microsoft® Windows® system, the log file is exported to the windows or winnt directory. On a Linux system, the log file is exported to the /var/log directory. Depending on the controller, the log file name will be either afa_.log or lsi_.
The following table describes the properties that are displayed for the Foreign Disks and Global Hot Spares. Property Status Definition These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal See "Storage Component Severity" for more information. Name State This property displays the name of the foreign configuration and is available as a link. The link enables you to access the physical disks that constitute the foreign disk.
4. Select Foreign Configuration Operations from the Controller Available Tasks drop-down menu. 5. Click Execute. Importing Foreign Configurations Some controllers enable you to import a foreign configuration so that virtual disks are not lost after moving the physical disks. To be imported, the foreign configuration must contain a virtual disk that is in either Ready or Degraded state.
3. Select the Information/Configuration subtab. 4. Select Foreign Configuration Operations from the Controller Available Tasks drop-down menu. 5. Click Execute. 6. On the Foreign Configuration Preview page, click Import/Recover. For controllers with firmware version 6.0 and earlier: 1. Expand the Storage tree object to display the controller objects. 2. Select a controller object. 3. Select the Information/Configuration subtab. 4.
3. Select the Information/Configuration subtab. 4. Select Clear Foreign Configuration from the Controller tasks. Related Information: l "Foreign Configuration Operations" l "Importing Foreign Configurations" l "Importing/Recovering Foreign Configurations" Physical Disks in Foreign Virtual Disks The Physical Disks in Foreign Virtual Disks page displays the physical disks and the dedicated hot spare, if any, included in the foreign configuration.
Progress This property displays the progress of an operation being performed on the physical disk. For example, if the physical disk is being rebuilt, then a value of 52% indicates that the rebuild is 52% complete. This property is only displayed when an operation is being performed on the physical disk. Bus Protocol This property displays the technology that the physical disk is using.
At 100%, the background initialization will be the highest priority for the controller, will minimize the background initialization time, and will be the setting with the most impact to system performance. To change the controller's background initialization rate: 1. Type a numerical value in the New Background Initialization Rate text box. The value must be within the 0 – 100 range. 2. Click Apply Changes. If you want to exit and cancel your changes, click Go Back to Previous Page.
l "Check Consistency" l "Cancel Check Consistency" Set Reconstruct Rate Does my controller support this feature? See "Supported Features." The Set Reconstruct Rate task changes the amount of system resources dedicated to the reconstruct task. The reconstruct task remakes the virtual disk after you have changed the RAID level or otherwise reconfigured the virtual disk.
In a daisy chain scenario where more than one enclosure is connected to a controller in a redundant path mode, Storage Management allows you to connect a maximum of three enclosures in a daisy chain. See the figure below for an example of a daisy chain configuration. If the communication channel between the connector and the first enclosure is lost, the redundant path configuration itself is lost. In this case, the health of the logical connector is displayed as critical.
Consider a case where you reboot your system and Storage Management, displays the Logical Connector with a path failure message. It is possible that you may have intentionally unplugged the second connector. In this case, the path failure message is not relevant. Else, there could be a fault in the connected cable or the cable may not be connected properly to the controller.
1. Expand the Storage tree object to display the controller objects. 2. Select a controller object. 3. Select the Information/Configuration subtab. 4. Select Set Patrol Read Mode from the Available Tasks drop-down menu. 5. Click Execute. You can also locate this task from the Change Controller Properties drop down menu. For more information, see "Change Controller Properties.
You can change any or all of the following properties using the Change Controller Properties task: l Rebuild Rate l BGI Rate l Check Consistency Rate l Reconstruct Rate l Abort check consistency on error l Revertible Hot Spare l Loadbalance l Auto replace member on predictive failure l Redundant path view NOTE: You can set these properties through the command line interface also. See "omconfig Controller Commands" for more information.
The status of the controller is affected by the preserved cache. The controller status is displayed as degraded if the controller has preserved cache. CAUTION: You may not be able to use Storage Management to manage the preserved cache in some cases. As an example, consider you have a RAID 1 level with two disks—D1 and D2. If you now remove D2, the virtual disk is degraded and the data in the controller cache is written to D1. At this point, D1 has the latest data.
Back to Contents Page Enclosures and Backplanes Dell™ OpenManage™ Server Administrator Storage Management User's Guide Backplanes Enclosures Set Asset Data SMART Thermal Shutdown Set Temperature Probe Values Changing the Mode on PowerVault 220S and PowerVault 221S Enclosures EMM Properties Enclosure Management Power Supply Properties Enclosure and Backplane Health Temperature Probe Properties and Tasks Fan Properties Enclosure and Backplane Properties and Tasks Physical disks can be contained i
Enclosure Physical Disks The enclosure's physical disks are displayed under the enclosure object in the tree view. Selecting a disk in the tree view displays the disk's status information. Enclosure Fans The fans are a component of the enclosure's cooling module. The fans are displayed by expanding the enclosure object in the tree view. You can select the Fans object to display their status information.
SMART Thermal Shutdown Does my enclosure support this feature? See "Supported Features." Enclosure management provides a feature which automatically shuts down the operating system, the server, and the enclosure when the enclosure's temperature reaches dangerous extremes. The temperature, when shutdown occurs, is determined by the enclosure temperature probe's Minimum Failure Threshold and the Maximum Failure Threshold. These thresholds are default settings that cannot be changed.
Enclosure and Backplane Health This screen displays the status of the enclosure or backplane and the components attached to the enclosure or backplane. Enclosure and Backplane Status Component status is indicated by the severity. A component with a Warning or Critical/Failure status requires immediate attention to avoid data loss if possible. A component's status may indicate the combined status of the component and its lower-level objects.
the loss of connection to any one EMM may cause the enclosure status to be displayed as degraded. Name This property displays the name of the enclosure or backplane. State This property displays the current status of the enclosure or backplane. Possible values are: Ready — The enclosure or backplane is functioning normally. Degraded — The enclosure has encountered a failure and is operating in a degraded state. The Degraded state does not apply to backplanes.
Drop-down Menu Enclosure Tasks: l "Enable Alarm (Enclosure)" l "Disable Alarm (Enclosure)" l "Set Asset Data" l "Blink" l "Set Temperature Probe Values" Enable Alarm (Enclosure) Does my enclosure support this feature? See "Supported Features." Use the Enable Alarm task to enable the enclosure alarm. When enabled, the audible alarm sounds whenever the fault LED lights. This may occur to signal events such as: l The enclosure temperature has exceeded the warning threshold.
Identifying an Open Connector for the Enclosure Does my controller support this feature? See "Supported Features." If you have not yet attached the enclosure to an open connector, you may need to identify a connector on the controller that can be used for this purpose. To identify an open connector: 1. Expand the Storage Management tree view until the controller object is expanded. When the controller object is expanded, the tree view displays the controller's connectors.
l "Fan Properties" l "Power Supply Properties" l "Temperature Probe Properties and Tasks" Set Asset Data Does my enclosure support this feature? See "Supported Features." You can change the enclosure's asset tag and asset name. The new asset tag and asset name that you specify are displayed on the enclosure's Information/Configuration subtab. To change the enclosure's asset tag and asset name: 1. Type the new asset tag name in the New asset tag text box.
If you want to return the temperature probe's Warning threshold to the default values, select the Reset to default values button and click Apply Changes. The default values are displayed in the Minimum Warning Threshold and Maximum Warning Threshold text boxes. NOTE: On some enclosures, Storage Management may experience a short delay before displaying the current enclosure temperature and temperature probe status.
Use this window to view information about the enclosure's fans. The fans are a component of the enclosure's cooling module. The following table describes the fan properties. Property Status Definition These icons represent the severity or health of the storage component. Normal/OK Warning/Non-critical Critical/Fatal See "Storage Component Severity" for more information. Name This property displays the name of the fan. State This property displays the current status of the fan.
Failed — The power supply has encountered a failure and is no longer functioning. Storage Management may also be unable to communicate with the enclosure using SES commands. The Failed state is displayed when the enclosure does not respond to a status query from Storage Management for any reason. For example, disconnecting the cable would cause this state to be displayed. Missing — The power supply is not present in the enclosure. Part Number This property displays the part number of the power supply.
Do the following to launch the Set Temperature Probe wizard: 1. Expand the Storage tree object to display the controller objects. 2. Expand a controller object. 3. Expand a Connector object. 4. Expand the enclosure object. 5. Select the Temperatures object. 6. Click Set Temperature Probe.
Back to Contents Page Alert Messages Dell™ OpenManage™ Server Administrator Storage Management User's Guide Alert Monitoring and Logging Viewing Alerts Alert Severity Levels Alert Message Format with Substitution Variables Configuring an Automated Response to Alerts SNMP Support for Storage Management Alerts Alert Descriptions and Corrective Actions Storage Management's alert or event management features let you monitor the health of storage resources such as controllers, enclosures, physical disks, and v
Each alert message in the Storage Management alert log has a severity level. The severity level is displayed in the Severity field of the alert message. The severity level indicates the nature of the alert. The alert severity levels are as follows: Alert Severity Component Status OK/Normal/Informational. No action is required. The alert is provided for informational purposes and does not indicate an error condition. For example, the alert may indicate the normal start or stop of an operation.
Example: 2049 Physical disk removed: Physical Disk 0:14 Controller 1, Connector 0 SAS Physical Disk Message Format: Physical Disk X:Y:Z Controller A, Connector B Example: 2049 Physical disk removed: Physical Disk 0:0:14 Controller 1, Connector 0 Virtual Disk Message Format: Virtual Disk X (Name) Controller A (Name) Message Format: Virtual Disk X Controller A Example: 2057 Virtual disk degraded: Virtual Disk 11 (Virtual Disk 11) Controller 1 (PERC 5/E Adapter) NOTE: The virtual disk and controller names a
By default, Storage Management installs SNMP trap forwarding support. For this support to function, you should install SNMP on the managed system prior to installing Storage Management. NOTE: For more information on installation requirements and SNMP, refer to the Server Administrator documentation. SNMP Trap Forwarding The alerts displayed in the Storage Management alert log are forwarded to the operating system event log.
Description: Device failed Cause: A storage component such as a physical disk or an enclosure has failed. The failed component may have been identified by the controller while performing a task such as a rescan or a check consistency. Action: Replace the failed component. You can identify which component has failed by locating the component that has a red X for its status. Perform a rescan after replacing the failed component. Severity: Critical/Failure/Error.
Cause: A physical disk in the disk group is offline. A user may have manually put the physical disk offline. Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: 2158. The clear alert is generated when the conditions producing the current alert have returned to normal.
Clear Alert Number: None. Related Alert Number: 2065, 2305, 2367 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2053 Description: Virtual disk created Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
SNMP Trap Number: 1203. See "SNMP Support for Storage Management Alerts" for more information. 2055 Description: Virtual disk configuration changed Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information.
Description: Virtual disk degraded Cause 1: This alert message occurs when a physical disk included in a redundant virtual disk fails. Because the virtual disk is redundant (uses mirrored or parity information) and only one physical disk has failed, the virtual disk can be rebuilt. Action 1: Configure a hot spare for the virtual disk if one is not already configured. Rebuild the virtual disk.
Description: Virtual disk format started Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: 2086. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: 2088. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2062 Description: Physical disk initialization started. Cause: This alert is provided for informational purposes.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2064 Description: Virtual disk rebuild started Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: 2091. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: None.
Description: Virtual disk Check Consistency cancelled Cause: The check consistency operation cancelled because a physical disk in the disk group has failed or because a user cancelled the check consistency operation. Action: If the physical disk failed, then replace the physical disk. You can identify which disk failed by locating the disk that has a red X for its status. Perform a rescan after replacing the disk.
Action: Restart the rebuild operation. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2075 Description: Copy of data completed on physical disk %2 from physical disk %1 Cause: This alert is provided for informational purposes. Action: None.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2081 SNMP Trap Number: 1204. See "SNMP Support for Storage Management Alerts" for more information. 2077 Description: Virtual disk format failed Cause: A physical disk included in the virtual disk failed. Action: Replace the failed physical disk. You can identify which physical disk has failed by locating the disk that has a red X for its status. Rebuild the physical disk. When finished, restart the virtual disk format operation.
SNMP Trap Number: 1204. See "SNMP Support for Storage Management Alerts" for more information. 2080 Description: Physical disk initialize failed Cause: The physical disk has failed or is corrupt. Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk that has a red X for its status. Restart the initialization. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Cause: A physical disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the rebuild. Action: Replace the failed or corrupt disk. You can identify a disk that has failed by locating the disk that has a red X for its status. Restart the virtual disk rebuild. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2048 Local Response Agent (LRA) Alert Number: 2081 SNMP Trap Number: 1204.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2085 is a clear alert for alert 2058. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2086 Description: Virtual disk format completed Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2088 Description: Virtual disk initialization completed Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2088 is a clear alert for alerts 2061 and 2136. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None.
Description: Virtual disk reconfiguration completed Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2090 is a clear alert for alert 2063. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2092 is a clear alert for alert 2065. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2094 Description: Predictive Failure reported. Cause: The physical disk is predicted to fail. Many physical disks contain Self Monitoring Analysis and Reporting Technology (SMART).
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2273 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751, 851, 901. See "SNMP Support for Storage Management Alerts" for more information. 2098 Description: Global hot spare assigned Cause: A user has assigned a physical disk as a global hot spare. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2100 Description: Temperature exceeded the maximum warning threshold. Cause: The physical disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot.
Local Response Agent (LRA) Alert Number: 2090 SNMP Trap Number: 1053. See "SNMP Support for Storage Management Alerts" for more information. 2102 Description: Temperature exceeded the maximum failure threshold. Cause: The physical disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot. Action: Check for factors that may cause overheating.
2104 Description: Controller battery is reconditioning. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: 2105. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151.
Action: Replace the disk that has received the SMART alert. If the physical disk is a member of a nonredundant virtual disk, ensure that you back up the data before replacing the disk. CAUTION: Removing a physical disk that is included in a nonredundant virtual disk will cause the virtual disk to fail and may cause data loss. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
CAUTION: Removing a physical disk that is included in a nonredundant virtual disk will cause the virtual disk to fail and may cause data loss. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2070 SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information. 2109 Description: SMART warning temperature.
CAUTION: Removing a physical disk that is included in a nonredundant virtual disk will cause the virtual disk to fail and may cause data loss. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2070 SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information. 2111 Description: Failure prediction threshold exceeded due to test – No action needed.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2091 SNMP Trap Number: 854. See "SNMP Support for Storage Management Alerts" for more information. 2114 Description: A Check Consistency on a virtual disk has been paused (suspended). Cause: The check consistency operation on a virtual disk was paused by a user. Action: To resume the check consistency operation, right-click the virtual disk in the tree view and select Resume Check Consistency. Severity: OK/Normal/Informational.
SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2116 Description: A virtual disk and its mirror have been split. Cause: This alert is provided for informational purposes. A user has caused a mirrored virtual disk to be split. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy.
Description: The write policy has changed. Cause: This alert is provided for informational purposes. A user has changed the write policy for a virtual disk. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2121 is a clear alert for alert 2048. Related Alert Number: 2050, 2065, 2158 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 752, 802, 852, 902, 952, 1002, 1052, 1102, 1152, 1202. See "SNMP Support for Storage Management Alerts" for more information. 2122 Description: Redundancy degraded Cause: One or more of the enclosure components has failed.
Clear Alert Number: 2124. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: 2048, 2049, 2057 Local Response Agent (LRA) Alert Number: 2080, 2090 SNMP Trap Number: 1306. See "SNMP Support for Storage Management Alerts" for more information. 2124 Description: Redundancy normal Cause: This alert is provided for informational purposes.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1203. See "SNMP Support for Storage Management Alerts" for more information. 2126 Description: SCSI sense sector reassign Cause: A sector of the physical disk is corrupted and data cannot be maintained on this portion of the disk. This alert is provided for informational purposes. CAUTION: Any data residing on the corrupt portion of the disk may be lost and you may need to restore your data from backup.
SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2128 Description: Background initialization cancelled Cause: Background initialization of a virtual disk has been cancelled. A user or the firmware may have stopped background initialization. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None.
Cause: Background initialization of a virtual disk has completed. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: Alert 2130 is a clear alert for alert 2127. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information.
Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2060 SNMP Trap Number: 753. See "SNMP Support for Storage Management Alerts" for more information. 2135 Description: Array Manager is installed on the system Cause: Storage Management has been installed on a system that has an Array Manager installation.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2137 Description: Communication timeout Cause: The controller is unable to communicate with an enclosure. There are several reasons why communication may be lost. For example, there may be a bad or loose cable. An unusual amount of I/O may also interrupt communication with the enclosure.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851. See "SNMP Support for Storage Management Alerts" for more information. 2139 Description: Enclosure alarm disabled Cause: A user has disabled the enclosure alarm. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851.
Description: Physical disk dead segments removed Cause: Portions of the physical disk were formerly inaccessible. The disk space from these dead segments has been recovered and is now usable. Any data residing on these dead segments has been lost. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2144 Description: Controller alarm disabled Cause: A user has disabled the controller alarm. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2100 SNMP Trap Number: 1153. See "SNMP Support for Storage Management Alerts" for more information. 2146 Description: Bad block replacement error Cause: A portion of a physical disk is damaged. See "Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error" for more information. Action: See "Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error" for more information.
2148 Description: Bad block medium error Cause: A portion of a physical disk is damaged. See "Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error" for more information. Action: See "Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error" for more information. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Action: See "Receive a "Bad Block" Alert with "Replacement," "Sense," or "Medium" Error" for more information. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2060 SNMP Trap Number: 753. See "SNMP Support for Storage Management Alerts" for more information. 2151 Description: Enclosure asset tag changed. Cause: A user has changed the enclosure asset tag.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851. See "SNMP Support for Storage Management Alerts" for more information. 2153 Description: Enclosure service tag changed. Cause: An enclosure service tag was changed. In most circumstances, this service tag should only be changed by Dell Support. Action: Ensure that the service tag was changed under authorized circumstances. Severity: OK/Normal/Informational.
2155 Description: The temperature probe minimum warning value changed Cause: A user has changed the value for the minimum temperature probe warning threshold. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1051. See "SNMP Support for Storage Management Alerts" for more information.
Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2158 Description: Physical disk online. Cause: An offline physical disk has been made online. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2162 Description: Communication regained Cause: Communication with an enclosure has been restored. This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information.
SNMP Trap Number: 904. See "SNMP Support for Storage Management Alerts" for more information. 2164 Description: See readme.txt for a list of validated controller driver versions. Cause: This alert is generated for informational purposes. Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller drivers. Action: See the Readme file for driver and firmware requirements.
Description: The RAID controller firmware and driver validation was not performed. The configuration file is out of date or corrupted. Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers. This situation has occurred because a configuration file is unreadable or missing data. The configuration file may be corrupted. Action: Reinstall Storage Management. Severity: Warning/Noncritical.
Action: See the Readme file for the driver requirements. Update the system to meet the minimum requirements and then reinstall Storage Management. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2050 SNMP Trap Number: 103. See "SNMP Support for Storage Management Alerts" for more information. 2169 Description: The controller battery needs to be replaced.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2171 Description: The controller battery temperature is above normal. Cause: The room temperature may be too hot. The system fan may also be degraded or failed. Action: Verify that the room temperature is normal. See the hardware documentation for acceptable operating temperatures.
SNMP Trap Number: 1151.See "SNMP Support for Storage Management Alerts" for more information. 2173 Description: Unsupported configuration detected. The SCSI rate of the enclosure management modules (EMMs) is not the same. EMM0 %1 EMM1 %2 Cause: The EMMs in the enclosure have a different SCSI rate. This is an unsupported configuration. All EMMs in the enclosure should have the same SCSI rate. The % (percent sign) indicates a substitution variable.
Description: The controller battery has been replaced. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2176 Description: The controller battery Learn cycle has started.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2177 is a clear alert for alert 2176. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2178 Description: The controller battery Learn cycle has timed out. Cause: The controller battery must be fully charged before the Learn cycle can begin.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2180 Description: The controller battery Learn cycle will start in %1 days. Cause: This alert is provided for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation. Action: None.
2182 Description: An invalid SAS configuration has been detected. Details: %1 Cause: The controller and attached enclosures are not cabled correctly. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation. Action: See the hardware documentation for information on correct cabling configurations. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information.
Cause: User cancelled the replace member operation. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2060. Local Response Agent (LRA) Alert Number: None SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2185 Description: Replace member operation stopped for rebuild of hot spare on physical disk Cause: This alert is provided for informational purposes.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2060 SNMP Trap Number: 753. See "SNMP Support for Storage Management Alerts" for more information. 2187 Description: Single-bit ECC error limit exceeded on the controller DIMM. Cause: The controller memory (the dual in-line memory module or DIMM) is malfunctioning. Action: Contact technical support to replace the controller memory.
SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2189 Description: The controller write policy has been changed to Write Back. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151.
Description: There are too many enclosures attached to the controller. This is an unsupported configuration. Cause: There are too many enclosures attached to the controller port. When the enclosure limit is exceeded, the controller loses contact with all enclosures attached to the port. Action: Remove the excessive enclosures. You must remove the enclosures that have been added last and that are causing the enclosure limit to be exceeded. Refer to the hardware documentation for valid configurations.
Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2194 Description: The virtual disk read policy has changed. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201 2196 Description: Dedicated hot spare unassigned. Physical disk %1 Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2196 is a clear alert for alert 2195. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None.
2198 Description: The physical disk is too small to be used for Replace member operation Cause: This alert is provided for informational purposes. Replace member operation cannot be performed on the physical disk as the target disk is smaller than the source disk. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 903.
(SAS HDD/SATA HDD/SATA SSD) from the rest of the virtual disk. SAS HDD, SATA HDD, and SATA SSD are not supported on the same virtual disk. Action: None. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information. 2201 Description: A global hot spare failed.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2203 Description: A dedicated hot spare failed. Cause: The controller is not able to communicate with a disk that is assigned as a dedicated hot spare. The disk may have failed or been removed.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2205 Description: A dedicated hot spare has been automatically unassigned. Cause: The hot spare is no longer required because the virtual disk it was assigned to has been deleted. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None.
2211 Description: The physical device is not supported. Cause: The physical device is not supported. The physical device may not have a supported version of the firmware or the physical device may not be supported by Dell. Action: If the physical device is supported by Dell, then update the firmware to a supported version. If the physical device is not supported by Dell, then replace the physical device with one that is supported. Severity: Warning/Noncritical.
Action: Replace the battery pack. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2100 SNMP Trap Number: 1153 2214 Description: Battery charge in progress. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151 2216 Description: The battery learn mode has changed to auto. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151.
2218 Description: None of the Controller Properties are changed. Cause: The firmware did not set the controller properties correctly. Action: You should change at least one controller property and run the command again. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information.
Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2221 Description: Auto Replace Member operation on Predictive Failure, Abort Check Consistency on Error, and Loadbalance changed.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2223 Description: Abort Check Consistency on Error, Allow Revertible Hot Spare and Replace Member, and Loadbalance changed. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2225 Description: Abort Check Consistency on Error and Loadbalance changed. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751.
Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2228 Description: Allow Revertible Hot Spare and Replace Member and Auto Replace Member operation on Predictive Failure changed.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2230 Description: Auto Replace Member operation on Predictive Failure changed. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2232 Description: The controller alarm is silenced. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information.
Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2235 Description: The Check Consistency rate has changed. Cause: This alert is provided for informational purposes. Action: None.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2237 Description: Abort Check Consistency on Error modified. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2239 Description: A foreign configuration has been cleared. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751.
Description: The Patrol Read mode has changed. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2242 Description: The Patrol Read has started.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Status: Alert 2243 is a clear alert for alert 2242. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2244 Description: A virtual disk blink has been initiated. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2246 Description: The controller battery is degraded. Cause: The controller battery charge is weak. As the battery charge weakens, the battery charger should automatically recharge the battery. If the battery has already met its recharge limit, then the battery pack needs to be replaced. Action: Monitor the battery to make sure that it recharges successfully.
Description: The controller battery is executing a Learn cycle. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2249 Description: The physical disk Clear operation has started.
Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: 2370. Related Alert Number: 2370. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2251 Description: The physical disk blink has initiated. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2253 Description: Redundant path restored Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751.
Description: The physical disk has been started. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2048, 2050, 2065, 2099, 2121, 2196, 2201, 2203 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2257 Description: Controller preserved cache is discarded.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2259 Description: An enclosure blink operation has initiated. Cause: This alert is for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851. See "SNMP Support for Storage Management Alerts" for more information. 2261 Description: A global rescan has initiated. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 101.
Description: Smart thermal shutdown is disabled. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 101. See "SNMP Support for Storage Management Alerts" for more information. 2264 Description: A device is missing. Cause: The controller cannot communicate with a device.
Action: Check the cables. See "Cables Attached Correctly" for more information on checking the cables. Verify that the controller has a supported version of the driver and firmware. You can download the most current version of the driver and firmware from the Dell Support website at support.dell.com. Rebooting the system may also resolve this problem. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2268 Description: %1, Storage Management has lost communication with the controller. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communication, then contact technical support for more information.
SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2270 Description: The physical disk Clear operation failed. Cause: A Clear task was being performed on a physical disk but the task was interrupted and did not complete successfully. The controller may have lost communication with the disk. The disk may have been removed or the cables may be loose or defective. Action: Verify that the disk is present and not in a Failed state.
Description: Patrol Read found an uncorrectable media error. Cause: The Patrol Read task has encountered an error that cannot be corrected. There may be a bad disk block that cannot be remapped. Action: Back up your data. If you are able to back up the data successfully, then fully initialize the disk and then restore from back up. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2276 Description: The dedicated hot spare is too small. Cause: The dedicated hot spare is not large enough to protect all virtual disks that reside on the disk group. Action: Assign a larger disk as the dedicated hot spare.
Local Response Agent (LRA) Alert Number: 2070 SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information. 2278 Description: The controller battery charge level is below a normal threshold. Cause: The battery is discharging. A battery discharge is a normal activity during the battery Learn cycle. Before completing, the battery Learn cycle recharges the battery. You should receive alert "2179" when the recharge occurs.
SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2280 Description: A disk media error has been corrected. Cause: A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block has been remapped. Action: Consider replacing the disk. If you receive this alert frequently, be sure to replace the disk. You should also routinely back up your data. Severity: OK/Normal/Informational.
Cause: The controller firmware attempted to do SMART polling on the hot spare but was not able to complete the SMART polling. The controller has lost communication with the hot spare. Action: Remove and then reinsert the physical disk that is the hot spare. After the physical disk is reseated, reassign it as the hot spare. To verify that communication with the hot spare is restored, initiate a Clear task on the hot spare (see "Clear Physical Disk and Cancel Clear") or run diagnostics on the hot spare.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1151. See "SNMP Support for Storage Management Alerts" for more information. 2287 Description: Protection policy for %1 has changed Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information.
Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2289 Description: Multi-bit ECC error on controller DIMM. Cause: An error involving multiple bits has been encountered during a read or write operation on the controller memory (the dual in-line memory module or DIMM). The error correction algorithm recalculates parity data during read and write operations.
2291 Description: An enclosure management module (EMM) has been discovered. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851. See "SNMP Support for Storage Management Alerts" for more information. 2292 Description: Communication with the enclosure has been lost.
Cause: An enclosure management module (EMM) has failed. The failure may be caused by a loss of power to the EMM. The EMM self test may also have identified a failure. There could also be a firmware problem or a multi-bit error. Action: Replace the EMM. See the hardware documentation for information on replacing the EMM. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2091 SNMP Trap Number: 1004 and 1104. See "SNMP Support for Storage Management Alerts" for more information. 2296 Description: An enclosure management module (EMM) has been inserted. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
SNMP Trap Number: 954. See "SNMP Support for Storage Management Alerts" for more information. 2298 Description: The enclosure has a bad sensor %1. Cause: The enclosure has a bad sensor. The enclosure sensors monitor the fan speeds, temperature probes, and so on. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the Alert Log and can vary depending on the situation. Action: Refer to the hardware documentation for more information.
Cause: The controller is not receiving a valid response from the enclosure. Action: Completely power down all enclosures attached to the system and reboot the system. Verify that the EMM and the controller firmware are at the latest supported version. If you do not have a supported version of the firmware available, it can be downloaded from the Dell Support website at support.dell.com. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None.
Action: Verify the health of the enclosure and its components. Run diagnostics and check the LEDs to identify hardware that has failed or that is degraded. Replace any hardware that is in a Failed state. See the hardware documentation for more information on replacing components and for additional troubleshooting information. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Clear Alert Number: None. Related Alert Number: 2211 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2305 Description: The physical disk is too small to be used for a rebuild. Cause: The physical disk is too small to rebuild the data. Action: Remove the physical disk and insert a new physical disk that is the same size or larger than the disk that is being rebuilt.
SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information. 2307 Description: Bad block table is full. Unable to log block %1 Cause: The bad block table is the table used for remapping bad disk blocks. This table fills as bad disk blocks are remapped. When the table is full, bad disk blocks can no longer be remapped which means that disk errors can no longer be corrected. At this point, data loss can occur. The %1 indicates a substitution variable.
2310 Description: A virtual disk is permanently degraded. Cause: A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the failure of more than one physical disk. In this case, both the source physical disk and the target disk with redundant data have failed. A rebuild is not possible because there is no longer redundancy. Action: Replace the failed disks and restore your data from backup. Severity: Critical/Failure/Error.
Description: A power supply in the enclosure has an AC failure. Cause: The power supply has an AC failure. Action: Replace the power supply. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: 2325. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: 2122, 2324. Local Response Agent (LRA) Alert Number: 2090 SNMP Trap Number: 1003.
Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2051 SNMP Trap Number: 104. See "SNMP Support for Storage Management Alerts" for more information. 2315 Description: Diagnostic message %1 Cause: This alert is provided for informational purposes. The %1 indicates a substitution variable.
Local Response Agent (LRA) Alert Number: 2061 SNMP Trap Number: 754. See "SNMP Support for Storage Management Alerts" for more information. 2318 Description: Problems with the controller battery or the controller battery charger have been detected. The battery health is poor. Cause: The controller battery or the controller battery charger is not functioning properly. Action: Replace the battery pack. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information.
2320 Description: Single-bit ECC error. The controller DIMM is critically degraded. Cause: The controller memory (the dual in-line memory module or DIMM) is malfunctioning. Action: Contact technical support to replace the controller memory immediately to avoid loss of functionality. See your system documentation for information about contacting technical support by using telephone, fax, and Internet services. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information.
Cause: The power supply unit is switched off. Either a user switched off the power supply unit or it is defective. Action: Check to see whether the power switch is turned off or on. If it is turned off, turn it on. If the problem is not corrected, verify that the power cord is attached and functional. If the problem is still not corrected or if the power switch is already turned on, then replace the power supply unit. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information.
Clear Alert Number: 2325. The clear alert is generated when the conditions producing the current alert have returned to normal. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2091 SNMP Trap Number: 1004. See "SNMP Support for Storage Management Alerts" for more information. 2325 Description: The power supply cable has been inserted. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2327 Description: The NVRAM is corrupt. The controller is reinitializing the NVRAM. Cause: The nonvolatile random access memory (NVRAM) is corrupt. This may occur after a power surge, a battery failure, or for other reasons. The controller is reinitializing the NVRAM. The controller properties will reset to the default settings after the reinitialization is complete. Action: None.
Cause: The text for this alert is generated by the controller and can vary depending on the situation. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text can vary depending on the situation. Action: Run the PHY integrity test diagnostics. Make sure the cables are attached securely. See "Cables Attached Correctly" for more information on checking the cables.
problem. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2332 Description: A controller hot plug has been detected. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2335 Description: Controller event log: %1 Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the Alert Log. This text is from events in the controller event log that were generated while Storage Management was not running.
SNMP Trap Number: 754. See "SNMP Support for Storage Management Alerts" for more information. 2337 Description: The controller is unable to recover cached data from the battery backup unit (BBU). Cause: The controller was unable to recover data from the cache. This may occur when the system is without power for an extended period of time or when the battery is discharged. Action: Verify that the battery is charged and in good health.
Description: The factory default settings have been restored. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information.
Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2342 Description: The Check Consistency found inconsistent parity data. Data redundancy may be lost. Cause: The data on a source disk and the redundant data on a target disk is inconsistent.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2080 SNMP Trap Number: 1203. See "SNMP Support for Storage Management Alerts" for more information. 2346 Description: Error occurred: %1 Cause: A physical device may have an error. The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the Alert Log. This text can vary depending on the situation. Action: Verify the health of attached devices.
SNMP Trap Number: 904. See "SNMP Support for Storage Management Alerts" for more information. 2348 Description: The rebuild failed due to errors on the target physical disk. Cause: You are attempting to rebuild data onto a disk that is defective. Action: Replace the target disk. If a rebuild does not automatically start after replacing the disk, then initiate the Rebuild task. You may need to assign the new disk as a hot spare in order to initiate the rebuild. Severity: Critical/Failure/Error.
Cause: The rebuild encountered an unrecoverable disk media error. Action: Replace the disk. Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2095, 2273 Local Response Agent (LRA) Alert Number: 2071 SNMP Trap Number: 904. See "SNMP Support for Storage Management Alerts" for more information. 2351 Description: A physical disk is marked as missing. Cause: This alert is provided for informational purposes. Action: None.
Clear Alert Status: Alert 2352 is a clear alert for alert 2351. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information. 2353 Description: The enclosure temperature has returned to normal. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information.
Local Response Agent (LRA) Alert Number: 2061 SNMP Trap Number: 754. See "SNMP Support for Storage Management Alerts" for more information. 2357 Description: SAS expander error: %1 Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the Alert Log. This text can vary depending on the situation. Action: There may be a problem with the enclosure. Verify the health of the enclosure and its components.
2359 Description: The physical disk is not certified. Cause: The physical disk does not comply with the standards set by Dell and is not supported. Action: Replace the physical disk with a physical disk that is supported. Severity: Warning/Noncritical. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: 2070 SNMP Trap Number: 903. See "SNMP Support for Storage Management Alerts" for more information.
Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2362 Description: Physical disk(s) have been removed from a virtual disk. The virtual disk will be in Failed state during the next system reboot. Cause: This alert is provided for informational purposes.
Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2366 Description: Dedicated spare imported as global due to missing arrays Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None.
2368 Description: The SCSI Enclosure Processor (SEP) has been rebooted as part of the firmware download operation and will be unavailable until the operation completes. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: 2049, 2052, 2162, 2292 Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 851.
Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1201. See "SNMP Support for Storage Management Alerts" for more information. 2371 Description: Attempted import of unsupported Virtual Disk type RAID%1 Cause: This alert is provided for informational purposes. Action: None.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2373 Description: Attempted import of unsupported Virtual Disk type RAID %1 Cause: This alert is provided for informational purposes. User has attempted to import a foreign virtual disk with unsupported RAID level on the controller Action: None. Severity: OK/Normal/Informational.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2375 Description: Attempted import of Virtual Disk with missing physical disk Cause: This alert is provided for informational purposes. User has attempted to import a foreign virtual disk with a missing physical disk. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None.
Cause: This alert is provided for informational purposes. User has attempted to import an orphan drive. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2380 Description: Foreign configuration has been partially imported. Some configuration failed to import. Cause: This alert is provided for informational purposes. Action: None. Severity: OK/Normal/Informational. See "Alert Severity Levels" for more information. Clear Alert Number: None.
SNMP Trap Number: 751. See "SNMP Support for Storage Management Alerts" for more information. 2382 Description: An unsupported configuration was detected. The controller does not support physical disks of type SSD: ,, Cause: A physical disk of media type SSD is attached to a controller that does not support SSD disks. Action: Replace the unsupported physical disk with a physical disk of media type HDD. Severity: Warning.
Cause: The number of physical disks you specified for the hot spare protection policy is violated. Action: Reassign the number of hot spares as specified in the protection policy for that RAID level. Severity: Warning. See "Alert Severity Levels" for more information. Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 1203. See "SNMP Support for Storage Management Alerts" for more information.
Clear Alert Number: None. Related Alert Number: None. Local Response Agent (LRA) Alert Number: None. SNMP Trap Number: 901. See "SNMP Support for Storage Management Alerts" for more information.
Back to Contents Page Frequently Asked Questions Dell™ OpenManage™ Server Administrator Storage Management User's Guide Why is a rebuild not working? How can I safely remove or replace a physical disk? How do I recover from removing the wrong physical disk? How do I know what firmware is installed? What controllers do I have? How do I turn off an alarm? What RAID level is best for me? This section provides frequently asked questions that address situations commonly experienced in a storage environment.
To display the firmware version of all controllers: 1. 2. Select the Storage object in the tree view. Click the Information/Configuration subtab. The Firmware Version column on the Information/Configuration subtab displays the firmware version for all controllers attached to the system.
Back to Contents Page Getting Started Dell™ OpenManage™ Server Administrator Storage Management User's Guide Launching Storage Management User Privileges Using the Graphical User Interface Using the Storage Management Command Line Interface Displaying the Online Help Common Storage Tasks Dell™ OpenManage™ Server Administrator Storage Management is designed for system administrators who implement hardware RAID solutions and understand corporate and small business storage environments.
https://:1311 where is the assigned name for the managed system and 1311 is the default port or https://:1311 where is the IP address for the managed system and 1311 is the default port. NOTE: You must type https:// (not http://) in the address field to receive a valid response in your browser. User Privileges Server Administrator provides security through the User, Power User, and Administrator user groups.
Drop-down Menus and Wizards for Running Tasks Many of the storage objects displayed in the tree view have tasks. Examples of these tasks include creating virtual disks, assigning hot spares, reconditioning a battery, and so on. To access a storage object's task, select the component in the tree view and then select the Information/Configuration subtab. The Information/Configuration subtabs have task drop-down menus or buttons for launching a task.
Back to Contents Page Protecting Your Virtual Disk with a Hot Spare Dell™ OpenManage™ Server Administrator Storage Management User's Guide Understanding Hot Spares Considerations for Hot Spares on PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, CERC ATA100/4ch, PERC 5/E, PERC 5/i, PERC 6/E, PERC 6/I, and CERC 6/I Controllers Considerations for Hot Spares on PERC 3/Si, 3/Di, and CERC SATA1.
A dedicated hot spare can only be assigned to the set of virtual disks that share the same physical disks. 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 physical disk included in any virtual disk on the controller.
Size Requirements for Global Hot Spares on PERC 3/Si, 3/Di, and CERC SATA1.5/6ch Controllers When assigning a physical disk as a global hot spare on a PERC 3/Si, 3/Di, and CERC SATA1.5/6ch controller, the physical disk should be as large or larger than the largest physical disk on the controller. Dedicated Hot Spare Considerations on PERC 3/Si, 3/Di, and CERC SATA1.5/6ch Controllers You can assign the same dedicated hot spare to more than one virtual disk.
Back to Contents Page Setting Hot Spare Protection Policy Dell™ OpenManage™ Server Administrator Storage Management User's Guide Dedicated Hot Spare Protection Policy Global Hot Spare Protection Policy Considerations for Hot Spare Protection Policy Considerations for Enclosure Affinity The Hot Spare Protection Policy is supported only on Serial Attached SCSI (SAS) controllers.
Considerations for Enclosure Affinity l Enclosure affinity settings for dedicated hot spare are applicable only on PERC 5 and PERC 6 family of controllers. l Enclosure affinity settings for a global/dedicated hot spare are not automatically set when you upgrade to Dell OpenManage version 6.1. l Enclosure affinity settings for a global/dedicated hot spare are not automatically set when you import a foreign virtual disk.
Back to Contents Page Moving Physical and Virtual Disks from One System to Another Dell™ OpenManage™ Server Administrator Storage Management User's Guide Required Conditions Migrating SCSI Virtual Disks to Another System Migrating SAS Virtual Disks to Another System This section describes how to move physical and virtual disks from one system to another.
This section applies to the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers The following describes how to migrate virtual disks and volumes from one system to another. Completing the migration requires the following activities: l "Moving the Disks" l "Saving the New Controller Configuration" Moving the Disks 1. 2. Shut down the system that the physical disks are being moved from.
Back to Contents Page Overview Dell™ OpenManage™ Server Administrator Storage Management User's Guide What's New in this Release? Installation Considerations for Storage Management Supported Controllers Supported Enclosures Support for Disk and Volume Management Dell™ OpenManage™ Server Administrator Storage Management provides enhanced features for configuring a system's locally-attached RAID and non-RAID disk storage.
NOTE: It is highly recommended that you uninstall FAST before installing Storage Management. Uninstalling FAST on a system that has both FAST and Storage Management installed will also uninstall the Adaptec filter driver. In this situation, you will need to reinstall Storage Management to restore the Adaptec filter driver. To prevent this, verify that FAST is uninstalled before installing Storage Management.
l PERC 6/I Integrated and PERC 6/I Adapter l PERC 6/I Modular l CERC 6/I controller l SAS 6/iR controller NOTE: Integrated mirroring on the PERC 4/IM controller enables you to mirror a physical disk that resides internally in the server. You can implement the integrated mirror using the PERC 4/IM BIOS. When implemented, Storage Management recognizes the integrated mirror as a virtual disk. You cannot, however, use Storage Management to create a virtual disk on the PERC 4/IM controller.
Back to Contents Page Quick Access to Storage Status and Tasks Dell™ OpenManage™ Server Administrator Storage Management User's Guide Storage Dashboard and Storage Health Monitoring Disk Reliability on RAID Controllers Storage Health Using Alarms to Detect Failures Hot Spare Protection Policy Using Enclosure Temperature Probes Storage Component Severity Rescan to Update Storage Configuration Changes Storage Properties and Current Activity Time Delay in Displaying Configuration Changes Alerts or E
Component status is indicated by the severity. A component with a Warning or Critical/Failure status requires immediate attention to avoid data loss, if possible. A component's status may indicate the combined status of the component and its lower-level objects. See "Determining the Health Status for Storage Components" for more information. It may be useful to review the Alert Log for events indicating why a component has a Warning or Critical status.
SMART performs predictive failure analysis on each disk and sends alerts if a disk failure is predicted. The RAID controllers check physical disks for failure predictions and, if found, pass this information to Storage Management. Storage Management immediately displays an alert icon on the disk. Storage Management also sends an alert to the Alert Log and the Microsoft® Windows® application log. NOTE: When a controller's I/O is paused, you will not receive SMART alerts.
Time Delay in Displaying Configuration Changes When you change the storage configuration, Storage Management quickly generates SNMP traps in response to the configuration changes. The Storage Management MIB (Management Information Base) is also updated to reflect storage configuration changes. However, it may take up to five minutes to update the MIB with the most recent storage configuration.
Back to Contents Page Storage Information and Global Tasks Dell™ OpenManage™ Server Administrator Storage Management User's Guide Storage Properties Global Tasks Storage Controllers Use this window to view high-level information about your system's storage. This window also enables you to launch global tasks that affect all controllers attached to the system. Storage Properties The Storage tree-view object has the following properties.
NOTE: On the PERC 3/Si, 3/Di, and CERC SATA1.5/6ch controllers, if you pause a check consistency that is being performed on a virtual disk, then the virtual disk state changes to Resynching Paused. Performing a Global Rescan while a virtual disk is in Resynching Paused state may cause the check consistency to resume. In this case, the virtual disk state changes to Resynching. To do a global rescan: 1. Select the Storage tree view object. 2. Click the Information/Configuration subtab. 3.
The firmware and drivers listed in the Readme file refer to the minimum supported version for these controllers. Later versions of the firmware and drivers are also supported. See the Dell Support website at support.dell.com for the most recent driver and firmware requirements. Minimum Required Driver Version This property displays the minimum driver version that is required by Storage Management. This property is only displayed if the controller driver does not meet the minimum requirement.
Back to Contents Page Understanding RAID Concepts Dell™ OpenManage™ Server Administrator Storage Management User's Guide What Is RAID? Organizing Data Storage for Availability and Performance Choosing RAID Levels and Concatenation Comparing RAID Level and Concatenation Performance Storage Management uses Redundant Array of Independent Disks (RAID) technology to provide storage management capability.
RAID Levels Each RAID level uses some combination of mirroring, striping, and parity to provide data redundancy or improved read and write performance. For specific information on each RAID level, see "Choosing RAID Levels and Concatenation." Organizing Data Storage for Availability and Performance RAID provides different methods or RAID levels for organizing the disk storage. Some RAID levels maintain redundant data so that you can restore data after a disk failure.
Data stored on a single disk can be considered a simple volume. This disk could also be defined as a virtual disk that comprises only a single physical disk. Data that spans more than one physical disk can be considered a spanned volume. Multiple concatenated disks can also be defined as a virtual disk that comprises more than one physical disk. A dynamic volume that spans to separate areas of the same disk is also considered concatenated.
RAID 0 Characteristics: l Groups n disks as one large virtual disk with a capacity of (smallest disk size)*n disks. l Data is stored to the disks alternately. l No redundancy data is kept. When a disk fails, the large virtual disk fails with no means of rebuilding the data. l Better read and write performance.
l Data is replicated on the two disks. l When a disk fails, the virtual disk still works. The data will be read from the failed disk's mirror. l Better read performance, but slightly slower write performance. l Redundancy for protection of data. l RAID 1 is more expensive in terms of disk space since twice the number of disks are used than required to store the data without redundancy.
l "Number of Physical Disks per Virtual Disk" l "Maximum Number of Virtual Disks per Controller" RAID Level 6 (Striping with additional distributed parity) RAID 6 provides data redundancy by using data striping in combination with parity information. Similar to RAID 5, the parity is distributed within each stripe. RAID 6, however, uses an additional physical disk to maintain parity, such that each stripe in the disk group maintains two disk blocks with parity information.
Figure 3-6. RAID 50 RAID 50 Characteristics: l Groups n*s disks as one large virtual disk with a capacity of s*(n-1) disks, where s is the number of spans and n is the number of disks within each span. l Redundant information (parity) is alternately stored on all disks of each RAID 5 span. l Better read performance, but slower write performance. l Requires as much parity information as standard RAID 5. l Data is striped across all spans. RAID 50 is more expensive in terms of disk space.
RAID 60 Characteristics: l Groups n*s disks as one large virtual disk with a capacity of s*(n-2) disks, where s is the number of spans and n is the number of disks within each span. l Redundant information (parity) is alternately stored on all disks of each RAID 6 span. l Better read performance, but slower write performance. l Increased redundancy provides greater data protection than a RAID 50. l Requires proportionally as much parity information as RAID 6.
RAID 10 Characteristics: l Groups n disks as one large virtual disk with a capacity of (n/2) disks, where n is an even integer. l Mirror images of the data are striped across sets of physical disks. This level provides redundancy through mirroring. l When a disk fails, the virtual disk is still functional. The data will be read from the surviving mirrored disk. l Improved read performance and write performance. l Redundancy for protection of data.
Related Information: See the following: l "Organizing Data Storage for Availability and Performance" l "Comparing RAID Level and Concatenation Performance" l "Controller-supported RAID Levels" l "Number of Physical Disks per Virtual Disk" l "Maximum Number of Virtual Disks per Controller" Considerations for RAID 10 and 50 on PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch Controllers On the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC A
RAID Level Data Read Performance Availability Write Performance Rebuild Performance Minimum Disks Required Suggested Uses 1 or 2 depending on the controller. More cost efficient than redundant RAID levels. Use for noncritical data.
Back to Contents Page Troubleshooting Dell™ OpenManage™ Server Administrator Storage Management User's Guide Common Troubleshooting Procedures Virtual Disk Troubleshooting Specific Problem Situations and Solutions This section contains troubleshooting procedures for common situations as well as for specific problems. Common Troubleshooting Procedures This section describes commands and procedures that can be used in troubleshooting.
Isolate Hardware Problems If you receive a "timeout" alert related to a hardware device or if you otherwise suspect that a device attached to the system is experiencing a failure, then do the following to confirm the problem: l l Verify that the cables are correctly attached. If the cables are correctly attached and you are still experiencing the problem, then disconnect the device cables and reboot the system. If the system reboots successfully, then one of the devices may be defective.
If the failed physical disk is part of a nonredundant virtual disk (such as RAID 0), then the failure of a single physical disk will cause the entire virtual disk to fail. To proceed, you need to verify when your last backup was, and if there is any new data that has been written to the virtual disk since that time. If you have backed up recently and there is no new data on the disks that would be missed, you can restore from backup.
If the physical disk that you removed is part of a redundant virtual disk that does not have a hot spare, then replace the physical disk and do a rebuild.
l l l l A physical disk has been removed, and the system has not yet attempted to write data to the removed disk. In this case, the system will not recognize the removal of a physical disk until it attempts a write operation to the disk. If the physical disk is part of a redundant virtual disk, then the system will rebuild the disk after attempting a write operation. This situation applies to PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch controllers.
If you have created a virtual disk that exceeds the 1TB limitation, you should do the following: 1. Back up your data. 2. Delete the virtual disk. 3. Create one or more virtual disks that are smaller than 1TB. 4. Restore your data from backup. Whether or not your Linux operating system limits virtual disk size to 1TB depends on the version of the operating system and any updates or modifications that you have implemented. See your operating system documentation for more information.
l "Storage Management May Delay Before Updating Temperature Probe Status" l "You are Unable to Log into a Remote System" l "Cannot Connect to Remote Windows Server™ 2003 System" l "Reconfiguring a Virtual Disk Displays Error in Mozilla Browser" l "Physical Disks Display Under Connector Not Enclosure Tree Object" Physical Disk is Offline or Displays an Error Status A physical disk may display an error status if it has been damaged, taken offline, or was a member of a virtual disk that has been del
If you receive an alerts 2146 through 2150 as the result of doing a rebuild or while the virtual disk is in a degraded state, then data cannot be recovered from the damaged disk without restoring from backup. If you receive alerts 2146 through 2150 under circumstances other than a rebuild, then data recovery may be possible. The following describes each of these situations.
Erroneous Status and Error Messages after a Windows Hibernation Activating the Windows hibernation feature may cause Storage Management to display erroneous status information and error messages. This problem resolves itself when the Windows operating system recovers from hibernation.
Back to Contents Page Virtual Disks Dell™ OpenManage™ Server Administrator Storage Management User's Guide Considerations Before Creating Virtual Disks Span Edit Creating Virtual Disks Virtual Disk Task: Reconfigure (Step 1 of 3) Reconfiguring/Migrating Virtual Disks Virtual Disk Task: Reconfigure (Step 2 of 3) Starting and Target RAID Levels for Virtual Disk Reconfiguration Virtual Disk Task: Reconfigure (Step 3 of 3) Maintain Integrity of Redundant Virtual Disks Format and Initialize; Slow and F
In addition to the considerations described in this section, you should also be aware of the controller limitations described in "Number of Physical Disks per Virtual Disk." Be aware that the following considerations apply when creating virtual disks: l Creating virtual disks on PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, CERC ATA100/4ch, PERC 5/E, PERC 5/i, PERC 6/E, and PERC 6/I controllers.
On some versions of the Linux operating system, the virtual disk size is limited to 1TB. Before creating a virtual disk that is larger than 1TB, you should make sure that your operating system supports this virtual disk size. The support provided by your operating system depends on the version of the operating system and any updates or modifications that you have implemented. In addition, you should investigate the capacity of your peripheral devices to support a virtual disk that is larger than 1TB.
NOTE: Channel redundancy only applies to controllers that have more than one channel and that attach to an external disk enclosure. Creating Virtual Disks Does my controller support this feature? See "Supported Features." 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 physical disks.
Table 14-1.
Does my controller support this feature? See "Supported Features." The virtual disk Check Consistency task verifies the accuracy of the redundant (parity) information. This task only applies to redundant virtual disks. When necessary, the Check Consistency task rebuilds the redundant data. To verify a virtual disk's redundant information: 1. Locate the controller on which the virtual disk resides in the tree view. Expand the controller object until the Virtual Disks object is displayed. 2.
On the PERC 3/Si, 3/Di, and CERC SATA1.5/6ch controllers, reconfiguring a concatenated virtual disk to a RAID 1 may cause the virtual disk to be in Resynching state. Performing a "Cancel Check Consistency" on a virtual disk while it is in Resynching state will cause the virtual disk to be in a Failed Redundancy state. See "Considerations for Concatenated to RAID 1 Reconfiguration on PERC 3/Si, 3/Di, and CERC SATA1.5/6ch Controllers" for more information.
3. Select the Virtual Disks object. 4. Select a task from the Available Tasks drop-down menu. 5. Click Execute. NOTE: Different controllers support different features. For this reason, the tasks displayed on the Tasks drop-down menu can vary depending on which controller is selected in the tree view. If no tasks can be performed because of controller or system configuration limitations, then the Tasks drop-down menu displays No Task Available.
NOTE: The Cancel Initialize task only applies to the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers. Cancel Background Initialization Does my controller support this feature? See "Supported Features." On PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, and 4e/Di controllers, background initialization of redundant virtual disks begins automatically after the virtual disk is created.
NOTE: On the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, the controller firmware uses the rebuild rate setting to control the system resource allocation for the Check Consistency task. See "Set Rebuild Rate" for more information. Cancel Check Consistency Does my controller support this feature? See "Supported Features." Use the Cancel Check Consistency task to stop a check consistency operation that is in progress.
NOTE: Renaming a virtual disk generates alert "2159." On the PERC 3/Si, 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controllers, alert "2159" displays the new virtual disk name. On the PERC 3/SC, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA100/4ch controllers, alert "2159" displays the original virtual disk name. Cancel Rebuild Does my controller support this feature? See "Supported Features." Use the Cancel Rebuild task to cancel a rebuild while it is in progress.
2. ¡ Select RAID 1 for mirroring disks. This selection groups two disks together as one virtual disk with a capacity of one single disk. The data is replicated on both disks. When a disk fails, the virtual disk continues to function. This feature provides data redundancy and good read performance, but slightly slower write performance. Your system must have at least two disks to use RAID 1. ¡ Select RAID 5 for striping with distributed parity.
If you need to change a selection, click Go Back To Previous Page to return to "Create Virtual Disk Express Wizard (Step 1 of 2)." NOTE: If a physical disk is receiving a SMART alert, it cannot be used in a virtual disk. For more information on SMART alerts, see "Monitoring Disk Reliability on RAID Controllers." 2. Review the Assign Dedicated Hot Spare section. A hot spare is an unused backup physical disk that can be used to rebuild data from a redundant virtual disk.
Storage Management calculates the optimum span composition in the following manner: l Determining span calculation: - Calculating the number of disks that can be utilized from the selected disks. - Maximizing the number of spans in order to increase the I/O performance l Determining the mirror for the physical disks: The mirror is determined in a way that ensures maximum possible redundancy. The algorithm will also try to match a physical disk for its mirror to a disk that is closest to it in size.
Depending on the RAID level you selected and the virtual disk size, this screen displays the disks and connectors (channels or ports) available for configuring the virtual disk. The following is an example of what might be displayed: Connector 0 The Connector section of the screen displays the controller's connectors and the disks attached to each connector. Select the disks to be included in the virtual disk. In this example, the controller has a single connector with five disks.
This screen enables you to select attributes for the virtual disk. These attributes include the name, size and read, write, and cache policy. Depending on the controller and your previous virtual disk selections, the items displayed on this screen can vary. Do the following: 1. Type the name of the virtual disk in the Name text box. The virtual disk name can contain only alphanumeric characters as well as spaces, dashes and underscores. The maximum name length depends on the controller.
3. Do one of the following: l Click Span Edit to edit the spans created in "Create Virtual Disk Advanced Wizard (Step 2 of 4)." This option is available only if the controller is a SAS controller with firmware 6.1 and later and you selected RAID 10. l Click Finish to create the virtual disk with the attributes shown on this screen. l Click Go Back To Previous Page to return to "Create Virtual Disk Advanced Wizard (Step 3 of 4)" if you want to change your selections.
To locate this task in Storage Management: 1. Expand the Storage tree object to display the controller objects. 2. Expand a controller object. 3. Select the Virtual Disks object. 4. Select Reconfigure from the Available Tasks drop-down menu. 5. Click Execute. Virtual Disk Task: Reconfigure (Step 2 of 3) Does my controller support this feature? See "Supported Features." This screen enables you to select the RAID level and size for the reconfigured virtual disk.
2. Click Finish to complete the virtual disk reconfiguration. If you want to exit without changing the original virtual disk, click Exit Wizard. NOTE: On some controllers, performing a Rescan while a reconfiguration is in progress will cause the virtual disk configuration and the physical disk state to display incorrectly. For example, changes to the virtual disk's RAID level may not be displayed and the state of physical disks that were added to the virtual disk may display as Ready instead of Online.
Use the Fast Initialize task to initialize all physical disks included in the virtual disk. The Fast Initialize task updates the metadata on the physical disks so that all disk space is available for future write operations. The initialize can be completed quickly because existing information on the physical disks is not erased, although future write operations will overwrite any information that remains on the physical disks. NOTE: Doing a Fast Initialize causes existing data to be inaccessible.
Virtual Disk Task: Delete Does my controller support this feature? See "Supported Features." Deleting a virtual disk destroys all information including file systems and volumes residing on the virtual disk. NOTE: When deleting virtual disks, all assigned global hot spares may be automatically unassigned when the last virtual disk associated with the controller is deleted. To delete a virtual disk: To identify which physical disks are included in the virtual disk, click Blink.
2. Click Rename. If you want to exit without renaming the virtual disk, click Go Back To Virtual Disk Page. To locate this task in Storage Management: 1. Expand the Storage tree object to display the controller objects. 2. Expand a controller object. 3. Select the Virtual Disks object. 4. Select Rename from the Available Tasks drop-down menu. 5. Click Execute. Virtual Disk Task: Change Policy Does my controller support this feature? See "Supported Features.
To Split a Mirror: Click Split Mirror. If you want to exit without splitting the mirror, click Go Back To Virtual Disk Page. CAUTION: Your virtual disk will no longer be redundant after performing a Split Mirror operation. To locate this task in Storage Management: 1. Expand the Storage tree object to display the controller objects. 2. Expand a controller object. 3. Select the Virtual Disks object. 4. Select Split Mirror from the Available Tasks drop-down menu. 5. Click Execute.
Related Information: l "Rescan to Update Storage Configuration Changes" l "Time Delay in Displaying Configuration Changes" Assign and Unassign Dedicated Hot Spare Does my controller support this feature? See "Supported Features." A dedicated hot spare is an unused backup disk that is assigned to a single virtual disk. When a physical disk in the virtual disk fails, the hot spare is activated to replace the failed physical disk without interrupting the system or requiring your intervention.
NOTE: You must also enable the Revertible Hot Spare option to use Replace Member Disk task. The destination physical disk should be in the Ready state, available to be written to, and of appropriate size and type. NOTE: The destination physical disk can also be an available hot spare. To Replace a Member Disk: (Step 1 of 2) 1. Select the physical disk in the Connector table that you want to replace. 2. Select the destination disk in the Disks available for replace member operation table.
