unRAID Permissions Problem

[Koshy]

unRAID 6.4.1

 

I usually set all my shares as private with some users having Read-only access, when I wanted to import some photos today to LightRoom I gave my user write access to the share but when I tried to import photos Light Room said I don't have write access. When I went to the share and tried to create a document I was able to do it in the root of the share but not a level up. Then I reboot the PC and the server, but nothing changed. I even tried making the share public but that did not make a difference either.

 

I'm attaching Diagnostics to this post.

 

Please Help 

tower-diagnostics-20180218-1234.zip

 

 

Update:

 

Running Docker Safe Perms has solved it but I still don't know what caused it and what to do prevent this from happening in the future.

[Frank1940]

Difficult to say but I would suggest reading in the thread from this point on for a few posts as it contains a lot of 'gotchas' with 'users' in SMB. 

 

      https://lime-technology.com/forums/topic/25064-user-share-problem/?tab=comments#comment-228392

 

 

 If it happens again, you should to use a Terminal Window (you can use the one in the GUI in 6.4.1) and run the command       ls -al        after you navigate to the directory with the issue.  Copy the output around the file(s) with the issue and post that up.  It sounds like you have an issue with owner and group names.   

[Koshy]

@Frank1940

 

It happened again here is what I got when I ran ls -al, I replaced the actual  name of the TV show with "TV.Show" when I posted the the output here I don't know if that matters.

 

total 17578708
drwxr-xr-x 1 nobody users       4096 Feb 26 08:03 ./
drwxrwxrwx 1 nobody users          6 Feb 26 15:03 ../
-rw-rw-rw- 1 nobody users 1526646672 Feb 26 14:57 TV.Show.S02E01.1080p.mkv
-rw-rw-rw- 1 nobody users 1271021209 Feb 26 13:20 TV.Show.S02E02.1080p.mkv
-rw-rw-rw- 1 nobody users 1253050915 Feb 26 13:20 TV.Show.S02E03.1080p.mkv
-rw-rw-rw- 1 nobody users 1188473414 Feb 26 13:20 TV.Show.S02E04.1080p.mkv
-rw-rw-rw- 1 nobody users 1198008150 Feb 26 13:20 TV.Show.S02E05.1080p.mkv
-rw-rw-rw- 1 nobody users 1862931845 Feb 26 13:20 TV.Show.S02E06.1080p.mkv
-rw-rw-rw- 1 nobody users 1206070298 Feb 26 13:20 TV.Show.S02E07.1080p.mkv
-rw-rw-rw- 1 nobody users 1372921017 Feb 26 13:20 TV.Show.S02E08.1080p.mkv
-rw-rw-rw- 1 nobody users 1521428996 Feb 26 13:20 TV.Show.S02E09.1080p.mkv
-rw-rw-rw- 1 nobody users 1355761302 Feb 26 13:20 TV.Show.S02E10.1080p.mkv
-rw-rw-rw- 1 nobody users 1324229395 Feb 26 13:20 TV.Show.S02E11.1080p.mkv
-rw-rw-rw- 1 nobody users 1411538183 Feb 26 13:20 TV.Show.S02E12.1080p.mkv
-rw-rw-rw- 1 nobody users 1508471360 Feb 26 13:20 TV.Show.S02E13.1080p.mk

 

[Frank1940]

OK.  What I see is the the permissions on the current directory are wrong.  The  current directory is the     ./   and I would suspect that it has a  'name' related to "TV.Show".)   The permissions should be      drwxrwxrwx   for you to have write permission in the directory.  You can find more information here:

 

        https://ryanstutorials.net/linuxtutorial/permissions.php

 

About half way down the page is "Permissions of Directories" section which contains the pertinent information.   

 

Most likely whatever Docker or plugin created this directory is not setup correctly.     

[Koshy]

All the data was transferred into a share in which I don't have write permission set, using the Filezilla docker, I then coped the data to another share with write permission to rename some files using Krusaider, this is when I found I couldn't rename the files.

 

What should I do differently to not end up in this situation again.

[Frank1940]

You should run the Docker Safe New Permission utility again.  That should fix this situation and any like it in the data array.  But it probably would prevent it from happening again.  To do that you have to figure out what program created this directory and change its configuration so that it sets the directory permissions correctly.  If it is Filezilla, you could look at the support thread for that Docker and see if that information is already there, or post up and ask the question.  

[Koshy]

I knew Docker Safe New Permission utility would fix it so I ran it after I posted the output and that did fixed it. I don't think Filezilla caused the problem I had a similar issue when I tried to do a Light Room import like I said in the original post, I don't think the Light Room share has been touched by an docker. Anyway thanks for your time.