Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Feb 2012 15:02:01 -0500
From:      Rick Miller <>
To:        =?ISO-8859-1?Q?Erik_N=F8rgaard?= <>
Subject:   Re: and vlan tagging
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
We have determined that it has failed after loading and
before loading the kernel.  Therefore, the kernel is not the problem.
I have also determined that vlan tagging is not the problem as it has
failed with vlan tagging disabled.  I don't believe it is the content
because it works in 3 out of 4 different environments.  In fact, in
the 4th environment in recent tests, it worked a handful of times
before failing again.

Suspecting network configurations at this point, but thanks for the
input provided thus far.  It has been immensely helpful.

On Mon, Feb 6, 2012 at 11:45 AM, Erik N=F8rgaard <> wr=
> On 06/02/2012 17:33, Rick Miller wrote:
>>>> 2) do you fetch the kernel successfully?
>>>> When using tftp, The kernel and kernel modules are fetched before the
>>>> memory
>>>> file system, so do pxeboot fetch the kernel but not the mfsroot?
>>>> The reason for these questions is that your problem may be with the
>>>> kernel
>>>> and kernel modules and not pxeboot. Just to be sure.
>>> I see what you are saying. =A0We will have to look at the packet
>>> captures to make that determination.
>> The target system loads and consequently requests the
>> following files:
>> /boot/boot.4th (which it does not find)
>> /boot/loader.rc
>> /boot/loader.4th
>> /boot/support.4th
>> /boot/defaults/loader.conf
>> /boot/device.hints
>> /boot/loader.conf
>> It is at this point where the failure occurs. =A0The contents of loader.=
>> are:
>> mfsroot_load=3D"YES"
>> mfsroot_type=3D"mfs_root"
>> mfsroot_name=3D"/boot/mfsroot"
>> Does this seem consistent with what you were theorizing that it's the
>> kernel that has the problem with vlan tagging and not
> See the other mail, the way pxeboot works IIRC, is that first the pxeboot=
> fetched using tftp, the pxeboot is given the next server and will fetch t=
> kernel, modules and other files from /boot/ on that server, (path respect=
> to the root of the tftp dir).
> The kernel loads and will then fetch the mfsroot file. As mentioned, by
> default this is done using nfs, and nfs is assumed if the kernel supports
> nfs, even if it only fetches one file. This I understand has to be this w=
> since the network configuration set with dhcp does not specify the protoc=
> So, if your kernel supports nfs it will not use tftp and hence fail.
> The details are somewhat distant to me, it's been some time since I messs=
> arround with this.
> hope this helps.
> BR, Erik
> --
> M: +34 666 334 818
> T: +34 915 211 157

Take care
Rick Miller

Want to link to this message? Use this URL: <>