Page 1 of 1
SABnzbd+ on FreeNAS 0.7.2
Posted: May 21st, 2011, 2:08 am
by tacov
Hi,
I've installed SABnzbd+ 0.6.0 on FreeNAS 0.7.2 and I've added a 2 TB HDD to my NAS server.
In FreeNAS, I've created a mountpoint for the hdd: /mnt/Taco/
Now the problem is that SABnzbd+ is saying that there is only 0,01 GB free space, while there is in reality 1.8 TB free space.
Please take a look at the following screenshots, however they are in Dutch, it should be recognizable what it is, if not please ask.
Image 1
Image 2
What should I set as downloadfolder for sab to see the correct disk?
Thanks in advance.
P.S. In image 1, the completed download and incomplete download folder is the same, but I've already editted that.
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 21st, 2011, 3:47 am
by shypike
On some systems, Python reports an incorrect amount of diskspace.
We cannot fix that in SABnzbd.
The only thing you can do is ignore it and *not* set a free space limit in Config->Folders.
(Or look for an upgrade of Python).
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 21st, 2011, 9:00 am
by tacov
Sadly it does not work when I set the minimum available space to "0". It still won't download any more than 77 mb.
The current version of python that I have installed is python 2.6.
I think python 2.6 is the latest version available for FreeBSD 7.3...
Do I have any other options?
This is a screenshot from my FreeNAS webGUI, where I have configged the mountpoint. Isn't there another way to config the download folder than mnt/Taco/downloads/complete?
Image 3
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 21st, 2011, 9:39 am
by shypike
tacov wrote:
Isn't there another way to config the download folder than mnt/Taco/downloads/complete?
Not sure what you mean. You mean set it to another path in SABnzbd?
Sure, just enter the full path.
BTW: currently your path start with "mnt/Taco/...", I think it should be "/mnt/Taco/...".
Without the leading slash it's a relative path, but I cannot see the base path at the top of the screen.
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 21st, 2011, 2:02 pm
by tacov
shypike wrote:
tacov wrote:
Isn't there another way to config the download folder than mnt/Taco/downloads/complete?
BTW: currently your path start with "mnt/Taco/...", I think it should be "/mnt/Taco/...".
Without the leading slash it's a relative path, but I cannot see the base path at the top of the screen.
Yes I tried that also, but it gives the following error:
Cannot create download_dir folder /mnt/Taco/downloads/incomplete
But the directories are actually there, I've checked it on SSH.
I think this is part of the problem, it should start with a slash.
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 22nd, 2011, 5:47 am
by shypike
If SABnzbd cannot create /mnt/Taco/downloads/complete,
then either it doesn't really exist or SABnzbd lacks the permission to create it.
Given that the error message claims SABnzbd cannot create the folder,
it seems to me that SABnzbd cannot see it in the first place.
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 22nd, 2011, 5:49 am
by tacov
shypike wrote:
If SABnzbd cannot create /mnt/Taco/downloads/complete,
then either it doesn't really exist or SABnzbd lacks the permission to create it.
Given that the error message claims SABnzbd cannot create the folder,
it seems to me that SABnzbd cannot see it in the first place.
I have found the problem: I didn't chmod the mountpoint.
I entered: chmod -R 777 /mnt/Taco
And then it did let me change it in sab and it displays the correct freespace now
Thanks a lot for your help
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 22nd, 2011, 5:58 am
by tacov
It is kind of weird though, I have a 100 mbit internet connection and I only get 3,2 mb/s in sabnzbd. I should get at least 10 mb/s.
Any idea why it could be slow?
Re: SABnzbd+ on FreeNAS 0.7.2
Posted: May 22nd, 2011, 6:01 am
by shypike
Possibly because SABnzbd is CPU and memory hungry.
It depends very much on your CPU.
Any recent PC/Apple should no problems.
On a an single-core Atom-based system running Server2003, I get about 5 MBytes/sec
from a 100 Mbit/sec fiber.