Jump to content

nomadgeek

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by nomadgeek

  1. 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.

  2. On 9/1/2022 at 4:19 PM, Evenimous said:

    I just want to be done with this thread, so I'll say what I'm doing to get around this here, and mark it as my solution. I already know this will work, but I wanted to learn a more proper way to do this, hence the rabbit hole I went down. If anybody ever finds a solution to this problem, please leave a reply on this thread for others to see.

     

    I'm genuinely disappointed with the Active Directory implementation in UnRAID. I love the operating system for what it is, and everything aside from these permissions has been a breeze. Setup was easy, configuring plugins was easy, the forum is very helpful, and everything is documented in a way that makes it easy to understand. I didn't really have a better alternative that wouldn't have been some ungodly expensive Microsoft product, so it was worth a shot. Regardless, here's what I'm going to do;

    1. I'm unable to access my files when the "root" user creates them with any commands like rsync, and I'm not aware of a way to log in as an active directory user in the terminal, since I can't log in as my UnRAID users, so I'll be doing the sinful method of transfer with file explorer one transfer at a time to make sure ownership is from my active directory account. I have approx 6.8TB of data, though a lot of it is in computer images, which tend to be larger in size, so almost half of the data will write sequentially, so it shouldn't be too awful in practice, just tedious.
    2.  Create new shares and start fresh for those, to ensure that permissions aren't borked from my previous activity on them. I'm probably not going to copy all of my old data, as this is a great opportunity to organize and get rid of what I don't need.

    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!

  3. 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.

  4. On 6/19/2022 at 10:45 AM, drogg said:

    I'm having issues with docker and file permissions after upgrading to 6.10.3. Has anyone found a fix? 

    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.)

  5.  

    23 hours ago, ricain59 said:

    The problem continu resolved with thas solution?

     

    Thank you.

    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.

  6. 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.

  7. 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.

  8. 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.

     

  9. 17 minutes ago, Tesla3327 said:

    Interesting. Glad I'm not alone at least. For me though simply trying to copy a 32GB folder onto the cache drive is enough to do it.

     

    Would you mind posting your build's specs if you have the time? I am considering a new MB at this point.

     

    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.

    • Upvote 1
  10. Quote

    PCI Devices and IOMMU Groups

    IOMMU group 0:[8086:3e1f] 00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 08)

    IOMMU group 1:[8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 08)

    [8086:1533] 01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

    IOMMU group 2:[8086:3e91] 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630]

    IOMMU group 3:[8086:1911] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model

    IOMMU group 4:[8086:a379] 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)

    IOMMU group 5:[8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)

    Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub

    Bus 001 Device 002 Port 1-5 ID 0781:5575 SanDisk Corp. Cruzer Glide

    Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub

    [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)

    IOMMU group 6:[8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)

    IOMMU group 7:[8086:a352] 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)

    [1:0:0:0] disk ATA Samsung SSD 860 4B6Q /dev/sdb 1.00TB

    [3:0:0:0] disk ATA ST4000VN008-2DR1 SC60 /dev/sdc 4.00TB

    IOMMU group 8:[8086:a33c] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0)

    IOMMU group 9:[8086:a33e] 00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0)

    IOMMU group 10:[8086:a330] 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)

    IOMMU group 11:[8086:a304] 00:1f.0 ISA bridge: Intel Corporation H370 Chipset LPC/eSPI Controller (rev 10)

    [8086:a348] 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)

    [8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)

    [8086:a324] 00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)

    IOMMU group 12:[10ec:8168] 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

    IOMMU group 13:[1b4b:9215] 03:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev 11)

    [6:0:0:0] disk ATA ST4000VN008-2DR1 SC60 /dev/sdd 4.00TB

    IOMMU group 14:[10ec:5763] 04:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. Device 5763 (rev 01)

    [N:0:1:1] disk ADATA SX6000LNP__1 /dev/nvme0n1 1.02TB

     

     

    CPU Thread Pairings

    Single:cpu 0

    Single:cpu 1

    Single:cpu 2

    Single:cpu 3

     

    USB Devices

    Bus 001 Device 001 Port 1-0ID 1d6b:0002 Linux Foundation 2.0 root hub

    Bus 001 Device 002 Port 1-5ID 0781:5575 SanDisk Corp. Cruzer Glide

    Bus 002 Device 001 Port 2-0ID 1d6b:0003 Linux Foundation 3.0 root hub

     

    SCSI Devices

    [0:0:0:0]disk SanDisk Cruzer Glide 1.00 /dev/sda 31.4GB

    [1:0:0:0]disk ATA Samsung SSD 860 4B6Q /dev/sdb 1.00TB

    [3:0:0:0]disk ATA ST4000VN008-2DR1 SC60 /dev/sdc 4.00TB

    [6:0:0:0]disk ATA ST4000VN008-2DR1 SC60 /dev/sdd 4.00TB

    [N:0:1:1]disk ADATA SX6000LNP__1 /dev/nvme0n1 1.02TB

     

    • Thanks 1
  11. 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

    • Like 1
  12. 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.

  13. 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.

     

  14. 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.

  15. On 4/24/2021 at 3:18 PM, thecode said:

    @limetechthis issue is open since November 2019, I suffer it from over a year (my report here 

    
    https://forums.unraid.net/bug-reports/stable-releases/683-wsdd-process-at-100-r1123

    I know your saying that no response does not mean the issue is not looked at, but this a year and a half. I have also suggested something which may be related in my post, is it ever going to be looked at?
    Thanks.
    btw (-i br0 does not solve it for me, two machines suffer from the same issue)

     

    Also had this issue on my otherwise fantastic 6.9.2 server. Added workaround. Will report back.

  16. 3 minutes ago, Squid said:

    Because the minimum the plugin supports is 6.9.0  Upgrade the OS, then upgrade the plugin

    🤦‍♂️ More coffee is required. My answer was right there in my question. I don't know what I was thinking. Cheers.

    • Haha 1
×
×
  • Create New...