New Ubuntu Setup, attempting to give emby access to a TrueNas SMB

[bastionntb 20]

As the title states.

TrueNas Info: TrueNAS-12.0-U6.1

Emby Info: 4.6.7.0

Ubuntu Info: 20.04

 

I always end up pulling my hair out of my head when attempting to get Linux to talk to file shares.

I'm a little inexperienced with it, so any help would be appreciated.

 

What I've done:

I've got the user "emby" on TrueNAS, and in the course of trying different things, I've matched the user IDs on both sides.

I've created a group called "networkaccess" and given it to Emby, again trying different things, I've added the group to both the emby server, and TrueNAS.

I've created a storage pool from TrueNAS, given "networkaccess" full rights. Additionally, I've given everyone full rights on the ACL.

For the share itself Everyone has full rights.

 

Why does this not work? Do I need samba on the emby server as well? Can it not access SMB otherwise?

 

Any help would be appreciated. Thanks!

[Q-Droid 989]

If it's between Linux and FreeBSD then why use a Windows filer protocol? Have you tried NFS?

 

[bastionntb 20]

3 hours ago, Q-Droid said:

If it's between Linux and FreeBSD then why use a Windows filer protocol? Have you tried NFS?

 

Thanks for the response!

 

I'm using SMB because Windows Devices use this share, (Unrelated to the request) I'm trying to convert all of our server environment into Linux, but our desktops are still Windows.

 

I have tried NFS, and I encountered similar issues, resulting in me trying to match IDs of users and such.

[Luke 42078]

What you could try is mounting the network share to a local path in the operating system, then add that local path into emby server instead of the smb share. Please see if that helps. Thanks 

[bastionntb 20]

5 minutes ago, Luke said:

What you could try is mounting the network share to a local path in the operating system, then add that local path into emby server instead of the smb share. Please see if that helps. Thanks 

I thought of this as well... I just don't understand why it's not working. I was hoping I could get some insight or something I missed. I'll do that to get myself up and running I suppose.

What's weird is if I use the emby account from a windows machine to log into the share, it works. But why doesn't it work when emby itself tries it?

[Q-Droid 989]

1 hour ago, DatsiK96 said:

Thanks for the response!

 

I'm using SMB because Windows Devices use this share, (Unrelated to the request) I'm trying to convert all of our server environment into Linux, but our desktops are still Windows.

 

I have tried NFS, and I encountered similar issues, resulting in me trying to match IDs of users and such.

You can use both for the same volume unless TrueNAS doesn't like it, then that's different matter. Also the share used by the Windows devices doesn't have to be the same one, or paths, used by the Emby server. Which brings up another potential issue - If you intend to create or copy media files from the Windows devices to the libraries used by Emby then you will have to sort out the ownership and permissions so that Emby can access and play said media. 

As @Luke posted you want to mount the SMB share to a local mount point on your Emby server in fstab instead of a UNC path. Mapping from a GUI as a different user also creates problems, it happens a lot. Examples in this thread, substitute the UID/GID for the emby user and group on your server.

 

 

[bastionntb 20]

7 minutes ago, Q-Droid said:

You can use both for the same volume unless TrueNAS doesn't like it, then that's different matter. Also the share used by the Windows devices doesn't have to be the same one, or paths, used by the Emby server. Which brings up another potential issue - If you intend to create or copy media files from the Windows devices to the libraries used by Emby then you will have to sort out the ownership and permissions so that Emby can access and play said media. 

As @Luke posted you want to mount the SMB share to a local mount point on your Emby server in fstab instead of a UNC path. Mapping from a GUI as a different user also creates problems, it happens a lot. Examples in this thread, substitute the UID/GID for the emby user and group on your server.

 

 

You know, I've done it before, used NFS and SMB on the same share... But I just really struggled with getting NFS to work.

I thank you all for your input!

I will try setting up an NFS share, mount it on the emby user as persistent, keep the SMB share mainly for read access,

 

However, inheritance should take precedence and remedy any file ownership issues, right? Specifically, when utilizing the SMB share under a different user?

[Q-Droid 989]

1 hour ago, DatsiK96 said:

However, inheritance should take precedence and remedy any file ownership issues, right? Specifically, when utilizing the SMB share under a different user?

If you're managing that in TrueNAS then yes, it should maintain access for Emby when dealing with multi-user file and directory creation.

[bastionntb 20]

1 minute ago, Q-Droid said:

If you're managing that in TrueNAS then yes, it should maintain access for Emby when dealing with multi-user file and directory creation.

Gotcha! Yeah I've told the permissions to inherit and applied them recursively. Should be enough I think...

So adding an NFS share did fix it, and it's working as expected. Now I guess I'll have to convert the other shares over and get their permissions working as well lol

Thanks again for the help!