CentOS7 network installation fails

Support
1

Hi,

I have noticed that there is some problem iwth installing CentOS7 from
network:

  1. CentOS7.1 gives this error:

<https://lh3.googleusercontent.com/-3ZLt0j0XLwA/Vp-fO2MH55I/AAAAAAAAhHk/XkclAkTmbGY/s1600/Capture.GIF>

  1. CentOS7.2 gives error related to "Pane is dead" due to not support XFS.

It's not happening on CentOS6 installations!!
My suspicion is that related to initrd.img and vmlinuz files which come
from the Image OS and stored in "/var/lib/tftpboot/boot" directory.
Is someone familiar with this issue? How can I solve it?

Thank,
EddieM

2

Eddie,

We ran into the same issue today. It appeared that there was a mismatch
between the xfs module and the kernel it was booting.

If you look into your tftpboot/boot directory, you'll find foreman copies
kernel images there. You'll see something like this:

··· ========== -rw-r--r--. 1 foreman-proxy foreman-proxy 5156528 Nov 19 22:20 CentOS-7.2-x86_64-vmlinuz -rw-r--r--. 1 foreman-proxy foreman-proxy 38508192 Dec 9 22:31 CentOS-7.2-x86_64-initrd.img ==========

In our case, it was a mismatch between the kernel and the initrd. Foreman
is supposed to copy these files from your repository when you set up a
build, but it was failing to overwrite one of the files with the media. In
our case, the media is in a local repository, so foreman’s proxy should be
copying the files from here:

<our_path>/CentOS/7.2.1511/os/x86_64/images/pxeboot/{vmlinuz,initrd.img}

Sizes matched, but md5sum for initrd.img didn’t match
CentOS-7.2-x86_64-initrd.img. Delete the file in the tftpboot/boot
directory. Then in foreman web interface cancel and initiate the build
again. This should copy the right files over.

I hope this is helpful for you.

Best,
Jesse Stroik

Space Science and Engineering Center
University of Wisconsin

3

Hi Jesse,

Thanks for the reply, I've figured it out already, I deleted these files in
tftpboot/boot and re-run the installations of CentOS 7 image, this action
recreated the vmlinuz and initrd.img files and fixed the XFS issue.
I still have one issue with the first step I’ve posted (with screenshot),
it happens when I installing the CentOS7 with static IP and not DHCP. Do
you know why can it be?! What causing this issue?

Thanks,
EddieM

··· On Wednesday, January 27, 2016 at 11:22:20 PM UTC+2, Jesse Stroik wrote: > > Eddie, > > We ran into the same issue today. It appeared that there was a mismatch > between the xfs module and the kernel it was booting. > > If you look into your tftpboot/boot directory, you'll find foreman copies > kernel images there. You'll see something like this: > > ========== > -rw-r--r--. 1 foreman-proxy foreman-proxy 5156528 Nov 19 22:20 > CentOS-7.2-x86_64-vmlinuz > -rw-r--r--. 1 foreman-proxy foreman-proxy 38508192 Dec 9 22:31 > CentOS-7.2-x86_64-initrd.img > ========== > > In our case, it was a mismatch between the kernel and the initrd. Foreman > is supposed to copy these files from your repository when you set up a > build, but it was failing to overwrite one of the files with the media. In > our case, the media is in a local repository, so foreman's proxy should be > copying the files from here: > > /CentOS/7.2.1511/os/x86_64/images/pxeboot/{vmlinuz,initrd.img} > > Sizes matched, but md5sum for initrd.img didn't match > CentOS-7.2-x86_64-initrd.img. Delete the file in the tftpboot/boot > directory. Then in foreman web interface cancel and initiate the build > again. This should copy the right files over. > > I hope this is helpful for you. > > Best, > Jesse Stroik > > Space Science and Engineering Center > University of Wisconsin > >