I’m sorry, forgot an important thing /etc/fstab. Here it is, but as a note after this restart in the morning I got access to both shares.
/dev/disk/by-id/ata-TOSHIBA_MK1031GAS_Z58P1118S-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK1031GAS_Z58P1118S-part2 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-TOSHIBA_MK1031GAS_Z58P1118S-part3 /home ext4 acl,user_xattr 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
#here is my samba share added manually
//192.168.1.1/australia /home/dan/australia cifs credentials=/home/dan/.ssh/.creds,_netdev,uid=dan,gid=users 0 0
#this was an attempting to add the share as a samba share unsuccessfully then i switched to nfs
#//192.168.1.9/home/dan/vuze_aruba/ /home/dan/aruba ext4 credentials=/home/dan/.ssh
#this is the nfs share which was added automatically by Yast I think
/.creds,_netdev,uid=dan,gid=users 0 0
aruba:/ /home/dan/australia2 nfs4 defaults 0 0
As I said noticed that the problem solved by itself and hopefully it will be like this or might be just not consistent I will have to live the experience.
to answer arvidjaar :
By prior to this I meant by adding a NFS share.
Samba share at boot time would be added to a specified location as in /etc/fstab. like it does now.
as per deano_ferrari’s suggestion I added the contents of /etc/fstab for a better understanding of the problem.
Now some more questions:
Isn’t it the same series of events that happen at boot? most certainly is. Maybe adding a delay in adding the share would increase the chances that the network is available and the shares will be added every time. The connection is from a laptop(wireless) to another desktop (cable connected) to the lan. Maybe the wireless connection adds a degree of delay to connect to the network and the samba and nfs protocol sometimes will make it on the final retry, like this morning.
Is that a parameter which could be changed? nr of retries?
I know that with samba if it is unsuccessful at start then you have to add it manually. Is the NFS client/server a continuous search and connect when/if available? or just at boot and that’s it?
As expected the Samba protocol is inconsistently mapping the share because of the network connection(wireless) which is not always there at athat specific time in boot. Sometimes is mounted, sometimes is not. I will try to delay the process. Meanwhile the NFS share is always there after boot, so very reliable.
>
>Hey…
>Is there any official fix for this? I have installed a new system and I
>just want to mount the NFS like I use to do it for decades… (is that
>too much to ask?? )
>I’m having the same issues. System boot too fast but not all the
>volumes get properly mounted (/etc/fstab)…
>Thanks
>Happy new year!
On 2013-05-13 23:21, Larry Finger wrote:
> On 05/13/2013 03:56 PM, qsummon wrote:
>>
>> Have this issue be addressed in OpenSuse 12.3?
>> Does anybody knows?
>
> It worked in 12.1 and 12.2, at least for me.
>
> You need to be a bit more specific about your problem.
He started this thread a year ago - all the details are here already
qsummon: systemd is supposed to be much better than it was, so the only
way to know is test it.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
)