This article explains why the alarm continues and the troubleshooting steps to resolve this issue.
After rebuilding a RAID group and reverting the hot spare drive to the hot spare again, the Intel® RAID Controller keeps beeping as if there was an error, which indeed doesn't exist. RAID group and hot spare drive are shown in optimal condition in both Intel® RAID BIOS Console and Intel® RAID Web Console 2 utility.
| Note |
All data should be backed up before proceeding and on a regular basis. |
If a backplane has empty slots and there's an available new drive, proceed as follows:
- Insert the new drive.
- Reboot the system.
- From the RAID console, go into the properties of this new drive (with an Unconfigured Good status) and see if there's a Replace Missing Drive option.
- Select the option, this will trigger the Copy-Back procedure itself.
- Once the process is complete, reboot the system.
If these steps do not work, the RAID volume should be deleted (cleared). Once this is done, re-create the array without initializing. Otherwise, you'll need to initialize the RAID group and restore all data.
Cause:
- This may occur after a drive failure and recovery, manual intervention changing the configuration, and/or reusing failed/removed drives.
- If a drive that failed or was unexpectedly removed from a RAID group is reused on the same Intel® RAID Controller, the drive will be marked as bad (unconfigured bad) by the controller, which keeps physical disk fail history.