NAS Can't be written to after upgrade to 0.5.0

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • 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.
timcdn
Newbie
Newbie
Posts: 26
Joined: March 5th, 2010, 5:29 pm

NAS Can't be written to after upgrade to 0.5.0

Post by timcdn »

Hi Guys

Running on a Mac, snow leopard 10.6.2.  I have a NAS that I use for media storage, DNS-323.

Prior to the upgrade I could write to my NAS, now I get the error:

Cannot create complete_dir folder

The strange thing is, I have two volumes on the NAS and I can still write to Volume_1 but not to Volume_2

They are both mounted, I can write to both via finder - but sabnzbd cannot write to Volume_2

Any ideas, because I am out of them.

Thanks

Tim
User avatar
sander
Release Testers
Release Testers
Posts: 9062
Joined: January 22nd, 2008, 2:22 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by sander »

So SABnzbd is running on your Mac, trying to write to your NAS, right?

Ideas:
- is SAB trying to write to a strange/forbidden (root) directory?
- is SAB trying to write as a different/guest user with little rights on the NAS?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
timcdn
Newbie
Newbie
Posts: 26
Joined: March 5th, 2010, 5:29 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by timcdn »

The two volumes have the same rights, same config.  Two days ago I was able to write to the drive - then I upgraded and for some reason I am unable to write to the second drive.

Are there additional setting in SAB now that would prevent me from writing to the drive?
nick5768
Newbie
Newbie
Posts: 4
Joined: March 9th, 2010, 11:00 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by nick5768 »

I am experiencing the same issue.

I have a SMB share mapped to my Z: drive on Windows 7 64-Bit and am unable to change the complete or incomplete download folders.  I get the following error: "Incorrect parameter Cannot create download_dir folder z:\usenet\incomplete".

I am able to change the monitoring folder which leads me to agree with timcdn that it looks like a write permissions issue.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by shypike »

I don't know what type of shares you have, but I have no problem at all with them.
Even when I set the location to a folder on  a read-only share, there's no problem.
(As long as the folder exists and I don't actually download anything).
Win7, XP, Linux, makes no difference.

SABnzbd checks whether a folder exists, if it doesn't it tries to create the folder.
Also the method used isn't really different from 0.4.12.

Are you sure the drives are mounted?
Can you describe the problem in more detail?
nick5768
Newbie
Newbie
Posts: 4
Joined: March 9th, 2010, 11:00 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by nick5768 »

I have FreeNAS 0.7 (revision 4919) machine that has a SMB/CIFS share.

I have that share mounted on my Windows 7 x64 computer as the Z drive (z:\).

I can read and write to the Z:\ through Windows Explorer and any of the other programs I have tried but when I put "z:\usenet\incomplete" into the Temporary Download Folder field (under Config / Folders) and click save I get a new page that says "Incorrect parameter" in h3 tags and below that "Cannot create download_dir folder z:\usenet\incomplete" in text followed by a "Back" button.

Here are the relevant portions from sabnzbd.log:

2010-03-09 16:59:46,565::ERROR::[dirscanner:293] Cannot read Watched Folder z:\usenet\monitored
2010-03-09 17:00:08,700::INFO::[misc:226] download_dir directory: z:\usenet\incomplete does not exist, try to create it
2010-03-09 17:00:08,700::ERROR::[misc:228] Cannot create directory z:\usenet\incomplete
2010-03-09 17:00:41,566::INFO::[misc:226] download_dir directory: d:\usenet\incomplete does not exist, try to create it
2010-03-09 17:00:58,871::INFO::[misc:226] download_dir directory: z:\usenet\incomplete does not exist, try to create it
2010-03-09 17:00:58,871::ERROR::[misc:228] Cannot create directory z:\usenet\incomplete

(These log entries show multiple attempts)

I had a 0.4.12 installation that worked correctly with the same Z:\, upon upgrading it did not work.

I then uninstalled Sabnzbd (with revo uninstaller to get rid of all registry/appdata remnants) and did a brand new installation and still have the same problem.

If there is anything other information that would be helpful just ask, I know I appreciate all the work you guys do on this program!
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by shypike »

Does "z:\usenet\monitored" exist?

The code trying to read the folder (and reporting the error) has not changed between 0.4.12 and 0.5.0.
nick5768
Newbie
Newbie
Posts: 4
Joined: March 9th, 2010, 11:00 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by nick5768 »

I've tried it both ways, same error each time.

I'll fool around with it some tomorrow and see if I can get something more helpful.
nick5768
Newbie
Newbie
Posts: 4
Joined: March 9th, 2010, 11:00 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by nick5768 »

I got it working today possibly by purging the queue (though I also was sometimes running it in safe mode and am not sure if this also contributed in some way).  If timcdn can try this I would be interested to see if it was 100% fixed by purging the queue.
timcdn
Newbie
Newbie
Posts: 26
Joined: March 5th, 2010, 5:29 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by timcdn »

Still getting the error after the purge.

Incorrect parameter

Cannot create complete_dir folder /Volumes/Volume_2/Downloads

But the drive is mounted and I can still write to it using finder.  Also, Plex is able to access the same NAS for video streaming.

If I restart, remount the drives, start sab it works.

Then for no particular reason, it stops working and can't find the mounted drive even though it's still available through finder.

Weird.
dkiar
Newbie
Newbie
Posts: 6
Joined: June 18th, 2011, 6:18 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by dkiar »

Argh so annoying!!
Been using this solid for 12 months.
First in a XP build on desktop hardware, then in a Win764bit build on laptop gear.
All folders point at a Microsoft 2003 server.

Blew the Win764bit away, built Server 2008R2 64bit, every setting set to exactly the same, now i get this error.
If i set folders to local C:\ it works fine; no error. Set to \\sername\folder1\folder2... i get the message people are getting here.... that includes mapped drive, even if the mapping is to the local C:\ !

*sad face*

Intel T7200,


Any help or assistance in the matter would be highly appreciated.

EDIT:

My apologies, I upgraded to 0.6.5 and issue is fixed instantly. I cant believe i missed upgrading :S
Thanks for creating one of the best apps I use. I would pay for this. Just need to figure out what its consistently slower then others.
Last edited by dkiar on June 18th, 2011, 9:30 pm, edited 1 time in total.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by shypike »

dkiar wrote: My apologies, I upgraded to 0.6.5 and issue is fixed instantly. I cant believe i missed upgrading :S
I would pay for this.
Just need to figure out what its consistently slower then others.
1. Which version did you use first? I don't recognize the problem you're describing.
    AFAIK, it always supported UNC (except for the "temporary download folder").
2. You can donate :)
3. You mean SABNzbd is slower than other Usenet programs. Yes it is, mainly because being written in Python instead of C++
    What will make it less a resource hog, is to set an article cache in Config->General (saves disk access).
dkiar
Newbie
Newbie
Posts: 6
Joined: June 18th, 2011, 6:18 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by dkiar »

Hi There,

1 - I "think" i had 0.6.2 installed. I can only guess as it was the only other Sab installer i had on my network.
Like i said, I had Win7 Enterprise 64bit installed on this laptop hardware, simply stuck 2008R2 on it and got the issue, EVERYTHING was setup the same.

At a guess i would imagine its a authenticating thing. I told sab to NOT start at login, and created a scheduled task to start it at BOOT (not a user login) Id associated it with an account that had RW access to the UNC path.
I upgraded and without changing a thing, i was able to place that same UNC path into the folders fields.

2 - If i had more then $3 right now i would. This Wed I'll donate some clams; I like Sab that much.

3 - I'm not all that code savvy, but would its being written in a higher level language like Python make it that much slower? The server never gets over 20% cpu utilization. I have run it on hardware ranging from 600 to the 1156 cpupassmark.com score setup its on now, and its never been able to fill my pipe. Iv come from a competing product that would saturate my 8Mb/s pipe without a sweat.

"What will make it less a resource hog, is to set an article cache in Config->General (saves disk access)."

    Sorry, are you saying i can set the "article cache limit" to see gains in download speed?

Thanks so much for your reply.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: NAS Can't be written to after upgrade to 0.5.0

Post by shypike »

The article caches saves on disk access which is an important bottleneck.
The way articles are assembled into files is rather clumsy and that is
mostly compensated for by the cache.
I can saturate my 100Mbit/sec line easily with rather mediocre hardware,
as long as I use a cache that can hold a complete file in memory.
That's about 11 Mbyte/sec.

The file assembly is one of the oldest parts that's still up for redesign.
Python itself is an issue for two reasons.
It's relatively expensive to do lowel level bit and byte handling
(although yEnc decoding is done by a C module)
and Python's TCP/IP library is not exactly a speed demon.
dkiar
Newbie
Newbie
Posts: 6
Joined: June 18th, 2011, 6:18 am

Re: NAS Can't be written to after upgrade to 0.5.0

Post by dkiar »

Interesting, iv set mine to 128MB.
I wonder why SAB isnt set to use the cache by default.
100Mb/s? wow. I tested Sab against the other reader i was using, messed with settings for weeks but i could never get it to run as fast.
Thanks again for your time!!
Post Reply