I ran into this with upstream last week: http://smoogespace.blogspot.com/2015/04/note-to-future-self-random-problems.html

The kernel and initrd.img must be the kernel and initrd.img that is in the version being used in the pivot root (eg if you have 7.0 kernel and 7.1 kernel). This was because the pxe boot was referring to an old kernel that I didn't realize until I checked what exactly the pxe server had.

On 24 April 2015 at 10:52, Michel Jouvin <[log in to unmask]> wrote:

I double-checked the kernel version used and the kernel version of the modules provided by initrd (using lsinitrd, I should have done it before) with SL 7.1: in fact, they are both the same, 3.10.0.229. But when PXE booting vmlinuz+initrd, I end up with kernel modules for 3.10.0.123 (version from 7.0) in /lib/modules... How this is possible? I removed the initrd file checked with lsinitrd to ensure that I was getting an error when booting about the missing file so I am really using this initrd file...

I am lost... Any idea is welcome!

Michel

Le 24/04/2015 17:52, Michel Jouvin a écrit :

Hi,

I don't know if this is related in some ways to the other recent thread about "SL 7.1, PXE install". I'm struggling with SL7.1 (and I have the same pb with CentOS 7.1) when trying to do a PXE install of a machine using the last versions of images/pxeboot/vmlinuz and initrd.img. The install fails when trying to set the default filesystem type to XFS (that I don't use on this machine) because the xfs module is not found. Looking at console (ALT/F2), I saw that the kernel version provided by vmlinuz (uname -r) is not matching the kernel version for which modules are provided in initrd (/lib/modules). If I take vmlinuz and initrd from SL7.0 I don't see the problem (but I am not sure I can install 7.1 booting with vmlinuz/initrd from 7.0).

Is it expected ? Am I doing a trivial mistake ? Or is there an issue ?

Stephen J Smoogen.