SABnzbd Forums

Hey Guys,

I've very recently been introduced to SAB and managed to get this setup in conjunction with Sickbeard on my QNAP. All looked to be well until the QNAP started to throw a few errors - initially around the HD's overheating.

Checking the system log I get literally thousands of the below errors (which vary very slightly):

"The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [Misc], field = [System Started], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance."

I have had to disable SAB for the time being but thought I'd give you the feedback so you can keep up the excellent work

Hope that helps. If there is any workaround or resolution please holler!

SABnzbd Version: 0.5.3
Python Version: 2.7
QNAP Model: TS-439 Pro II
QNAP Firmware Version: 3.3.1 Build 0720T

What is the RAM disk used for?
If SABnzbd starts writing it's "cache" folder to to,
then I can imagine that it will become full very fast.
Do you have any SABnzbd folders located on the RAM disk?

Hey Shypike,

I have configured all the folders to use the raid array to store all complete, incomplete, cache etc data by using the web-based folders are of the UI. Whilst SAB has an active download in process I have monitored these folders and am pretty sure that they are not being used during the download process at all i.e. there was no growth in file size.

I have checked the SABnzbd.ini file and sure enough all directories are pointing to the right place but there still seems to be an issue. To perhaps throw a little more light on the topic, the thread below is the exact issues I have:

http://forum.qnap.com/viewtopic.php?f=1 ... sk#p154837

I have replied to this in hope I might get a bit of extra detail to assist. Any thoughts?

The board is not accessible to me.
But even so, I doubt if I can help with solving more general NAS problems.
I have no idea what /etc/config/uLinux.conf is used for.
SABnzbd doesn't use it, maybe the other programs do (like SickBeard)?

Thanks for the response. I reckon its too late in the process for Sickbeard to be to blame here, seems like the problem hits as soon as SAB tries to unpack a download. I think it is here that in some way the RAM Disk is being used.

If anyone else has any thoughts please shout up!