Synology disk utilization 100% when downloading/unpacking

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
Teapot418
Newbie
Newbie
Posts: 2
Joined: April 17th, 2023, 2:09 pm

Synology disk utilization 100% when downloading/unpacking

Post by Teapot418 »

When I download using Sabnzbd (also tried Nzbget same problem) my NAS slows down. When I check the resource monitor the disk utilization is 100%.

In order to solve this problem I bought an NVMe SSD (Volume2) and use it as a volume. I moved all docker containers to Volume2 disk. Every path in Sabnzbd is points towards Volume2.

Here comes the weird part. When this problem occurs Volume2 disk utilization is about 20% but Volume1 (HDD) is 100%.

Does anyone know how this is possible? I checked the processes in the resource monitor but they don’t show which process causes this.
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:

Re: Synology disk utilization 100% when downloading/unpacking

Post by safihre »

Did you have enough Article Cache setup? Because it could be using your volume1 if your sabnzbd.ini is stored there.
This you can see in the first page of the Config.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Teapot418
Newbie
Newbie
Posts: 2
Joined: April 17th, 2023, 2:09 pm

Re: Synology disk utilization 100% when downloading/unpacking

Post by Teapot418 »

Thank you for your reply. Just to make sure I mounted the config folder to my ssd folder even though the container should be installed on the SSD also. Unfortunately it did not resolve the problem..
Post Reply