JRascagneres

Are you referring to this setting? If so no... Otherwise I'm not intentionally using active directory?

Thanks for your response. The new permissions script fixes the already created directories but when I end up creating another directory the directory has the same issue. I thought the ACL was interesting but the same happens when I create a directory from a windows machine too so I don't think its my fstab entry? I have removed the dir_mode and file_mode with no success.

So... I have two users: "windowspc" and "homeserver1" they both have read/write access to my "main-array" share. I connect with my ubuntu server with the following /etc/fstab entry: //192.168.4.24/main-array /mnt/storage-server-01 cifs vers=3.0,rw,_netdev,noserverino,credentials=/etc/storage-server-creds,file_mode=0666,dir_mode=0777 0 0 I create a folder on my server using the above. Its connected with "homeserver1". When doing "ls -al" on the unraid server I see I made: drwxrwx---+ 1 homeserver1 users 6 Jun 4 00:28 test/ This clearly means that when I try to view the folder on a network mount from my windows machine, which is connected with the "windowspc" user I don't have the ability to read that folder. Any ideas? TIA

@Frank1940Sorry for the confusion. The /mnt/storage-server-01 is on the server thats connected to unraid. Thats the mount point for the unraid share remotely. @dlandonThe writes should be going through samba as the screenshots of the writes are on a remote server.

@Frank1940 I have SMB setup on my server //192.168.1.203/main-array /mnt/storage-server-01 cifs vers=3.0,credentials=/etc/storage-server-creds,rw,uid=nobody,gid=users,iocharset=utf8,file_mode=0777,dir_mode=0777,noperm 0 0 I then have docker on the server which writes to /mnt/storage-server-01 etc....

@Frank1940 Apologies for late delay. It did seem to help but the issue is I only write certain files to unraid over the network and keep metadata locally. Obviously having the PGID, PUID set to those causes issues when writing locally. UMASK did seem to help somewhat though. Is there no way to just force samba to operate with those settings? Thanks!

@Frank1940 Thanks for your response. Sooo... "New Permissions" works for existing files obviously but doesn't help when creating new ones. Yes Typically the files / folders are indeed created through docker (but on another system connected through samba) PGID - 1000 --> Just the user I have on my system, again connected to unraid via samba. PUID - 1000 --> As above No UMASK set.

I'm having a complete nightmare with samba permissions. Essentially I have a Plex folder inside of a share which I'm making available over the network using samba. Its a private share. I have the following based on information I found on the forums: I attempt to add a file using `touch`: This does get created but with the following: Creating a folder works: However permissions are off: Share settings: Is anyone able to help here? Its driving me mad.

Yeah I know but still not sure how that helps anything? Still doesn't affect write access? My problem: user1 writes a doc on SMB user2 attempts to access doc - Doesn't have permission as doc owner is set to user1

How would secure affect how other users can read / write a file written by another user?

Can I not keep it private but somehow make sure all users can access it?

I mapped the drive

I wrote the C file from an NFS share on my ubuntu machine. The New Folder was created from my SMB share on my windows machine. The computer is not a VM. Personal machine on the network.

As seen in the below screenshot whenever I make a file it gets created with my 'windowspc' user which is a user created through UNRAID and then used to access my share through windows. However, this means that when I want to view the file from another user I don't have permission to access it. Anyway to allow all users to access this?

Sorry I did this: You can re-enable the hard drive and reconstruct it as follows: Stop the array. Go to the Main page (Devices in version 4.7) and unassign the disk. Go to the Main page (Array Operations section) and start the array. Stop the array again. Go to the Main page (Devices in version 4.7) and re-assign the disk. Go to the Main page (Array Operations section) - the system should indicate there is a "new" drive to replace the disabled one. Check the confirmation box and click the Start button to start a reconstruct/rebuild of the disk.