Clevernickname
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Clevernickname
-
-
I found this post while searching for solutions. After messing around a bit, this worked for me. Took a long time however.
WARN - this could really mess up your file permissions. This worked for me, but might not work for you.
1) Use WinSCP to reset permissions on your shares and all files in those shares to your Domain Administrator account. If the domain/user don't show up in WinSCP, it probably means unraid isn't connected. It might also mean that you changed the default owner in the settings to something else.
WinSCP has a checkbox to apply to children; you'll need to check that checkbox.
2) You should then be able to use your domain admin account on a windows box to set the correct owners for the files/directories. I use groups. One for read access (groupname-R) and one for write access (groupname-RW). I also leave the administrator account as full access; otherwise, I won't be able to change permissions using that account.
While #1 is pretty quick, #2 was really slow for me. I'm all done now, but I've been working through this for a couple of hours.
I have no idea why all of the permissions where lost after upgrading; my groups where still assigned, but the files where owned by something else.
6.10.0-RC4 Permissions Issues
in General Support
Posted
Ah, I actually had multiple issues, but it depended on the share:
1) Some shares, I could read dirs/files, but not do anything else
2) Some shares, I could not access at all (same problem as you, I think?)
3) Some shares I could read and add new files, but could not make changes. Since I backup my families machines to the array (and then sync those folders to cloud), that meant that changed files where not being backed up.
I'm baffled on why the above occurred and why it was not consistent when it failed. So far, I've got everything working again with AD. I did see odd error messages in the logs when this happened, but I did not think to save them. Something about the access belonging to multiple ids.