Ok, I think I want to change some things up with my hard disk setup to better optimize my setup. Right now I have 5 disks in array with 1 parity for 6 total. My parity is a 5tb HDD, then for rest of my array i have 2 - 5tb, 2 - 4tb and 1 - 256gb SSD.

 

My concern comes down to my SSD setup. On that disk I have it set aside for Dockers, Plugins and VM's only. My main applications being Plex, ruTorrent and a Windows 10 VM. Plex and my Windows 10 VM are usually on 24/7. So I believe this means my SSD and my Parity drive are always spun up? The parity already has to do a lot of read and writes but this added workload from my current setup I think can be fixed.

 

I have 2 unused 128gb SSD set aside right now. I believe what I want to do is only use 1 of them to setup my new Docker, Plugin, VM drive for unRaid. But what I want to have this setup outside of my raid array in unraid, but setting it up as a cache disk. Not necessarily for the performance part, but just for the fact it does not require the parity drive to be spun up.

 

Does this all sound like I am headed in the right direction of what I want to do? I really dont need to copy my VM data from the SSD, but my docker, plugin folders would be ideal if possible.

 

Would appreciate some input for this, thanks in advance for the help!!!

I use 2 x 120GB SSD in btrfs raid1 cache which is supported by unRAID. Whether you do it that way or with just a single cache disk, I have always recommended putting your apps etc on the cache disk instead of the array since writes to cache do not involve parity. Also better than a disk mounted outside the array because unRAID already manages the cache disk for you. Just put your apps, VMs, etc in shares set to Use cache disk: Only.

Would there be a simple way to remove my ssd from the array and make it the cache drive without losing any data?

You will have to rebuild parity without the SSD using Tools - New Config and assign the SSD to the cache slot. You might back it up first just in case. Ask if you can't figure out the details.

Ok, while I believe that I understand how to use the New Config, I'd like to double check before I proceed.

 

 

Here is my current setup.

 

My big question is, when removing my SSD with the New Config tool, can I reassign my other data disks to new drive positions as well? So my 5tb are now in slots 1&2 and 4tb in 3&4?

 

Will this affect my user shares disk assignments too?

 

Thanks in advance for the help.

Yes you can change the slots as you like. Just be sure you don't assign a data drive to the parity slot! If you have any shares configured to include or exclude specific disk numbers then you will have to update those settings for the new numbering.

I must admit, going in blind using the New Config tool sure did pucker up my butthole.

 

After all is said and done, I was able to re-assign my hard drives in descending capacity and move my SSD to the cache slot.

 

The only hiccup was the user shares. I think I have it all straightened out now.

 

Just to make sure I have it setup correctly, I want all my data disks to never us cache, and then my SSD to only use cache?

 

Lastly where does the mover backup the cache drive too? I was able to setup a schedule but nothing about a directory.

The only hiccup was the user shares. I think I have it all straightened out now.

 

Just to make sure I have it setup correctly, I want all my data disks to never us cache, and then my SSD to only use cache?

You do not set whether a disk uses cache - you set whether a User Share uses the cache.

 

Lastly where does the mover backup the cache drive too? I was able to setup a schedule but nothing about a directory.

Mover does not backup the cache.  What it does is copy files belonging to a User Share that is set to use the cache to the data disks (using the strategy set for the user Share).  It does not copy any files belonging to User Shares that are set to be cache only.