unTECH

I can't find anything either. Well, at least things seem to be working properly aside from that, so thanks for the help with the main issue!

Ah, wait -- tried copying, it seems to be going now! Altho I have a different error -- "Jul 7 14:52:33 Discovery winbindd[2618]: [2023/07/07 14:52:33.681475, 0] ../../source3/winbindd/winbindd_cache.c:3464(set_global_winbindd_state_offline) Jul 7 14:52:33 Discovery winbindd[2618]: set_global_winbindd_state_offline: Offline requested" flooding the log

Rebooted, slightly different error: "This security ID may not be assigned as the owner of this object." -- when trying to change it from "3002 (Unix User\3002)".

I'm not able to remove or add users right now; I'm just told "access denied" when trying to make changes. Not seeing the SMB panics because I can't copy anything due to permissions

Alright, tried all that... Now I'm getting a permissions error. I'd checked before and everything looked fine -- now shares are showing a Unix user as the owner, and it gives me a "permission denied" when I try to change the owner or permissions.

Just double checked, and yes, it is.

Only user on the tower should be root, right? That was my understanding as well. Here's the fresh diags discovery-diagnostics-20230707-1143.zip

- Disabled Multi-channel; no difference - Fixed network config - disabled bonding - installed the AD Extras plugin and switched to tdb Unfortunately, same results after these changes. Not sure why it's showing all shares set to public for you -- I double checked, and many of my shares are set to private as well as hidden. Only a handful of shares are public.

discovery-diagnostics-20230707-0946.zipHere you go

Just tried from another machine; a single file will transfer fine, but when it's multiple files, I get it again. Windows copy stops with "An unexpected error occurred".

It seems to be all files at this point, at least from a particular machine. Tried rebooting and a different file, same result.

I'm trying to copy files to a share, and getting the following in my syslog: I was able to copy some files fine, and then this started happening. Is this a Samba bug, or something else?

After manually updating to 6.12.1, the update function works again!

Issue resolved after updating to 6.12.2

After having some network issues, I'm now unable to get my tower to rejoin the domain. Not sure when it got disconnected. I'm on the network, tower is visible to other machines, has a DHCP reservation and all. However, when trying to join, I get an error from avahi-dnsconfd: In trying to research, I found someone with a similar error: However, after following the FAQ, I confirmed that my system had the correct avahi password, and can't find any other leads. Issue started under 6.11.5, persisted after updating to 6.12.0 and 6.12.1

It's definitely weird. I did notice that when I removed the network config files it would work, but then once I set the network up again, it would stop working... I guess I'll just ignore it since it isn't really causing an issue. Thanks for the help

So, update: Had some network issues take out a Windows server, so several changes were made; I was able to get the server accessible via the webGUI again. Now, this is great, but there's still the CLI login issue. Put in the username, it goes to a new line, but isn't actually taking the password; whatever I type shows in plain text. After 60 seconds it times out. I did find that if I boot the server in GUI mode, I can log in and do what I need to do, so it's not a huge problem... But still seems like a bug. I've now updated to 6.12.1 and it still does it.

Hmm... There's a DHCP reservation for the server, must be hitting something there. I'll investigate the network side and follow up.

Ok, so, interestingly... I tried just renaming network-rules.cfg, and it would recreate that file but still not work. Renaming both, it creates a new network-rules.cfg, but not network.cfg. It won't get a proper IP address [seems to default to 169.254.221.41, which is not in any of our scopes], but I can log into the CLI after renaming both. Which is good that it did, because it didn't automatically do diags with later reboots, so I was able to run the command. --- Edit: removed diags because I realized they weren't sanitized.

Hmm... So, turns out the main cable had slightly wiggled out of the port on the switch somehow. Swapped that out, now I see activity on all 3 interfaces from the back of the machine. However, I still can't ping it, connect to the web GUI, or log into the CLI... Going to try renaming the network files you mentioned

Ahh, sorry, I thought /logs was the full logs without anonymization. Here you go! --- Edit: removed diags because I realized they weren't sanitized.

Are the diagnostics files stored anywhere on the flash drive that I can access from another machine? I'm not even able to log into the CLI at this point [I didn't see anything listed in the link about what to do if CLI is inaccessible]

Alright, so that did gracefully shut it down [I didn't realize it would stop the array, I thought that had to be done before sending for shutdown] -- unfortunately, after starting it up again, it seems to be in the same state. Can't ping it at the IP it lists, same behavior with not taking a password and timing out... Is my only option to try rebuilding the flash drive at this point, since I can't log in at all?

So, aside from occasional SMB access issues that would require a reboot, my tower has been running fine. Today, I had my shares become inaccessible, so I went to reboot it... Can't connect to the web GUI. Can't ping the tower. Connect a monitor and keyboard to the tower; was able to type in username "root", but when I hit enter, it goes to a new blank line; whatever I type shows up, but it isn't taking it as a password. 60 seconds later it times out and the CLI login resets, asking for username. Since I can't connect to the web GUI and can't log into CLI... is there anything I can do? Or do I just need to do an unclean restart and hope the array isn't impacted? Current version is unRAID 6.11.5

A bit of an update, but no progress -- I manually updated to 6.11.5, but the issue persists. I also realized that the time was wrong on the server; I thought it might have been an issue with the default NTP servers, so I tried putting in alternates from nist.gov, and it fails to update the time from any of their servers. I then decided to make sure I could ping them, but I can't -- "Name or service not known (-2)", and even pinging google.com gives this error. I'm looking into it being some network issue again -- we have been having issues with our domain servers acting strangely, so maybe they're not playing nice with DNS.