Support Forum

Where did you see those log entries?
They shouldn't be there..

Sorry forgot to post that I found the problem and it will be fixed in 1.2.1!

I will add a check to make sure we start from the right volume.

Of course it will first try the lowest sever. Because usually people use an unlimited server as their primary, and a block account as a secondary server that should only be used in case the unlimited server doesn't have the download.

First all articles will be tried on the server with the lowest priority.
Then, it will directly try the second lowest priority (server B) when the lowest priority (server A) doesn't have it.

You're very welcome to submit a change on our github repo: https://github.com/sabnzbd/sabnzbd

The sorting code hasn't been changed in a long while!

Usually this happens when a download is discovered that is missing from all your (primary) servers.
SAB will try all articles first on your primaries, then move to the next level and try them all there, and so on.
The more servers you have configured, the longer it takes.

Fixed it, will be in 1.2.1!

Thanks so much for helping us! That's some great debugging there.

We removed the TryList at the NZBQueue-level, could you see if this fixes it?
https://github.com/sabnzbd/sabnzbd/arch ... rylist.zip

Will be fixed in 1.2.1!

Do you have you enable_unrar turned on in Config Specials?

Indeed!

Oh yes, indeed the dirscanner will continue..

Let us know indeed

If you're not connected to the interface and you're not downloading to the disk, SAB won't access it and it will spin down.

It's probably something to do with the number of servers and some timeouts. We have heard more problems of stalling (non starting) downloads, but just can't reproduce it..