Mount an smb share with fstab vs sudo mount… problems
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
This works in the terminal.. sudo mount -t cifs -o username=user,password=pass //10.100.136.4/bus /media/bus
This does not work in fstab on boot.. //10.100.136.4/bus /media/bus cifs username=user,password=pass,_netdev 0 0
What am I doing wrong? I need this to automatically mount this share on boot.
I can run sudo mount -a and mount the drive manually after boot, so I thought maybe the _netdev is not delaying properly? I have set a static IP in the network manager but have not tried in /etc/network/interfaces yet, that shouldn't make a difference but??
cfis-utils is installed.
Another odd thing is when I connect to the share in Gnome>Files>Connect to Server with the same creds, I get rw access to the share. But when using the mount command, I only have read permission. Same when I connect to the share in Windows, read and write. This really isn't an issue as even though I cannot write to the share, the application that I need to backup to the share can!?
I would really like to understand that.
The share is on another ubuntu desktop. I created a new linux user "user", a new group, assigned that user to the group, set permissions.. pretty much followed this tut..https://www.linuxbabe.com/ubuntu/system-config-samba-ubuntu-16-04
ubuntu samba fstab cifs
asked Sep 11 at 0:48
Paul
61
add a comment |Â
up vote
1
down vote
favorite
This works in the terminal.. sudo mount -t cifs -o username=user,password=pass //10.100.136.4/bus /media/bus
This does not work in fstab on boot.. //10.100.136.4/bus /media/bus cifs username=user,password=pass,_netdev 0 0
What am I doing wrong? I need this to automatically mount this share on boot.
I can run sudo mount -a and mount the drive manually after boot, so I thought maybe the _netdev is not delaying properly? I have set a static IP in the network manager but have not tried in /etc/network/interfaces yet, that shouldn't make a difference but??
cfis-utils is installed.
Another odd thing is when I connect to the share in Gnome>Files>Connect to Server with the same creds, I get rw access to the share. But when using the mount command, I only have read permission. Same when I connect to the share in Windows, read and write. This really isn't an issue as even though I cannot write to the share, the application that I need to backup to the share can!?
I would really like to understand that.
The share is on another ubuntu desktop. I created a new linux user "user", a new group, assigned that user to the group, set permissions.. pretty much followed this tut..https://www.linuxbabe.com/ubuntu/system-config-samba-ubuntu-16-04
ubuntu samba fstab cifs
asked Sep 11 at 0:48
Paul
61
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
This works in the terminal.. sudo mount -t cifs -o username=user,password=pass //10.100.136.4/bus /media/bus
This does not work in fstab on boot.. //10.100.136.4/bus /media/bus cifs username=user,password=pass,_netdev 0 0
What am I doing wrong? I need this to automatically mount this share on boot.
I can run sudo mount -a and mount the drive manually after boot, so I thought maybe the _netdev is not delaying properly? I have set a static IP in the network manager but have not tried in /etc/network/interfaces yet, that shouldn't make a difference but??
cfis-utils is installed.
Another odd thing is when I connect to the share in Gnome>Files>Connect to Server with the same creds, I get rw access to the share. But when using the mount command, I only have read permission. Same when I connect to the share in Windows, read and write. This really isn't an issue as even though I cannot write to the share, the application that I need to backup to the share can!?
I would really like to understand that.
The share is on another ubuntu desktop. I created a new linux user "user", a new group, assigned that user to the group, set permissions.. pretty much followed this tut..https://www.linuxbabe.com/ubuntu/system-config-samba-ubuntu-16-04
ubuntu samba fstab cifs
asked Sep 11 at 0:48
Paul
61
This works in the terminal.. sudo mount -t cifs -o username=user,password=pass //10.100.136.4/bus /media/bus
This does not work in fstab on boot.. //10.100.136.4/bus /media/bus cifs username=user,password=pass,_netdev 0 0
What am I doing wrong? I need this to automatically mount this share on boot.
I can run sudo mount -a and mount the drive manually after boot, so I thought maybe the _netdev is not delaying properly? I have set a static IP in the network manager but have not tried in /etc/network/interfaces yet, that shouldn't make a difference but??
cfis-utils is installed.
Another odd thing is when I connect to the share in Gnome>Files>Connect to Server with the same creds, I get rw access to the share. But when using the mount command, I only have read permission. Same when I connect to the share in Windows, read and write. This really isn't an issue as even though I cannot write to the share, the application that I need to backup to the share can!?
I would really like to understand that.
The share is on another ubuntu desktop. I created a new linux user "user", a new group, assigned that user to the group, set permissions.. pretty much followed this tut..https://www.linuxbabe.com/ubuntu/system-config-samba-ubuntu-16-04
ubuntu samba fstab cifs
ubuntu samba fstab cifs
asked Sep 11 at 0:48
Paul
61
asked Sep 11 at 0:48
Paul
61
asked Sep 11 at 0:48
Paul
61
asked Sep 11 at 0:48
Paul
61
asked Sep 11 at 0:48
Paul
61
61
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
You may try to wait a little. Change to your specs and add to /etc/rc.local:
(
until ping -nq -c3 10.100.136.4; do
# Waiting for network
sleep 1
done
mount -t cifs -o vers=1.0,credentials=/home/<user>/<creds_file>,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev //10.100.136.4/bus /media/bus 2> /home/<user>/mounterr.log
)&
Sure you may left the direct user/password in the command, but to have the special file with creds may be more convenient. The format of the file is
user=<user>
password=<password>
There may be some unexpected nuances. For example, I had to add "vers=1.0" whith the Linux Mint 18.3, while it was not necessary in 18.1.
answered Sep 11 at 2:58
darkSideOfTheMoon
162
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You may try to wait a little. Change to your specs and add to /etc/rc.local:
(
until ping -nq -c3 10.100.136.4; do
# Waiting for network
sleep 1
done
mount -t cifs -o vers=1.0,credentials=/home/<user>/<creds_file>,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev //10.100.136.4/bus /media/bus 2> /home/<user>/mounterr.log
)&
Sure you may left the direct user/password in the command, but to have the special file with creds may be more convenient. The format of the file is
user=<user>
password=<password>
There may be some unexpected nuances. For example, I had to add "vers=1.0" whith the Linux Mint 18.3, while it was not necessary in 18.1.
answered Sep 11 at 2:58
darkSideOfTheMoon
162
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
add a comment |Â
up vote
1
down vote
You may try to wait a little. Change to your specs and add to /etc/rc.local:
(
until ping -nq -c3 10.100.136.4; do
# Waiting for network
sleep 1
done
mount -t cifs -o vers=1.0,credentials=/home/<user>/<creds_file>,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev //10.100.136.4/bus /media/bus 2> /home/<user>/mounterr.log
)&
Sure you may left the direct user/password in the command, but to have the special file with creds may be more convenient. The format of the file is
user=<user>
password=<password>
There may be some unexpected nuances. For example, I had to add "vers=1.0" whith the Linux Mint 18.3, while it was not necessary in 18.1.
answered Sep 11 at 2:58
darkSideOfTheMoon
162
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
add a comment |Â
up vote
1
down vote
up vote
1
down vote
You may try to wait a little. Change to your specs and add to /etc/rc.local:
(
until ping -nq -c3 10.100.136.4; do
# Waiting for network
sleep 1
done
mount -t cifs -o vers=1.0,credentials=/home/<user>/<creds_file>,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev //10.100.136.4/bus /media/bus 2> /home/<user>/mounterr.log
)&
Sure you may left the direct user/password in the command, but to have the special file with creds may be more convenient. The format of the file is
user=<user>
password=<password>
There may be some unexpected nuances. For example, I had to add "vers=1.0" whith the Linux Mint 18.3, while it was not necessary in 18.1.
answered Sep 11 at 2:58
darkSideOfTheMoon
162
You may try to wait a little. Change to your specs and add to /etc/rc.local:
(
until ping -nq -c3 10.100.136.4; do
# Waiting for network
sleep 1
done
mount -t cifs -o vers=1.0,credentials=/home/<user>/<creds_file>,iocharset=utf8,file_mode=0775,dir_mode=0775,_netdev //10.100.136.4/bus /media/bus 2> /home/<user>/mounterr.log
)&
Sure you may left the direct user/password in the command, but to have the special file with creds may be more convenient. The format of the file is
user=<user>
password=<password>
There may be some unexpected nuances. For example, I had to add "vers=1.0" whith the Linux Mint 18.3, while it was not necessary in 18.1.
answered Sep 11 at 2:58
darkSideOfTheMoon
162
answered Sep 11 at 2:58
darkSideOfTheMoon
162
answered Sep 11 at 2:58
darkSideOfTheMoon
162
answered Sep 11 at 2:58
darkSideOfTheMoon
162
162
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
add a comment |Â
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Yes, that would certainly work... as a workaround, but it should not be this hard to mount at boot but appears it may be. I had not seen this post when i asked the question here but it seems very similar with similar suggestions to yours. [linuxquestions.org/questions/slackware-14/delay-mount-947028/]
– Paul
Sep 12 at 12:39
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
Sure I've found it somewhere, but lost the link (your link in wrong, BTW). And I don't see why does it seem hard at all. At least to try.
– darkSideOfTheMoon
Sep 13 at 18:06
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
LoL, can't even get a link right... it is linuxquestions.org/questions/slackware-14/delay-mount-947028 I ended up using AutoFS... which is what i should have used to begin with.
– Paul
Sep 18 at 21:45
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f468141%2fmount-an-smb-share-with-fstab-vs-sudo-mount-problems%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password