January 10, 20251 yr Hey guys, would really appreciate your help since I haven't found an answer on the forum yet. My Unraid server has the following configuration: Array Parity: HDD Disk 1: SSD Disk 2: HDD Shares appdata, system, isos, domains, MinecraftData -> Primary Storage: Array, Included Disks: Disk 1 (SSD), Excluded Disks: None MediaShare -> Primary Storage: Array, Included Disks: All, Excluded Disks: Disk 1 (SSD) Both HDDs are configured to spin down when not in use (after 15 mins). This is important to me since the server is close to my bed and I don't want noisy disks rattling in the cabinet at night. I've only used my server for occasional media streaming via Jellyfin so far, and the disks behaved as expected: Since the appdata-Share is only allowed to reside on the SSD, the Jellyfin-Container did not spin up any HDDs when I did not use it. Only when I accessed Jellyfin to watch movies, did my HDDs spin up. After finishing watching on Jellyfin, the HDDs spinned down and everything was fine. I now started to host a Minecraft Server (Image: marctv/minecraft-papermc-server) as a container. The appdata-Share is still the same (bound to the SSD). I also had to define a place for the MinecraftData-Folder which stores the world map, settings, ... . I created a user share named MinecraftData with the above-mentioned settings and passed it on to the container, expecting it to never spin up any HDDs whilst not in use and only spin up the parity disk when in use. The server works, but the parity drive is active and keeps spinning the entire time - regardless of any players actually on the server or not. Since the server is close to my bed, I can't keep the server running all the time (if I want to catch any sleep). ? How can I host the Minecraft Server on my SSD without keeping the HDD parity disk spinning 24/7 ? Whilst writing this post, I question if I've set up my disks correctly and if I should've used the SSD in a cache pool instead? Maybe the Minecraft Server is accessing the SSD all the time, which triggers the parity disk all the time... I'm very thankful for your help 😄 Edited January 12, 20251 yr by ThinServerAdmin Issue got solved
January 10, 20251 yr Community Expert Solution Typically SSDs should go in a pool outside the array. SSDs in the array cannot be trimmed and can only be written at parity speed. Any writes to array data disks also updates parity at the same time.
January 10, 20251 yr Community Expert And you want all files for the Docker/Vm related "default" shares on a pool also so Dockers/VMs will perform better and so array disks can spin down since these files are always open. https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares
January 12, 20251 yr Author Hey @trurl thanks for the clarification. I've shrunk my array, created a cache pool with the SSD, assigned my appdata/system/MinecraftData/... shares to the cache, struggled with Docker since it didn't recognize its docker.img file anymore, but now I've got everything set up and running as expected! CA AppData Backup does a regular backup to my array to keep the data more secure. Thanks!
January 12, 20251 yr Community Expert On 1/10/2025 at 4:42 PM, trurl said: And you want all files for the Docker/Vm related "default" shares on a pool also so Dockers/VMs will perform better and so array disks can spin down since these files are always open. https://docs.unraid.net/unraid-os/manual/shares/user-shares/#default-shares You can see how much of each disk or pool is used by each user share by clicking Compute... for the share on the User Shares page.
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.