I need help fixing this error.  Server has uptime of 3 days but log is at 97%. 

 

Thanks

tower-diagnostics-20211027-1935.zip

Oct 26 15:22:35 Tower kernel: CIFS: Attempting to mount //VOLUMIO-MB/Internal Storage
Oct 26 15:22:35 Tower unassigned.devices: Successfully mounted '//VOLUMIO-MB/Internal Storage' on '/mnt/remotes/VOLUMIO-MB_Internal Storage'.
Oct 26 15:22:35 Tower unassigned.devices: Adding SMB share 'VOLUMIO-MB_Internal Storage'.
Oct 26 15:22:35 Tower unassigned.devices: Remote SMB/NFS mount '//LANDS-HACKMINI/EVO 870 1TB SSD' is not set to auto mount.
Oct 26 15:22:35 Tower unassigned.devices: Remote SMB/NFS mount '//THE-QUEENS-WAY/Users' is not set to auto mount.
Oct 26 15:31:41 Tower smbd[16010]: [2021/10/26 15:31:41.652924,  0] ../../source3/lib/popt_common.c:68(popt_s3_talloc_log_fn)
Oct 26 15:31:41 Tower smbd[16010]:   Bad talloc magic value - unknown value
Oct 26 15:31:41 Tower smbd[16010]: [2021/10/26 15:31:41.652945,  0] ../../source3/lib/util.c:829(smb_panic_s3)
Oct 26 15:31:41 Tower smbd[16010]:   PANIC (pid 16010): Bad talloc magic value - unknown value
Oct 26 15:31:41 Tower smbd[16010]: [2021/10/26 15:31:41.652993,  0] ../../lib/util/fault.c:222(log_stack_trace)
Oct 26 15:31:41 Tower smbd[16010]:   BACKTRACE:

Looks like your problems with SMB begin after UD remote mount. And those traces continue to the end of logs

Thanks @trurl. What do I need to do to fix? Remove remote devices, restart server or is the solution something else?

Restarting is the easiest way to clear logs. Don't know what the actual solution to those SMB traces are, I guess you could try not mounting the remotes to see if they go away.

 

Google this:

talloc magic value site:forums.unraid.net

Thanks!  I'll give that a try

Just to give an update. 

After doing the google search like you suggested, I found this post relating to time machine.

 

https://forums.unraid.net/bug-reports/stable-releases/691-time-machine-no-longer-works-after-upgrading-from-683-bad-talloc-magic-value-unknown-value-r1393/

 

I remembered that I did try connecting and setting up time machine yesterday but kept getting the beach ball. I stopped trying, thinking that I would get back to it some time later. I now realize that this was the cause of the log error.  I followed the tip of removing "fruit:locking=netatalk" from the SMB config line.  Time machine is working fine now. No log issues.  

 

Thanks again for the help!

Edited October 28, 20214 yr by TekDRu