The funny characters are just because the log is being rendered with the wrong characterset. Sould look like ->
I’m not sure the issue you link is the same - there are different error messages.
Samba seems to sprinkle conf files far and wide. Not clear which can be safely wiped without upsetting the samba client in kodi. Where’s @DBMandrake when you need him?
Funny thread keeping so many people interested (and busy).
Coming back to the log in post #75.
We see that smbd crashed, right? Isn’t smbd logging to /var/log/samba/log.smbd ?
And what about letting @brifletch start smbd interactively using the parameters behind SMBDOPTIONS,bring out messages to stdout and perhaps use a debug level?
My bad. Strange - it applies only to smbd and nmbd and in the system journal this message is being generated from mediacenter. So maybe something funny in the AppStore python?
But the quote you gave is from systemd so corruption in the samba server itself?
It didn’t. I reinstalled the December update image, restored from backup (but for some reason none of my addon settings have been restored, which is a PITA) and I reinstalled the SMB server from the Addon store.
Same error message when I try to connect to the osmc folder
Thanks for keeping me right. It seems to have installed correctly. From Windows I can now see the osmc folder and a USB stick that is plugged in to the Vero 4K (previously, I was only seeing the osmc folder), but trying to connect is still giving me the same error.
Thanks for the update. Still wondering if anything happen to your Win10 Client settings. As mentioned I will do a clean setup this evening to test.
Maybe you also want to try with a clean virtual machine of Win10 https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
Thanks guys. I have a sleeping child on me at the moment so will have to get back to this later. FWIW I can connect to all my other networked machines via SMB from the PC. It’s just the Vero 4K that’s giving me a headache!
Ok, understand that while also important you can connect from openelec to it which means the fundamental samba server on the Vero works.
Just when you have time provide dmesg | paste-log output
Sorry, but Can't access Vero 4K/OSMC from Windows - #33 by brifletch told us this is also not working. In case this changed meanwhile, I’m out since there are too many changes in related circumstances to keep them up without repeated reading the whole story.