jhbunraid

Unfortunately, this has not helped. The cache is currently 'full' (it's hit the min free space set of 30GB) and on opening Sonarr and Radarr they say 'unable to open database file'. Both containers are set up use data share set to cache only.

I was about to reply and say I am doing this but I've just realised I set the min size on the share and not the cache pool! I'll do this now. Thank you.

Hi. First post, go easy on me! I've been using Unraid for a few weeks now, made some mistakes, fixed some, learned a lot. My latest is leaving SABznbd downloader to fill my cache pool and expecting it to spill into my array, which it did. However, my docker containers became unresponsive because cache had run out of space and appdata share was set to cache only. Make sense... now. My shares... SABnzbd operates incomplete and completed downloads into media. The cache is made up of 2 x 500GB SSDs which is great for redundancy for data (aka appdata (not sure why I renamed it from default now!)) and system, anything other than media(?). Therefore, I think I should just buy 1 x 4TB SSD, place it on a separate pool and assign media to use it. Regardless of whether 4TB is overkill, in principle is this sensible, won't work, or something in between? Or should I be operating one pool and use sub pools which means buy something like 2 x 4TB SSDs? I've not read up lots on sub pools yet, sorry.

That's good to hear. Changing the RAM slot didn't help me. Then I started more specific research about the motherboard. I found a few reports of all Intel 13th and 14th gen CPUs having issues. Then found the Asrock support page for the motherboard said there a specific setting for Intel suggested settings if you have instability. Well, the screenshot of the settings is not that of v17+ firmware but I found a setting at the bottom of CPU config section which was disabled. Having enabled it my server's been up for its longest time now and I've been running parity and downloading constantly to cache and moves to array and streaming Plex all to try and stress it. It's having no problems so far.

Sorry, I can't read. Saw you mentioned the i3-14100 but you're actually thinking about getting that one. I wouldn't based on my build.

Last week I built your build, well sort of. I have a Asrock Z790 Pro RS with i3-14100. I am getting crashes multiple times a day. Best I've had is 16 hours. I also saw "weird display output". Rest of the build is: 16GB Corsair Vengeance DDR5 RAM 2x 20TB Toshiba N300 3.5 HDD (Array) 2x Crucial T500 500GB SSD (cache pool) Thermaltake PF3 850 PSU I've tried: >Memtests - all good. >Updated BIOS. >Swapping USB boot drives - using USB 2 slot, USB 3.2 Slot, USB-C slot. >Change SATA cables. >Plugged into and not into UPS. >Changed docker from macvlan to ipvlan. >Set up logs to persist and nothing is logged at time of crash. >Uninstalled all plugins and containers. >Monitoring temps, nothing getting very hot. Most resent (30mins ago) I've swapped the RAM from slot B2 to A1. How is your stability since your last message?