Bug#642571: marked as done (NFS root no longer works with oldstable DHCP server)
Your message dated Sun, 25 Mar 2012 08:16:50 +0000
with message-id <20120325081650.GB770@64-142-29-25.dsl.static.sonic.net>
and subject line Re: NFS root no longer works with oldstable DHCP server
has caused the Debian Bug report #642571,
regarding NFS root no longer works with oldstable DHCP server
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
642571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642571
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-35squeeze2
On an NFS root boot with this version, the boot fails after reporting
"IP-Config: no response after __ seconds - giving up" once "__" reaches
100. It then outputs "/inet:...can't open '/tmp/net-*.conf'" and
"Kernel panic" etc. (Sorry, these message are from memory, since I'm
sending this from the machine that fails, and no logs get written.)
The old release still boots fine (though I'm using the newer modules for
now):
----------
$ uname -rvm
2.6.32-5-amd64 #1 SMP Wed May 18 23:13:22 UTC 2011 x86_64
----------
The DHCP server is dhcp3-server 3.1.1-6+lenny6. When the newer kernel
boots, it logs the DHCPDISCOVER/OFFER, but no DHCPREQUEST/ACK. There is
iptables firewalling on the DHCP server, but no blocked packets are
reported. Otherwise the server and client are directly connected.
Client boot options are:
----------
append root=/dev/nfs nfsroot=__.__.__.__:/___ ip=dhcp rw
----------
--- End Message ---
--- Begin Message ---
This is not a bug. It resulted from the initramfs-tools upgrade in
squeeze, which replaced the default "DEVICE=eth0" line with "DEVICE=".
I accepted the change, although I was depending on the old value. (I'm
not yet using the ip= kernel parameter.)
--- End Message ---
Reply to: