Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Permissions issue with Transmission and Unraid share in Xen VM

Featured Replies

Hello all,

 

This is a bit of a noob question but I wasn't able to figure it out. My setup is the following.

 

Unraid 6 beta 5 running Xen. I have a share setup with user "titatom". The share is read-write for everyone.

 

I have a Ubuntu Server VM running as guest on Unraid as domU. I connect to the Media share on my array via nfs in fstab. The share appears as belonging to nobody and group users. I have Transmission running on that VM. It downloads files to ~/Downloads. Files are owned by titatom.

 

I am unable to copy or move the downloaded files to my Unraid share. I have tried manually and via Sickbeard post-processing script. Since my unraid share is open to all I though this should just work. Also if I change the downloaded files to chmod 777, still no go.

 

Could it be an issue with the way I connect to the Unraid share from the Ubuntu VM ?

 

Cheers !

 

Tom

 

Make sure the umask is set to 0 in the transmission settings.json file. Transmission must be stopped to edit the file successfully.

  • Author

Unfortunately that did not did the trick but I gave you false information without knowing. I actually connect via cifs. Here is my stab. uid is set to nobody which I think might explain my problem. Can I change the uid to titatom ?

 

Thanks a lot for your answer !

 

Tom

 

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/xvda1 during installation
UUID=53855ffe-d2b9-4cca-8bea-2282b8648c30 /               ext4    errors=remount-ro 0       1
# swap was on /dev/xvda5 during installation
UUID=31da7ca4-05af-4f2b-86d8-e572e6bf08a3 none            swap    sw              0       0
# Media Mount
//Serveur/Media /media/Media cifs credentials=/home/titatom/.smbcredentials,uid=nobody,gid=users 0 0

  • Author

Changing the uid to my VM username in fstab fixed the problem. I can now write to the share via sickbeard postprocessing !

 

Thanks fot the help ! :)

 

Tom

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.