osmc@osmc:~$ sudo mount -a
mount: /etc/fstab: parse error: ignore entry at line 5.
mount: mount point 0 does not exist
mount: mount point 0 does not exist
Yeah, pretty sure that’s going to cause a problem as the cifs options are the fourth parameter and the delimiter is spaces.
Unfortunately, my unix knowledge is pretty basic. You may be able to escape the spaces in the username with a \
i.e xxxx\ xxxx\ xxxx
or maybe
“xxxx xxxx xxxx” or ‘xxxx xxxx xxxx’
but that’s just guesswork on my part.
You can also store the username and password in a separate file for security purposes and then reference the file with a credentials specifier. Just search for fstab and credentials. That’d deal with the problem with the fstab line being ignored. However, whether all three parts of the username would be read from the credentials file is something I’m not sure of.
p.s. it’s late here in the UK so I’ve got to get some sleep now!
Thank you, james_ss. I was also able to get going this way. Although I’d still prefer to have things working via Kodi, this is certainly a good solution until a fix is implemented upstream.
WOW lesson learned, if it ain’t broke don’t fix it.
I will be more cautious of blindly performing updates in the future. Cant believe there is no simple rollback.
What a pain.
Funny how the initial approach is to fix it on the SMB (PC/mac etc) server when the problem/change is obviously in OSMC.
So in my case I have a win-XP server with single no password logon serving the PI and 3 other PCs in the house where they would all need updating if I start adding passwords etc not what I want to do.
Adding the PW allows the authentication so I could go that route for the time being but its a pain.
Dont really want to re-install but that may be the way out.
Windows XP is end of life and network compatibility cannot always be guaranteed with old OS’ that are no longer supported by their original manufacturer
Even though this solution is obviously not as convenient as using the built in Kodi smb client, I believe that if you have performance issues or problems with network latency then kernel mode is the preferred solution for smb.
And obviously, copying files from / to the smb share at the unix level is a doddle!
The errors in “mount point 0” are my fault…i’ve messed up the fstab with iPhone edit…so the 0 0 at the and of line 1 and 2 were in wrong positions (line 2 and 4)…
Those lines are correct:
/dev/mmcblk0p1 /boot vfat defaults,noatime 0 0
/dev/mmcblk0p2 / ext4 defaults,noatime 0 0
After iPhone edit with Reflection they were:
/dev/mmcblk0p1 /boot vfat defaults,native
0 0
/dev/mmcblk0p2 / ext4 defaults,noatime
0 0
And I get rid of the username issue via the special charset \040 to chain my composite username.
Now with the fstab modified with automount smb share the Library upgrade (covers, actors etc) still works?
Are the folder extrafanart and extrathumbs inside every single folder still “writable” and “readable” by OSMC ?
Any chance I could get you to expand on what you did to get your Time capsule share working. I’ve tried adding my mount point to fstab and creating my Media folder in mnt, but still not connecting to my Airport.
If that was directed at me ActionA, thanks, but I had already tried adding that to my smb.conf… Still no go. Just grabbing straws wherever I can to try to get it going again, lolz.
