Macos samba client crashes OSMC smbd

Help and Support Raspberry Pi
1

Connecting to sub-directory on USB disk from Macos fails.
Been happening for a while, complete new build of OSMC, no difference.
Fine from Win10 laptop.

Code:
smbd.service - Samba SMB Daemon Loaded: loaded (/lib/systemd/system/smbd.service; disabled; vendor preset: enabled) Drop-In: /usr/lib/systemd/system/smbd.service.d └─smb-app-osmc.conf Active: active (running) since Tue 2024-07-23 11:29:14 ACST; 1h 41min ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 608 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 609 (smbd) Status: "smbd: ready to serve connections…" Tasks: 4 (limit: 3931) CPU: 2.719s CGroup: /system.slice/smbd.service ├─609 /usr/sbin/smbd --foreground --no-process-group ├─611 /usr/sbin/smbd --foreground --no-process-group ├─612 /usr/sbin/smbd --foreground --no-process-group └─660 /usr/sbin/smbd --foreground --no-process-group Jul 23 13:08:54 osmc smbd[853]: If you are running a recent Samba version, and if you think this problem is not yet f> Jul 23 13:08:54 osmc smbd[853]: [2024/07/23 13:08:54.150181, 0] …/…/lib/util/fault.c:169(smb_panic_log) Jul 23 13:08:54 osmc smbd[853]: =============================================================== Jul 23 13:08:54 osmc smbd[853]: [2024/07/23 13:08:54.150277, 0] …/…/lib/util/fault.c:170(smb_panic_log) Jul 23 13:08:54 osmc smbd[853]: PANIC (pid 853): Signal 11: Segmentation fault in 4.13.13-Debian Jul 23 13:08:54 osmc smbd[853]: [2024/07/23 13:08:54.150619, 0] …/…/lib/util/fault.c:274(log_stack_trace) Jul 23 13:08:54 osmc smbd[853]: BACKTRACE: 0 stack frames: Jul 23 13:08:54 osmc smbd[853]: [2024/07/23 13:08:54.150837, 0] …/…/source3/lib/dumpcore.c:315(dump_core) Jul 23 13:08:54 osmc smbd[853]: dumping core in /var/log/samba/cores/smbd Jul 23 13:08:54 osmc smbd[853]:

Hope you guys can help.
Thanks,
Luke

2

Since OSMC is shipping smb v 4.13.x something, there is a known issue with Mac clients in Debian. I believe Debian was as usual “a bit behind” for stability, I’ve not checked which version is in next Debian upgrade for OSMC. The smb-package 4.13.x from Ubuntu didn’t have exact same issue but there something mentioning multi channel support, and Mac’s rebooting with mounted shares, triggering a segfault in smbd. Since I’m have no access to any box running Apple, I can’t really verify or test any possible changes right now.

3

Thanks for your informative reply joakim_s. At least I know where to look. Cheers.

4

I don’t have a Mac but if SMB Multichannel is to blame, you can disable it on the Mac or file server.
For Mac: Configure SMB Multichannel behavior - Apple Support
short version: add the following line to the /etc/nsmb.conf file:
mc_on=no

For Linux or NAS (If not available in the GUI):
add or edit the line to /etc/samba/smb.conf
server multi channel support = no

I’ve never came across SMB Multichannel until last week when I had to troubleshoot and discus it on two occasions. Turns out it has 0 benefit unless both your server and client are connected with multiple network connections to each other.
I’ve noticed several NAS manufacturers are using this option to provide a cool screenshot of their NAS delivering 5 Gbps disk speeds but i doubt many people have 4 cables between their NAS and client to come close to this higher level enterprise setup or lab setup.

5

Hi nAFutro, Thank you for the effort to respond and your insight.
Unfortunately your suggestions did not resolve my problem.
I think Apple have broken Samba and do not care to fix it.
I am actively seeking other solutions
Thanks again.