There's no command to force a spare into the raidset.   Before you attempted to move it out of the pool will will involve a lot of IO activity on that member, do you have a backup?     If so, or when you do.  You  could during a quiet IO period try to fail the controller over and see if the passive controller when it picks up the drives will see the need to rebuild.   If you do decide to migrate the array out  of the pool, and if you have critical volumes that will fit on ONE member you can BIND volumes to individual members.  it's slower but would prioritize your volumes vs. moving the member to another pool will not allow that.   Also do not DELETE that member.  Create a new pool, and move that member to that new pool.  Once it's there, THEN you can delete it.   When you add it back into the group, please don't use RAID5 anymore.  Use RAID6.    Regards,  Don     
I have a PS6000 that shows a warning of degraded. When I look at the Group manager, all disks show online and status healthy.  I logged into the CLI and ran the diskview -j to see the status of the disks. [IMAGE] [IMAGE] which drive do you think would be causing the degraded status?  Could it be drive 9 ?  GUI shows all are working and spares are fine.  Could it be a false warning?
PS6000 shows degraded but GUI shows healthy.