Now possibly looking at filenames being the issues since they're hashed. If Im understanding correctly your setup you have sabnzbd on a windows 10 box than Radarr/Sonarr running in a dockers on unraid. So far all settings we've walked through step by step are set but it's not working. The disk usage is above 90 in these times. While unrar or (automatic) unpacking the whole NAS gets very slow and almost unreachable. I am having similar issues, however, with any files movies, music, or tv not being able to import. NAS with sabnzb unrar/unpacking consumes too much CPU & disk usage. I've checked permissions on the NAS folders but there are no differences between 'tv' and 'movies'.Īpologies for the incomplete paths above but as a New user I am not allowed to post links.ĭid you ever get anywhere with this? I am on sonarr discord working on this very thing. I also have Radarr configured for Movies, which is working correctly, using similar config but being delivered to (nas - Movies). 'No files found are eligible for import in Downloads - complete - sander Release Testers Posts: 8568 Joined: January 22nd, 2008, 7:22 pm Re: SABnzbd-3.1.0Beta1 open always unrar window by sander September 3rd, 2020, 12:40 pm I can confirm: a quick popup of the CMD window, and then it's gone. after renaming/copying the file is locked again (because plex is scanning the new file) and sabnzbd copies it. ![]() on windows the file gets locked this way so it cannot be renamed and sabnzbd starts copying it. the moment a new file is placed created plex will try to scan it. However, Sonarr should be looking to pick up these files and carry out the rename and move to my QNAP NAS unc path (nas - TV) but this isn't happening, for ANY tv episodes.Īs an example: the activity queue in Sonarr shows episodes as 'Downloaded - Waiting to Import'. In my case the output folder is being watched by another program (Plex). I have configured TV episodes to write C: Downloads - incomplete which then correctly moves to C: Downloads - complete once complete. I am running Windows 10 with the latest version of Sonarr and sabnzbd. I read that it is common for files to get corrupted during uploads to USENET.Ailgim wrote: ↑ February 22nd, 2020, 10:07 am I thought as long as I selected "add recovery record," and set it at 100% the upload should be good! But I guess I was wrong. I have never see this bevor on other versions. I use latest SABnzbd-3.1.0Beta1 and always whene i start a download i get a DOS Windows from urar.exe. So, I was wondering, is there a collective maximum size limit on split files that SABnzbd can handle? I didn't bother using PAR2 because I felt the file I was uploading would have become far larger than the file was worth. Oh, yes, one other possiblity: maybe the problem is in your unrar version 3.x. SABnzbd-3.1.0Beta1 open always unrar window. I Usually get either "missing files," or "can't unpack," etc, etc. 16GB, 18GB files), I noticed that SABnzbd has difficulty extracting the RAR'd files. ![]() However, when I use WinRAR for really large files (ex. ![]() ![]() I've noticed that when I archive files using WinRAR (100mb split), and upload those files to USENET, SABnzbd extracts those files with no problem. I wasn't sure if my assumptions were true. I have tried to disable 'Direct Unpack' but the result is the same. The unpacked files still get the date/time stamp they have in the archive, not the date/time of unpacking. I was hurrying up to leave work! LOLOL I should have reread this. I have checked the switch 'ignoreunrardates' to ON and restarted SABnzbd. Oh damn, I really apologize, I didn't realize who bad I screwed up this post. I've tested downloading with SAB using nzb's that contain only WinRARs. AnythingOldSchool wrote: ↑ January 31st, 2020, 6:20 am
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |