Hello,

 

I had some SSDs that I added to the array to test some stuff but I don't want them in the array anymore. How can I completely remove them from the array and not have the red Xs in my configuration anymore. I don't plan to ever replace them. Do I have to go create a new configuration? If so, what happens to the data on the disks now?

 

Thanks.

-Tools -> New Config -> Retain current configuration: All -> Apply

 

Go back to the main page, unassign the SSDs and start the array, parity will be re-synched, data on the array disks won't be touched.

I assume that your method Johnnie will result in an unprotected array while the parity is rebuilt, right? I am looking at the method below so as to protect the array the entire time. What do you think?

 

It looks like this post in the section "The "Clear Drive Then Remove Drive" Method"

9 minutes ago, srfnmnk said:

What do you think?

 

It's a valid option, it will mean an extra write cycle on the SSDs though, not sure the script still works with latest unRAID but manual mode works for sure.

I think I'd rather have a single write cycle on the SSD than a read/write on all the other disks in the array including the 5TB parities, wouldn't you?

 

the script seemed to still work. Validating parity now...I have some HighPoint controllers (working on a switch to LSI) so parity checks are always eventful but I figured I'd try one nonetheless after removing the SSD. ::fingerscrossed::

4 hours ago, srfnmnk said:

I think I'd rather have a single write cycle on the SSD than a read/write on all the other disks in the array including the 5TB parities, wouldn't you?

 

It depends, I have backups so I'd use the 1st option, faster and less wear on the SSDs.

 

Also, if you're doing a parity check before it's going to do the same I/O as the 1st method, only difference is reads instead of writes on the parity disks, but like I said earlier it's a valid option to keep the array protected and I've used it before.

 

 

Cool, thanks Johnnie, I don't have backups, I have a little too much data to manage backups. Thank you for your feedback.