There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

[Help] Unable to write files to an SMB share on a NAS

Edit: I found the solution! All I had to do was add the uid with my username, then I also had to add “forceuid” for it to actually go through. My fstab entry now looks like:

//192.168.1.21/Media-Library /mnt/Home-NAS/Media-Library cifs user=Jellyfin,password=password,uid=my_uid,forceuid,iocharset=utf8 0 0

Thank you @lemmyreader for posting the solution from Stack Exchange!


Hello! I have an Ubuntu server with a NAS mounted using cifs-utils, and I’ve created an entry in fstab for the share to be mounted at boot.

My fstab entry looks like this:

//192.168.1.21/Media-Library /mnt/Home-NAS/Media-Library cifs user=Jellyfin,password=password,iocharset=utf8 0 0

(The password is not actually “password” of course)

However, while I’m able to access the share perfectly fine, and even have a Jellyfin server reading from it, I cannot write files to the share without using sudo. I have some applications that manage metadata for music, and they’re not able to change or add files in any way.

I am however able to access the share from my Fedora machine just fine with the same credentials, since I use KDE, I just added them to the default “Windows Share Credentials” setting. I don’t have the issue where I have to use sudo to modify files, so I know it’s just an issue with the share mounted to the server and not permission issues on the NAS itself.

What am I doing wrong?

lemmyreader ,

Here a post with similar question and an answer from two years ago where the OP claims that using uid= did not work : unix.stackexchange.com/…/mount-t-cifs-only-mounts…

From that link the comment starting with this paragraph below may work :

It occurs to me that as (a) I’m the only one accessing this share and (b) mode changes are not written back to the CIFS filesystem anyway, it doesn’t matter whether the mode is 777 or 755. Therefore, the following fixes the issue:

Eric_Pollock OP ,
@Eric_Pollock@lemmy.dbzer0.com avatar

That worked! Thank you very much!

boredsquirrel ,
@boredsquirrel@slrpnk.net avatar

I think you should mount using gvfs or kiofuse and not fstab, to have user permissions?

Or use udisksctl

tvcvt ,

To amplify RedWeasel’s very good answer, fstab runs as root and unless you specify otherwise, the share will mount with root as the owner on the local machine. From the perspective of the Samba server, it’s the Jellyfin user accessing the files, but on the local machine, but local permissions come into play as well. That’s why you can get at the files when you connect to the share from Dolphin in your KDE system—it’s your own user that’s mounting the share locally.

RedWeasel ,

Try adding to the fstab options uid=#### with the #### replaced with the user id you are using. If you are using more users other options may be needed.

Edit: also check ‘man mount.cifs’ for other options.

acockworkorange ,

Could it be set with a gid and with write permissions for the group, therefore giving users in that group write access?

RedWeasel ,

Yes, that should work as well.

acockworkorange ,

Thanks!

Eric_Pollock OP ,
@Eric_Pollock@lemmy.dbzer0.com avatar

That unfortunately didn’t work, but I really do appreciate your response.

I just had to add an entry for my uid and then “forceuid”, and it worked!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines