After a degraded array completes a rebuild, the beeping continues but with longer intervals than when degraded.
The beeping is due to newer firmware that recognizes when a hot spare replaces a failed drive. The controller is expecting a copy back procedure to put the disk/slot order back to the original configuration.
To perform a copy back:
- After the rebuild completes, insert a new drive into slot one. Beeping frequency changes, but continues because a hot spare does not yet exist.
- Make the disk in slot one the hot spare. The beeping stops, and the prompts to perform a copy back procedure begin. The data is copied from the disk in slot ten to the disk in slot one, and the disk in slot ten becomes the hot spare drive.
You can also stop the beeping by re-creating the hot spare, and choosing whether or not to do the copy back procedure.