Jump to content

Library access SMB Error


nbat58

Recommended Posts

Has anyone had a similar issues were the library scanning can't access the NAS server were the media is stored?

The Emby server is on the Nvidia Sield 16gb and the library scanning was launched form a windows 10 pc.

 

The media is stored on a UNIX NAS server OmniOS (this is practically the same as CentOS):

 

Below is an extract from Emby log:

 

    SharpCifs.Smb.SmbException: SharpCifs.Smb.SmbException: Failed to connect: 0.0.0.0<00>/192.168.1.28
      at SharpCifs.Smb.SmbFile.DoShareEnum (System.Collections.Generic.List`1[T] list, System.Boolean files, System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00194] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.DoEnum (System.Collections.Generic.List`1[T] list, System.Boolean files, System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00072] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.ListFiles (System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00006] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.ListFiles () [0x00000] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.SharpCifsFileSystem.ListFiles (SharpCifs.Smb.SmbFile dir, System.Boolean recursive) [0x00000] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.SharpCifsFileSystem.GetFileSystemEntries (System.String path, System.Boolean recursive) [0x00010] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileSystemEntries (System.String path, System.Boolean recursive) [0x0000e] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at MediaBrowser.Controller.Providers.DirectoryService.GetFileSystemEntries (System.String path) [0x00010] in <b123a5df771042b08ba153add7d7ebc4>:0
      at MediaBrowser.Controller.IO.FileData.GetFilteredFileSystemEntries (MediaBrowser.Controller.Providers.IDirectoryService directoryService, System.String path, MediaBrowser.Model.IO.IFileSystem fileSystem, MediaBrowser.Controller.IServerApplicationHost appHost, MediaBrowser.Model.Logging.ILogger logger, MediaBrowser.Controller.Library.ItemResolveArgs args, System.Int32 flattenFolderDepth, System.Boolean resolveShortcuts) [0x00000] in <b123a5df771042b08ba153add7d7ebc4>:0
      at Emby.Server.Implementations.Library.LibraryManager.ResolvePath (MediaBrowser.Model.IO.FileSystemMetadata fileInfo, MediaBrowser.Controller.Providers.IDirectoryService directoryService, MediaBrowser.Controller.Resolvers.IItemResolver[] resolvers, MediaBrowser.Controller.Entities.Folder parent, System.String collectionType, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions) [0x0008c] in <93946144fbd34f2ba494ac56f8d20c0d>:0
    SharpCifs.Util.Transport.TransportException: I/O error occurred.
      at SharpCifs.Util.Transport.Transport.Connect (System.Int64 timeout) [0x001c2] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbTransport.Connect () [0x00006] in <93946144fbd34f2ba494ac56f8d20c0d>:0
    SharpCifs.Util.Transport.TransportException: Connection timeout
      at SharpCifs.Util.Transport.Transport.Connect (System.Int64 timeout) [0x0012d] in <93946144fbd34f2ba494ac56f8d20c0d>:0
    
    
    Source: Emby.Server.Implementations
    TargetSite: Void DoShareEnum(System.Collections.Generic.List`1[system.Object], Boolean, System.String, Int32, SharpCifs.Smb.ISmbFilenameFilter, SharpCifs.Smb.ISmbFileFilter)
      at SharpCifs.Smb.SmbFile.DoShareEnum (System.Collections.Generic.List`1[T] list, System.Boolean files, System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00194] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.DoEnum (System.Collections.Generic.List`1[T] list, System.Boolean files, System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00072] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.ListFiles (System.String wildcard, System.Int32 searchAttributes, SharpCifs.Smb.ISmbFilenameFilter fnf, SharpCifs.Smb.ISmbFileFilter ff) [0x00006] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at SharpCifs.Smb.SmbFile.ListFiles () [0x00000] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.SharpCifsFileSystem.ListFiles (SharpCifs.Smb.SmbFile dir, System.Boolean recursive) [0x00000] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.SharpCifsFileSystem.GetFileSystemEntries (System.String path, System.Boolean recursive) [0x00010] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileSystemEntries (System.String path, System.Boolean recursive) [0x0000e] in <93946144fbd34f2ba494ac56f8d20c0d>:0
      at MediaBrowser.Controller.Providers.DirectoryService.GetFileSystemEntries (System.String path) [0x00010] in <b123a5df771042b08ba153add7d7ebc4>:0
      at MediaBrowser.Controller.IO.FileData.GetFilteredFileSystemEntries (MediaBrowser.Controller.Providers.IDirectoryService directoryService, System.String path, MediaBrowser.Model.IO.IFileSystem fileSystem, MediaBrowser.Controller.IServerApplicationHost appHost, MediaBrowser.Model.Logging.ILogger logger, MediaBrowser.Controller.Library.ItemResolveArgs args, System.Int32 flattenFolderDepth, System.Boolean resolveShortcuts) [0x00000] in <b123a5df771042b08ba153add7d7ebc4>:0
      at Emby.Server.Implementations.Library.LibraryManager.ResolvePath (MediaBrowser.Model.IO.FileSystemMetadata fileInfo, MediaBrowser.Controller.Providers.IDirectoryService directoryService, MediaBrowser.Controller.Resolvers.IItemResolver[] resolvers, MediaBrowser.Controller.Entities.Folder parent, System.String collectionType, MediaBrowser.Model.Configuration.LibraryOptions libraryOptions) [0x0008c] in <93946144fbd34f2ba494ac56f8d20c0d>:0

Edited by nbat58
Link to comment
Share on other sites

Can you try instead mounting the SMB path as a local path on your server machine, and then add that local path to Emby? Let me know how that compares. Thanks.

Link to comment
Share on other sites

Sorry do you mean on the machine running the Emby server or the NAS server, I have also tried adding a windows 10 PC with media on it with the same result.

Link to comment
Share on other sites

Not sure how that is done on the Nvidia Shield, I have been doing some searching without success, on the shield the server is recognised and mounted without any prompts for IP address input.

Link to comment
Share on other sites

Well this sure looks familiar, got a Shield with 2 NAS and since the v4 update I don't have access to my libraries either. Looking at my logs I see "SmbException: Failed to connect to server", not quite the same error you seem to get but almost an identical problem still...

 

Hope it gets sorted out soon :unsure:

Edited by acutech
Link to comment
Share on other sites

unhooked

Settings/storage&reset.

 

Transfer files over local network turns the shields' samba server on and generates a username/passphrase combination.

 

Mount network storage lets you mount other devices smb shares.

 

The shield smbd has been buggy in the past and you might have to toggle into that to give it a kickstart occasionally.

 

Mounting shares works well too, except emby isn't doing whatever nvidia requires to grant remote write access, so you can't delete or record to nas. (you could do an anon world write share but that would just let anything nuke your files - or worse)

 

The exception here seems to be that whenever plex is writing to your share, everything else uses those credentials. Like, whenever I pvr in plex emby is able to generate .nfo files and delete files.

Not sure if there's another trick one could pull to make that full time, but read only access is generally all I need.

 

mounts are made available under the /storage tree.  (/storage/GET/Shared/PVR) is my nas recording drive which is exported from the host - get, and the share name/export name /Shared.

Edited by unhooked
Link to comment
Share on other sites

The answer most likely is that we don't support any authentication at this time for SMB shares, so unless they're shared anonymously over the network then it won't work.

Link to comment
Share on other sites

I have managed to get the NAS recognised, it was strange, I just had to remove the manual IP when choosing a folder on the server and instead picking the chosen folder path that Emby suggested and the NAS is recognised and the content has been scrapped, however, I can't manage for the life of me find the path of the windows PC with media on, when I input manual the IP address as in \\192.168.1.65 emby does not find or recognise the path.

 

Is there an easy solution to getting Emby to find and recognise the Windoes 10 path and IP?

  • Like 1
Link to comment
Share on other sites

All is well now that I have downloaded the latest 4.0.1.0 all theh folders and drives are recognised.

 

Thank for all the help.

Link to comment
Share on other sites

Funny cause I had to use the IP address instead of the hostnames Emby was suggesting... I have used the path emby suggested and then replaced the hostname with the ip address and it started behaving normal again...

 

Glad you got it working.

 

Cheers,

Link to comment
Share on other sites

@acutech: There's always more than one way to skin a cat :D , well done, glad yours is bahaving as well, I will be doing more testing in the next few days, then it will be Emby Premiere trigger pulling, I won't be using all the features but I don't mind as this helps further developements and features.

 

On another note: I have just posted on the Anroid Emby app forum as I've got the .avi files that won't play at all, I am sure it may be either the Shield Android or Emby settings to tweek (I hope..., as I won't have the time to convert all of those avi files of mine).

Edited by nbat58
Link to comment
Share on other sites

Funny cause I had to use the IP address instead of the hostnames Emby was suggesting... I have used the path emby suggested and then replaced the hostname with the ip address and it started behaving normal again...

 

Glad you got it working.

 

Cheers,

Interesting, thanks for the info !

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...