1 of 1 people found this helpful
The controller by its self can not mark a drive as a spare to rebuild from this is down to the driver and software in windows.
If you say it happened without you setting a drive as a space or was never asked in windows to rebuild on another drive then this is a bug to which what driver and software for the RAID was you using when this happened? Was it Rapid Storage Technology 9.6 or an older Matrix Storage Manager?
Message was edited by: PeterUK
turns out the end user WAS asked if he wanted to rebuild the array using the 3rd drive and he answered, "yes" , so I'm pretty sure it wasn't marked as a spare initially.