SABnzbd Forums

Hi all,

I have 2 Qnaps. Well say Qnap 1 and Qnap 2.

Qnap 1 is where my TV files are and Qnap 2 is where SABnzb is.

Qnap 2 has my library path mounted from Qnap 1. So when on Qnap 2 I can see all my TV files from Qnap 1. SAB can see them as well.

But when downloading new files SAB says the drive is full, even tho it is not.

Below are a few screenshots to hopefully help.

https://www.dropbox.com/s/dlzgeke3sasb9 ... 6.jpg?dl=0

https://www.dropbox.com/s/q3qgyzvhp8m6d ... 6.jpg?dl=0

First guess: that directory /mnt/rf/nd/.... is not accessible for the account SAB is running under. Could be a typo, not mounted, or maybe a rights things

If you can handle command line on your QNAP, and you can find the location of SABnzbd, and you understand the below, you can verify like this:
Also, on the NAS with SAB, what is the output of

Beware using that mount location: QTS won't reliably give the same mount the same path each time the share is mounted.

Might be better to manually mount the share from QNAP 1 on QNAP 2 (at the CLI)... that way you can ensure it'll always mount to the same place.

Not sure, but I think I've read in the SABnzbd notes not to use network locations for your downloads. I'll check this and post back.

Haha, just missed it.

@sander, can SABnzbd use a network share for the download path?

OneCD wrote: ↑April 23rd, 2022, 1:24 am @sander, can SABnzbd use a network share for the download path?

Oh, this is risky to answer ... let's try.

Of course ... as long as SAB does not know it's a network share

SAB does not know or care about what kind of drive it is, as long as the host OS presents it as normal, usable disk space. Criterium: does "ls <blabla>" or "dir <blabla>" work. If so, SAB can use it (plus it needs writing rights, and free disk space)

SAB cannot mount shares itself.

Thanks mate.

Best-guess (until the OP responds) is that the location they've configured in SAB for Downloads is one of the remote share mounts available in the QNAP FileStation app.

These are mounted onto a very small drive: ... so, if the current mount location is different, SAB will be trying to write to a 66MB drive. Naturally, this will fill-up quite quickly.

Maybe just a semantic thing: "drive says full." ... Better to say "SAB sees 0 GB free space"

sander wrote: ↑April 23rd, 2022, 1:19 am First guess: that directory /mnt/rf/nd/.... is not accessible for the account SAB is running under. Could be a typo, not mounted, or maybe a rights things

If you can handle command line on your QNAP, and you can find the location of SABnzbd, and you understand the below, you can verify like this:

Code: Select all

sander@witte2004:~/git/sabnzbd$ python3
Python 3.8.10 (default, Mar 15 2022, 12:22:08) 
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from sabnzbd.filesystem import *

>>> diskspace_base("/tmp/")
(116.37757873535156, 27.542598724365234)

>>> diskspace_base("/does/not/exist/")
(0.0, 0.0)

>>> diskspace_base("blamount://nonsense/stuff")
(0.0, 0.0)

>>>

Also, on the NAS with SAB, what is the output of

Code: Select all

ls -al /mnt/rf/nd/0/<and al the rest>

Wow! Thanks for the fast help guys!

I'm ok with cli but not great at what commands to run. so any and all help will be appreciated.

But here's my output on the Qnap with SAB.

[~] # ls -al /mnt/rf/nd/0/<and al the rest>
-sh: syntax error near unexpected token `newline'
[~] # ls -al /mnt/rf/nd/0/
total 0
drwxrwxrwx 3 admin administrators 60 2022-04-22 07:29 ./
drwxrwxrwt 3 admin administrators 60 2022-04-22 07:29 ../
drwxrwxrwx 4 admin administrators 80 2022-04-22 16:06 040f1300d2dc65d71a0153f2a63942bd1daecb78/

OneCD wrote: ↑April 23rd, 2022, 1:53 am Thanks mate.

Best-guess (until the OP responds) is that the location they've configured in SAB for Downloads is one of the remote share mounts available in the QNAP FileStation app.

These are mounted onto a very small drive:

Code: Select all

[~] # df /mnt/
Filesystem                Size      Used Available Use% Mounted on
none                     66.0M     42.7M     23.3M  65% /

... so, if the current mount location is different, SAB will be trying to write to a 66MB drive. Naturally, this will fill-up quite quickly.

This is the output from this command.

[~] # ls -al /mnt/rf/nd/1/
/bin/ls: cannot access /mnt/rf/nd/1/: No such file or directory
[~] # df/mnt/
-sh: df/mnt/: No such file or directory

Just to clarify.

When I said it was mounted I ran remote mount. When looking at it now and kind of understanding your posts I don't think this is a true mount.

So ... solve the mounting, make sure the mount is seen at OS level (check with the ls command), and then SAB will be happy again.

Thanks Sander,

Can you tell me the best way to go about mounting another drive from another qnap as I'm not familiar with that?

This is what I'm using now, but doesn't work.

/mnt/rf/nd/0/040f1300d2dc65d71a0153f2a63942bd1daecb78

Fubie wrote: ↑April 23rd, 2022, 3:23 pm
Can you tell me the best way to go about mounting another drive from another qnap as I'm not familiar with that?

No, I can't. I've never used a QNAP.

But to avoid mounting stuff, you can run SABnzbd on your QNAP 1.

That's the catch. I have TV show's on 1 qnap and movies on the other. So either way I will need to mount a drive to another Qnap.

What protocol are you using for your shares? SMB, NFS, etc...

What are the LAN IP addresses for each QNAP? Which is QNAP1 & QNAP2?