SL 7.1 PXE install: xfs not found

[Michel Jouvin]

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 ?

Re: SL 7.1 PXE install: xfs not found

[Michel Jouvin]

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 ?

Re: SL 7.1 PXE install: xfs not found

[Connie Sieh]

I will research this.

--

Connie J. Sieh
Computing Services Specialist III

Fermi National Accelerator Laboratory
630 840 8531 office

http://www.fnal.gov
cs...@fnal.gov

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 ?

Re: SL 7.1 PXE install: xfs not found

[Michel Jouvin]

Thanks Connie!

I am pretty sure there is something wrong on my side but I cannot find 
what. This morning I downloaded again 7.1 distrib (rsync) and I have 
still the same problem. But a collegue of mine did the same and it works 
for him. He sent me his kickstart file and using exactly the same one 
(except the url to the distrib) I still have the problem...


Installing from 7.0 (with errata) works...

I cannot imagine that this problem is impacted by the firmware... I 
never saw such a weird problem! I dont understand where the 
/lib/modules/3.10.0.123 can come from when booting 7.1 vmlinuz+initrd.


Cheers,

Michel

Le 28/04/2015 18:38, Connie Sieh a écrit :

I will research this.

--

Connie J. Sieh
Computing Services Specialist III

Fermi National Accelerator Laboratory
630 840 8531 office

http://www.fnal.gov
cs...@fnal.gov

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 ?

Re: SL 7.1 PXE install: xfs not found

[Stephan Wiesand]

Salut Michel,

as a data point: SL7.1 PXE/kickstart installs work for me, including XFS. We're 
mirroring the distro with rsync too (the tree, not the ISOs) and use the 
kernel/initrd from os/images/pxelinux.

Cheers,
Stephan

On Apr 28, 2015, at 18:43 , Michel Jouvin wrote:

> Thanks Connie!
> 
> I am pretty sure there is something wrong on my side but I cannot find what. 
> This morning I downloaded again 7.1 distrib (rsync) and I have still the same 
> problem. But a collegue of mine did the same and it works for him. He sent me 
> his kickstart file and using exactly the same one (except the url to the 
> distrib) I still have the problem...
> 
> Installing from 7.0 (with errata) works...
> 
> I cannot imagine that this problem is impacted by the firmware... I never saw 
> such a weird problem! I dont understand where the /lib/modules/3.10.0.123 can 
> come from when booting 7.1 vmlinuz+initrd.
> 
> Cheers,
> 
> Michel
> 
> Le 28/04/2015 18:38, Connie Sieh a écrit :
>> I will research this.
>> 
>> -- 
>> 
>> Connie J. Sieh
>> Computing Services Specialist III
>> 
>> Fermi National Accelerator Laboratory
>> 630 840 8531 office
>> 
>> http://www.fnal.gov
>> cs...@fnal.gov
>> 
>> 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 ?
>>> 

-- 
Stephan Wiesand
DESY -DV-
Platanenenallee 6
15738 Zeuthen, Germany

Re: SL 7.1 PXE install: xfs not found

[Stephen John Smoogen]

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  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.

Re: SL 7.1 PXE install: xfs not found

[Michel Jouvin]

Hi,

Yes, I'm aware of this and this is what I checked first. In fact, I 
removed the initrd from the directory where vmlinuz was located and it 
produced an error during PXE boot. Thus I am confident that I am using 
the intended vmlinuz and initrd. What really worries me is that the end 
result, just after the %pre script (the pb is the same is the script is 
empty), is that /lib/modules contains modules for an older kernel 
version... The only possibility for me would be to have the old initrd 
version (7.0) but I don't even have it on my system!


Cheers,

Michel

Le 28/04/2015 19:20, Stephen John Smoogen a écrit :


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 > 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.

Re: SL 7.1 PXE install: xfs not found

[Orion Poplawski]

On 04/28/2015 11:25 AM, Michel Jouvin wrote:
> Hi,
> 
> Yes, I'm aware of this and this is what I checked first. In fact, I removed
> the initrd from the directory where vmlinuz was located and it produced an
> error during PXE boot. Thus I am confident that I am using the intended
> vmlinuz and initrd. What really worries me is that the end result, just after
> the %pre script (the pb is the same is the script is empty), is that
> /lib/modules contains modules for an older kernel version... The only
> possibility for me would be to have the old initrd version (7.0) but I don't
> even have it on my system!


Double and triple check against upstream images.  I had an issue where cobbler
was somehow using the wrong source for the initrd image it was serving..


-- 
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   or...@nwra.com
Boulder, CO 80301   http://www.nwra.com