I will research this.
--
Connie J. Sieh
Computing Services Specialist III
Fermi National Accelerator Laboratory
630 840 8531 office
http://www.fnal.gov
[email protected]
On Fri, 24 Apr 2015, Michel Jouvin wrote:
I double-checked the kernel version used and the kernel version of the=20
modules provided by initrd (using lsinitrd, I should have done it=20
before) with SL 7.1: in fact, they are both the same, 3.10.0.229. But=20
when PXE booting vmlinuz+initrd, I end up with kernel modules for=20
3.10.0.123 (version from 7.0) in /lib/modules... How this is possible? I=20
removed the initrd file checked with lsinitrd to ensure that I was=20
getting an error when booting about the missing file so I am really=20
using this initrd file...
I am lost... Any idea is welcome!
Michel
Le 24/04/2015 17:52, Michel Jouvin a =C3=A9crit :
Hi,
I don't know if this is related in some ways to the other recent=20
thread about "SL 7.1, PXE install". I'm struggling with SL7.1 (and I=20
have the same pb with CentOS 7.1) when trying to do a PXE install of a=20
machine using the last versions of images/pxeboot/vmlinuz and=20
initrd.img. The install fails when trying to set the default=20
filesystem type to XFS (that I don't use on this machine) because the=20
xfs module is not found. Looking at console (ALT/F2), I saw that the=20
kernel version provided by vmlinuz (uname -r) is not matching the=20
kernel version for which modules are provided in initrd=20
(/lib/modules). If I take vmlinuz and initrd from SL7.0 I don't see=20
the problem (but I am not sure I can install 7.1 booting with=20
vmlinuz/initrd from 7.0).
Is it expected ? Am I doing a trivial mistake ? Or is there an issue ?
