please help: NFS client setup with Yast does not work in 13.2

English Network/Internet
1

Hi,
I am trying to get my desktop connected with my NAS system. In terminal mode with su and the command:

mount //192.168.x.x/folder /NAS/localfolder

it works perfectly (after I confirm the password) and I can access the NAS-folders through e. g. Dolphin. However, I would like to automount upon startup, so I am trying with Yast, but still failing to set it up correctly.

In Yast, I type in the commands (paths see above) in the NFS client setup dialogue and get a return message:
Unable to mount the NFS entries from /etc/fstab

Any help is very much appreciated.

Best,
Knut

2

Yiou then better show us what is in your /etc/fstab

cat /etc/fstab

I also read that you have to type a password when mounting. How do you think that can work during boot time?

3

On 2015-08-06 13:46, hcvv wrote:

> I also read that you have to type a password when mounting. How do you
> think that can work during boot time?

If he has to enter a password, it can’t be NFS, but Samba. YaST NFS
module will not work.

To verify this situation, the output of “mount | grep NAS” would say.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

4

Thanks for your replies. To answer your questions:

cat /etc/fstab returns the following:

/dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part2 / reiserfs acl,user_xattr 1 1
/dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part3 /home reiserfs defaults 1 2

please allow my comment:
I did try various entries into fstab; all causing major crashes during startup, so I deleted them all. Any idea how to insert the paths correctly?

mount | grep NAS

does not return anything.

No, it is not Samba (I did not configure Samba at all, so I doubt it is running).

Many thanks again,
Knut

5

First:
Please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

Then, your fstab does not contain any entry for your NFS (or whatever it is) mount. Thus YaST did not create that. Maybe you better explain with “YaST NFS module will not work.”. That is of course very vague and can range from “there is no YaST NFS Client module in the list” until “I configured it with YaST, buit it does not mount” and anything in between ad beyond.

And last, ir seems that you executed that mount | grep statment while it is not mounted. That does not show very much. So we do another one:

  1. mount the file system in the way you do it always manualy
  2. show us the complete
mount

And about that password you mention. Do you mean the root password that belongs to the su command?

6

On 2015-08-06 20:26, carverknut wrote:
>
> Thanks for your replies. To answer your questions:
>
> cat /etc/fstab returns the following:

Hum.

Nex time, please use code tags for pasting all that. Use the ‘#’ button
in the forum editor - for command outputs and listings
http://susepaste.org/images/15093674.jpg


> /dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part1        swap    swap    defaults 0 0
> /dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part2        /       reiserfs        acl,user_xattr 1 1
> /dev/disk/by-id/ata-Hitachi_HDP725050GLA360_GEC534RJ0408SE-part3        /home   reiserfs        defaults 1 2

> please allow my comment:
> I did try various entries into fstab; all causing major crashes during
> startup, so I deleted them all. Any idea how to insert the paths
> correctly?

Well, the trick is NOT to reboot to try an fstab modification, but try
it yourself before.

> mount | grep NAS
>
> does not return anything.

Then the NAS is not mounted. Please repeat with it mounted. Change the
word “NAS” above with whatever directory you use to actually mount the NAS.

> No, it is not Samba (I did not configure Samba at all, so I doubt it is
> running).

Well, NFS doesn’t use password. Samba does.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

7

OK, second go.

I have mounted (as described above as su; the NAS requires any user to give a password to acces the respective folders and authorizations read/write, read only, etc.)) and this is what

mount | grep NAS

returns:

//192.168.1.2/share on /NASknut/share type cifs (rw,relatime,vers=1.0,cache=strict,username=knut,domain=NASKNUT,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.2,unix,posixpaths,serverino,acl,rsize=1048576,wsize=1048576,actimeo=1)

cat /etc/fstab

returns the same output as before, i. e. my local hard disks and partitions.

I expected Yast to mount the NAS with the corresponding folders and to give it a mount point, so users can access them with their passwords and use the files on the NAS. Hmm.

Many thanks for your support again,
Knut

8

… and some more:

mount | grep NASknut

returns the following (upon manual mount through su in terminal mode)


//192.168.1.2/share on /NASknut/share type cifs (rw,relatime,vers=1.0,cache=strict,username=michael,domain=NASKNUT,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.2,unix,posixpaths,serverino,acl,rsize=1048576,wsize=1048576,actimeo=1)
9

Pl;ease do not separate command and output and also copy/paste the prompts wityh it… E.g.:

henk@boven:~> mount | grep run
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
gvfsd-fuse on /run/user/500/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=500,group_id=500)
gvfsd-fuse on /var/run/user/500/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=500,group_id=500)
henk@boven:~>

And your output shows that it is mounted cifs. That is NOT NFS. It is some SAMBA thingy andI personaly have no knowledge about SAMBA (I have about NFS, that is why I bothered to answer here).

But there will be many peolpe that have SAMBA knowledge about cifs mounts. Thus just wait and see.

And of course your /etc/fstab did not change. We (you) did not do anything with it.

And you forgot to explain wshat you mean with “YaST NFS module will not work.” Please read the posts here carefully and aser all questions. Even when a question/request is not clear or whateveer, at least tell that. Not getting answeers is frustrating for helpers. And frustrated helpers will leave your thread.
BTW, forget that YaST NFS now, as this is no NFS, it is of no importance anymore.

10

Hi,
thanks for the hint on typesetting. I will try to improve on this.

Well, what I want is to mount the respective drives/folders on my NAS in order to access various users with their desktop machines to use them in everyday life. I would like to have an automated mount upon startup (with a later password keyed in). Being a user rather than a network expert, please excuse my limited skills.

I mean by saying “Yast does not work in mounting NFS” that I expected Yast to update /etc/fstab with the NAS routing data (e. g. 192.168.x.x and so on) once I entered all the data and make it available after startup. But it does not - for reasons I cannot tell or even resolve. Now I learn that it is cifs - can that be automatically mounted upon startup?

As long as it is convenient for users to access their NAS folders upon startup of their machines, I do not care if it is NFS or cifs (but that is just my user’s perspective).

Best,
Knut

11

On 2015-08-07 12:26, carverknut wrote:

> I mean by saying “Yast does not work in mounting NFS” that I expected
> Yast to update /etc/fstab with the NAS routing data (e. g. 192.168.x.x
> and so on) once I entered all the data and make it available after
> startup. But it does not - for reasons I cannot tell or even resolve.
> Now I learn that it is cifs - can that be automatically mounted upon
> startup?

YaST NFS Client module fails because it is not an NFS share, it is a
Samba, aka cifs, share.

There is a yast2-samba-client module, though, but it is called “Windows
domain membership”, so that will not be useful in this case, I’m afraid

> As long as it is convenient for users to access their NAS folders upon
> startup of their machines, I do not care if it is NFS or cifs (but that
> is just my user’s perspective).

Basically, NFS is Unix/Linux style. Samba is Windows style. The crucial
difference is that Samba does not, can not, use Linux attributes
(permissions, ownership) on files. Thus, you can not use that NAS to do
Linux backups.

The line in fstab should be something similar (untested) to


//192.168.1.2/share  /NASknut/share cifs defaults,nofail  0 0

If a password is needed, it can go into another file, but I don’t
remember how. Have a read here:

> Samba and Suse: HowTo Set up an openSUSE-Windows Home Office LAN/Network.

The site is not up 24 hours a day, but it explains all the details well.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

12

I understand why you want it. But as the password is asked when you mount it, I do not see how you can mount first and add the password later. It is mounted or not.
But again, let people who know about cifs answer this.

It is of no importance anymore, because it isn’t NFS. But you still do not say where you entered all the data. YaST is a huge lump, when you start it, it offers al lot of subjects. You do not tell anything about what yoy clicked and what you got and when you filled in exactly what. It is not nice to explain in text all you do with a GUI interface (that is why we prefer commands that can be shown easy here), but you have to.
Thus next time, you want to explain anything you did with a GUI, tell all steps. Do never assume that the reader will understand anything you do not tell.

You have to use what the NAS povides. we can not know what the NAS offers. You must read it’s manual to know if it offers NFS or not.

13

On 2015-08-07 15:26, hcvv wrote:

> I understand why you want it. But as the password is asked when you
> mount it, I do not see how you can mount first and add the password
> later. It is mounted or not.

“man mount.cifs” explains it :slight_smile:

Best would be to use “credentials=filename” in the options section of
the fstab line.

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

14

Hi,
the NAS system I use is a Synology 415+ type. I guessed that it would also feature linux NFS connections. You proved me wrong. Thanks for clarifying. I thought (being a major linux fan and long-time user), NFS would be the protocol to apply.

Well, then it should be cifs. Thanks for the help and the link. I shall come back and ask for more help if I do not succeed with the starting help. Cross fingers!

best,
Knut

15

When you checked it’s documentation and it does not mention NFS at all, it will not provide it.

When you bought the NAS, you should have checked before bying. Quessing is habit you must try to get rid of in the computer world.

16

On 2015-08-07 19:36, carverknut wrote:
>
> Hi,
> the NAS system I use is a Synology 415+ type. I guessed that it would
> also feature linux NFS connections. You proved me wrong. Thanks for
> clarifying. I thought (being a major linux fan and long-time user), NFS
> would be the protocol to apply.

According to my local provider, it supports FTP, SMB2, AFP, NFS and WebDAV.

And also according to the manufacturer:

https://www.synology.com/en-global/products/DS415+

«Enjoy seamless files sharing across Windows®, Mac®, and Linux®
platforms as DS415+ offers comprehensive network protocol support
including FTP, SMB2, AFP, NFS and WebDAV. With Windows AD and LDAP
integration, DS415+ can fit effortlessly into any existing network
environment - there is no need for IT administrators to maintain two
sets of credentials. You also won’t worry about missing files with the
Recycle Bin feature which is supported on AFP, CIFS, File Station, and
WebDAV. All files deleted in a shared folder will be automatically moved
into the Recycle Bin. Learn more»

You probably have to enable or configure it on the NAS.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

17

Hi,
this is why I initially wanted to start over with NFS. But cifs is OK, too. What do you suggest?

By the way, adding this line to fstab


//192.168.1.2/share  /NASknut/share cifs defaults,nofail  0 0

produces a clean startup. Also positive: Dolphin (the file manager) shows the mounted device /NASknut/share. Unfortunately, when I click on it,
I get an error message by Dolphin saying that


An error occurred while accessing 'share on 192.168.1.2', the system responded: mount: only root can mount //192.168.1.2/share on /NASknut/share

What am I doing wrong?

18

Hi,
concerning NFS setup on the NAS: I enabled the NFS service for all respective users and folders, also NFSv4.

But, as said before, I am also happy with cifs up and running.

best,
Knut

19

On 2015-08-07 20:36, carverknut wrote:

> produces a clean startup.

Heh. The “nofail” in the line is a safeguard: if it is impossible to
mount it, mount will say nothing, and boot proceeds. You have to verify
the output of “mount” to verify that it did mount.

> What am I doing wrong?

add “users”. Ie “nofail,users”.

Try “mount /NASknut/share” without rebooting. If it asks for a password,
abort. Read the manual and add a credentials file.

Me, I prefer NFS, if I’m going to use Linux.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

20

Hi,
with your help, cifs is working nicely. Users can access their folders on the NAS automatically. Problem solved. Eeeh, almost. What, if I still wanted NFS… ?

best,
Knut