[Mageia-discuss] fstab problem

[Anne Wilson]

On 15/06/12 19:13, Frank Griffin wrote:
> On 06/15/2012 01:42 PM, AL13N wrote:
>> Op vrijdag 15 juni 2012 16:46:03 schreef Anne Wilson:
>>> 'mount: wrong fs type, bad option, bad superblock on
>>> 192.168.0.200:/Anne,
>>>
>>> has dmesg something? did you have nfs in lsmod?
>>>
>
> Shortly before release I and others noticed that a lot of basic services
> that were converted to systemd were no longer starting automatically at
> boot. I thought that it was fixed, but you might check to see that NFS
> has actually been started.

Combining replies:

Sander:  nfs-utils-clients wasn't installed on the misbehaving laptop. 
After installation, all the 192.168.0.40 mounts work, the 192.168.0.200 
ones don't.  More digging to be done.

The errors for those two are:

'mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified'

Not sure what I have to do about statd - my efforts don't seem to have 
achieved much.

AL113N: 'useer' is a red herring :-)  I was typing what I could see on 
the netbook screen.  This is a new install and I hadn't slowed down the 
keyboard repeat - doing that now.  dmesg didn't have anything to say, 
and nfs is in lsmod.

Frank: since the 192.168.0.40 mounts are now working, I think we can 
assume that nfs is started.  Or maybe not - nfs-common.service is 
reported as loaded but dead.  I've restarted it, but it has no effect on 
the troublesome mounts.

Anne
-- 
Need KDE help? Try
http://userbase.kde.org or
http://forum.kde.org