mounting NFSROOT via wrong iface (again :( ) - very long email
Carsten Aulbert
Carsten.Aulbert at aei.mpg.de
Mon Dec 19 13:46:53 CET 2011
Hi
On Monday 19 December 2011 09:46:22 Carsten Aulbert wrote:
> It does take the bootif variable from PXE, but somehow thinks the secondary
> DHCP reply more important. If I disable the second DHCP it works nicely.
> Any idea why this is?
I'm still wading through all this, and I think there is a bug in do_netsetup()
(file 'live' from live-initramfs-tools 2.0.15-1)
Unless I'm wrong, this is what happens:
/scripts/live-premount/select_eth_device checks for nics with a link
in my case it results in
cat /conf/param.conf
DEVICE=eth1
DEVICE=eth2
then in or after live-premount/modules this file gets sourced
+ /scripts/live-premount/modules
+ [ -e /conf/param.conf ]
+ . /conf/param.conf
+ DEVICE=eth1
+ DEVICE=eth2
and DEVICE ends up being only eth2 (wrong in my case)
do_netsetup then sees I want to use NFS:
+ [ -z nfs ]
and starts ipconfig eth2 only and from there on it's all wrong...
+ ipconfig eth2
tee /netboot.config
IP-Config: eth2 hardware address 00:30:48:da:88:cd mtu 1500 DHCP RARP
[ 16.388891] RPC: Registered udp transport module.
[ 16.393590] RPC: Registered tcp transport module.
[ 16.398288] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 16.410214] Slow work thread pool: Starting up
[ 16.414705] Slow work thread pool: Ready
[ 16.418668] FS-Cache: Loaded
[ 16.431832] FS-Cache: Netfs 'nfs' registered for caching
IP-Config: eth2 guessed broadcast address 172.31.255.255
IP-Config: eth2 guessed nameserver address 172.28.22.4
IP-Config: eth2 complete (from 172.28.22.4):
address: 172.25.12.7 broadcast: 172.31.255.255 netmask: 255.240.0.0
gateway: 0.0.0.0 dns0 : 172.28.22.4 dns1 : 0.0.0.0
rootserver: 172.28.22.4 rootpath:
filename :
+ OLDHOSTNAME=titan3
+ . /tmp/net-eth2.conf
+ DEVICE=eth2
+ IPV4ADDR=172.25.12.7
+ IPV4BROADCAST=172.31.255.255
+ IPV4NETMASK=255.240.0.0
+ IPV4GATEWAY=0.0.0.0
+ IPV4DNS0=172.28.22.4
+ IPV4DNS1=0.0.0.0
+ HOSTNAME=
+ DNSDOMAIN=
+ NISDOMAIN=
+ ROOTSERVER=172.28.22.4
+ ROOTPATH=
+ filename=
+ [ -z ]
[...]
Why is the previous knowledge of "bootif" thrown away and it just stoically
walks on?
Cheers
Carsten
More information about the linux-fai
mailing list