The thing you should have done is to start a new thread.
I think we are going to need to do some CLI (command line) things to get this fixed.
Hot-Spares are only activated by the complete failure of a drive that is having problems. I don't know what you did here, but you appear to have activated a spare, and also somehow added another mirror. It is a really strange looking situation.
I don't know how this happened, because I don't know exactly what steps you took, but I think we can clear this up. Just don't worry about it too much because you have fully three disks holding the data for that vdev right now, so you should't have any risk of data loss.
If you give the model number of the system, I could tell you for sure, but the 48 bay chassis I am familiar with should do this. You need to be able to SSH in from a terminal, I like Cygwin, but you can use PuTTY if you like. It is just so you can use the command line. The command is
sesutil locate da10 on
to start the light blinking, then
sesutil locate da10 off
when you are done. It works in systems that have a SAS expander backplane. I have (at work) system from Supermicro, Chenbro and QNAP that all work with that.
Don't need the serial number, just the da#...
If you need to get the device number from the gptid, you can use
glabel status
to show the gptids and da#..
The drive
Code:
gptid/5e600107-cb7b-11e5-8fa9-002590c44bba
is the spare, and the GUI doesn't make it clear but you say,
I would use glabel status to be certain.
From the command line, you can't address the drive by the da# for this, so you must be able to relate the da# you are working on back to the gptid, because the pool was formed using the gptid, not da#. You should be able to give the command,
detach SM2_stable_pool gptid/5e600107-cb7b-11e5-8fa9-002590c44bba
which should return the spare to the spare group.
Please do that and let me know what the result is.