I have a storage space in server 2012 R2 (migrated from Win8) that is in an unhealthy state. It's a parity space on a pool that has two dedicated journal drives. The journal drives are no longer in our plane of existence and have been replaced in the pool with two new journal drives, however, I cannot remove the old journal drives as they are in a "Lost Connection" state.
Connect-VirtualDisk responds with "Failed." - no error code or other message. Same from the GUI.
Attempting to remove the offending disks from the pool, I get an error code that tells me they are still in use by the storage space. So I repair the storage space and the repair command completes, with no change (it still won't use the new journal drives). I've set the old drives to "retired", no change, I can't remove them from the pool as they are still in use by the storage space.
How can I convince the storage space to use the shiny new journal disks and let go of the old ones so I can remove them from the pool? The space hadn't been written to in months, so I don't believe there's a risk of data corruption. It doesn't really matter anyways, I'd gladly give up a few write operations to have the rest of the 6TB to be readable again.
Remove physical disks from pool - error "disks in use" - disks in "Lost Connection" state
Add new journal disks to the pool - no error
Repair storage space (to get it to use the new journal) - no error, doesn't do anything
Bring virtual disk (space) online - error - unhealthy state - won't use new journal disks
Any thoughts on getting the space to use the new disks or on letting the old ones go ?