Support Forum

Could you maybe see in the log if there's a traceback for that "Saving X failed" and post it here? It's right below the message in the log.

External can work, but would normally always say to do incomplete folder on internal drive.

You should update your unrar to unrar-nonfree, not the free one that comes with some OS'es.
Is that possible?

What version of SABnzbd?
Can you try 1.2.1RC1?

Try setting the number of connections to 8, does that help?

Aaah a VPN.. That explains.
We build safeguards in 1.2.0 to make sure it doesn't slowdown on a VPN, but seems not to be working..

If the drive isn't available when SAB is started (for example Windows wasn't done mounting it yet), it will revert back to using the default derectories.
You can set the Special setting 'wait_ext_drive' to increase the amount of seconds SAB should wait for it to become available on startup.

In 1.2.1 it will be fixed, from then on the HTML will be removed from that line.

What were you using before? 1.2.0?

Tell us a bit more about your setup: what OS do you use? What version of Sabnzbd? Do you not have Rar listed on your Cleanup list? Are all categories set to +Delete? Next we can inspect the log. If you turn on Debug logging in the Status window and then see what is in the par2 section. Probably some...

It's a bug! Found and fixed it, will be in the next 1.2.1 release.

It's probably something sabnzbd does wrong.
We didn't invest much time in the sorting recently, with everybody using apps like Sonarr or sickbeard.
But if you have some python knowledge, you can always come and help us fix this, since you have the best real life test setup

Can you try deleting your sabnzbd and sabnzbd settings completely (you can see the settings file location on first page of Config). And then reinstall fresh.
It seems something got wrong with the settings.
And make sure to use sabnzbd 1.2.0.

You should try and reinstall python disttools and/or setuptools and/or packaging (it's a pip module). Either using pip or apt.

If SB accesses the file exactly when SAB is trying to rename it, Windows will not allow a rename and Python/SAB chooses the hard way of just copying.
In 1.2.1 we will put a workaround to wait 3 seconds and then try again a simple rename, before doing the last-resort copy.