User's Manual

Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information.

Clear Alert Number: None.

Related Alert Number: None.

2079

Description: Virtual disk initialization failed

Cause: The controller cannot communicate with attached devices. A disk may be removed or contain errors. Cables may also be loose or defective.

Action: Power down and reseat the physical disks. Verify the health of attached devices. Review the Alert Log for significant alerts. If a physical disk has failed,
then replace the physical disk. If the virtual disk is on a SAS controller, run the PHY integrity diagnostic tests. Make sure the cables are attached securely. See
"Cables Attached Correctly" for more information on checking the cables.

Severity: Critical/Failure/Error. See "Alert Severity Levels" for more information.

Clear Alert Number: None.

Related Alert Number: None.

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.

2081

Description: Virtual disk reconfiguration failed

Cause: A physical disk included in the virtual disk has failed or is corrupt. A user may also have cancelled the reconfiguration.
