0 B/s download speed even for test files

[anon_ac13]

From one to the next moment my SABnzbd stopped working/downloading anything at all.

I have to admit that my space was full and I moved some stuff, but now it got > 300 GB free space left. But even the 100 MB test file won't download. It does queue up as forced item, but it won't download.

The connection to the server is working fine. The log just says added to queue and pause and resume, but nothing else Any clues?

I am running version 4.3.2 in a docker container if that helps.

[sander]

Reboot your system?

[anon_ac13]

Reboot your system?

I tried that without success. If I would at least have any hint what to look for

[sander]

Reasons for SABnzbd to pause:

* SABnzbd is paused by the pause/play-button in the upper left corner
* SABnzbd is paused because there is not enough disk space
* SABnzbd is paused because of a scheduled pause (so time-based, see Schedule)
* SABnzbd is paused because there is no working / active Newsserver (check with Server -> Test Server)
* SABnzbd is paused because all individual downloads are paused
* SABnzbd is paused because a category (Config -> Categories) is set to priority Paused

[anon_ac13]

Reboot your system?

Apperently after thinking about it ... I did not restart my system, but only sabnzbd itself and the docker container, but not the system.

So I restartet the whole system and see what?! It does work

Thanks again

[anon_ac13]

Well... it ain't over yet ^^ After some time it just goes down to 0 again and won't continue downloading at all. Rebooting the system all the time now is no solution

[anon_ac13]

but now I did find something in the logs after this behavior kept repeating: reboot system - everything fine. after a while - down to 0 B/s.

here is the log:

https://pastebin.com/Mn4yRH49

[sander]

only a few lines, no reboot ...

Post all lines

[anon_ac13]

I just copied the lines that seemed useful to me. And my guess was right (so far).

I was already wondering, if my harddrive is not working properly anymore. The delays are probably coming from writing/reading errors.

I swapped the harddrive to a different one and now everything is working fine!

Problem solved: Issue was a defect harddrive. Hint: Assembler delays in the log