I would recommend against giving newmedia full control, because that means newmedia has the ability to modify permissions. What it sounds like to me is that you have inherit set with the newmedia user in windows and not for the others. Access is denied."Īny advice on what the issue is and what I need to do to resolve? Thank you! "An error occurred while applying security information to Z:\movies Failed to enumerate objects in the container. If I try to set permissions on a child folder, I get the following error: To set permissions without removing the inherited permissions, click No and either change the permissions on a child folder or make the changes while logged in locally." "Remotely setting permissions on the folder at the root of a share removes all inherited permissions from the root folder and all subfolders. I do get the following error in Windows when trying to set the permissions: When I check permissions in Windows, I see that newmedia has Full Control permission to the root of the share, but doesn't seem to have permissions to any child folders. I am able to open any other files on my FreeNAS share, just not any that have been downloaded via the jailed Sabnzbd install. You require permission from FREENAS\newmedia to make changes to this file" "You need permission to perform this action. I get the following error message in Windows: When the files download via Sabnzbd, I am not able to open them or copy them. Very helpful, though I seem to have a permissions issue. At this point you should be able to run pkg update and pkg upgrade and everything should go smoothly. If stuff breaks then you can easily rollback the datasets.ĥ. Take a snapshot of your jail datasets before upgrading anything. That way if anything breaks when you update it, you are only out one plugin instead of all of them.)Ĥ. (This is a little redundant, but it will benefit you with isolation between plugins. When you rebuild your jails, go ahead and build each plugin in its own jail. (I know its a pain, but this will give you the new iocage backend)ģ. After upgrading to 11.2 rebuild all of your jails from scratch. Hold off on upgrades until moving to freenas 11.2Ģ. The commands to update your services are:īut if you do that in freenas 11.1-U5 it will break everything because they are using a different repository for the new iocage jails.ġ. When I get the time, I'll update the guide to include plex, transmission and freenas 11.2. I have not updgraded to 11.2 yet, so these have not been tested. I would really appreciate a hand getting this working, hopefully in a simple manner that doesnt require me to edit much with every container update.Here are a few pointers that I sent to other users regarding upgrades. I have tried to sudo chmod but the container does not have sudo, I have tried to umount the location and see if it lets me edit it while its not mounted but this also failed. As sonarr runs as a different user than root it does not have write permission to /mnt/folder and I’m guessing this is the cause of my problems. However if I look at chmod for the mount inside the container sonarr its 755 rather than 777 and im unable to change it. This is working fine and I can even use touch to create a file from the sonarr container console (root) but not the user that is running the sonarr service. Tried a few different methods to present the SMB share to the linux dockers, settled on mounting /mnt/folder on my host and passing it through as a volume (rw). I’m running a windows file server (due to a legacy reason), presented as \\server\folder\ with full read/write to user1, both ntfs and share permissions. I’m having problems with Sonarr (but im sure will also see it in radarr, lidarr, nzbget, etc etc)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |