Hi,
I've got another one... NFS error 101 with NFSROOT has been discussed a
lot, and hpa gave an answer to it which appears right. It's ENETUNREACH,
and I suspect my diskless box does not set its IP parameters right.
PXElinux is set up as follows:
label linvdr
kernel kernel-linvdr
append initrd=initrd-linvdr acpi=off root=/dev/nfs \
nfsroot=192.168.20.1:/opt/tftpboot/linvdr,rsize=8192,wsize=8192 \
nfsaddrs=192.168.20.20:192.168.20.1:192.168.20.99:255.255.255.0:linvdr
(append line broken for readability only)
I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck.
Why in the world would the kernel not configure its IP values? It's a SuSE
8.0 default kernel, and it has everything set:
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_DIRECTIO=y
CONFIG_ROOT_NFS=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_TCP=y
...
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
I could understand it is a config problem if the very same DHCP/TFTP/NFS
server wasn't able to serve as an autoinstall server using the same
settings for PXE boot... But if I set the IP values explicitly this should
work in any case, right? The DHCP server is a 3.0.1rc6 from SuSE 8.0.
*confused*
--
To A Quick Young Fox:
Why jog exquisite bulk, fond crazy vamp,
Daft buxom jonquil, zephyr's gawky vice?
Guy fed by work, quiz Jove's xanthic lamp --
Zow! Qualms by deja vu gyp fox-kin thrice.
-- Lazy Dog
Harald Milz wrote:> Hi, > > I've got another one... NFS error 101 with NFSROOT has been discussed a > lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, > and I suspect my diskless box does not set its IP parameters right. > > PXElinux is set up as follows: > > label linvdr > kernel kernel-linvdr > append initrd=initrd-linvdr acpi=off root=/dev/nfs \ > nfsroot=192.168.20.1:/opt/tftpboot/linvdr,rsize=8192,wsize=8192 \ > nfsaddrs=192.168.20.20:192.168.20.1:192.168.20.99:255.255.255.0:linvdr > > (append line broken for readability only) > > I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck. > > Why in the world would the kernel not configure its IP values? It's a SuSE > 8.0 default kernel, and it has everything set: >Do you have multiple interfaces on this machine? If so, apparently the kernel auto-configuration won't do its thing unless it's told which interface to use (which you don't.) -hpa
* Harald Milz <milz at seneca.muc.de> [2003-12-30 01:31:32 +0100]: <snip>> label linvdr > kernel kernel-linvdr > append initrd=initrd-linvdr acpi=off root=/dev/nfs \ > nfsroot=192.168.20.1:/opt/tftpboot/linvdr,rsize=8192,wsize=8192 \ > nfsaddrs=192.168.20.20:192.168.20.1:192.168.20.99:255.255.255.0:linvdrIsn't nfsaddrs deprecated (use ip= instead) ? <snip>> I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck.perhaps ip=::::::dhcp ? <snip>> Why in the world would the kernel not configure its IP values? It's a SuSE > 8.0 default kernel, and it has everything set: > > CONFIG_NFS_FS=y > CONFIG_NFS_V3=y > CONFIG_NFS_DIRECTIO=y > CONFIG_ROOT_NFS=y > CONFIG_NFSD=m > CONFIG_NFSD_V3=y > CONFIG_NFSD_TCP=y > ... > CONFIG_IP_PNP=y > CONFIG_IP_PNP_DHCP=y > CONFIG_IP_PNP_BOOTP=y > CONFIG_IP_PNP_RARP=yhmm. looks good. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT services phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email: contact at metux.de cellphone: +49 174 7066481 --------------------------------------------------------------------- Diese Mail wurde mit UUCP versandt. http://www.metux.de/uucp/
Hi, Harald Milz <milz at seneca.muc.de> schrieb am 30.12.03 02:11:04:> I've got another one... NFS error 101 with NFSROOT has been discussed a > lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, > and I suspect my diskless box does not set its IP parameters right. > > PXElinux is set up as follows: > > label linvdr > kernel kernel-linvdr > append initrd=initrd-linvdr acpi=off root=/dev/nfs \ > nfsroot=192.168.20.1:/opt/tftpboot/linvdr,rsize=8192,wsize=8192 \ > nfsaddrs=192.168.20.20:192.168.20.1:192.168.20.99:255.255.255.0:linvdr > > (append line broken for readability only) > > I also tried ip= instead of nfsaddrs= as well as ip=dhcp, no luck. > > Why in the world would the kernel not configure its IP values? It's a SuSE > 8.0 default kernel, and it has everything set: > >[..]looks OK.> I could understand it is a config problem if the very same DHCP/TFTP/NFS > server wasn't able to serve as an autoinstall server using the same > settings for PXE boot... But if I set the IP values explicitly this should > work in any case, right? The DHCP server is a 3.0.1rc6 from SuSE 8.0.Just in case: Is the network interface configured into the kernel? If the kernel doesn't have any network driver there's not much point of configuring an IP address on this interface ... So look for some messages about your network card in the kernel output, and also see if there are any messages about IP autoconfig. If this doesn't work: Which kernel version? DHCP config? Kernel messages? Regards, Josef ______________________________________________________________________________ Nachrichten, Musik und Spiele schnell und einfach per Quickstart im WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110
Harald Milz <milz at seneca.muc.de> wrote:> > I've got another one... NFS error 101 with NFSROOT has been discussed a > lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, > and I suspect my diskless box does not set its IP parameters right.Duh. The best one in 10+ years of Linux. A consequence of using factory kernels with "everything" compiled in. Naturally, the network card driver was _not_ compiled in, and putting it into the initrd doesn't make very much sense either. *slap* Sorry for being dumb. Strangely, mounting the root fs v3,tcp does not work, the kernel times out on retrieving the RPC ports. Only v2,udp works. One other filesystems works fine v3,tcp when mounted later, though. -- The gentlemen looked one another over with microscopic carelessness.