fstab mac mount not working with new mac share?

**cbanakis** · March 4th, 2013

Hopefully someone can figure this out, because it makes no sense to me.

This is my original fstab line that has been working for years.

Code:

//192.168.99.95/My\040Docs /home/chris/M13-Docs cifs uid=chris,credentials=/etc/cifspw

I am replacing the Mac, that this line points to.

I setup everything the same exact way, except with the new ip.

Code:

//192.168.99.99/My\040Docs /home/chris/M13-Docs cifs uid=chris,credentials=/etc/cifspw

But for some reason it will not work with the new server.

Code:

sudo mount -a
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Does anyone know what could possibly be different that causes this not to work with the new mac share?

Thanks in advance

**cbanakis** · March 4th, 2013

After further research, it looks like the problem is that the new mac has Mountain Lion installed.

And from Lion on, Macs use smbx instead of smb.

So I guess my question is, how do I mount an xmbx share via fstab?

**cbanakis** · March 6th, 2013

Ok, I am finally getting somewhere.

I added the following options to fstab

Code:

nounix,sec=ntlmssp

So now it looks like this

Code:

\\192.168.99.99/My\040Docs /home/chris/M13-Docs cifs uid=chris,credentials=/etc/cifspw,nounix,sec=ntlmssp

Now if I

Code:

sudo mount -a

everything seems to be in order.

However, it is not mounting automatically on startup for some reason?

So I can now permanently mount the share, but I need to do it with

Code:

sudo mount -a

in terminal, every time I power on my computer?

Any thoughts on that?

Thanks

**Morbius1** · March 6th, 2013

It could be the reemergence of a very old bug where fstab is read and executed before the network is up, fails for the cifs mount, and never goes back.

What I suggested back then was to make your workaround permanent:

Add a file to if-up.d:

Code:

gksu gedit /etc/network/if-up.d/remount

With this content:

Code:

#!/bin/sh
mount -a

Make the file executable:

Code:

sudo chmod +x /etc/network/if-up.d/remount

Anything in if-up.d will execute only after your network is up.

**cbanakis** · March 8th, 2013

Thanks for your post.

It did not work, though I did finally get it working.

Just to be clear though, this is not a linux, or fstab related bug.

This is because Apple decided they can make a better samba than the one that has been perfected over the last 20 years. And boy were they wrong.

This issue expands far beyond Ubuntu.

Since I got Mountain Lion up and running (Upgraded from Snow Leopard)

No Windows computers have been able to connect to the Mac shared folders.
No Linux computers have been able to connect to the Mac shared folders.
No Android devices have been able to connect to the Mac shared folders.

Everything worked fine with Snow Leopard, but that was before Apple decided to fix samba.

Now Ubuntu computers are all connecting perfectly.

I added the options 'user' and 'auto' to my fstab, and all is well.

Code:

 //192.168.99.99/My\040Docs /home/chris/M13-Docs cifs uid=chris,credentials=/etc/cifspw,nounix,sec=ntlmssp,user,auto

Thanks Apple.

If you left everything alone, I might have gotten something productive done over the last 2 weeks.

Thanks to you, I managed to acomplish nothing other than getting everything to work like it used to.

Windows connections are still sketchy, and Android simply will not work, unless Apple fixes it from their end.

But all my Ubuntu needs are met, for now.