Hello everyone!

I am completly new to unraid. so far I really liked it!

I created a user called PsxMicha and created a Data share. I have PsxMicha full read and write access to this share
I have a problem though. When I first setup unraid, I copied all my files over from my old windows server 2019 machine with rsync to the Data share

I can delete every while I copied with rsync, but when I wanna delete a file I downloaded/extracted with SABNZBD I get this error on windows

Can someone help me out here? What else do I need to do except give mu user read/write access? I also added my user to windows credential manager and I have the same username and password as on my windows machine

Edited September 5, 20241 yr by psxmicha

Suggest asking for help in the existing container support thread:

 

I just realize it's not only the container. I also can't change anything in my picture folder that I copied over with rsync from my old windows server. 

So I have multiple folders where I don't have write access, even though I gave my user full read/write permissions.

It's weird, I can delete/modify some folders, but others I can't. They're all in the same share

Edited September 5, 20241 yr by psxmicha

8 minutes ago, psxmicha said:

I also can't change anything in my picture folder that I copied over with rsync from my old windows server. 

Run the new permissions tool for that, but note that it should not be run on the appdata share

Ok I ran the tool on my share, but I still have the issue that I can delete/modify in my picture folder (inside my media share) but some files I just can't modify and I get the same error . For example I can modify folders/files like Christmas 2023, but I can't modify files like Screenshots or iCloud Photos

Edited September 5, 20241 yr by psxmicha

post the output from

ls -l /mnt/path/to/affected/share

 

root@Unschwitz:~# ls -l /mnt/user/media/Pictures/Screenshots
total 262172
-rw-rw-rw- 1 nobody users  631195 Feb  9  2018 Screenshot\ (1).png
-rw-rw-rw- 1 nobody users 1692750 Mar 20  2020 Screenshot\ (2).png
-rw-rw-rw- 1 nobody users   65218 Nov 19  2023 Screenshot\ 2023-11-19\ 135004.png
-rw-rw-rw- 1 nobody users   24564 Nov 19  2023 Screenshot\ 2023-11-19\ 140849.png
-rw-rw-rw- 1 nobody users   62648 Nov 19  2023 Screenshot\ 2023-11-19\ 141141.png
-rw-rw-rw- 1 nobody users   16633 Nov 19  2023 Screenshot\ 2023-11-19\ 142836.png
-rw-rw-rw- 1 nobody users   67241 Nov 19  2023 Screenshot\ 2023-11-19\ 155724.png
-rw-rw-rw- 1 nobody users   48882 Nov 19  2023 Screenshot\ 2023-11-19\ 160456.png
-rw-rw-rw- 1 nobody users  124399 Nov 20  2023 Screenshot\ 2023-11-20\ 191900.png
-rw-rw-rw- 1 nobody users 2234819 Nov 20  2023 Screenshot\ 2023-11-20\ 195818.png

and this is my iCloud Photos folder:

 

total 2940696
-rw-rw-rw- 1 nobody users  71987193 Aug 17 06:15 -1912453873827069272\ (Edited)(1).mp4
-rw-rw-rw- 1 nobody users    250974 Aug 17 06:15 -1912453873827069272\ (Edited).mp4
-rw-rw-rw- 1 nobody users  68884742 Aug 17 06:15 -1912453873827069272.mov
-rw-rw-rw- 1 nobody users 157656101 Aug 17 06:15 -1912453873827069272.mp4
-rw-rw-rw- 1 nobody users  62269677 Aug 18 05:27 -7640938937799032141\ (Edited).mp4
-rw-rw-rw- 1 nobody users  68298794 Aug 18 05:27 -7640938937799032141.mp4
-rw-rw-rw- 1 nobody users    100541 May 11 13:14 00059750-7665-4562-871d-e4155846b061.jpg
-rw-rw-rw- 1 nobody users    139884 Nov 20  2023 00249c1c-5aba-4b06-9d8f-db1a53c2ac08.jpg
-rw-rw-rw- 1 nobody users     86560 Feb 18  2024 00b41828-dcfe-48e9-995f-1788e2c760d5.jpg
-rw-rw-rw- 1 nobody users    157906 Dec  6  2023 00cbafea-5933-4034-85b1-ffe74ba32aa7.jpg
-rw-rw-rw- 1 nobody users   2157249 Dec  4  2023 010BB8D3-1B9C-4A27-B018-DE8D10E4FDBF.jpg
-rw-rw-rw- 1 nobody users     75871 Nov 16  2023 01245513-75d9-45ee-93c5-7a92c27882cb.jpg
-rw-rw-rw- 1 nobody users    234474 Dec  4  2023 0164e2ce-7efa-48b0-9a1a-061b1d5db360.jpg
-rw-rw-rw- 1 nobody users    153361 Nov 21  2023 0189b952-78d8-415e-ab54-92ba646385e7.jpg
-rw-rw-rw- 1 nobody users   1033331 Nov 25  2023 01EAF844-5DCF-4EA1-9AD0-AEEC517FC960.jpg
-rw-rw-rw- 1 nobody users    167225 Feb 18  2024 01b72fcc-66b3-4bc1-bca0-d5518fed6fbf.jpg
-rw-rw-rw- 1 nobody users     54501 Nov 27  2023 0200206c-01aa-40d5-ba23-09d9e6a5c4ab.jpg
-rw-rw-rw- 1 nobody users     92857 Nov  1  2023 02077af9-a298-4c12-969f-6efffe2dcd4d.jpg

 

Edited September 5, 20241 yr by psxmicha

How are trying to delete them?  You do realize that many of these files contain a <space> character in the file name.   The   ls   command shows this <space> as a    \<space>    where the backslash is an escape character in shell, which means it will preserve the literal value of the following character, unless it's an exception like newline or a special shell character. 

I try to delete it normaly from Windows Explorer or Directory Opus on Windows. I always get the same error like in my first post

The permissions are normal, if you are not exporting the share publicly try doing that

I get the same exact error when the share is set to public  

Do you have a different PC you could test with?

I get the exact same error on two other computers. But except of "You require permission from S-1-5-21..." it says "you require permission from unschwitz/nobody..."

At this point of dealing with SMB issues, I am always prone to recommend setting up things using this information in this post:

 

         https://forums.unraid.net/topic/110580-security-is-not-a-dirty-word-unraid-windows-1011-smb-setup/

 

IT can solve many issues.  But since you have access but just can't delete/edit files, lets have a look at the permissions on the directories all the way back up the directory tree using this command:

 

ls -al  /mnt/path/to/affected/share

 

Drop off one level each time until you get back to this point:

 

Notice the permissions on the directories at this point.  This is the first point where you should find any permissions on a directory that are different from this:

 

All directories should have permissions of   drwxrwxrwx     and the group of   users   (The owner can well be nobody or any other 'Share Access user'  as Unraid automatically assigns all Share Access users as members of the users group.) 

 

If you find any other symbols (like, "+" or "t"),  they are probably causing a problem.  Report back with what you find.

 

17 minutes ago, Frank1940 said:

All directories should have permissions of   drwxrwxrwx

doesn't this mean that the Screenshots directory doesn't have write permissions? 


Also I have this + here on the picture folder. Which means I messed up on the windows side if I understand the guide correctly?

Edited September 5, 20241 yr by psxmicha

7 minutes ago, psxmicha said:

doesn't this mean that the Screenshots directory doesn't have write permissions? 

Yes.    And looking at the second screenshot, I would suggest running the New Permissions tool on on the 'media' share.  (I seem to recall that it should fix both of these.)

 

Directory permissions are a bit of weird animal.  They seem to affect things a long way down the directory tree.

 

By the way, I would suspect that rsync is a part of the problem.  I recall seeing several other instance of these types of problems when it does copies the permissions of one type of file system to another with great precision.  (Of course, that is waht is intended to do...)

I already ran the New Permissions tool many times. 

Using google I found this 

I used this command and got rid of the plus. I ran new permissions again, but some folders are still dr-xr-xr-x
I have some basic linux knowledge, but I can't remember how to change the permission on the folder. If you could help me here I'd much appreciate it. 

Edit: seems like I fixed it. running find /mnt/user/media -type d -exec chmod 777 {} \; changed all permissions on my folders inside pictures

 

Edited September 5, 20241 yr by psxmicha

1 minute ago, psxmicha said:

I ran new permissions again, but some folders are still dr-xr-xr-x
I have some basic linux knowledge, but I can't remember how to change the permission on the folder. If you could help me here I'd much appreciate it. 

@JorgeB, Do you know what is happening here.  I thought New Permissions was suppose to fix these problems.  Have you encountered this type of problem before.

The post is marked solved, did running the new permissions tool fixed it?

No.

4 hours ago, psxmicha said:

Edit: seems like I fixed it. running find /mnt/user/media -type d -exec chmod 777 {} \; changed all permissions on my folders inside pictures

 

3 minutes ago, JonathanM said:

Edit: seems like I fixed it. running find /mnt/user/media -type d -exec chmod 777 {} \; changed all permissions on my folders inside pictures

Thanks, I think the tool should have fixed that, but will investigate later when I have some time.

8 hours ago, JorgeB said:

The post is marked solved, did running the new permissions tool fixed it?

no, the tool had no effect on the folders with Dr-xr-xr-x permissions. I had to change those manually

The tool was not working as the description, apparently it's been like this since 6.0.0, the initial idea was to leave read-only folders as read-only, but the tool description was incorrect, but LT decided to keep the description as is, so for the next release, the tool will changes any read-only folder to read/write, read-only files are still kept read-only.

1 hour ago, JorgeB said:

so for the next release, the tool will changes any read-only folder to read/write, read-only files are still kept read-only.

 

I can see where this will still be a problem.  In my opinion, the number of people who will want the group permissions to remain read only will be a very small portion of the total universal of Unraid users.  (If one is using Share Access users to access shares through SMB, they are likely gaining access through the group permissions.  If the Linux file permissions for group are r-- and the SMB permissions are Read-Write for the Share Access user, it is entirely possibility that that user will be denied write access!) 

 

I can recall several instances where Dockers were generating files on the array where the files were 755 or 644 and it was addressed using the New Permissions Tool.  I can not recall any complaint of someone having an issue with files having unexpected write permissions.

 

EDIT:

@limetech, Any comments...

Edited September 23, 20241 yr by Frank1940

10 hours ago, Frank1940 said:

I can see where this will still be a problem. 

It can, but that is what the tool is supposed do:

 

 

We can always have the users run a command manually that would also change any read-only files to read/write if they want.