May 10May 10 Hey guys, I’m honestly not sure what direction to take my Unraid build anymore.I started years ago with a small X99 setup and 16GB of RAM, then slowly upgraded and added more stuff until it turned into a full EPYC server. Now I’m trying to clean it up and figure out the best long-term storage layout instead of just randomly adding drives.Current setup is basically:- EPYC server on ASRock Rack ROMED8-2T- 128GB ECC RAM- GTX 1070 passed through to a Windows 11 VM- 12TB parity- 8TB + 4TB + 8TB XFS array- 2TB Samsung 990 Pro ZFS pool for Docker/VMs- 1TB Samsung 980 Pro cache/ingest pool- Extra 1TB NVMe, SATA SSDs, and two matching 8TB HGST drives unassignedAlso, is there any way to get a real read/browsing cache in Unraid?I don’t mean the normal write cache where new files hit SSD first and mover sends them to the array later. I mean something more like: when I browse folders, search files, open photos, thumbnails, etc., it feels faster and doesn’t have to hit the spinning drives every time.
May 10May 10 Community Expert 3 hours ago, chryz said:I don’t mean the normal write cache where new files hit SSD first and mover sends them to the array later. I mean something more like: when I browse folders, search files, open photos, thumbnails, etc., it feels faster and doesn’t have to hit the spinning drives every time.ZFS pool with an SSD based special vdev will do this, all the metadata (and small files, if you want) will be on the SSD, you can browse folders much faster, and the disks won't spin up until you actually read/write a file, but it's a pool, so it loses some of the Unraid array advantages. But it also has some, like better general performance.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.