nomadgeek

This is still happening to me every few days on 6.12.3. Went unresponsive (no ping/gui/ssh/etc) this afternoon and had to hard-off the machine. Now, only a few hours later and SSH server is slow to respond to keystrokes and the gui charts/etc hitch and skip off and on.

I have very little additional advice - I just wanted to throw you my support behind your frustration with AD integration. It seems to work great when you initially configure it but if anything goes wrong fixing it seems near impossible. I'm seriously thinking I made a big mistake going with unraid for my fileserver; may be moving to FreeNAS in the near future. Good luck!

I have really struggled with AD permissions for a while now. It initially worked fine when I setup the server but sometime about 6-8 months ago something went pear-shaped and I've tried a bunch of things to fix it. 80% of the time when I reboot the unraid server the UID/GIDs change so permissions are wrong on the root shares. I can't get Inheritance enabled no matter how many times I turn it on and Windows iterates through all of the files. I really need a comprehensive tutorial on how unraid expects this to be configured, unix permissions and Windows permissions. I have three unraid servers, one of which I'm using as a Windows file server for my users. I'm seriously considering moving to FreeNAS in an attempt to get away from these issues.

This depends on your config. Are you working with AD or just UNRAID linux users? You either need to adjust the permissions on the file system back to nobody:users (99/100) or run your containers as the uid/gid of a user with perms on the files you're trying to interact with using the container (incl. the docker config files.)

Yes. The UNRAID server stopped forgetting people existed once it cleared out all of the old UIDs. I did have one employee whose domain account never gained access again and I ended up just creating him a new AD account for him to use to solve the issue.

Try the solution I added in the other thread below. This solved the 'randomly losing AD users' problem.

I finally solved almost all of my issues last week by swapping the backend auth method of Samba by adding this to my SMB Extras: [global] idmap config * : backend = tdb idmap config * : range = 3000-4000000000 I had to go through and reassign all of the permissions because everyone's UID/GID changed but once I did that I stopped losing people in the system like I was in my previous posts. I only have one unexplained problem left - a single user just doesn't exist no matter what I try.

Just reporting back to say that this issue continues; the server frequently forgets that an AD user exists requiring me to 'wbinfo -i user' the username and then flush. That'll bring the user back. It happens several times a day for individual users - a different one each time.

See my comments in this thread; I've basically worked out all of the conflicting permission problems between linux and windows by (a) never using my linux user to interact with shared files and (b) running the handful of docker containers that need to interact with shared files as a domain user. My only outstanding problem is that winbind seems to 'forget' that a domain user exists which has never happened before. I give more detail in this thread.

Pretty frustrating though - it means I have to come in early the next morning to power off the server and turn it back on before any of my users get to the office and start to complain they can't get to any of their files.

I have also had this problem when my NVME cache disk is under some load (usually in the middle of the night while backups are running/uploading to it). The drive is connected to the port directly on the motherboard and simply turning off the server and turning it back on solves the issue (but a reboot does not). I haven't been able to find a long-term solution. Backups occur every night but the failure only happens every few months (but then maybe twice in a few days).. seems pretty random. Dell Inc. 07WP95 , Version A02 Dell Inc., Version 1.7.0

I'm using Windows AD and also have permissions issues, though different ones. I think I've worked out a lot of the problems by running the hand full of docker containers that need access to user shares as a domain user but now I'm dealing with an intermittent problem where winbind will "forget" that a domain user exists. When I run 'wbinfo -i username' it can't find it even though it's listed in 'wbinfo -u'. If I clear the cache with 'net cache flush' and check again the user is found (and now has access as expected.) Didn't have any of these issues in the prior version.

Update: I re-owned the shares by looking up the UID & GID for the domain admin (ls -lan) and then chown -R XX:XX share-name got it back to the Domain Admin.. so that's solved - I can edit permissions from Windows again. Doesn't answer the interoperability problem.. I think I can solve the backup software problem by running that container as a UID from AD instead of the default but scanning coming from my copier is a different issue.

I've encountered the same AD issue for the last few days since I upgraded to 6.10.1 (and now 6.10.2). I have permissions issues all over the place. It looks like the Windows "Owner" of the root shares has been reset to Nobody (from Domain Admin) and I can't take ownership no matter what I try. My users are creating files that linux (e.g. a docker container that backs up files) can't access; my copier (which logs in using an UNRAID user) makes files that they can't access. Pretty disastrous. Commenting mostly so I can follow this thread - I'll report back if I find a workable solution.