Support Forum

If you put it on pastebin I can try taking a look at it. If you're not comfortable doing that then you can try emailing it to safihre. It's possible that this was fixed very recently because there was a problem that could cause stuff like this. If you want to try the latest build and have a Github a...

I don't think it can guess the category if it's not in the nzb file but there are various other ways to select the category. Have you seen https://sabnzbd.org/wiki/configuration/3.4/categories ?

It's supposed to abort the downloading or finish by itself, but sometimes it breaks if an article disappears from the internal list. Do you have debug logging enabled? Click the wrench to check. Click Show Logging on the same window to download the log file. I suspect that this can happen if one of ...

What happens if you su to the sabnzbd user and try to run it?

If they're all unlimited then try to give them all the same priority. Have you tried varying the number of connections for each server?
https://sabnzbd.org/wiki/advanced/highspeed-downloading

The original problem may be related to an issue in the regex package.
https://github.com/morpheus65535/bazarr/issues/771

SABnzbd has no ability to make files WinDirStat can't see and it doesn't seem like you've tried to follow my suggestion for disabling SSD caching systems, but sure, suit yourself.

If you can see the file name(s) then google it to find out what you're using and how to disable it. If not then you have to check if any of the available systems are enabled on your PC. The most popular ones are probably Microsoft Superfetch and Intel SRT/Optane.

As an alternative to tracking all the articles it could have an option that makes it redownload incomplete files. It's not ideal but it would fix the issue in this case.

Try using https://windirstat.net/ to find out where the data is stored and what it looks like. Maybe you're using some sort of SSD cache?

I have no idea how to fix this but it might be helpful if you could run
GDK_SYNCHRONIZE=1 sabnzbdplus -b1 -l2

and see if it stops after the exact same log line.

There are problems at various stages of unpacking the 100MB test so I'm suspecting a hardware problem. Could be cause by a range of things, like overclocking, overheating, bad RAM or disk problems.

Please click wrench, enable debug logging, do the 100MB download again, click wrench, show logging, and post the relevant part on pastebin or similar.

So, that is the same as clicking "Retry", right? No, he's using duplicate postings of the same content. If one has a bad part1.rar and the other a bad part2.rar and they're uncompressed then par2 may be able to use good data from the other posting to recover the content. I've tried it mys...

Seems like your default pip3 program installed the module for Python 3.8 even though your default python3 is 3.7.