Running 11.4 and a wifi link to lan, I set up an NFS share with NAS exactly as I had with 11.3.
Big problem. I am now locked out of my system as when I try and boot, the boot process stalls waiting for NFS. Of course there is no wifi link at this stage in the boot process so I am stuffed.
There must have been something in the shutting down process which stopped this in 11.3?
I have tried safe mode boot but still no luck.
Please could somebody help me get past this so I can boot up and then delete the NFS share until there is a fix?
Budgie2
PS How can I look at the boot log, assuming I can ever boot the system again? In addition to the line showing the above NFS problem, there is another long error message which I want to post here for advice. There used to be a log access button somewhere, I thought in Yast but can’t see it now.
On Tue, 05 Jul 2011 23:36:02 +0000, Budgie2 wrote:
> Please could somebody help me get past this so I can boot up and then
> delete the NFS share until there is a fix?
From the grub menu, type “s” or “1” and enter your root password - that’ll
get you into single user mode, and you can comment out the offending line
in the /etc/fstab file.
On 07/05/2011 06:51 PM, Jim Henderson wrote:
> On Tue, 05 Jul 2011 23:36:02 +0000, Budgie2 wrote:
>
>> Please could somebody help me get past this so I can boot up and then
>> delete the NFS share until there is a fix?
>
> From the grub menu, type “s” or “1” and enter your root password - that’ll
> get you into single user mode, and you can comment out the offending line
> in the /etc/fstab file.
If you have some patience, it will time out after 180 seconds.
Of course there is no wifi link at this stage in the boot process
That is not true allways. Only if you use network manager (which was not what you said). When you use ifup,the network will start before NFS is mounted (wifi or not).
Hi and thanks to all for the help. I am back on line with laptop once more.
Henk, I was using network manager so I shall change back to ifup as I need the NFS mount at my base location. . This begs two questions:
what is the advantage of network manager?
If I revert to ifup and go to a different location where NFS will not be available will I have a similar problem on booting?
In a normal Unix/Linux system, the network is configured (by root) and then everything works as intended by the designers of Unix.
In a system where you walk around with the box, using on all sorts of places where you need different network configurations or even have to choose between the (wifi) networks available, it is the loged in end-user who must be able to do things. This is often the case with laptops. The end-user must have a tool to configure the network without becoming root and using the CLI or YaST to do the configuration. Therefore network manager was invented. There is a server program (a deamon) that runs as root and does the real configuration and there are clients like knetworkmanager, that are the end-user interface to this deamon.
It might be clear to you that when the end-user configured (indirect) the network, (s)he can only do this after (s)he is loged in and the client is started. And as login is logicaly way after the boot process, the network is only available after one of the end-users loged in (I even dare not guess what happens when several users log in and all try to use their network manager client ). However there are possibilities to configure the deamon in such a way that a default configuration is used when the deamon is started, thus making the network available much earlier. I do not use NM, thus I can not help you here.
Thus one must decide if one goes for ifup or network manager after assessing he use of the system (fixed network configuration or walk around one. Regardless of cabled/wifi.
I have a n NFS client system here which sometimes boot without the NFS server being available (not to moving the client, but simlpy because the server is down). This never gives any extra waiting during boot.
Hi Henk,
Many thanks for the clear and helpful rationale for Network Manager. What you say makes sense and I agree that when away from home it does make life easier. My travels now are sadly rare and I use my laptop at home so changing to ifup does not create any problems.
Having changed to ifup method however, I am still experiencing the 3 min delay during boot. From the booting text that scrolls up screen during boot, the system tries to use eth0 and fails (because eth0 is not connected) and then goes straight to NFS. It does not set up wlan0 until after the delay. Any ideas why your explanation does not apply here?
You apparently haven’t configured eth0 and/or wlan0 correct. And you fail to tell if the waiting for eth0 is when the cable is connected or not.
Either check evreything in the appropriate YaST module or/and post the contents of /etc/sysconfig/network/ifcfg-eth0 and* /etc/sysconfig/network/ifcfg-wlan0*.
It could be that the starting of the wifi runs parallel to the rest of the startup runs and takes considerable time. Different from a cabled NIC. @Ecky’s solution seems to be usable (if the starting of the wifi does not take so much time that even that is to quick).
Hi hcvv,
I have no trouble with eth0. I was trying to explain what happened during boot process. Since I posted there have been other replies and I like the suggestion of only starting NFS after I have wifi connection. I shall try that as I think it is the correct approach.
Thanks again all.
I shall now return to trying to diagnose my AP problem which has become so bad I have had to boot into Windoze XP to post this. As a result of changing to ifup and back again I have a (2) after the SSID on laptop! This happens even after I have deleted all old connection details I can see. How can I flush all the old rubbish so I can start again with a clean system? Rebooting doesn’t do it.
Budgie2
On 2011-07-08 02:06, Budgie2 wrote:
> 1. what is the advantage of network manager?
Easier on the move.
> 2. If I revert to ifup and go to a different location where NFS will
> not be available will I have a similar problem on booting?
Yep.
Time ago there was a feature called “profiles”. We could boot with a
different profile, that would change such things. Different configurations
for different sites - and not only the network.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
robin I’m not entirely even sure what that means though I have seen something like starting mandatory interfaces in boot msgs
Going on what the word mandatory means I’m guessing something like an interface that must be started because something relies on it, such as trying to start the wi-fi adaptor because nfs depends on it maybe?
The thing with using after.local to start ntfs, it does work faster on ifup than using network manager, but even then still not soon enough to be using an nfs export for /home though again, I’ve only tried it on laptops and the power management of wi-fi adaptors works differently in laptops than dekstops I think?
Might there even be a difference if using a usb adaptor in a laptop rather than it’s onboard one, I think I have a usb one lying around here somewhere I’ll see if I can dig it out later and compare
On 2011-07-12 21:36, Ecky wrote:
>
> robin I’m not entirely even sure what that means though I have seen
> something like starting mandatory interfaces in boot msgs
>
> Going on what the word mandatory means I’m guessing something like an
> interface that must be started because something relies on it, such as
> trying to start the wi-fi adaptor because nfs depends on it maybe?
Yes, that’s the idea. the wifi interface has to be defined as mandatory, so
that boot up waits till ready, instead of continuing.
/etc/sysconfig/network/config:
Type: string
Default: “”
Here you may specify which interfaces have to be up and configured properly
after ‘rcnetwork start’. rcconfig will return ‘failed’ if any of these
interfaces is not up. You may use interface names as well but better use
hardware descriptions of the devices (eth-id-<macaddress> or eth-bus-…
See
man ifup for ‘hardware description’). The network start script will wait for
these interfaces, but not longer as set in WAIT_FOR_INTERFACES.
You need not to add dialup or tunnel interfaces here, only physical devices.
The interface ‘lo’ is always considered to be mandatory and can be omitted.
If this variable is empty, rcnetwork tries to derive the list of mandatory
devices automatically from the list of existing configurations.
Configurations
with names bus-pcmcia or bus-usb or with STARTMODE=hotplug are skipped. (try
On 2011-07-13 03:36, Ecky wrote:
>
> Interesting stuff
>
> So in theory then setting the wi-fi adaptor as mandatory it should come
> up before starting any services that rely on the network such as nfs
> right?
That is what I expect, yes.
> 2.23 am here and I need my beauty sleep so that’s something to play
> with tomorrow
4:27 here :-p
Keep us posted on the result
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Well the result is … darned home was mounting all along!
Dropped into a console instead of trying to login from kdm, logged in and then issued an ls, list of files I got was those in the nfs /home, opened a couple of files in vi and all was cool
So, I issued a startx and found it was a different problem, I get a .xsession-errors permission denied error, which explains the kstartupconfig4 error I was getting from kdm
Checked out the permissions on the .xsession-errors file and it’s read & write for the user
Next thing I tried was connecting the laptop with a cable instead of wi-fi and there was no such error
So, the issue isn’t mounting the nfs /home after all, turns out I can’t start X over wi-fi when using an nfs /home whereas I can over a cable using the nfs /home for some reason, tried resetting the permissions but made no difference
No ideas on what I can try to resolve that one
Incidentally, whether the adaptor is set to mandatory or not makes no difference whatsoever to this behaviour, but one point on that, if I set it to mandatory using the hw address as displayed in ifconfig get a no interface detected msg, setting it with wlan0 worked
Hi guys,
As OP I am following this thread and hope you can find an answer. In the meantime I cancel my nfs share before closing and open again when I need it.
I think it has been stated before, but ifup does not solve the problem. The mandatory service approach seems convincing but I cannot quite follow what I must edit to mandate wlan0 being up. If this is indeed the solution please could you advise what I should do in due course.
Meanwhile and as I type this my NetworkManager applet continues to show repeated disconnects and reconnects and I shall start a new thread on this problem.
Many thanks,
). However there are possibilities to configure the deamon in such a way that a default configuration is used when the deamon is started, thus making the network available much earlier. I do not use NM, thus I can not help you here.