I am having what I assume is a permission issue on both Mac and PC. I have a root share set up according to this Space Invader Ones video (is this out of date now?) that I set up a while back. 

 

 

I can map my Unraid root share and see the shares in Finder, some of them will allow access, some wont, even with what appears to be identical settings in the Shares tab for permissions.

 

Sometimes they allow me to access the folders, but often will quickly kick me out and when I try again I am told I dont have permissions.

 

In the past I have used Docker Safe New perms, and most of the time I will be able to access the folders and files, however after short or longer periods the issue arrises again.

 

Possibly related, I have had a periodic issue in the last couple of months where from a couple of days to a couple of weeks, the server will hang. Not sure how else to say it, I cannot so much as ping it and the video output on the Motherboard is blank (Ryzen 1600x so that checks out), so is the output from the Quadro M2000 (passed through to Plex Docker in normal use).

 

Hard power cycling has been my answer (followed by a parity check to which I have not had any failures (yet)).

 

Attached the diagnostic file.

Thanks!

 

venus-diagnostics-20230508-2158.zip

9 hours ago, chip6439 said:

I can map my Unraid root share and see the shares in Finder, some of them will allow access, some wont, even with what appears to be identical settings in the Shares tab for permissions.

 

Sometimes they allow me to access the folders, but often will quickly kick me out and when I try again I am told I dont have permissions.

 

In the past I have used Docker Safe New perms, and most of the time I will be able to access the folders and files, however after short or longer periods the issue arrises again.

 

Have you looked at at the actual permissions, owner, and group on the server file system?  Using the following command in a GUI Terminal Window to look at one of my shares (Media):

ls -al /mnt/user/Media

You should find this as being the typical output:

-rw-rw-rw- 1 nobody users    7095852 Dec 23  2016 CannonBall_vs_Feather.mp4
-rw-rw-rw- 1 nobody users    1238088 Dec 12  2016 Cleaning\ Out\ The\ Garage\ -\ Meanwhile\ Somewhere\ Facebook.mp4
drwxrwxrwx 1 nobody users        300 Aug 27  2019 Family\ DVD\ Videos/
-rw-rw-rw- 1 nobody users    9072458 Mar 28  2019 Have_a_Great_Flight.MP4
drwxrwxrwx 1 nobody users        203 Apr  6 22:40 Movies/

 

Note that directories begin with a    drwx   and files begin with a   -rw-   

 

These reason for looking at these is that you say the problem is fixed by New Permissions.  What New Permission does is to set owner to     nobody,      group to      users,   and the permissions as shown.  You ask how do these get set wrong?  It is usually caused by a mis-configured Docker or VM.   Look at the file giving the problem and at the directory path to that file to see that the permissions are as expected.

 

 

9 hours ago, chip6439 said:

Possibly related, I have had a periodic issue in the last couple of months where from a couple of days to a couple of weeks, the server will hang. Not sure how else to say it, I cannot so much as ping it and the video output on the Motherboard is blank (Ryzen 1600x so that checks out), so is the output from the Quadro M2000 (passed through to Plex Docker in normal use).

 

AMD Ryzen chips require some special settings to be stable when running Unraid.   Google    unraid.net   Ryzen 1600x crashes   for details.   

Edited May 9, 20233 yr by Frank1940

Here is the response when I do so from the root directory.

Am I correct in seeing that I am missing write permissions on the root share? I feel like that wouldn't prevent me from opening shares within the root share, and why some work and some don't.

 

drwxrwxrwx+  1 nobody users  4096 May  8 18:22 ./
drwxr-xr-x  13 root   root    260 May  8 18:11 ../
-rw-rw-rw-   1 zach   users 14340 May  8 21:58 .DS_Store
drwxrwxrwx   1 nobody users    31 Aug 30  2019 .Trash-99/
-rw-rw-rw-   1 zach   users  4096 May 10  2022 ._.DS_Store
drwxrwxrwx+  1 nobody users    96 Sep 10  2022 Media/
drwxrwx---+  1 nobody users    41 May 16  2022 TimeMachine/
drwxrwxrwx   1 nobody users   498 Feb 19 13:22 appdata/
drwxrwx---+  1 nobody users    23 May  8 17:52 audiobooks/
drwxrwxrwx+  1 nobody users  4096 Sep 11  2022 backups/
drwxrwxrwx+  1 nobody users    31 Sep 11  2022 backupsdesktop/
drwxrwxrwx+  1 nobody users    65 Mar 22  2021 dndsessions/
drwxrwx---+  1 nobody users    20 Nov 24  2020 downloads/
drwxrwxrwx+  1 nobody users    37 May 30  2022 gameplayvideos/
drwxrwx---+  1 nobody users    71 Sep 10  2022 isos/
drwxrwxrwx+  1 nobody users    18 Sep 11  2022 minecraft/
drwxrwxrwx+  1 nobody users    18 Sep 11  2022 mineos/
drwxrwx---+  1 nobody users    18 May  8 18:30 moni/
drwxrwxrwx   1 nobody users  8192 May  4 09:24 movies/
drwxrwxrwx   1 nobody users    78 Oct  9  2019 music/
drwxrwxrwx   1 nobody users  4096 Oct  8  2021 musicals/
drwxrwx---   1 nobody users   142 Aug 30  2019 nextcloud/
drwxrwxrwx   1 nobody users    42 May 24  2022 photography/
drwxrwxrwx+  1 nobody users    34 Mar 26  2022 programs/
drwxrwxrwx   1 nobody users    47 Aug 17  2019 system/
drwxrwxrwx+  1 nobody users    31 May  8 18:50 t...r/
drwxrwx---+  1 nobody users    14 Aug 26  2020 tv/
drwxrwxrwx   1 nobody users     0 Nov 30  2021 vmdisks/
drwxrwxrwx   1 nobody users   100 May  8 21:36 zachsfiles/

 

A note, when I try to open the downloads share from the root share I get that it can't be found... Edit: I re-connected to the root share and now its just saying I don't have permissions like the rest are.

 

When I try to open photography from the root share I am getting that I do not have permissions.

 

 

 

 

 

 

Here is a screenshot from finder. 

Edited May 9, 20233 yr by chip6439
Corrections/More Info

I am noticing that it seems that files with the + at the end of the perms are the ones for the most part giving me the issue, where might the ACLs come from? 

See this example of a   "+" sign in the permissions.

That can be a problem. This "+" means that ACL (Access Control List) permissions have been assigned to this resource in addition to the standard Linux permissions.  Start by reading here:

 

     https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/#comment-1058963

 

I understand that AD (Active Directory) can sometimes do this but then you had better always be using AD to control access via SMB. 

 

One more thing, it sounds like you are using a MacOS. there is a section of the forum dedicated to MacOS SMB issues..   You can find it here:

 

     https://forums.unraid.net/forum/103-macossmb/

 

Hope this helps...

Edited May 9, 20233 yr by Frank1940