I have several Supermicro servers with LSI Megaraid controllers, 9266-8i. One recently lost a drive; I replaced it as usual, but it is still beeping on reboot. It is set up as RAID 10 + hotspare.
MegaCli64 -AdpEventLog -GetEvents -f events.log -aALL && cat events.log shows me:
Event Description: Global Hot Spare created on PD 08(e0xfc/s0) (global,rev) Event Description: Reminder: Potential non-optimal configuration due to drive PD 08(e0xfc/s0) commissioned as emergency spare
Since the beep pattern is 1 second on, 3 seconds off, which is the code for "SPEAKER_HOTSPARE_ENTRY - A hot spare drive has completed the rebuild process and has been brought into the array", I assume this is the root of the problem. I have updated to the latest firmware, since the release notes mentioned the "Potential non-optimal configuration" message, but no change.
Anyone have an idea on how to clear this?
Source: IBM tip H206526
There is no functional impact. To prevent the message from appearing in the system event logs:
- Open MegaRAID Storage Manager.
- Select Tools --> Monitor Configure Alerts.
- Select Change Individual Events.
- Highlight event ID 406.
- Deselect the System log check box.
Having a similar issue here. Configuration is an Intel RS2BL040 RAID controller (rebranded LSI I'm sure). 4 hard drives in a RAID10 configuration.
Failed drive was replaced months ago. Server was rebooted for the first time and RAID controller started beeping even though everything shows as optimal. I noticed a drive (assuming the drive that was installed recently to replace the bad drive) shows "Emergency Spare: Yes" in its properties. The other drives show "No".
I have not noticed the "Non-Optimal" message in the server logs, but the issue seems to be the same. I tried adjusting this setting for event ID 406 in RAID Web Console but the beeps still occur when the server is rebooted until the alarm is silenced.
Intel says it's OK to leave as-is (which I don't like), or they recommend clearing the RAID10 configuration and recreating without initializing. They claim that this will clear the "Emergency Spare" flag on the drive and my data will be intact (but that I should backup first of course).
I don't like it, seems there should be an easier/better solution! Sounds like a firmware bug.
I have LSI controller, RAID 10 with four disks. One disk went bad, hot-swap replace -> automatically set hot spare flag on new disk and got same warning as above. Turn machine off, physically remove replacement disk, separately did quick format to unset RAID participation, replaced disk and turned machine on. Automatically found disk and started rebuild into RAID with unset hot spare flag.
Trick seems to be finding time when machine can be shut down for cold-swap with fresh disk.
I encountered this situation when I replaced bad drive (in Raid 10 with four drives) with hot-swap. LSI megaraid automatically set emergency spare flag during new drive build.
I cleared this by later removing the new drive with computer powered down, separately did a quick (re)format to clear the RAID data, then replacing drive prior to repower/boot. The new drive was discovered fresh on boot and rebuilt into the RAID with emergency spare flag off.