NFS shares fail to mount in 12.3 beta bug or just me?

English Install/Boot/Login
#1

I don’t know that is is a bug or a bad configuration on my part so I am asking here before wasting anyone’s time on bugzilla.

I created the mount points using Yast2 NFS Client set up

The fstab entries were made correctly by Yast2 NFS Client setup.

 /dev/disk/by-id/ata-ST3250823AS_3ND1T4AT-part1    swap    swap    defaults 0 0 
/dev/disk/by-id/ata-ST3250823AS_3ND1T4AT-part2    /    ext4    acl,user_xattr 1 1 
/dev/disk/by-id/ata-ST3250823AS_3ND1T4AT-part3    /home    ext4    defaults 1 2 
proc    /proc    proc    defaults 0 0 
sysfs    /sys    sysfs    noauto 0 0 
debugfs    /sys/kernel/debug    debugfs    noauto 0 0 
usbfs    /proc/bus/usb    usbfs    noauto 0 0 
devpts    /dev/pts    devpts    mode=0620,gid=5 0 0 
192.168.1.100:/bu/5002012    /5002012    nfs    defaults 0 0 
192.168.1.100:/Four/NewPlace    /Four/NewPlace    nfs    defaults 0 0 
192.168.1.100:/data/adata    /data/adata    nfs    defaults 0 0 
192.168.1.100:/mmshare/mmshare    /mmshare/mmshare    nfs    defaults 0 0 
192.168.1.100:/home/flamebait/Music    /Flamebait/music    nfs    defaults 0 0 
192.168.1.100:/home/flamebait/asusAnime    /asusAnime    nfs    defaults 0 0 
192.168.1.100:/moreAnime/reallybigplace    /realltbigplace    nfs    defaults 0 0

Yast2 NFS client set up fails hanging at 50% for quite a while and finally returns this error when it goes to mount the shares:
"Unable to mount the NFS entries from fstab?

The error messages from the boot log are

[1;32m  OK  [0m] Reached target Remote File Systems (Pre).
         Mounting /realltbigplace...
         Mounting /asusAnime...
         Mounting /Flamebait/music...
         Mounting /mmshare/mmshare...
         Mounting /data/adata...
         Mounting /Four/NewPlace...
         Mounting /5002012...
         Starting SuSEfirewall2 phase 2...
[1;32m  OK  [0m] Started SuSEfirewall2 phase 2.
[1;31mFAILED[0m] Failed to mount /realltbigplace.
See 'systemctl status realltbigplace.mount' for details.
[1;33mDEPEND[0m] Dependency failed for Remote File Systems.
[1;33mDEPEND[0m] Dependency failed for Postfix Mail Transport Agent.
[1;31mFAILED[0m] Failed to mount /asusAnime.
See 'systemctl status asusAnime.mount' for details.
[1;31mFAILED[0m] Failed to mount /Flamebait/music.
See 'systemctl status Flamebait-music.mount' for details.
[1;31mFAILED[0m] Failed to mount /mmshare/mmshare.
See 'systemctl status mmshare-mmshare.mount' for details.
[1;31mFAILED[0m] Failed to mount /data/adata.
See 'systemctl status data-adata.mount' for details.
[1;31mFAILED[0m] Failed to mount /Four/NewPlace.
See 'systemctl status Four-NewPlace.mount' for details.
[1;31mFAILED[0m] Failed to mount /5002012.
See 'systemctl status 5002012.mount' for details.

I looked in /var/logs but didn’t see any systemctl log. So I don’t have that info and am not sure where to look.

#2

This probably doesn’t answer your question. However, I am successfully using an NFS client on 12.3 Beta1.

I edited “/etc/auto.master”, created “/etc/auto.nfs”, and created one symlink (from the command line).

I used Yast run-level-services to setup nfs and autofs. There were a couple of bogus error messages, reported as bug 799491 but otherwise everything worked.

What I have not done (but should do) is attempted to setup an NFS server. I hope somebody else has tested that.

#3

I got it playing through multiple things.
Can’t say which one did it exactly.
I didn’t have to mess with any scripts.

100% playing everything I need right now.

#4

Had to prepare 10 PC’s for a customer and ran into the problem on 12.2. I found out that setting the network device to be activated " At boot " instead of " At cable connection " made the difference. Can anybody confirm this?

#5

That seemed to be the default I had when I looked in YAST2
Seemed I had to restart the NFS server on the machine with the share to get it to go. Once I did I could reboot and mount the shares during boot.
It looks like the system is looking for those shares before the interface is ready though.

#6

I use automount (autofs) to avoid that problem. I also want my laptop to be able to access the NFS shares when at home, but I don’t want that to interfere with booting when away from home.