My array currently has two SSD’s in it.

Because the array doesn’t support TRIM I have been led to believe this is a bad idea.

The NVME drive currently has my appdata and my VM data on

The other SSD has my plex metadata on.

I want to move both of these drives to unassigned but without losing the data and without the drives being emulated by the array, so I can re-map my appdata and VM’s and metadata after they have been moved.

Is this possible? If not what would people recommend?

 

Tools - New Config, assign disks however you want, leaving out those SSDs. Be sure you don't assign any disk with data on it to any parity slot. Then start the array to rebuild parity based on the disks assigned to the array. The SSDs you have removed will be mountable with Unassigned Devices plugin.

Thanks for that. I have a few questions, based on your suggestion.

1. Will the data in the new array will stay intact?

2. I currently have my shares writing to specific disks will this need to be updated, I assume so as drive numbering will change?

3. Will my array be available during parity rebuild?

4. My SSD's are currently formatted to the Array format, does this matter when using them as unassigned disks?

5. Would their be any harm in leaving them where they are, as I understand it, write performance is impacted but read performance which is important for VM's and plex metadata is not, what is the impact of not having TRIM, would having them as unassigned drives give them TRIM?

1. yes
2. yes
3. yes
4. Unassigned Devices can read all Unraid filesystems as well as many others.
5. An alternative approach would be to take advantage of the multiple pools feature in 6.9 and put them in another pool for use by dockers and VMs. That is what I have done.