LSI 9361: Alarm Continues After Rebuild with Emergency-Spare State
Problem
The source describes an LSI 9361 controller that continued beeping after rebuild, with a drive showing emergency spare: yes or commissioned spare: yes. If the condition is unclear, collect controller logs and contact the vendor support channel given in the source: lckf@ieisystem.com.
Case cause and scope
The vendor describes a RAID 1 member being moved to another host and rebuilt with an empty drive. Afterward, the drive retained both member and emergency-spare attributes. The article lists LSI 9361 cards, but this cause must be confirmed from the actual controller/drive state; a continuing alarm can also require other diagnosis.
Source resolution
Confirm backups, drive identities and array health before following a procedure that removes a member or triggers a rebuild. These steps apply to the described spare-state case, not every rebuild alarm.
- Open Ctrl Mgmt. Clear Maintain PD Fail History and apply the change.
Before: Maintain PD Fail History is checked.
After: Maintain PD Fail History is unchecked; the other pictured settings are retained.
- Set Emergency Spare to GHS (Global Hot Spare) and save.
- For the confirmed affected drive, the source instructs removing/reinserting it and allowing rebuild. If several drives show the condition, process only one at a time and wait for its rebuild to finish successfully before touching the next. Do not remove another member if redundancy has not been restored.
Broadcom documents Emergency Spare as a controller policy with None, UG, GHS and UG/GHS choices. Here GHS is the source’s policy selection, not an instruction to arbitrarily convert a data member into a new hot spare. The two source images illustrate the history checkbox; they do not show the Emergency Spare selector.