I am currently serving my digital media collection over a Samba server. I have the shares mapped to network drives on Windows machines, and as CIFS fs on linux. I followed the direction on Swerdna’s site (here)](http://www.swerdna.net.au/linhowtosambacifs.html). The mount command line works fine:
mount -t cifs -o username=klein,password=klein //192.168.1.70/SharedMedia /home/zak89/SharedMedia/
I am dedicated to good passwords, as you can plainly see.
However, the following line in fstab (also from Swerdna’s tutorial) is not working (that is, on reboot the shares are not automatically mounted):
zak89 wrote:
> I am currently serving my digital media collection over a Samba server.
> I have the shares mapped to network drives on Windows machines, and as
> CIFS fs on linux. I followed the direction on Swerdna’s site ‘(here)’
> (http://www.swerdna.net.au/linhowtosambacifs.html). The mount command
> line works fine:
>
>
> Code:
> --------------------
> mount -t cifs -o username=klein,password=klein //192.168.1.70/SharedMedia /home/zak89/SharedMedia/
>
> --------------------
>
>
> I am dedicated to good passwords, as you can plainly see.
>
> However, the following line in fstab (also from Swerdna’s tutorial) is
> not working (that is, on reboot the shares are not automatically
> mounted):
>
>
> Code:
> --------------------
> //192.168.1.70/SharedMedia /home/zak89/SharedMedia/ cifs username=klein,password=klein,_netdev,uid=zak,gid=users 0 0
>
> --------------------
>
>
> Any ideas on this?
I’m not Swerdna, but could it be that the network is not yet
established when fstab is processed? If so, create an executable
script that sleeps for 30 seconds or so, and then does the mount. This
is what I had to do for NFS mounts on a wireless network controlled by
NM. For wireless, the sleep had to be 60 sec.
>
> I am currently serving my digital media collection over a Samba server.
> I have the shares mapped to network drives on Windows machines, and as
> CIFS fs on linux. I followed the direction on Swerdna’s site ‘(here)’
> (http://www.swerdna.net.au/linhowtosambacifs.html). The mount command
> line works fine:
>
>
> Code:
> --------------------
> mount -t cifs -o username=klein,password=klein
> //192.168.1.70/SharedMedia /home/zak89/SharedMedia/
>
> --------------------
>
>
> I am dedicated to good passwords, as you can plainly see.
>
> However, the following line in fstab (also from Swerdna’s tutorial) is
> not working (that is, on reboot the shares are not automatically
> mounted):
>
>
> Code:
> --------------------
> //192.168.1.70/SharedMedia /home/zak89/SharedMedia/ cifs
> username=klein,password=klein,_netdev,uid=zak,gid=users 0 0
>
> --------------------
>
>
> Any ideas on this?
>
> (Come on, swerdna, ‘I voted for your tag group.’
> (http://tinyurl.com/985fp2) Now it’s your turn to help me. Just
> kidding. )
>
>
Did you set the crontab as described on Swerdna’s site? The basic problem is
that when fstab is read at boot the network is not yet functioning, thus the
crontab. I would suggest setting the “sleep” time to 20 rather than 10.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
OK, since you voted for my tags: Is there a typo? Should it be uid=zak89 (because you mount it in /home/zak89/etc, maybe zak doesn’t exist??)?
The CLI mount command works. The thing that’s different about the fstab mount, from the CLI mount is the uid,gid options. Try without that and see if it works, then think “why is that” if it does work.
Of course, the other responders (what’s the word?) points may be the problem instead.
My username is zak. However, my /home directory is zak89.
Actually, zak is my initials, and it’s my preferred spelling of my first name, Zachary. However, I tack 89 on the end to make it easier to get a username on forums etc. For some reason on my last install I changed it all to zak89 for consistency, but all my Linode accounts are “zak” and it makes it trickier when ssh-ing. So I changed my username back to zak. Confusing.
I highly suspect it’s related to the network not being brought up in time. I use a WG11v2 chipset with the rtl8187 driver and it’s always reluctant to connect.
Just kidding. )