Brand: Hewlett Packard Enterprise
Category: Storage
Document Type: Manual
Language: EN
Manual for MSA 1040/2040
Uploaded: Nov. 21, 2025, 8:17 p.m.
Manual Publish Date: 2016-06-01
Warranty Information
Warranty information is not explicitly detailed in this document.
Events and LEDs
Event notification can be set to four different levels: Informational, Warning, Error, and Critical. Each level signifies a different severity of system events, from general information to critical failures requiring immediate attention.
Disk Drives
The manual details various disk drive statuses, including Available, Failed, Global spare, and Leftover. It also provides troubleshooting steps for disk error conditions such as media errors, hardware errors, and SMART errors. Recommended actions range from reseating disks to replacing them, with references to "Using the Trust Command" for data recovery.
Vdisk or Disk Group Status
Vdisk or disk group statuses include Critical, Fault Tolerant (with or without down drives), Offline, Quarantined (critical, offline, or with down drives), and Up. Each status indicates the health and availability of the virtual disks or disk groups.
Management Controller Issue
The Management Controller (MC) is responsible for array management functions like user accounts and configuration. Issues can arise if the MC becomes unresponsive, requiring restart procedures.
Power Supply Faults and Power Cycle
The system is designed with redundant power supplies. Troubleshooting involves checking power supply status, LEDs, and connections. A full system power cycle is generally not required but can be performed by shutting down controllers and then the array.
Chassis Replacement
Chassis issues are rare and typically involve physical defects preventing FRU installation or midplane problems. Verification of the specific FRU is necessary before considering chassis replacement.
Using the Trust Command
The trust command is a disaster-recovery tool used to re-synchronize metadata and make Leftover/Failed drives active members of a Vdisk/disk group. It is a last resort for recovering data when no backup exists.
Troubleshooting and error codes
Table 5 Disk error conditions and recommended actions
| Symptom | Recommended Action |
|---|---|
| Event 8 reports that the RAID controller can no longer detect the disk. | Reseat the disk. If it does not solve the problem, replace the disk. |
| Event 8 reports a media error for the disk. | If all the volumes and Vdisks or disk groups are online and available, then replace the disk. If the drive is marked as Leftover or Failed, and data recovery is needed, see "Using the Trust Command" (page 26). |
| Event 8 reports a hardware error for the disk. | If all the volumes and Vdisks or disk groups are online and available, then replace the disk. If the drive is marked as Leftover or Failed, and data recovery is needed, see "Using the Trust Command" (page 26). |
| Event 8 reports an Illegal Request sense code for a command the disk supports. | If all the volumes and Vdisks or disk groups are online and available, then replace the disk. Otherwise, if the drive is marked as Leftover or Failed, and data recovery is needed, see "Using the Trust Command" (page 26). |
| Event 8 reports that RAID-6 logic intentionally failed the disk. | Replace the disk. |
| Event 55 reports a SMART error for the disk. | If all the volumes and Vdisks or disk groups are online and available, then replace the disk. If the drive is marked as Leftover or Failed, and data recovery is needed, see "Using the Trust Command" (page 26). |
| At the time, a disk failed, the dynamic spares feature was enabled, and a properly sized disk was available to use as a spare. | No action required; the system automatically uses that disk to reconstruct the Vdisk or disk group. Replace the failed disk when reconstruction has completed. |
| At the time, a disk failed, the dynamic spares feature was enabled but no properly sized disk was available to use as a spare. | The best option is to supply an appropriately sized spare so the system can automatically use the new disk to reconstruct the Vdisk or disk group, and replace the failed disk once reconstruction has completed. If that is not possible, and all Vdisks or disk groups are online and your data is available, then replace the failed disk with an appropriately sized disk. Assign the replacement disk as a spare unless dynamic sparing is enabled. |
| At the time, a disk failed, the dynamic spares feature was disabled and no dedicated spare or properly sized global spare was available. | The best option is to supply an appropriately sized disk using the SMU or CLI. Assign it as a dedicated Vdisk or disk group spare and let the system automatically reconstruct the Vdisk or disk group, then replace the failed disk once reconstruction is complete. If that is not possible, and all Vdisks or disk groups are online and the data is available, then replace the failed disk with an appropriately sized disk. Assign the replacement disk as a spare. |
| The status of the Vdisk or disk group that originally had the failed disk status is Good. | Use SMU to assign the new disk as either a global spare or a Vdisk or disk group spare. |
| The status of the disk installed is LEFTOVR | All the member disks in a Vdisk or disk group contain metadata in the first sectors. The storage system uses the metadata to identify Vdisk or disk group members after restarting or replacing enclosures. This disk was a member of a Vdisk or disk group on another system, and that Vdisk or disk group does not exist on this system. Clear the drive metadata if it is not required for a Vdisk or disk group from another array. |
| If the status of the Vdisk or disk group that originally had the failed disk status is OFFL (Offline) or QTOF (Quarantined Offline), one or more disks have failed in a RAID-0 Vdisk or disk group. Two or more disks have failed in a RAID-1, 3, or 5 Vdisk or disk group. Three or more disks have failed in a RAID-6 Vdisk or disk group. | The data in the Vdisk or disk group is inaccessible and at risk. Attempt to recover by reseating the last failed drives. If that does not resolve the issue, and data recovery is needed, see "Using the Trust Command" (page 26). |
| The status of the Vdisk or disk group that originally had the failed disk indicates that the Vdisk or disk group is being rebuilt. | Wait for the Vdisk or disk group to complete its operation. Do not remove any leftover drives until the rebuild is complete. |
| The status of the Vdisk or disk group that originally had the failed disk is CRIT (Critical) or QTDN (Quarantined with a down disk). | If this status occurs after you replace a defective disk with a known good disk, the enclosure midplane might have experienced a failure. Replace the enclosure. |