| 1 |
Hi, |
| 2 |
|
| 3 |
> rpcbind: server 192.168.2.1 not responding, timed out |
| 4 |
> Root-NFS: Unable to get nfsd port number from server, using default |
| 5 |
> Looking up port of RPC 100005/1 on 192.168.2.1 |
| 6 |
> rpcbind: server 192.168.2.1 not responding, timed out |
| 7 |
> Root-NFS: Unable to get mountd port number from server, using default |
| 8 |
> Root-NFS: Server returned error -5 while mounting /diskless/192.168.2.11 |
| 9 |
> VFS: Unable to mount root fs via NFS, tryi9ng floppy. |
| 10 |
> VFS: Cannot open root device "nfs" or unknown-block(2,0) |
| 11 |
> Kernel Panic - not syncing: VFS unable to mount root fs on unknown- |
| 12 |
> block(2,0) |
| 13 |
> |
| 14 |
> Both client and server have root nfs turned on it their respective |
| 15 |
> kernel. |
| 16 |
Make sure the client also has CONFIG_IP_PNP_DHCP=y and the necessary NIC |
| 17 |
drivers compiled in (not as module). |
| 18 |
|
| 19 |
> pxelinux.cfg is this: |
| 20 |
> |
| 21 |
> DEFAULT /kernel8 |
| 22 |
> APPEND root=/dev/nfs rw nfsroot=192.168.2.1:/diskless/192.168.2.11 |
| 23 |
> init=sbin/init |
| 24 |
Add ip=dhcp to APPEND so that the kernel does DHCP again for an IP. Otherwise |
| 25 |
it might not be connected to the network when it boots and be unable to reach |
| 26 |
the NFS server. |
| 27 |
|
| 28 |
|
| 29 |
Greetings, |
| 30 |
Sascha |
Archives