archive mirror
 help / color / mirror / Atom feed
From: Wakko Warner <>
To: Marco Schwarz <>
Subject: Re: Serious Problems with diskless clients
Date: Thu, 26 Sep 2002 07:18:47 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>; from Marco Schwarz on Thu, Sep 26, 2002 at 12:26:40PM +0200

> my diskless clients have some severe problems on one of my servers.
> Sometimes (right now most of the time) everything just hangs at the same place when
> starting up the kernel. Here are the last messages I get (right before this
> IP-Config is running and looks OK):
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
> ds: no socket drivers loaded !
> Looking up port of RPC 100003/2 on
> portmap: server mot responding, timed out !
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on
> portmap: server mot responding, timed out !
> Root-NFS: Unable to get mountd port number from server, using default
> mount: server not responding, timed out
> Root-NFS: Server returned error -5 while mounting /netclients/
> VFS: Unable to mount root fs via NFS, trying floppy
> VFS: Insert root floppy and press ENTER
> I am thinking right now that we have some problems with network hardware,
> but maybe its a Software problem. Could someone tell me what the 'Looking up
> port of RPC 100003/2 on' in kernel startup is doing an why it
> could fail ?
> We have Kernel 2.4.10 on both server and clients (I also tried 2.4.19, but
> it changed nothing).

I have 2 diskless machines both tftping the kernel from the network and they
work just fine.  Both are using kernel 2.4.19 vanalla with a small patch to
force ip=auto if nfs=/dev/nfs

[wakko@gohan:/] uname -a
Linux gohan 2.4.19 #1 SMP Tue Sep 3 13:02:36 EDT 2002 i686 unknown
[wakko@gohan:/] mount
rod:/tftpboot/gohan on / type nfs
/proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)

It's a very small patch to make that work w/o saying ip=auto on the command
line (I did this originally because I used a kernel disk w/o a boot loader
on some boxes at work)

--- net/ipv4/ipconfig-orig.c	2001-11-19 20:48:35.000000000 -0500
+++ net/ipv4/ipconfig.c	2001-11-19 20:56:21.000000000 -0500
@@ -1105,7 +1105,11 @@
        proc_net_create("pnp", 0, pnp_get_info);
 #endif /* CONFIG_PROC_FS */
-	if (!ic_enable)
+	if (!ic_enable
+#if defined(IPCONFIG_DYNAMIC) && defined(CONFIG_ROOT_NFS)
+	   )
		return 0;

I did a cut'n'paste so I don't know if it will apply correctly but you get
the idea.

One thing I had problems with was using USB to mount the rootfs (usb hdd
actually) and I suspect the same with a USB nic (loading the kernel from

 Lab tests show that use of micro$oft causes cancer in lab animals

  reply	other threads:[~2002-09-26 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 14:55 2.2.22 on HP Vectra 90/5: Machine check exception on boot Ville Herva
     [not found] ` <>
2002-09-26  9:59   ` Ville Herva
2002-09-26 10:26     ` Serious Problems with diskless clients Marco Schwarz
2002-09-26 11:18       ` Wakko Warner [this message]
2002-09-26 20:58         ` Daniel Egger
2002-09-26 17:53       ` Denis Vlasenko
2002-09-26 13:16         ` Marco Schwarz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).