[K12OSN] bootup slow -- nfs server not responding

Rob Owens rob.owens at biochemfluidics.com
Thu Sep 11 11:14:43 UTC 2008

Peter Scheie wrote:
> Rob Owens wrote:
>> george kocke wrote:
>>> Rob Owens wrote:
>>>> The reason I upgraded the RAM is because I've been getting slow boot
>>>> times on the thin clients, with the message "nfs server not responding"
>>>> showing up at least 10 times during the boot process.  The clients
>>>> eventually boot successfully.  The upgrade didn't seem to help, but
>>>> hey,
>>>> it was cheap and easy to try.
>>> Sorry if anyone else has responded with this, but the URL below helped
>>> me when I ran into this problem:
>>> http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding
>> This seems to have solved my problem.  I only tested it on PXE so far,
>> but the problem has completely disappeared when PXE booting.
>> For the archives:
>> My "append" line in pxelinux.cfg/default was slightly different than the
>> one shown on the wiki.  I simply added:
>>     MOPTS=nolock,ro,wsize=2048,rsize=2048
>> to the end of my existing "append" line.
> I've had to use this same setting with some clients with 100Mb NICs when
> they are plugged into a gigabit port on the swithc (say, an 8-port
> switch with all gbit ports), even though they boot just fine when
> plugged into a 100Mb port (and server is plugged into the gbit port).
That's exactly my situation!  In fact, our old 100Mb switch (with 1000Mb
uplink) recently went bad, and was replaced with a full 1000Mb switch.
I guess that must be when the trouble started.


The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. If you are not the addressee, any disclosure, reproduction,
copying, distribution, or other dissemination or use of this transmission in
error please notify the sender immediately and then delete this e-mail.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted lost, destroyed, arrive late or
incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message which arise as a result of e-mail
transmission. If verification is required please request a hard copy


More information about the K12OSN mailing list