[Samba spitting out errors when I do a windows copy (Also making it not working)]

11 hours ago, Holmesware said:

Working for me too.

 

Now the only error in my logs is this one.

 

Jul 29 20:21:53 <SERVER> smbd[16622]: sys_path_to_bdev() failed for path [.]!
Jul 29 20:21:53 <SERVER> smbd[16622]: [2021/07/29 20:21:53.567047, 0]../../source3/lib/sysquotas.c:565(sys_get_quota)

 

The path[.]! will refect what ever path the connected user it in. I get tons to these as well.

 

Interesting.  I just checked my logs and I don't have any instances of those.  I wonder if our setups are different enough that it doesn't occur for me?  My logs only go to back 7/16/2021, but I don't have that error message at all.

 

I have a 2019 AD server with failover to a secondary;  Both unraid boxes are joined to the AD server and all share access is managed by AD.

 

Both are setup to log to seq (https://datalust.co/seq) with seq running the syslog plugin.

[Samba spitting out errors when I do a windows copy (Also making it not working)]

10 hours ago, Holmesware said:

https://www.samba.org/samba/docs/current/man-html/idmap_tdb.8.html

https://www.samba.org/samba/docs/current/man-html/idmap_ad.8.html

 

One of these might be the answer.

 

I'll test it if you can help me find a way to make changes to the smb-names.conf file that persist through a restart of the samba service.

 

POSSIBLE SOLUTION:

**** identify error ****

open the syslog from the webgui of unriad and watch for the idmap error message

 

From a windows machine command prompt:

net use A: \\<unraid server name>\<share name>

 

go into A: drive and dir

Look for the idmap error in syslog

 

go back to C drive

net use /delete A:

 

**** solution start ****

 

Go the the UNRAID server add the following lines to the beginning of  /boot/config/smb-extra.conf

 

[global]

idmap config * : backend = tdb

idmap config * : range = 1000-4000000000

 

Restart Samba with the command 'samba restart'

 

**** test solution ****

 

open the syslog from the webgui of unriad and watch for the idmap error message

 

From a windows machine command prompt:

net use A: \\<unraid server name>\<share name>

 

go into A: drive and dir

No idmap error in log

 

Can someone back this up? I've tested it on 2 of my servers with success.

 

 

 

Edit: 0 errors in the last 8 hours on both of my unraid servers after making this change;  I'd say this did it.  I used to get hundreds or thousands of these messages a day.  All my file shares still work, and AD security is being respected as well.  

 

----

 

Alright, this seems to have done the trick for me as well.

 

I get a lot of these through out the day, so I'll check my log file again tonight.

[Samba spitting out errors when I do a windows copy (Also making it not working)]

On 7/27/2021 at 4:38 PM, Holmesware said:

From the unRAID server you're having this error from; Run the command nmblookup -S <SERVER NAME> -d 5

 

Somewhere in there look for:

doing parameter null passwords = Yes

WARNING: The "null passwords" option is deprecated
doing parameter idmap config * : backend = hash

 

Check out the /etc/samba/smb-names.conf file

null passwords = Yes
idmap config * : backend = hash
idmap config * : range = 10000-4000000000

 

This has to be related to the log entry

winbindd[1428]: 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.

 

Not sure how to fix this but I think I'm on to something.

 

 

 

 

I'm not really familiar with samba at all, but based on the idmap source code here -

 

https://github.com/samba-team/samba/blob/master/source3/winbindd/idmap_hash/idmap_hash.c

 

And a couple of commits around it, it sounds like we shouldn't have this in our configs anymore 

 

idmap config * : backend = hash
idmap config * : range = 10000-4000000000

 

That being said, I don't know what to replace it with.  It looks like it's being used to hash a AD userid to a unix userid?

 

https://marc.info/?l=samba-technical&m=148768565527552&w=2

 

EDIT: Ok, yes this is the problem.  I've no idea at the moment how to work around it though.

 

See: https://www.samba.org/samba/docs/current/man-html/idmap_hash.8.html

 

 

[Samba spitting out errors when I do a windows copy (Also making it not working)]

On 7/18/2021 at 5:11 PM, Holmesware said:

I have multiple servers with this exact same issue.

 

<SERVERNAME> winbindd[21875]: 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

 

Not sure I understand the solution or even the problem. Which Plug-in is the issue?

 

Plugins:

CA

Fix Common Problems

Unassigned Devices

User Scripts

ZFS for unRAID 6

 

 

 

 

I believe Samy traced his problem to an issue with his MikroTek router, not something on Unraid himself.  I'm getting this error constantly, but I'm not using a MikroTek router, so my cause must be something else.

 

[Samba spitting out errors when I do a windows copy (Also making it not working)]

My syslog server is hammered with these as well - All of the messages appear to be this:

 

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

 

I can provide the logs or diagnostics as needed.