[syslinux] Root-NFS not mounting using PXELinux - error 101

Timm Gleason timm at gleason.to
Thu Dec 19 14:40:43 PST 2002


I seem to be having trouble getting the NFS root filesystem to mount after
the kernel boots. As per thread from 2002 16 January
(http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I
double checked my DHCP config files, but to no avail. It cannot seem to
attach to the mountd port on the bootserver. Here is some output from the
kernel:

loop: loaded (max 8 devices)
Intel(R) PRO/1000 Network Driver - version 4.4.12-k1
Copyright (c) 1999-2002 Intel Corporation.
eth0: Intel(R) PRO/1000 Network Connection
eth1: Intel(R) PRO/1000 Network Connection
SCSI subsystem driver Rev

Network driver is loading. Then the thing just won't hook up.

NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
GRE over IPv4 tunneling driver
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 192.168.102.150
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.102.150
RPC: sendmsg returned error 101
portmap: RPC call returned error 101
Root-NFS: Unable to get mountd port number from server, using default
RPC: sendmsg returned error 101
mount: RPC call returned error 101
Root-NFS: Server returned error -101 while mounting /nfsroot
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER

Here is the pxelinux.cfg/default file.

default linux
append root=/nfsroot nfsroot=192.168.102.150:/nfsroot console=ttyS1,9600n8
prompt 1
timeout 100


Here is the dhcpd.conf file.

allow booting;
allow bootp;

subnet 192.168.102.0 netmask 255.255.255.0 {
        option domain-name              "my.domain.net";
        option subnet-mask              255.255.255.0;
        option broadcast-address        192.168.102.255;
        option domain-name-servers      192.168.1.1;
        option routers                  192.168.102.1;
        filename                        "pxelinux.0";
        option time-offset              -8;     # Pacific Standard Time
        option root-path                "/nfsroot";

        range 192.168.102.151 192.168.102.155;

}

Here is the Intel PXE output.

CLIENT MAC ADDR: 00 07 E9 04 45 99  GUID: CBBB9181 E3C8 11D6 BE6B
00108365A7E7
CLIENT IP: 192.168.102.151  MASK: 255.255.255.0  DHCP IP: 192.168.102.150
GATEWAY IP: 192.168.102.1

PXELINUX 1.66 2002-01-01  Copyright (C) 1994-2002 H.
PXELINUX 1.66 2002-01-01  Copyright (C) 1994-2002 H. Peter Anvin
UNDI data segment at:   00090D40
UNDI data segment size: B450
UNDI code segment at:   0009C190
UNDI code segment size: 30E0
PXE entry point found (we hope) at 9C19:0106
My IP address seems to be C0A86697 192.168.102.151
ip=192.168.102.151:192.168.102.150:192.168.102.1:255.255.255.0
TFTP prefix:
Trying to load: pxelinux.cfg/C0A86697
Trying to load: pxelinux.cfg/C0A8669
Trying to load: pxelinux.cfg/C0A866
Trying to load: pxelinux.cfg/C0A86
Trying to load: pxelinux.cfg/C0A8
Trying to load: pxelinux.cfg/C0A
Trying to load: pxelinux.cfg/C0
Trying to load: pxelinux.cfg/C
Trying to load: pxelinux.cfg/default
boot:

Frankly, I am out of ideas as to which thing to change in order to make it
work.  I tried using mknbi-linux on the kernel and all that does is cause
a weird rainbow ascii filled screen when the kernel tries to boot. Should
I be doing anything special to the kernel in enable this feature, besides
the kernel configuration changes?  I did an 'rdev linux /dev/nfs' on the
kernel.

Thanks

Thursday, December 19 2002
--                              | As I said before, I never repeat
Timm Gleason                    | myself.
http://www.gleason.to/          |
http://www.uranushertz.to/      |
Quis custodiet iposos custodes? |


-----PGP PUBLIC KEY BLOCK AVAILABLE-----




More information about the Syslinux mailing list