mtseymour

bmartino1: Thank you very much for your insights and help! Attached is the diagnostic. The system has been rebooted several times and the problem has re-occurred soon after the reboot. Diagnostics attached. I ran smbstatus and did not see anything out of the ordinary. I seen a single user logging into several shares from 7 different IPs which is 100% normal and expected. Several other users also logging in from single IPs to their own shares as well as shared shares. A few other things. Whenever I have a management session open it stops responding every once and a while and I need to refresh. If i have the web console open it will close on me randomly... but ping never times out at all... after refreshing several times it still times out... If I try to putty in during this time it times out as well: After a few minutes it will again respond and I can open a web console again. It took me 2 tries to get the diagnostics. the first time it got hung up. I should have taken a screenshot on the command it hung up on. I had to close the page and try again. The second attempt worked. Not sure if it was because of the command it was attempting to run or because of the same issue that was causing the managementsmb_status_users_removed.txt page to time out. For the system monitoring theory with uptime kuma, what might cause that to happen? I have uptime kuma monitoring the shares using a tcp connection on port 445 and another monitor just pinging the server. Both of these monitors I have been using for at least a few years I think and the file share uptime failure has only recently started to happen. The ping time monitor is always green (only goes down when I need to reboot the server). I cant think of any changes that were made that might cause a change in the monitoring of the file shares. When I tried running your commands the management window kept closing on me. Very fustrating. Took me many tries just to get the commands to run before the window would close. root@Tower:~# ps aux | grep smbd | wc -l 46 root@Tower:~# root@Tower:~# ps aux | grep smbd | head -50 root 2300 0.0 0.0 90696 16132 ? Ss Mar15 0:17 /usr/sbin/smbd -D root 2304 0.0 0.0 87436 8684 ? S Mar15 0:02 /usr/sbin/smbd -D root 2305 0.0 0.0 87444 8256 ? S Mar15 0:01 /usr/sbin/smbd -D root 23760 0.0 0.1 112172 35284 ? S Mar15 0:15 /usr/sbin/smbd -D root 23861 0.0 0.1 110288 28116 ? S Mar15 0:02 /usr/sbin/smbd -D root 25371 0.0 0.0 112780 22488 ? S Mar17 0:00 /usr/sbin/smbd -D rents+ 28268 0.0 0.1 111072 34076 ? S Mar15 0:16 /usr/sbin/smbd -D root 52889 0.0 0.0 107808 20764 ? S Mar15 0:01 /usr/sbin/smbd -D root 55057 0.0 0.0 108084 24132 ? S Mar15 0:01 /usr/sbin/smbd -D root 87360 0.0 0.0 106672 21764 ? S Mar15 0:01 /usr/sbin/smbd -D root 99808 0.0 0.1 112104 36120 ? S Mar15 0:18 /usr/sbin/smbd -D root 128488 0.0 0.0 107296 24272 ? S Mar15 0:01 /usr/sbin/smbd -D root 190327 0.0 0.1 120448 35256 ? S Mar15 1:02 /usr/sbin/smbd -D root 210907 0.0 0.0 107620 20504 ? S Mar15 0:01 /usr/sbin/smbd -D root 225143 0.0 0.0 106692 19660 ? S Mar15 0:01 /usr/sbin/smbd -D root 316348 0.0 0.0 105284 18368 ? S Mar15 0:01 /usr/sbin/smbd -D root 373229 0.0 0.1 114428 35096 ? S Mar15 0:13 /usr/sbin/smbd -D root 451515 0.0 0.0 107712 20400 ? S Mar15 0:01 /usr/sbin/smbd -D root 464390 0.5 0.1 121292 44652 ? S Mar15 21:15 /usr/sbin/smbd -D root 522708 0.0 0.0 96012 17400 ? S Mar17 0:00 /usr/sbin/smbd -D root 725216 0.0 0.1 103404 24552 ? S Mar15 0:01 /usr/sbin/smbd -D root 1050293 0.0 0.0 106992 20940 ? S Mar15 0:01 /usr/sbin/smbd -D root 1065804 0.0 0.1 109968 27244 ? S Mar15 0:01 /usr/sbin/smbd -D root 1301116 0.0 0.0 113948 21760 ? S Mar17 0:00 /usr/sbin/smbd -D root 1708097 0.0 0.1 112772 27048 ? S Mar17 0:00 /usr/sbin/smbd -D root 1954625 0.0 0.0 92956 17496 ? S Mar16 0:00 /usr/sbin/smbd -D root 1984598 0.0 0.1 110588 32364 ? S Mar16 0:01 /usr/sbin/smbd -D root 2165204 0.0 0.0 110592 22024 ? S Mar16 0:00 /usr/sbin/smbd -D root 2209221 0.0 0.0 106576 21224 ? S Mar16 0:00 /usr/sbin/smbd -D root 2309112 0.0 0.0 108256 18924 ? S Mar16 0:00 /usr/sbin/smbd -D root 2309113 0.0 0.0 107292 12168 ? S Mar16 0:00 /usr/sbin/smbd -D root 2320308 0.0 0.1 110328 25164 ? S Mar16 0:00 /usr/sbin/smbd -D root 2876642 0.0 0.0 109832 21088 ? S Mar16 0:00 /usr/sbin/smbd -D root 3177781 0.0 0.0 97104 20216 ? S 02:44 0:00 /usr/sbin/smbd -D root 3241966 0.0 0.0 112924 21044 ? S 03:00 0:00 /usr/sbin/smbd -D root 3306383 0.0 0.0 112768 21536 ? S 03:18 0:00 /usr/sbin/smbd -D root 3386105 0.0 0.0 105192 20272 ? S 03:41 0:00 /usr/sbin/smbd -D root 3392259 0.0 0.0 4268 2484 pts/0 S+ 03:43 0:00 grep smbd root 3887882 0.0 0.1 113008 32564 ? S Mar17 0:00 /usr/sbin/smbd -D root 3954609 0.0 0.0 112456 23932 ? S Mar17 0:00 /usr/sbin/smbd -D root 4075869 0.0 0.1 115732 35052 ? S Mar17 0:08 /usr/sbin/smbd -D root 4136288 0.0 0.0 95852 17964 ? S Mar17 0:00 /usr/sbin/smbd -D root 4148336 0.0 0.1 112988 27240 ? S Mar17 0:00 /usr/sbin/smbd -D root 4161288 0.0 0.1 112456 29120 ? S Mar17 0:00 /usr/sbin/smbd -D root 4192413 0.0 0.0 95852 18224 ? S Mar17 0:00 /usr/sbin/smbd -D root@Tower:~# ive also added some log files with smb diagnostics (sanitized of user/share names but still readable) JorgeB: which customizations do you mean? I am in the process of removing all unneeded plugins but it is slow going with the management timing out tower-diagnostics-20260318-0300.zip

What do you mean by that last part "you have some form or kind of tracking that is creating or makeing a conenction to test nad that test is going crazy"? could it be the amount of users and shares? There are many users using a few specific shares constantly. Or do you mean it could be something else entirely? Oh, and thank you so much for the reply (the very quick reply at that!!!!)

Hi Everyone, Thank you for any help in advance. sorry for the redactions and removals of some of the information in the screenshots. im not sure if its absolutely necessary for me to do so, but id rather error on the side of caution. Here is some info that might help knowing to help troubleshoot: net ads testjoin version="7.2.3" 6.12.54-Unraid 16:28:52 up 1 day, 8:05, 0 users, load average: 4.57, 4.76, 4.66 Version 4.23.4 Version 4.23.4 Ping to winbindd succeeded checking the trust secret for domain MTSEYMOUR via RPC calls succeeded Workgroup: MTSEYMOUR Realm: MTSEYMOUR.CA Bind Path: dc=MTSEYMOUR,dc=CA LDAP port: 389 Server time: Mon, 16 Mar 2026 16:28:52 PDT KDC server: 192.168.1.4 Server time offset: 0 Join is OK root@Tower:/var/log/samba# I have recently had some issues with shares breaking. I initially noticed this because I use uptimekuma to keep track of my services. My ping on my unraid server is fine, but port 445 check with TCP to check the shares has been going up and down. I Keep seeing this: But even when its down sometimes I can still reach my shares. I am not at all a unraid or slackware expert so I use AI to help me figure some things out. Im hoping to get some real-person advice here above all else (especially above AI advice!@) I should mention this is an active directory joined unraid. In my syslogs I see this error over and over again, with differeht share names: Mar 16 09:50:50 Tower smbd[2008201]: chdir_current_service: vfs_ChDir(/mnt/user/SHARENAME) failed: Permission denied. Current token: uid=12192, gid=10515, 7 groups: 12192 10515 13699 13698 3003 3004 3005 Mar 16 09:50:50 Tower smbd[2008201]: [2026/03/16 09:50:50.237822, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) and i see these errors with a few other shares as well. AI had me run the following to help me diagnose the issue: root@Tower:/var/log# grep -A 5 -i idmap /etc/samba/smb.conf root@Tower:/var/log# testparm -s 2>/dev/null | grep -i idmap net conf list 2>/dev/null | grep -i idmap idmap cache time = 300 idmap config mtseymour : range = 10000-999999 idmap config mtseymour : backend = rid idmap config * : range = 3000-7999 idmap config * : backend = tdb root@Tower:/var/log# AI had me do some checks. It had me check my processes and how long they have been running: (a few were skipped between screenshots) and then it had me check if "idmap cache has a stale or inconsistent entry, or winbind is being queried with a local UID and can't map it back to a SID cleanly under load." and also had me check if Samba/Winbind credential caching timeout issue. ps aux | grep smbd | wc -l ps aux | grep smbd | head -50 root 2300 0.0 0.0 90696 18096 ? Ss Mar15 0:09 /usr/sbin/smbd -D root 2304 0.0 0.0 87436 9708 ? S Mar15 0:01 /usr/sbin/smbd -D root 2305 0.0 0.0 87444 9240 ? S Mar15 0:00 /usr/sbin/smbd -D root 23760 0.0 0.1 109740 36568 ? S Mar15 0:08 /usr/sbin/smbd -D root 23861 0.0 0.1 107276 25996 ? S Mar15 0:01 /usr/sbin/smbd -D root 28268 0.0 0.1 106384 29588 ? S Mar15 0:06 /usr/sbin/smbd -D root 52889 0.0 0.1 104304 26688 ? S Mar15 0:00 /usr/sbin/smbd -D root 55057 0.0 0.1 106016 26576 ? S Mar15 0:00 /usr/sbin/smbd -D root 87360 0.0 0.0 102220 21908 ? S Mar15 0:00 /usr/sbin/smbd -D REDACTED+ 99808 0.0 0.1 109672 36236 ? S Mar15 0:12 /usr/sbin/smbd -D root 128488 0.0 0.1 105668 26216 ? S Mar15 0:00 /usr/sbin/smbd -D root 190327 0.0 0.1 107708 34832 ? S Mar15 0:28 /usr/sbin/smbd -D root 210907 0.0 0.1 105640 25952 ? S Mar15 0:01 /usr/sbin/smbd -D root 225143 0.0 0.0 103540 21140 ? S Mar15 0:00 /usr/sbin/smbd -D root 316348 0.0 0.0 102356 20516 ? S Mar15 0:00 /usr/sbin/smbd -D root 373229 0.0 0.1 108652 29652 ? S Mar15 0:05 /usr/sbin/smbd -D root 451515 0.0 0.1 103260 30680 ? S Mar15 0:00 /usr/sbin/smbd -D root 464390 0.4 0.1 113824 41044 ? S Mar15 7:37 /usr/sbin/smbd -D root 478361 0.0 0.0 91576 19512 ? S Mar15 0:00 /usr/sbin/smbd -D root 531334 0.0 0.1 108244 24596 ? S Mar15 0:01 /usr/sbin/smbd -D root 587352 0.0 0.0 106176 24200 ? S Mar15 0:00 /usr/sbin/smbd -D root 689694 0.0 0.1 107012 29040 ? S Mar15 0:01 /usr/sbin/smbd -D root 720181 0.0 0.1 105032 29332 ? S Mar15 0:01 /usr/sbin/smbd -D root 725216 0.0 0.1 103404 26976 ? S Mar15 0:00 /usr/sbin/smbd -D root 1050293 0.0 0.0 106992 23368 ? S Mar15 0:00 /usr/sbin/smbd -D root 1065804 0.0 0.0 105536 22508 ? S Mar15 0:00 /usr/sbin/smbd -D root 1877069 0.0 0.1 108204 32920 ? S 07:07 0:00 /usr/sbin/smbd -D root 1888805 0.0 0.0 105472 24284 ? S 07:16 0:00 /usr/sbin/smbd -D root 1937220 0.0 0.0 92948 19532 ? S 07:55 0:00 /usr/sbin/smbd -D root 1952025 0.0 0.0 106196 22584 ? S 08:07 0:00 /usr/sbin/smbd -D root 1954625 0.0 0.0 92956 19860 ? S 08:10 0:00 /usr/sbin/smbd -D root 1984598 0.0 0.0 105468 21500 ? S 08:34 0:00 /usr/sbin/smbd -D root 1999888 0.1 0.1 109912 36516 ? S 08:46 0:49 /usr/sbin/smbd -D root 2007802 0.0 0.1 108276 29996 ? S 08:52 0:16 /usr/sbin/smbd -D root 2008201 0.0 0.1 106712 26176 ? S 08:53 0:00 /usr/sbin/smbd -D root 2019064 0.0 0.1 110596 36260 ? S 09:01 0:16 /usr/sbin/smbd -D root 2055133 0.0 0.1 107576 25164 ? S 09:30 0:00 /usr/sbin/smbd -D root 2063033 0.0 0.1 108124 28608 ? S 09:37 0:01 /usr/sbin/smbd -D root 2146597 0.0 0.1 109192 36760 ? S 10:40 0:10 /usr/sbin/smbd -D root 2165204 0.0 0.0 107520 21528 ? S 10:55 0:00 /usr/sbin/smbd -D root 2168444 0.0 0.1 108356 24380 ? S 10:57 0:00 /usr/sbin/smbd -D root 2209221 0.0 0.0 106576 23204 ? S 11:28 0:00 /usr/sbin/smbd -D root 2216792 0.0 0.1 108720 35252 ? S 11:34 0:06 /usr/sbin/smbd -D root 2255404 0.0 0.0 106576 22684 ? S 12:04 0:00 /usr/sbin/smbd -D root 2279780 0.0 0.1 111720 35568 ? S 12:23 0:02 /usr/sbin/smbd -D root 2309112 0.0 0.0 108256 21352 ? S 12:46 0:00 /usr/sbin/smbd -D root 2309113 0.0 0.0 105468 11736 ? S 12:46 0:00 /usr/sbin/smbd -D root 2320308 0.0 0.1 108504 27080 ? S 12:55 0:00 /usr/sbin/smbd -D root 2390986 0.0 0.1 108628 32964 ? S 13:50 0:00 /usr/sbin/smbd -D root 2402109 0.0 0.0 108256 22692 ? S 13:58 0:00 /usr/sbin/smbd -D root@Tower:/var/log# This is what AI had concluded: ##################ai copy paste starts here###################### Now we have everything we need. The fix is straightforward — you need to add deadtime and a winbind credentials cache timeout to smb-extra.conf, which is the correct place to put persistent custom config on Unraid (it survives reboots, unlike smb.conf which gets regenerated). A few observations from the full picture first: 59 smbd processes but only ~37 active sessions in smbstatus — so there are already ~20 orphaned processes accumulating PID 464390 (SOMEUSERNAME from 192.168.1.16) has been running since Mar 15 and has consumed 7 minutes 36 seconds of CPU — that's the heaviest session by far and likely your ReportServer automation The ANOTHERUSERNAME user connecting from 172.40.1.135 is coming in from what looks like a different subnet (Starlink/off-site?) — that's worth noting No deadtime is set anywhere in smb.conf, confirming idle sessions never expire The fix — add to /boot/config/smb-extra.conf: bash cat >> /boot/config/smb-extra.conf << 'EOF' # Kill idle smbd processes after 15 minutes of no activity deadtime = 15 # How long winbind caches credentials (seconds) - reduces DC hammering winbind cache time = 300 # Ensure winbind refreshes group membership periodically winbind offline logon = yes # Prevent runaway smbd process accumulation max smbd processes = 200 EOFThen verify it looks right: bash cat /boot/config/smb-extra.confThen test the config is valid and reload: bash testparm -s 2>/dev/null | grep -E "deadtime|winbind cache|max smbd" /etc/rc.d/rc.samba reloadAfter the reload, the existing 59 processes will persist until their clients disconnect or hit the new deadtime, but no new orphans will accumulate. Within an hour you should see the count drop significantly, and the intermittent WBC_ERR_DOMAIN_NOT_FOUND errors should stop. The remaining issue to address separately: the XX user failing on YY/YYYYY is a legitimate missing group membership — if VV should have access, add unraid-YYYYY to that user in Unraid's user management GUI. Same applies to any other shares where the permission denials are expected vs. accidental. ##################################################### (some things redacted for reasons.) Now I should note that yesterday I had this exact same issue happen and AI had recommended pretty much the exact same thing. Instead of doing its recommendation I rebooted the server thinking that it would help get rid of the stalled proceesses. Instead I found the issue had not gone away and seen it start again today. Does what the AI suggest make sense? Will this stop it from intermittently going down every so often? also, one last thing, when i do a cat log.smbd all i see is this over and over for many different shares.: i hope to get any help at all with this issue. Any insight at all will be greatly appreciated! thank you for any help!@ if there are any questions I can answer please ask! IF theres anything else I can add please do let me know!

I trust limetech, but I dont trust users. Heres to hoping ops recommendations at least get put on the roadmap (hopefully within 6 years). Lack of basic security features is the #1 reasons I am not buying or upgrading more licenses. Still love unraid, just not its lack of enthusiasm to improve security.

The whole mentality of not implementing security features and upgrades because unraid is designed to be used for home use only is kind of strange imho. unraid can have optional security features implemented while still dissuading business use. The argument against implementing security features because of how unraid is designed to be used is really not much of an argument at all, I think. You can have security features like MFA (among others) implemented with unraids current intended use case with no downsides that I can think of. At the very least I think a plugin for this and other security features would be attractive. Even simple MFA where you get a code in your email is better than none. Maybe I should try throwing something like this together..

Hi there, If a teams notification could be added in the 'agents' section under "notifications" in the settings section this would be amazing. Im sure I would not be the only one to use it. On top of it, you can chain together all sorts of actions with power automate when a teams alert comes through if you set it up. It would be fantastic.

I would formally like to request support for active directory user sync and user/group controls natively in unraid. The AD support unraid does have is through a plugin and it is not very clear. I see other users asking the same questions I am and going unanswered. This would be an amazing feature, and would buy another license if full AD syncing was supported just to support unraid if this was implemented.

if this isnt supported I would like to request this please (It does not appear to be supported).

Hi there, I was wondering if there was a way to add a share on an unraid server that has been added to a domain where the share can only be accessed by select AD users or a specific AD group. Currently, if you join unraid to a domain, anyone on the domain is able to add the shared folder without a username and password as long as they are also a member of the domain. In other words, I want to restrict access to shares via users and groups in an AD environment, but instead I find that when I join unraid to a domain, by default, everyone on that domain has access to that share, regardless of what users are assigned to the share. Is this a bug? Am I missing something?

when I say "my username and password" i actually mean "root" and the root password.

I just went to try it on a different browser and now its giving me HTTP ERROR 500 when I try to log in with my user name and password. - this has ublock on it (chrome) when i try to log into it with out any extensions or browser add ons or adblockers or anything, in incognito mode - this is when it just goes back to the login page without any error codes... I have just tried it in opera, edge, chrome and firefox, all in private/icog mode with no plugins or extensions with the same results Maybe restarting it via ssh would fix it? Im just worried something might break worse. How likely might this be?

Hi everyone, Today I tried logging into one of my unraid servers to find that it is not letting me log in via web browser on port 80. I simply get sent back to the original login page with no error message saying invalid login or anything like that. I am able to SSH in no problem with the password that was working previously. What might be causing this, and whats the best way to fix it? I am running 6.12.13 but I believe there is an update pending for 7.0. When i look at the log via the ssh session I see this: /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Feb 1 16:26:49 monte3 webGUI: Successful login user root from 192.168.101.6 Feb 1 16:27:01 monte3 crond[2393]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Feb 1 16:27:26 monte3 webGUI: Successful login user root from 192.168.101.6 Feb 1 16:28:01 monte3 crond[2393]: exit status 2 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Feb 1 16:28:11 monte3 sshd-session[10527]: Connection from 192.168.101.6 port 57538 on 192.168.0.2 port 9999 rdomain "" Its showing me that I was able to log in but it brings me right back to the login page. Im not sure what that system stats script is doing but im sure its not related. I can see my dockers are still running, and shares are working, but I just cant log in thank you for any help!

OMG YES! Thank you so much! This worked! I deleted the vdisk and re-enabled dockers, then added containers and got them back! thank you!!

Hey there, Thank you so much, that has brought my cache drive back, and i can see all of the data in it, but when i point Default appdata storage location to /mnt/cache/appdata (where I can see all of my dockers) and try to start docker, it still comes up with no dockers. Am I still able to recover them at this point?

hey there, So I am trying to upgrade a kingston 240GB ssd to a 800GB intel ssd for my cache drive and I think I screwed up big time. I misunderstood the instructions and how primary and secondary storage worked. I thought that the way it worked was that if you had data on your cache drive as primary, it would spill over to your array if your cache became full if you had your array as secondary. with that flawed logic in my head, this would never work, i thought: as step four from here: So what I did instead was I did: cp -a /mnt/cache/. /mnt/disk12/temp_backup/ after that completed, I shut down, installed the new disk, but it showed me this: I went ahead and clicked yes and started the array, and when i did cp -a /mnt/disk12/temp_backup/. /mnt/cache/ everything looked like it was going to work, except for the fact that there was an error, it said something like "cannot copy swap, text in use" or something similar. I should have screenshotted it, but it said something to that effect. I went to my dockers and found nothing there. I attempted to correct the paths from /mnt/user/ back to /mnt/cache (where I had them before the drive swap) and it just would not start no matter what. I attempted to do an appdata backup/restore plugin restore but it wouldnt work either. So, just wanting my dockers to work again I attempted putting the old cache drive back in, but of course when i boot up the array doesnt come online and it says that the cache drive is missing. selecting the original (smaller) cache drive says its "wrong". Selecting no drive gives me the option of starting the array, but says "Start will remove the missing cache disk and then bring the array on-line. Yes, I want to do this" Can anyone assist me in fixing this? I know its my own fault, I dont have anyone to blame but myself. The thing is tho, I dont care about any of the data on the array except for the dockers. they lived on the cache drive, and backups of them were made to the array. If it makes things simpler I dont mind wiping everything if i can just get a couple of the dockers back again. Diagnostics attached monte3-diagnostics-20240327-2131.zip