I have a 1tb NVME SSD installed and setup as a 'cache' drive. I'm not sure what it's cache-ing, but can I use it as a download drive? Maybe partition it 50/50 for 'cache-ing' and downloads?
I would use it to download / seed before moving files to the main media array. I currently have a download folder on the 'media' array for downloads, which might spin up any of my many drives for downloads or seeding.
Thanks in advance

Just configure whatever share you want to use it however you want.

@YaSo The fact you have a pool called ‘cache’ and the Unraid ‘caching’ facility are two independent things.

The Unraid ‘caching’ capability is configured at the individual share level and can be configured to use any pool regardless of what the pool is called.

Conversely the fact you have a pool called ‘cache’ does not mean it needs to be used for that (although it can be). It is commonly used to support docker containers or VMs.

Hmm, I thought the 'cache' drive was used by the Unraid OS automatically somehow, actually never really knew how it was used. So I can just create a 'download-temp' folder on the SSD and point my downloads there then? No need to partition anything? (I'm coming at this from a Windows user's mindset)

23 minutes ago, YaSo said:

So I can just create a 'download-temp' folder on the SSD and point my downloads there then? No need to partition anything?

Yes. Note that since all top level folders on any pool or array drive automatically get treated as shares of the same name you may just want to call it ‘download’. Where a share resides is controlled in the share settings.

23 minutes ago, YaSo said:

I thought the 'cache' drive was used by the Unraid OS automatically somehow, actually never really knew how it was used

It is not automatically used for ‘caching’ purposes - that needs to be configured where needed at the share level. However by default it IS used for supporting docker containers and VMs.

4 hours ago, itimpi said:

by default it IS used for supporting docker containers and VMs.

Ideally, Docker/VM related shares - appdata, domains, system - would have all files on cache or other pool with nothing on the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

If you want more specific advice

Attach Diagnostics ZIP to your NEXT post in this thread.

OK, I set up a share on the cache SSD. One thing, I can see the new share as a drive letter in WIndows, but unlike my Media share, I don't also see it under 'Network' in Windows Explorer. Afaik, the shares are setup the same way, any idea why Windows 'network' doesn't see it but I can see it as a drive letter?