Am 28.09.2013 17:31, schrieb Steven Hess:
Trying to create some NFS mounts in YAST hangs at 50% and does not continue or recover. Create entries to fstab but renders system unbootable even in recovery mode.
I have no useful other data and am a complete newbie to testing so I can't really create a bug report against the new ruby YAST
Running KDE on x64 13,1 beta System is a Dell 775 Optiflex core two duo with 3 gb ram
Steven
I got the same problem. systemctl status nfs.service gave me the answer: lxvm1:/mnt # systemctl status nfs.service nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: activating (start) since Sun 2013-09-29 16:52:09 CEST; 1min 1s ago Control: 3911 (nfs) CGroup: /system.slice/nfs.service ├─3911 /bin/bash /etc/init.d/nfs start ├─3932 /usr/sbin/rpc.idmapd ├─3935 mount -at nfs,nfs4 ├─3936 /sbin/mount.nfs4 192.168.0.8:/Bilder /mnt/bilder -o rw └─3938 /usr/sbin/rpc.gssd -D Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: unable to resolve 192.168.0.8 to hostname: Name or service not known Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: failed to read service info Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: unable to resolve 192.168.0.8 to hostname: Name or service not known Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: failed to read service info Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: unable to resolve 192.168.0.8 to hostname: Name or service not known Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: failed to read service info Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: unable to resolve 192.168.0.8 to hostname: Name or service not known Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: failed to read service info Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: unable to resolve 192.168.0.8 to hostname: Name or service not known Sep 29 16:52:10 lxvm1 rpc.gssd[3938]: ERROR: failed to read service info --> I added an entry for IP 192.168.0.8 (my NFS test server) to /etc/hosts and startet the YaST2 nfs client configuration again. This time it did work. regards, Hendrik -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org