I have just (re-) installed Sonarr, set up and functioning with Sabnzbd, both running on the same W10 machine and doing everything on a local network share (unRaid network). I can post a log, but it’s basically just an infintie list of :
Import failed, path does not exist or is not accessible by Sonarr: W:\Staging\tv\Downton.Abbey.S01E02.720p.BluRay.x264-SHORTBREHD
If I open up Windows Explorer, that path (W: is mapped to \tower1\disk3 and \Staging\tv is where everything that is downloading goes) works fine and all the files and folders exist.
Note that \tower1\disk3\TV is mapped to Y:\ on the local device - and has all of the series folders perfectly accessible via the Explorer interface.
If I try to manually import the shows…no joy - I get the error in the title [No files found are eligible for import] even though I have an Explorer window open that shows that exact path and an MKV in the folder with the proper name.
Note: I gave up on Sonarr about a year or so ago because I could never get it to recognize a network attached server, and (iirc) the answer back then was “Sonarr doesn’t do network devices, you should store everything locally”. Is it possible to make this work now? I would prefer to re-path everything to UNC, but Sonarr doesn’t seem to recognize it. Suggestions?
If you’re running Sonarr as a service, then by default it runs using the local SYSTEM account which means that it will be unable to view network paths. The workaround is either to run Sonarr manually every time you logon, or set the service to run using your user credentials.
To set the service to run with your user credentials, open the system services (Start -> Run -> services.msc), find the Sonarr service (called NzbDrone), double click on it, then enter your username and password under the Log On tab.
Thanks - it’s currently is running as “me” - logging in under my username, which has administrative privileges.
Is it true that Sonarr still can’t browse UNC paths? I’ve tried but it only seems to offer local, physical disks. Nothing mapped (which makes sense), but it also can’t seem to browse a network location. Is there a switch somewhere which allows this?
Curious - that should work. I set it up in a very similar way myself earlier today and it is working nicely accessing my files stored on an offboard NAS appliance. I presume you restarted the service after changing the service Log On settings?
In my case I did it slightly differently in that I created a dedicated service account and granted explicit access to the file shares, but if you’re using your own account credentials it should just work.
Yes, it was restarted. What’s weird is that everything else sees the server - sab, couch potato, syncback (which runs as a service and uses my login when I’m not logged in directly)…everything.
Let me ask - should I be able to browse the network shares when I set up a show?
edit: to clarify: this is the screen where I think I should be able to browse the UNC path, but can’t:
It does appear that you can’t browse from that level, but if I enter the share name (in my case \nas1\Video\ - with the trailing backslash) then I can browse from there.
FWIW, thats never been our stance. For Windows services + mapped network drives that is 100% the answer though, but thats because Windows doesn’t support them and when they work at first they usually fail later on. Our ((FAQ)) explains some of the issues and possible workarounds.
If you want to use a mapped network drive run Sonarr either as a console window or a tray icon using the startup folder to start it automatically. UNC paths should work fine with Sonarr running as a service, but there may be some issues with authentication since services and logged in users have different contexts (which is the underlying reason why you can’t use a service with a mapped network drive).
This is a limitation of how the file system works, effectively we’re getting a list of folders, but \\nas only lists available shares, not actual folders (Windows Explorer handles showing them in another way) and you don’t start to get directories until the slash is added at the end because thats when Sonarr first gets a folder to work with.
Thanks for the reply - it could be I was trying shares, but I think I hit a brick wall at the UNC versions as well. Knowing that someone else can browse UNC paths gives me hopw.
I’m not certain what the issue was, but running as an application works - it can see the network drives via UNC paths (or, at least it can get the free space). This is a machine that I can always logged into, and I can set to autologin on restart, so I’ll go with that for now. Obviously that doesn’t solve the problem, but at least it’s a workaround.
