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.
I've followed a few docs and got SAB to install and tron on my pi. Everything seems to run ok but now I'm finding problems with the pi connecting to my news server. From the server config the test fails. I can ping the server and the credentials are correct.
I think there was 2 issues.
1) I had some weird permissions on the incomplete folder - I fixed them up and it seemed to help.
2) The biggest problem is using a low quality microusb cable. This caused the voltage to be about 4.2V which caused the network to keep dropping. I changed it out to decent cable and now get 4.9V - no more network drops and it runs at full speed. (With SickBeard running in memory as well)
bigdavethehorn wrote:Any tips on stabilising SAB on the Pi? I have successfully downloaded a 123MB file and a 2GB file, however anything larger seems to crash the Pi.
What kind of crash? What's the verbose output of SAB?
And: what does your "free -m" show during the download?
I'm not sure what kind of crash unfortunately, I run SAB on a schedule from midnight until 08:00. When I attempt to view the queue in the morning, I can't access SAB remotely (via http), or the Pi direct via VNC, SSH or keyboard.
The solution appears to be switch it off and on
I'm running Debian Wheezy and SAB, that's about it. I haven't yet adjusted the "8192 kbytes" setting in Wheezy, is it worth a shot?
Ok, I increased the vmin setting from 8192 to 16384 and added smsc95xx.turbo_mode=N in /boot/cmdline.txt
I think it worked, maybe to early to tell just yet, but I managed a couple of large downloads (3GB & 10GB) and the Pi was still responsive in the morning.