greenskye

If this is what you do and you're not having problems, then it seems simpler. Maybe my system was just too old + my config issues were causing the problem. Wow, can't believe I've had that backwards for like 7 years. Updated the mover and pinned the CPU in NZBGet to CPU 0, so hopefully that helps. Between this and a new system, I'm hopeful this is no longer an issue. Since it's a consumer motherboard it doesn't have quite enough ports. Or it does if I was going with all high capacity drives, but spending a bit for an HBA card and giving me plenty of Sata ports seems useful. Plus I've been itching to get a rackmount case for my server rack and this helps justify the upgrade And the iGPU would maybe be enough, but I've already got the Quadro and it's working so why not. In your opinion is it worth buying a higher size than normal parity drive just to not have to replace it for a bit or better to just stick with your chosen 'standard' size? I'll admit this is mostly an emotional decision for me as I almost always buy drives one at a time. Never getting to actually 'use' my latest drive because it's always the biggest and therefore becomes parity was annoying to me (started out with 4 TBs drives, then didn't get to use my 8 TB until the next year when I bought a second 8 TB, same story for when I upgraded to 12 and then 14 TB.) But I'm not sure if I'm just being ridiculous about it. The last several years I tend to buy 1 drive every black friday, but I know lots of people drop $$$ on a bunch of drives all at once. Maybe this time I should just stick with 3x 18 TBs with 1 being parity instead? It means when I do buy a 20 or 22 TB drive next time I don't get to use it though...

Ok, hadn't looked into CPU pinning before. That seems like a good option for usenet. My plan is dual NVMe drives for appdata as a cache pool, mirrored. It looks like the new ZFS options would be good for this? (At least in 7.0). Should appdata and usenet unpacking be on the same cache drive? Or have two cache pools? I have spare sata SSDs I could throw in simply for separating apps from active downloads/unpacking. So I'm not sure what I've configured wrong. I have a /Downloads share (cache only) and a /Media share (Cache enabled). But copying a completed file from /Downloads -> /Media takes forever. Like sometimes 20-30 minutes. So if I download something I want to watch right away it takes a tediously long time to become available in Plex. I don't understand why the process is so slow, because both locations should exist on the same SSD cache drive. Should be writing from /Downloads ssd location -> /Media ssd location and then the mover moving it into the main array nightly. But it's so slow. I want the move from the download location to it's final media location (ignoring if it's in cache or main array) to be faster so it shows up in Plex sooner. Honestly I don't even understand what a user in unraid is even for? So far it's just me who accesses it so I think I just gave myself all permissions. I just didn't know if I was supposed to do something like have an admin account and separate account for when I access files via SMB or something. Current build is: Xeon E3-1225 Supermicro X10SL7-F 20 GB DDR3 ECC Quaddro 2200 1 TB Sata SSD 36 TB array (14 TB Parity, 12 TB, 2x 8 TB, 2x 4 TB) Proposed new build (repurposing old gaming machine, marked with *) *i7-9700k *MSI MPG Z390 GAMING PLUS ATX LSI 9400-16i HBA card *32 GB DDR4 *Quaddro 2200 2x 1 TB NVMe for appdata/cache pool mirrored (ZFS?) Reuse existing 1 TB sata SSD for download cache? Purchase much larger parity drive (tired of keep having to upgrade it). 24 TB? 26 TB? Purchase some new high capacity data drives (2x 18 TBs?) Reuse any >= 8 TB drives from existing system. I also have a wide variety of small sata SSDs (500 GB or less) and older HDDs (4 TBs or less) if needed for anything, but I mostly assumed they weren't worth the space.

I'm finally looking to update my aging (~2017) unraid server (first build). It's... sort of been cludged together and while it functions, I know it's not very optimized. The plan is to build a completely separate server and copy files over. I have several questions on current best practice and my searches have been inconclusive. The server is used mostly for Plex/*arrs (Mostly usenet, with a little bit of torrents). But I'd also like to expand into backups and Home Assistant. Zero plans for VMs. Trash vs SpaceInvader share structure I believe I currently have roughly a SpaceInvader share (though to be honest I didn't follow his guides, just muddled through). It's kind of a hodgepodge that I'd like to clean up I have two main problems I'd like to fix: 1. My entire system slows to a crawl whenever usenet is unpacking something. My understanding is that the unpacking process is maxing out my single cache SSD, which is also what runs all my apps and is why I have issues. I believe the recommended fix is multiple cache pools. One for appdata and one for downloads/unpacking. I don't fully understand how to set this up however. 2. I semi-frequently want to watch something that I've downloaded asap, but it takes forever to move the files to my media share. My understanding is that the Trash guide solves for the second problem, but I don't know that it solves for the first problem. Ideally I'd like a solution that solves both problems, but if that's not possible, then I'd prefer to solve the usenet unpacking issue as a priority. With these considerations I'm not sure how to setup cache? Should I do 1 cache pool for apps, 1 for main share and 1 for usenet unpack? Other Settings I'm also unclear on other general settings and things that might no longer be best practice. When I first setup my server parity check was run weekly. I think I've seen that this is no longer recommended? When and how often are recommended for parity, mover, trim, etc? Best practice for users and security? Any other settings to take a look at? valhalla-diagnostics-20250113-1442.zip

I'm not sure if this was what others meant by 'force update', but here's what worked for me: 1. Change docker tag to 'latest' and apply 2. Check for updates. A new update for Sonarr should appear 3. Apply update 4. Successfully migrated from preview -> latest!

Also experienced the same issue. Just moved back to preview for now, but can't figure out how to successfully migrate back to stable branch.