CentOS 7.5 PXE kernel/initrd mismatch
Posted: 2018/07/18 16:10:11
I've been using the pxeboot kernel & initrd since 7.3. The current versions are failing to start the installation. Here's the output upon death:
anaconda 21.48.22.93-1 for CentOS Linux 7 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
15:50:00 Running pre-installation scripts
15:50:01 Not asking for VNC because of an automated install
15:50:01 Not asking for VNC because text mode was explicitly asked for in kickstart
Traceback (most recent call last):
File "/sbin/anaconda", line 1206, in <module>
setupDisplay(anaconda, opts, addon_paths)
File "/sbin/anaconda", line 715, in setupDisplay
anaconda.initInterface(addons)
File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda.py", line 220, in initInterface
self._intf = TextUserInterface(self.storage, self.payload,
File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda.py", line 168, in storage
self._storage.setDefaultFSType(self.instClass.defaultFS)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1761, in setDefaultFSType
self._check_valid_fstype(newtype)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1736, in _check_valid_fstype
raise ValueError("new value %s is not valid as a default fs type" % fmt)
ValueError: new value non-existent xfs filesystem is not valid as a default fs type
Exception AttributeError: "'NoneType' object has no attribute 'udev_unref'" in <bound method Context.__del__ of <pyudev.core.Context object at 0x7f8656fe0650>> ignored
Pane is dead
In the past when I'd come across this kind of error, it was usually because the kernel and initrd were older (or didn't match) the OS repository being installed (i.e., CentOS 7.3 pxeboot images attempting to install CentOS 7.5). But I'm using the most current pxeboot images.
It seems odd to me that the kernel and initrd.img files have different dates (they're usually the same). The vmlinuz is 20-Apr-2018, but the initrd.img is 03-May-2018.
And probably the most convicting, if you go to shell (after getting the above output), the /lib/modules directory (the intird.img) shows:
3.10.0-514.el7.x86_64
But a "uname -a" (the vmlinuz) reveals: 3.10.0-862.el7.x86_64
Kernel mismatch.
How we go about repairing these images? Or is there something that I might ignorantly be missing, in order to get these to work?
Any help is appreciated. Thanks!
anaconda 21.48.22.93-1 for CentOS Linux 7 started.
* installation log files are stored in /tmp during the installation
* shell is available on TTY2
15:50:00 Running pre-installation scripts
15:50:01 Not asking for VNC because of an automated install
15:50:01 Not asking for VNC because text mode was explicitly asked for in kickstart
Traceback (most recent call last):
File "/sbin/anaconda", line 1206, in <module>
setupDisplay(anaconda, opts, addon_paths)
File "/sbin/anaconda", line 715, in setupDisplay
anaconda.initInterface(addons)
File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda.py", line 220, in initInterface
self._intf = TextUserInterface(self.storage, self.payload,
File "/usr/lib64/python2.7/site-packages/pyanaconda/anaconda.py", line 168, in storage
self._storage.setDefaultFSType(self.instClass.defaultFS)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1761, in setDefaultFSType
self._check_valid_fstype(newtype)
File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1736, in _check_valid_fstype
raise ValueError("new value %s is not valid as a default fs type" % fmt)
ValueError: new value non-existent xfs filesystem is not valid as a default fs type
Exception AttributeError: "'NoneType' object has no attribute 'udev_unref'" in <bound method Context.__del__ of <pyudev.core.Context object at 0x7f8656fe0650>> ignored
Pane is dead
In the past when I'd come across this kind of error, it was usually because the kernel and initrd were older (or didn't match) the OS repository being installed (i.e., CentOS 7.3 pxeboot images attempting to install CentOS 7.5). But I'm using the most current pxeboot images.
It seems odd to me that the kernel and initrd.img files have different dates (they're usually the same). The vmlinuz is 20-Apr-2018, but the initrd.img is 03-May-2018.
And probably the most convicting, if you go to shell (after getting the above output), the /lib/modules directory (the intird.img) shows:
3.10.0-514.el7.x86_64
But a "uname -a" (the vmlinuz) reveals: 3.10.0-862.el7.x86_64
Kernel mismatch.
How we go about repairing these images? Or is there something that I might ignorantly be missing, in order to get these to work?
Any help is appreciated. Thanks!