![]() You mean greyed out like this with a tick in it? And it's using all your cores according to your dashboard? And we've said it's included? Yeah, it's using multicore. I've checked in unraid's dashboard whether all cores are in use during a verify and unpack and they seem to be (although there not maxed) i just wanted to ask whether it was nomal that the "Enable Multicore Par2" option was greyed out? I read earlier in the thread that the multicore par2 was included in this container? I've entered the "Extra PAR2 Parameters" as -t+ but was concerned that if the enable multicore par2 option was greyed out it wouldnt be using it? Hi guys, I'm running the latest container of linuxserver.io's sabnzbd. Thanks for any help provided! I've spent hours trying to solve this annoyance and I think I've exhausted all my ideas. I can attach error name and log info tonight, but was hoping someone already came across this same issue and could comment. I have removed/deleted and reinstalled the Docker with no change.When I turn off sorting, it completes without issue.I have passed it files from Sickbeard and Sonarr with the same effect.I have reset permissions through unRaid (with newperms), as well as setting permission to 777 inside SAB.It is set up identically to the other instance of this docker.I didn't capture the exact error name, but can add more info tonight). Also, SAB throws up a post processing error (Apologies. I can manually delete the folder without issue. The problem is that whenever I enable Sorting in SAB, it performs the sort, moves the file to the correct spot, but is unable to delete the source folder and the _ADMIN_ folder inside it. Works perfectly on one, and almost perfectly on the other. I have this docker running on two machines. ![]() So I have encountered some odd behaviour. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |