I've moved my UnRAID array over to ESXi and unfortunately one of the disks in my array (Samsung SM951) is not compatible with hardware passthrough and this will not be able to be mounted to the array.  Luckily the only data I had on that disk was some software ISO's which I can easily replace via backups.

 

So my question is, what's the procedure for removing this "missing" disk from the array so I can bring my array back to a protected state?

Screenshot of current array and then Tools > New config

Screenshot of current array and then Tools > New config

 

Thanks!

Getting parity back in the right slot is the critical part.  Note that at Parity Sync will initiate after a New Config.

I've moved my UnRAID array over to ESXi and unfortunately one of the disks in my array (Samsung SM951) is not compatible with hardware passthrough and this will not be able to be mounted to the array.  Luckily the only data I had on that disk was some software ISO's which I can easily replace via backups.

 

So my question is, what's the procedure for removing this "missing" disk from the array so I can bring my array back to a protected state?

You should never have a SSD in the array.

You should never have a SSD in the array.

Never is a strong word.

 

I did read on the forum that some people have had no problem with SSD on array (beside write speed being slowed down by the parity HDD but read speed is still good).

 

I think the "never" only applies to the parity disk cuz LT says they are not sure how TRIM would affect it.

I think the "never" only applies to the parity disk cuz LT says they are not sure how TRIM would affect it.

 

Trimming any SSD on the array, be it parity or data, would probably cause parity sync errors, on v6.1+ TRIM is disable and not possible on array devices, so it's not an issue, even so using SSDs on the array is not supported by LT because their internal garbage collection algorithms could lead to sync errors, all evidence indicates that this is not an issue, but anyone using one should at least do frequent parity checks in the beginning, if any unexpected sync errors are found the SSD should be removed from the array or it can compromise a disk rebuild.