the_names_james

I've recently come across another issue; sometimes NZBget will download a file fully but gets stuck on the unpacking stage. This usually occurs after a file is added to an empty queue, and persists regardless of how many items are added to the queue (first item hangs at unpack, everything else awaits PP). Restarting the container fixes the issue and allows NZBget to pick up where it left off - as soon as the container is restarted it begins unpacking - however until it's restarted the unraid main page shows constant writes to the cache. This can go on for hours and the cache remains at an elevated temperature until I restart the container. Is there a setting I can adjust to minimise the chances of an unpacking freeze?

Removing the docker, deleting the Radarr folder inside appdata and reinstalling fixed all issues. Cause still unknown but at least it's been cured.

Not quite sure what's going on here but I've been stuck seeing this whenever I try to access radarr from a web browser. Issue started last night. I can access the radarr main page from my phone where I'm shown a mobile version of the site, the issue only seems to occur when I try to access it from windows PC's. Does anyone have an idea why this is happening? Or what I can do to resolve it? Also as a separate whenever I try to update library I get a failed message. Again, this has only been happening since last night.

Perfect, thank you

Is there a way to have nzbget’s intermediate folder on an unassigned drive? Right now everything is located on my cache pool with all paths coming off the root directory; is it possible to relocate the InterDir to a separate disk? If I try to reassign the InterDir to /mnt/[UD]/intermediate it just creates a new path inside the root directory

Mobo port isn't seen/working but I have a spare pcie single port card and since switching to that I haven't been able to replicate the issue so I guess, for the meantime at least, I'll have to put it down to a hardware problem.

add on intel pci NIC

I recently started a trial and have the server set up as it should be. I assigned a static IP rather than allowing DHCP to assign it however I'm experiencing random network disconnects which can only be resolved by restarting the machine. I have the exact same problem regardless of whether I bond my ports or use a single port. When I say random, it often happens when I'm navigating through the shares via windows explorer although not exclusively. Attached is my diagnotics zip, any help resolving this would be greatly appreciated. tower-diagnostics-20190502-1249.zip