redmumba

This has been extremely helpful; as far as the shares go, if I point my docker container at my `media` folder on the array, and I configure the share to use a cache drive, will docker itself read through the cache, or will it always read directly from the underlying disk?

What about the "cache" drives? Based on all the documentation and videos, in 6.x it seems like these were "first class citizens." What does that look like in 7.x? Just a pool named "cache"?

I'm migrating off a self-managed store to unRAID because, well... I'm tired of maintaining it. However, I am totally lost as to how the storage management works--and yes, I have [read through the documentation](https://docs.unraid.net/unraid-os/manual/storage-management/). Basically, what do I do when I have vastly different storage disks? For example, right now I have: * 128G flash drive that unRAID lives on (Samsung Bar Plus) * 1TB m2 NVME which has historically been where the operating system resides * 1TB 2.5" SSD (store thumbnails and other stuff for Immich for fast access) * 2x 2TB 5400RPM , zfs mirrored (photos using Immich) * 2TB 5400RPM (frigate clips) * 2x 14TB EXOs X16s, zfs mirrored (movies, TV shows, etc.) When I initially set this up, I basically modeled it like I would a normal system. However, I'm realizing that this is the "wrong" way of doing this as I have no "array" disks specified so everything is basically a cache. What's the right way to model storage when there are significantly differences in capacity?