Just made the jump from 4.7 to the latest beta (5.14?). It went pretty smoothly aside from it messing with my Sabnzbd post scripts and I got squeezebox up and running -the only reason I upgraded.

Anyhow I see it changed all the permissions of my all files in the raid too. I am just wondering if I add new media to this am I supposed to match the permissions that unraid has just set to them? What are the reasons for this permissions? Sorry I know I should research this more but I am spent from hoping around slimserver forums etc.

thank you

I have realised that copying anything to the array alters the permissions of the file.

I download/add new files to my cache first then use a script to move them to the array correctly.

If I have a file -rwxrwx--- and move to the array it goes to -rwxr-x---.

Even tho sabnzbd is set to download as 770 transferring them to raid after makes them inaccessible from xbmc/win7 (as i confirmed earlier).

Aside from copying some new media to say disk 2 and then using this command

chmod -R go-rwx,u-x,g+u,ug+X /mnt/disk2
chown -R nobody:users /mnt/disk2

is there any other way I can do this as changing the files before they move doesnt work. thanks

I never change permissions when copying data to unraid or when downloading with SABNZB.

hmm.. I wonder would this be due to the fact that I haven't upgraded from basic to pro yet and cannot add users for active directory? although sab downloads on unraid itself with permissions set to 770 (edit and I cant access them either)

@settings, I think you are absolutely right. When I upgraded from 4.7 to 5B14 I noticed that file permission changed when using Unraid in a certain way. My problem only happened when I use MC to transfer files from a USB drive to the Unraid. I can no longer W (write and delete) those files. I used CHOWN and CHMOD to change file permission to no avail. ls -l clearly showed that each file has RW for everyone, and the owner and group are nobody:users.

hey husky55,

well you can change the permissions of files on the actual raid itself so you can access them again but it is a pain. Like I just got squeezebox server going on unraid and I just went to make a podcast folder on the cache and of course I couldnt in windows, opened putty made one in unraid, closed it and went to paste a new podcast in there "Sorry but you dont have permissions blah", so i need to make a script to chmod that folder everytime i add a podcast

Im sure this is some silly problem on my part but its real annoying and I was so happy with unraid 4.7 and i wanted squeeze so needed an upgrade. Is this the same in the pro version?

I had a similar issue but found a way around it.

I was using a chache drive for my shares and found that when I would save a file from the PC in my office to a user share, then attempt to open the file from the PC in my living room (both Win 7) it would say that I dont have permission to open the file. The PC that copied the file to the unraid server could open the file fine. I would re-run the permissions tool and it would correct it. At first I thought it had something to do with the cache drive not assigning the proper permissions as I noticed most people complaining of the same issue were using cache drives. I disabled the cache drive and saved directly to the share and had the same results. Eventually I figured out that I had a drive mapping in windows 7 to an unraid share that was using the user "root" for the permissions of its mapping. It wouldn't ask for a login when saving to the shares, it just kept using root to access and save the file. When I right clicked on the file and looked at the permissions, it would say "TOWER\root" instead of "TOWER\nobody" like the other files that had been modified by the permissions tool. Once I discovered this, I removed the drive mapping, then re-mapped it checking the box to use different credentials and used my user id/password that I had setup in unraid under users and now it works fine.

The general solution to permission issues is not to use the root login. Any other login should work. Root makes files the owned by the root group. Any other user should make files owned by the user group and thus be accessible by all other users.