Even dropping back to the old method of “username=xxx,password=xxx” doesn’t work. The command “mount -a” returns no errors, but the two folders are empty. A share on a Windows 10 machine works fine, so I can only assume it’s a change in samba on my server. Has anyone heard of this?
As an aside, I do have NFS shares that work. Does NFS cause more or less of a performance hit on the Pi?
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Well anything that reduces the hit on the Pi is good for me, so I’ve just left the NFS connections for now. I figured it was to do with the upgrade on the server because they disappeared on both Pi’s after the server had rebooted and never came back. I’m not really bothered, I’ll just switch them all over to NFS. I just thought someone might have noticed it and found the reason, which would save me googling around for hours.
My problem was caused by a Windows 10 update that removed support for SMB v1, as reported above in this thread. I had OSMC set to use SMB v1 only, so I couldn’t access the shares. I changed the OSMC setting to use any version of SMB and my problem was solved.