I used to have a working system based on an earlier version of Asset but since upgrading my Raspberry Pi and moving to Asset 6.1 I haven't managed back to a working system.
It is all based on the failure of the share commands in fstab.
I have tried all the suggestions in this thread and the only one that works is the manual mount command. As someone else has said, this means a remount and rescan ever time the Pi goes down for whatever reason.
There must be a better way. Any other suggestions greatly welcomed.
.............otherwise I might have to dig my CDs out of storage!
things changed with newer versions of Raspian and seemed to change again v recently as it was not working, I resolved the issue and then it broke again. This is what I use for cifs (SMB) connection:
//xxx.xxx.xxx.xxx/media /home/pi/nas cifs nofail,username=admin,password=yourpassword,vers=3 .0,x-systemd.automount and it is working away now
Philip
Many thanks for that suggestion.
Before I implement it can I just ask whether I should also be activating SMB version 3 on my Synology NAS. As it stands the NAS uses the range SMB1 to SMB2 and Large MTU.
I just went ahead and activated the SMB version 3 on my NAS.
I then implemented your suggested syntax referring to vers=3.0 in fstab, rebooted and hey presto! It's up and running again.
Thank you very much indeed Philip (psweetie).
I was too hasty!
In fact it only mounted one of my libraries and when I rebooted to see whether it might mount both libraries nothing mounted.
Looks as though I'll have to go back to manual mounting.
The treasure trove that is the world-wide web has at last got me sorted.
Just in case anyone else suffers the complete meltdown of their networked music system like I did, I should at least put on record the means by which I got it up and running again.
I used the information outlined in the June 2018 post from Jacques Gerber - thanks Jacques!
You can find the info here:https://raspberrypi.stackexchange.com/a/84757
I would still try it with vers=3.0 and SMB 1 is slower than newer versions as I understand it. Agree with setting the "wait for network on boot" option within the boot section of raspi-config. I do have that set.
Philip
Good suggestion - I'll try that Philip.
Silence means it will have worked...........otherwise I'll be back..........and hopefully not worse than before!
Comment