Re: PXE-install fails on one of two identical setups.
Thomas Alexander Frederiksen wrote:
This problem showed up out of nowhere, and has left me somewhat puzzled.
First up, the setup:
We use PXE and TFTP to boot sarge, and preseeding to automate the
installs. We have a local install mirror set up.
<cut>
Here are a few extra bits of info, or rather, logfile sniplets.
First up, the kernel and initrd.gz are fetched using TFTP.
Secondly, the installer fetches a few files:
82.103.129.98 - - [28/Nov/2005:15:49:40 +0100] "GET /preseed HTTP/1.1"
2004806 "-" "Wget" "-"
82.103.129.98 - - [28/Nov/2005:15:49:41 +0100] "GET
/debian/dists/sarge/Release HTTP/1.1" 200 22834 "-" "Wget" "-"
82.103.129.98 - - [28/Nov/2005:15:49:41 +0100] "GET
/debian/dists/stable/Release HTTP/1.1" 200 22834 "-" "Wget" "-"
82.103.129.98 - - [28/Nov/2005:15:49:41 +0100] "GET
/debian/dists/stable/main/debian-installer/binary-i386/Packages.gz
HTTP/1.1" 200 30276 "-" "Wget" "-"
82.103.129.98 - - [28/Nov/2005:15:49:41 +0100] "GET
/debian/pool/main/b/base-installer/base-installer_1.13.4_i386.udeb
HTTP/1.1" 200 74914 "-" "Wget" "-"
Here, the installer stops, and anna reports this on the debugging terminal:
anna[1365]: DEBUG resolver (usb-storage-modules-2.4.27-2-386-di): mark
anna[1365]: WARNING **: bad md5sum
Pressing retry once has these results:
82.103.129.98 - - [28/Nov/2005:15:59:51 +0100] "GET
/debian/pool/main/b/base-installer/base-installer_1.13.4_i386.udeb
HTTP/1.1" 416 0 "-" "Wget" "-"
82.103.129.98 - - [28/Nov/2005:15:59:52 +0100] "GET
/debian/pool/main/b/base-installer/base-installer_1.13.4_i386.udeb
HTTP/1.1" 200 74914 "-" "Wget" "-"
and anna's comment is...
anna[1365]: wget:
anna[1365]: Server returned error 416: HTTP/1.1 416 Requested Range Not
Satisfiable^M
anna[1365]:
anna[1365]: WARNING **: bad md5sum
Using cancel a few times sends me back to the installer menu, where I
select our local mirror using ftp rather than http. Anna now loads
everything and I can continue with the installation.
Trying to use ftp as the primary transfer method gives the same result,
only with slightly less detailed logging on the mirror server - i.e. I
have to switch method halfway into the pre-install configuration to keep
the installer going.
As mentioned earlier, this only happens on one of two identical setups,
and it is driving me nuts...
Any ideas, anyone?
/Thomas
Reply to: