Repairable files not being repaired automatically?
Posted: 22 Apr 2020, 17:25
I've just started using NZBGet after having previously used SabNZBd for some time. I swiped over because eI was told it was a less power hungry system.
My setup is simple, I have a Synology DS1019+ and I'm using the linuxio Docker image of NZBGet. it's allowed 4gb of ram and processing power isn't limited to it. All files download to a local disk in theNAS
When I first set it up, it was downloading slower than my old setup but a bit of searching and I got it to be at least as fast as the old setup was, if not a little quicker.
My issue is that it downloads a file, then seems to put the file in the history, looking at the file in history it's tagged as repairable. It then does nothing more with the downloaded files. Radarr software appears to think the file has failed and tries to download another version. As far as I can tell, I have all the unpack settings set to auto repair and unpack a file, is ether something not so obvious that I'm likely to be missing here?
Also, extracting seems to be much slower than SabNzbd too? There must be a settings somewher that I'm missing?
My settings are as follows:
Check and repair
CrcCheck : YES
PArcheck: Auto
ParRepair: Yes
ParScan: Exetnded
ParQuick: Yes
PArBuffer: 2048MB
PArThread: 0
PArRename: Yes
RarRename: Yes
DirectRename: Yes
HealthCheck: Delete
ParPauseQueue: No
Unpack
Unpack: Yes
DirectUnpack: Yes
UnpackPauseQuere: No
UnpackCleanup: No
Everything else left as was
Download Queue:
Flush Queue: No (was slowing it down to much as yes)
ContinuePartial: No
Article Cache: 200
Direct Write: Yes
WRitebuffer: 0
Filename: Auto
ReorderFiles: Yes
Poststratergy: Balance
Hopefully somebody can spot something! Thanks in advance to anyone who looks to help.
My setup is simple, I have a Synology DS1019+ and I'm using the linuxio Docker image of NZBGet. it's allowed 4gb of ram and processing power isn't limited to it. All files download to a local disk in theNAS
When I first set it up, it was downloading slower than my old setup but a bit of searching and I got it to be at least as fast as the old setup was, if not a little quicker.
My issue is that it downloads a file, then seems to put the file in the history, looking at the file in history it's tagged as repairable. It then does nothing more with the downloaded files. Radarr software appears to think the file has failed and tries to download another version. As far as I can tell, I have all the unpack settings set to auto repair and unpack a file, is ether something not so obvious that I'm likely to be missing here?
Also, extracting seems to be much slower than SabNzbd too? There must be a settings somewher that I'm missing?
My settings are as follows:
Check and repair
CrcCheck : YES
PArcheck: Auto
ParRepair: Yes
ParScan: Exetnded
ParQuick: Yes
PArBuffer: 2048MB
PArThread: 0
PArRename: Yes
RarRename: Yes
DirectRename: Yes
HealthCheck: Delete
ParPauseQueue: No
Unpack
Unpack: Yes
DirectUnpack: Yes
UnpackPauseQuere: No
UnpackCleanup: No
Everything else left as was
Download Queue:
Flush Queue: No (was slowing it down to much as yes)
ContinuePartial: No
Article Cache: 200
Direct Write: Yes
WRitebuffer: 0
Filename: Auto
ReorderFiles: Yes
Poststratergy: Balance
Hopefully somebody can spot something! Thanks in advance to anyone who looks to help.