From: Sascha Hlusiak <saschahlusiak@arcor.de>
To: gentoo-user@lists.gentoo.org
Cc: Cocoy Dayao <cocoy.dayao@gmail.com>
Subject: Re: [gentoo-user] root-nfs question
Date: Mon, 4 May 2009 10:34:46 +0200 [thread overview]
Message-ID: <200905041034.53075.saschahlusiak@arcor.de> (raw)
In-Reply-To: <6AE9F121-C5C7-4874-B5E6-B1BD50062C43@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi,
> rpcbind: server 192.168.2.1 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on 192.168.2.1
> rpcbind: server 192.168.2.1 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> Root-NFS: Server returned error -5 while mounting /diskless/192.168.2.11
> VFS: Unable to mount root fs via NFS, tryi9ng floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Kernel Panic - not syncing: VFS unable to mount root fs on unknown-
> block(2,0)
>
> Both client and server have root nfs turned on it their respective
> kernel.
Make sure the client also has CONFIG_IP_PNP_DHCP=y and the necessary NIC
drivers compiled in (not as module).
> pxelinux.cfg is this:
>
> DEFAULT /kernel8
> APPEND root=/dev/nfs rw nfsroot=192.168.2.1:/diskless/192.168.2.11
> init=sbin/init
Add ip=dhcp to APPEND so that the kernel does DHCP again for an IP. Otherwise
it might not be connected to the network when it boots and be unable to reach
the NFS server.
Greetings,
Sascha
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-05-04 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 7:57 [gentoo-user] root-nfs question Cocoy Dayao
2009-05-04 8:34 ` Sascha Hlusiak [this message]
2009-05-04 10:01 ` Cocoy Dayao
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200905041034.53075.saschahlusiak@arcor.de \
--to=saschahlusiak@arcor.de \
--cc=cocoy.dayao@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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