mouseskowitz

@Geoff Bland thank you for getting that bug report created!

Has anyone submitted a bug report for this yet? https://forums.unraid.net/bug-reports/

My DC is on a separate host and available during unraid boot.

My prediction was correct and it's broken again after 7 days. I tried @harpesichord suggestion and now I'm totally locked out of the folder that was owned by the broken user. I've reverted the change and the names at least show back up for the owner and groups of the other shares. Changing the owner via command line isn't fixing things like in the past as the the permissions aren't being given to the owner. Anyone know how to fix this?

I looked back at my notifications of issues with my backups, and it was 7 days in between. If that holds true, I'll be back on the 22nd. To get to the root cause, does anyone have troubleshooting steps would should do next time to get actionable data to get this fixed?

I never had an issue with AD in 6.9.x, but it's been nothing but issues since upgrading to 6.10.x. The odd thing is that it seems to be isolated to my backup user. I'm not sure what is different about this user that makes unraid hate it. I'm sure that unraid is the problem as I can access files with the same user and machine on my TrueNAS shares. I'm willing to do some troubleshooting if anyone has any ideas. I'm seeing the same response to ```wbinfo -i <user>``` as Brianara3 for the problem user. Edit: I was able to get the user working again by rebooting unraid, leaving the domain, and rejoining. We'll see how long it takes to break again.