Geoff Bland

Thanks - this got my Dell Poweredge R720XD working with the Unraid USB Creator built USB stick on the internal USB slot.

I have raised a bug for this - feel free to add any details you like to try and get this fixed.

I have also been having the same problem - I am locked out of all my shares with SMB in my UNRAID server. It had been working fine for years but sems the 6.10.2 upgrade it seems intermittent most times I am locked out but occasionally I am able to get in. As yet is not affecting all users just some of them. I note my log disk is 98% full most of the space taken by some very large syslog files. These syslog files are constantly reporting many SMB errors - mostly refusing mount requests due to "smbd: check_account: Failed to convert SID S-1-5-21-**********-**********-*********-1105 to a UID (dom_user[DOMAIN\username])" errors.

As the zeroing of the second disk was going to take over a month to complete I aborted this. I then ran a parity check to be sure all was OK. I then re-did the zeroing of the first disk (only) - then removed the first disk from the array and rebuilt it. Again ran a parity check to be sure all was OK. Then I started a zeroing of the second disk again - and this time it ran at the normal speed. I was able to remove the second disk and rebuild the array a second time, all worked as expected this time. So it seems like either there's some problem zeroing two disks one after the other without removing the first from the array or I was unlucky and had some gremlins that day.

One thing I have noticed is that if I try to display logs (from the Logs button at the top of the UNRAID web pages) this sits there waiting and never shows any logs.

Thanks for the response. Diagnostics as requested. Disk 2 is the disk being zeroed now that is running slowly. Disk 1 has already successfully been zeroed. unraid01-diagnostics-20220522-1340.zip

I am removing 2 old 500GB drives from my UNRAID server. I am using the clear disk script here The first run on the clear disk script took around 12 hours to run and has zeroed the first disk. Running the clear disk script again has found the second disk to clear and has so far taken 36 hours to zero only 28GB – only 5% of the disk. At this rate it will take over a month to zero this disk. Obviously, I don’t want to wait that long as something could eventually get written to the disks I am removing. Is it OK to run the clear disk script on two separate drives? I can’t see anything in the script that would fail and my understanding of UNRAID parity leads me to believe this should be OK? Am I missing something?

I have now resolved this. These are the steps that I took that fixed this issue - I am not sure if all of them needed to be done. First I created a new AD domain user for UNRAID and gave it Domain Admin rights. I then updated the UNRAID SMB settings with the new user and password. The settings page did not show this had been accepted and if the Leave Domain button is pressed the web page does not register the domain is now left - that makes it impossible to re-join the domain without restarting the UNRAID server. This is a bug. I then restarted the UNRAID server and it re-joined the domain automatically with the new AD account I had given it (this was a bit of a surprise as I though I had left it disconnected from the domain). Now all access rights are back. Some files are marked with access to the wrong users - those added over the days we had problems. But these can be detected and corrected to have the correct permissions. So to recap, to fix: - create new AD domain user for UNRAID - on SMB settings, leave domain then update user name and password to new AD domain user - reboot UNRAID - UNRAID should restart and use the new AD user and join the domain - check permissions and users on recent added files and correct as required

Does anyone have any ideas on this? Is there anyway to check that UNRAID is correctly syncing with Active Directory? Anyway to reset the permissions on the shares and files - doing it form the web GUI does not seem to work.

I have been running UNRAID for years now with no problems at all but 9 days ago I found the server unresponsive and black screened so I had to power off/on. Since then I have noticed that my Windows AD domain accounts have lost access to many shares & directories - although not all of them. I also tried to leave & re-join the domain to reset things in the Settings | SMB page but pressing Leave does nothing and UNRAID is still joined to the domain. I tried creating a new share that only my AD account had RW access to in the private SMB share. This seemed to work and I was able to access the share and create folders and files. But weirdly the files are set to be owned not by me but by a different owner - my account is geoff but the new file and folder I created is owned by user jellyfin. I also note that Windows shows that both everyone and jellyfin user has been given RW access to these files and directories - but the SMB share is set so only the geoff account has RW access. root@UNRAID01:~# ls -laR /mnt/user/accesstest /mnt/user/accesstest: total 0 drwxrwxrwx 1 unraid domain users 20 Jan 26 00:38 ./ drwxrwxrwx 1 776996452 776995329 6 Jan 25 23:59 ../ drwxrwxrwx 1 jellyfin domain users 24 Jan 26 00:38 new_folder/ /mnt/user/accesstest/new_folder: total 4 drwxrwxrwx 1 jellyfin domain users 24 Jan 26 00:38 ./ drwxrwxrwx 1 unraid domain users 20 Jan 26 00:38 ../ -rw-rw-rw- 1 jellyfin domain users 14 Jan 26 00:00 test_doc.txt What do I need to do to fix this?

Thanks for the response. Yes, all existing users are working fine. Just cannot add a new user.

Further investigation shows that UNRAID does "know" of this user root@UNRAID01:~# id vcuser uid=2018509937(vcuser) gid=2018509313(domain users) groups=2018509313(domain users) So it it getting this used from the Windows AD - as the user has been created in the domain? Has something changed here - or am I missing something? I believed that to get Windows User access to UNRAID that I needed to create the AD user first and then add the same named user to UNRAID?

Adding a new user has started failing on the UNRAID GUI - it did use to work fine. No errors are reported on in the GUI but it just returns to the Add User screen but no new user has been added. The system log reports the following: Dec 14 14:52:36 UNRAID01 winbindd[15731]: [2021/12/14 14:52:36.532516, 0] ../../source3/winbindd/idmap_hash/idmap_hash.c:115(idmap_hash_initialize) Dec 14 14:52:36 UNRAID01 winbindd[15731]: idmap_hash_initialize: The idmap_hash module is deprecated and should not be used. Please migrate to a different plugin. This module will be removed in a future version of Samba Dec 14 14:52:36 UNRAID01 root: useradd: user 'vcuser' already exists Dec 14 14:52:36 UNRAID01 useradd[24296]: failed adding user 'vcuser', data deleted Dec 14 14:52:36 UNRAID01 emhttpd: shcmd (400971): exit status: 9 Dec 14 14:52:36 UNRAID01 chpasswd[24299]: pam_unix(chpasswd:chauthtok): user "vcuser" does not exist in /etc/passwd I have tried several different user names and all fail. The /etc/passwd file does not contain the users I am adding. What should I try next? Edit: version is 6.9.2

A client only version of this Docker would be very useful - for users that want to just backup selected UNRAID folders to other URBACKUP servers. I have been using URBACKUP for about a year now to backup onsite and offsite & just started using UNRAID as a central file server. So need to set up a URBACKUP client on my UNRAID server now.