RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1544511 - Kernel upgrade error with missing dracut module
Summary: Kernel upgrade error with missing dracut module
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-12 17:22 UTC by Gregory Young
Modified: 2018-02-15 09:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-15 09:23:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
journalctl -t dracut (246.91 KB, text/plain)
2018-02-14 19:31 UTC, Gregory Young
no flags Details


Links
System ID Private Priority Status Summary Last Updated
CentOS 14409 0 None None None 2018-02-12 17:22:38 UTC

Description Gregory Young 2018-02-12 17:22:38 UTC
Description of problem:

On UEFI systems, dracut cannot update the initramfs due to the missing vfat dracut module.

The error is somewhat misleading. Adding the vfat module to the dracut modules option does not fix the issue, adding "uefi-libs" to the dracut modules list does.

On UEFI systems, dracut should be configured to load this module as it is required. From the CentOS perspective, the /etc/dracut.conf should be modified during install on UEFI systems to include the "uefi-libs" module:

Patch:

19c19
< #add_dracutmodules+=""
---
> add_dracutmodules+="uefi-lib"

Version-Release number of selected component (if applicable):

[root@localhost system]# rpm -qa dracut
dracut-033-502.el7_4.1.x86_64

On downstream CentOS 7.4:

[root@localhost system]# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

How reproducible:

Every kernel update on a Hyper-V based Gen 2 VM with UEFI enabled.

Steps to Reproduce:

1. Install CentOS 7.4.1708 from the minimal ISO on Hyper-V as a Generation 2 VM with UEFI enabled.
2. Upgrade the kernel to latest:

yum -y update kernel

3. Note the error:

dracut module 'vfat' cannot be found or installed.
mkinitrd failed
warning: %posttrans(kernel-3.10.0-693.11.6.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package kernel-3.10.0-693.11.6.el7.x86_64

4. Reboot.
5. Select the new kernel. Note the kernel panic.
6. Reboot.
7. Select the old kernel.
8. Check /boot, not the initramfs is missing for the new kernel.
9. edit /etc/dracut.conf

19c19
< #add_dracutmodules+=""
---
> add_dracutmodules+="uefi-lib"

10. mkinitrd or yum -y reinstall kernel
11. Note no error.
12. Check /boot and see the initramfs is now present.
13. Reboot.
14. Select the new kernel (yes, odds are you will experience the grub2 default boot item issue, which I believe is fixed in the next grub2 build for CentOS 7).
15. System boots as expected.

Actual results:

[root@localhost tmp]# yum update kernel
Loaded plugins: fastestmirror, langpacks
base | 3.6 kB 00:00:00
extras | 3.4 kB 00:00:00
updates | 3.4 kB 00:00:00
(1/2): extras/7/x86_64/primary_db | 145 kB 00:00:00
(2/2): updates/7/x86_64/primary_db | 5.3 MB 00:00:02
Determining fastest mirrors
 * base: mirror.scalabledns.com
 * extras: mirrors.umflint.edu
 * updates: centos.mirrors.tds.net
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================
 Package Arch Version Repository Size
====================================================================================================
Installing:
 kernel x86_64 3.10.0-693.11.6.el7 updates 43 M

Transaction Summary
====================================================================================================
Install 1 Package

Total download size: 43 M
Installed size: 59 M
Is this ok [y/d/N]: y
Downloading packages:
updates/7/x86_64/prestodelta | 680 kB 00:00:03
kernel-3.10.0-693.11.6.el7.x86_64.rpm | 43 MB 00:01:01
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : kernel-3.10.0-693.11.6.el7.x86_64 1/1
dracut module 'vfat' cannot be found or installed.
mkinitrd failed
warning: %posttrans(kernel-3.10.0-693.11.6.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package kernel-3.10.0-693.11.6.el7.x86_64
  Verifying : kernel-3.10.0-693.11.6.el7.x86_64 1/1

Installed:
  kernel.x86_64 0:3.10.0-693.11.6.el7

Complete!
[root@localhost tmp]# uname -a
Linux localhost.localdomain 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Expected results:

No errors installing new kernel.

Additional info:

For reference, testing Hyper-V Host is an Intel based Windows 10 Enterprise x64 Version 1709, build 16299.214.

Hardware is a Dell Optiplex 7050 with UEFI enabled and Windows installed after converting to UEFI. Intel Core i7-6700, 32GB RAM.

VM is Generation 2, Secure Boot disabled (as I thought it was causing the issue originally). 2 Cores, 4GB Ram. SCSI attached virtual disk. Default options for Checkpoints, Paging and start/stop actions. Integration Services are all but Data Exchange and Backup. Firmware is set to boot from File (shimx64.efi) after initial install.

Comment 2 Lukáš Nykrýn 2018-02-13 10:02:28 UTC
Hmm this is weird, what actually requests the vfat module on your system? Can you please check your dracut configuration and the installed modules?

Comment 3 Harald Hoyer 2018-02-13 10:06:03 UTC
This must have spaces:
add_dracutmodules+=" uefi-lib "

uefi-lib though is only needed by "fcoe-uefi". So, unless you have a root on FCoE and need the UEFI configuration, "uefi-lib" is _not_ needed.


Regarding:
> dracut module 'vfat' cannot be found or installed.
There is no vfat dracut module! Only a kernel module. This looks like a configuration error.

What is the output of:

# egrep . -r /lib/dracut/dracut.conf.d/ /etc/dracut.conf.d

Comment 4 Gregory Young 2018-02-13 16:00:02 UTC
I agree, there is no vfat module, only the fat module, but adding that to the add_dracutmodules line has no effect.

I suspect, based on the error, that is has to do with the UEFI partition needing to be FAT32 for Hyper-V.

Here is the output:

[root@localhost 100.0.0.199 ~]# egrep . -r /lib/dracut/dracut.conf.d/ /etc/dracut.conf.d
/lib/dracut/dracut.conf.d/50-nss-softokn.conf:# turn on nss-softokn module
/lib/dracut/dracut.conf.d/50-nss-softokn.conf:add_dracutmodules+=" nss-softokn "
/lib/dracut/dracut.conf.d/01-dist.conf:# dracut config file customized for RedHat/Fedora.
/lib/dracut/dracut.conf.d/01-dist.conf:# i18n
/lib/dracut/dracut.conf.d/01-dist.conf:i18n_vars="/etc/sysconfig/keyboard:KEYTABLE-KEYMAP /etc/sysconfig/i18n:SYSFONT-FONT,FONTACM-FONT_MAP,FONT_UNIMAP"
/lib/dracut/dracut.conf.d/01-dist.conf:i18n_default_font="latarcyrheb-sun16"
/lib/dracut/dracut.conf.d/01-dist.conf:i18n_install_all="yes"
/lib/dracut/dracut.conf.d/01-dist.conf:stdloglvl=3
/lib/dracut/dracut.conf.d/01-dist.conf:sysloglvl=5
/lib/dracut/dracut.conf.d/01-dist.conf:install_optional_items+=" vi /etc/virc ps grep cat rm "
/lib/dracut/dracut.conf.d/01-dist.conf:prefix="/"
/lib/dracut/dracut.conf.d/01-dist.conf:systemdutildir=/usr/lib/systemd
/lib/dracut/dracut.conf.d/01-dist.conf:systemdsystemunitdir=/usr/lib/systemd/system
/lib/dracut/dracut.conf.d/01-dist.conf:systemdsystemconfdir=/etc/systemd/system
/lib/dracut/dracut.conf.d/01-dist.conf:udevdir=/usr/lib/udev
/lib/dracut/dracut.conf.d/01-dist.conf:hostonly="yes"
/lib/dracut/dracut.conf.d/01-dist.conf:hostonly_cmdline="no"
/lib/dracut/dracut.conf.d/01-dist.conf:early_microcode="yes"
/lib/dracut/dracut.conf.d/76-phys-port-name.conf:install_items+=" /usr/lib/udev/phys-port-name-gen "
/lib/dracut/dracut.conf.d/76-phys-port-name.conf:install_items+=" /usr/lib/udev/rules.d/76-phys-port-name.rules "
/lib/dracut/dracut.conf.d/01-microcode.conf:early_microcode="yes"
/lib/dracut/dracut.conf.d/02-rescue.conf:dracut_rescue_image="yes"

Comment 5 Harald Hoyer 2018-02-14 09:55:22 UTC
> I agree, there is no vfat module, only the fat module, but adding that to the
> add_dracutmodules line has no effect.

Oh, there _is_ a vfat kernel module.

$ modinfo vfat
filename:       /lib/modules/3.10.0-850.el7.x86_64/kernel/fs/fat/vfat.ko.xz
author:         Gordon Chaffee
description:    VFAT filesystem support
license:        GPL
alias:          fs-vfat

_But_ vfat is a _kernel_ module.. not a _dracut_ module. So it would be
add_drivers+=" <kernel_module> "
and _not_:
add_dracutmodules+=" <kernel_module> "

So, if you had in the past:
add_dracutmodules+=" vfat "
that would explain the error message:
dracut module 'vfat' cannot be found or installed.

Because it should have been
add_drivers+=" vfat "


What is your /etc/dracut.conf then?

Comment 6 Gregory Young 2018-02-14 13:48:00 UTC
The stock version of the dracut config on the Hyper-V Gen2 UEFI box is below:

[root@localhost ~]# cat /etc/dracut.conf
# PUT YOUR CONFIG HERE OR IN separate files named *.conf
# in /etc/dracut.conf.d
# SEE man dracut.conf(5)

# Sample dracut config file

#logfile=/var/log/dracut.log
#fileloglvl=6

# Exact list of dracut modules to use.  Modules not listed here are not going
# to be included.  If you only want to add some optional modules use
# add_dracutmodules option instead.
#dracutmodules+=""

# dracut modules to omit
#omit_dracutmodules+=""

# dracut modules to add to the default
#add_dracutmodules+=""

# additional kernel modules to the default
#add_drivers+=""

# list of kernel filesystem modules to be included in the generic initramfs
#filesystems+=""

# build initrd only to boot current hardware
#hostonly="yes"
#

# install local /etc/mdadm.conf
#mdadmconf="no"

# install local /etc/lvm/lvm.conf
#lvmconf="no"

# A list of fsck tools to install. If it's not specified, module's hardcoded
# default is used, currently: "umount mount /sbin/fsck* xfs_db xfs_check
# xfs_repair e2fsck jfs_fsck reiserfsck btrfsck". The installation is
# opportunistic, so non-existing tools are just ignored.
#fscks=""

# inhibit installation of any fsck tools
#nofscks="yes"

# mount / and /usr read-only by default
#ro_mnt="no"

# set the directory for temporary files
# default: /var/tmp
#tmpdir=/tmp


***********************************************************************

As you can see, neither the uefi-libs module, nor the vfat driver is added by the default configuration. As a result, unless modified manually in advance, the kernel upgrade will result in a dracut failure, and subsequently a failure to boot, unless the older kernel is selected.

Comment 7 Harald Hoyer 2018-02-14 15:50:50 UTC
What is in your /etc/kdump.conf ?

Comment 8 Harald Hoyer 2018-02-14 15:52:23 UTC
And the output of:

# journalctl -t dracut
# grep dracut /var/log/messages

Comment 9 Gregory Young 2018-02-14 16:04:13 UTC
[root@localhost ~]# cat /etc/kdump.conf
# This file contains a series of commands to perform (in order) in the kdump
# kernel after a kernel crash in the crash kernel(1st kernel) has happened.
#
# Directives in this file are only applicable to the kdump initramfs, and have
# no effect once the root filesystem is mounted and the normal init scripts are
# processed.
#
# Currently, only one dump target and path can be specified.  If the dumping to
# the configured target fails, the default action which can be configured via
# the "default" directive will be performed.
#
# Supported options:
#
# raw <partition>
#           - Will dd /proc/vmcore into <partition>.
#             Use persistent device names for partition devices,
#             such as /dev/vg/<devname>.
#
# nfs <nfs mount>
#           - Will mount nfs to <mnt>, and copy /proc/vmcore to
#             <mnt>/<path>/%HOST-%DATE/, supports DNS.
#
# ssh <user@server>
#           - Will scp /proc/vmcore to <user@server>:<path>/%HOST-%DATE/,
#             supports DNS.
#             NOTE: make sure the user has write permissions on the server.
#
# sshkey <path>
#           - Will use the sshkey to do ssh dump.
#             Specify the path of the ssh key to use when dumping
#             via ssh. The default value is /root/.ssh/kdump_id_rsa.
#
# <fs type> <partition>
#           - Will mount -t <fs type> <partition> <mnt>, and copy
#             /proc/vmcore to <mnt>/<path>/%DATE/.
#             NOTE: <partition> can be a device node, label or uuid.
#             It's recommended to use persistent device names
#             such as /dev/vg/<devname>.
#             Otherwise it's suggested to use label or uuid.
#
# path <path>
#           - "path" represents the file system path in which vmcore
#             will be saved.  If a dump target is specified in
#             kdump.conf, then "path" is relative to the specified
#             dump target.
#
#             Interpretation of "path" changes a bit if the user didn't
#             specify any dump target explicitly in kdump.conf.  In this
#             case, "path" represents the absolute path from root. The
#             dump target and adjusted path are arrived at automatically
#             depending on what's mounted in the current system.
#
#             Ignored for raw device dumps.  If unset, will use the default
#             "/var/crash".
#
# core_collector <command> <options>
#           - This allows you to specify the command to copy
#             the vmcore.  The default is makedumpfile, which on
#             some architectures can drastically reduce vmcore size.
#             See /sbin/makedumpfile --help for a list of options.
#             Note that the -i and -g options are not needed here,
#             as the initrd will automatically be populated with a
#             config file appropriate for the running kernel.
#             The default core_collector for raw/ssh dump is:
#             "makedumpfile -F -l --message-level 1 -d 31".
#             The default core_collector for other targets is:
#             "makedumpfile -l --message-level 1 -d 31".
#
#             "makedumpfile -F" will create a flattened vmcore.
#             You need to use "makedumpfile -R" to rearrange the dump data to
#             a normal dumpfile readable with analysis tools.  For example:
#             "makedumpfile -R vmcore < vmcore.flat".
#
#             For core_collector format details, you can refer to
#             kexec-kdump-howto.txt or kdump.conf manpage.
#
# kdump_post <binary | script>
#           - This directive allows you to run a executable binary
#             or script after the vmcore dump process terminates.
#             The exit status of the current dump process is fed to
#             the executable binary or script as its first argument.
#
# kdump_pre <binary | script>
#           - Works like the "kdump_post" directive, but instead of running
#             after the dump process, runs immediately before it.
#             Exit status of this binary is interpreted as follows:
#             0 - continue with dump process as usual
#             non 0 - reboot the system
#
# extra_bins <binaries | shell scripts>
#           - This directive allows you to specify additional binaries or
#             shell scripts to be included in the kdump initrd.
#             Generally they are useful in conjunction with a kdump_post
#             or kdump_pre binary or script which depends on these extra_bins.
#
# extra_modules <module(s)>
#           - This directive allows you to specify extra kernel modules
#             that you want to be loaded in the kdump initrd.
#             Multiple modules can be listed, separated by spaces, and any
#             dependent modules will automatically be included.
#
# default <reboot | halt | poweroff | shell | dump_to_rootfs>
#           - Action to perform in case dumping fails.
#             reboot:   Reboot the system.
#             halt:     Halt the system.
#             poweroff: Power down the system.
#             shell:    Drop to a bash shell.
#                       Exiting the shell reboots the system.
#             dump_to_rootfs:  Dump vmcore to rootfs from initramfs context and
#                       reboot. Useful when non-root dump target is specified.
#             The default option is "reboot".
#
# force_rebuild <0 | 1>
#           - By default, kdump initrd will only be rebuilt when necessary.
#             Specify 1 to force rebuilding kdump initrd every time when kdump
#             service starts.
#
# force_no_rebuild <0 | 1>
#           - By default, kdump initrd will be rebuilt when necessary.
#             Specify 1 to bypass rebuilding of kdump initrd.
#
#             force_no_rebuild and force_rebuild options are mutually
#             exclusive and they should not be set to 1 simultaneously.
#
# override_resettable <0 | 1>
#           - Usually an unresettable block device can't be a dump target.
#             Specifying 1 when you want to dump even though the block
#             target is unresettable
#             By default, it is 0, which will not try dumping destined to fail.
#
# dracut_args <arg(s)>
#           - Pass extra dracut options when rebuilding kdump initrd.
#
# fence_kdump_args <arg(s)>
#           - Command line arguments for fence_kdump_send (it can contain
#             all valid arguments except hosts to send notification to).
#
# fence_kdump_nodes <node(s)>
#           - List of cluster node(s) except localhost, separated by spaces,
#             to send fence_kdump notifications to.
#             (this option is mandatory to enable fence_kdump).
#

#raw /dev/vg/lv_kdump
#ext4 /dev/vg/lv_kdump
#ext4 LABEL=/boot
#ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
#nfs my.server.com:/export/tmp
#ssh user.com
#sshkey /root/.ssh/kdump_id_rsa
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31
#core_collector scp
#kdump_post /var/crash/scripts/kdump-post.sh
#kdump_pre /var/crash/scripts/kdump-pre.sh
#extra_bins /usr/bin/lftp
#extra_modules gfs2
#default shell
#force_rebuild 1
#force_no_rebuild 1
#dracut_args --omit-drivers "cfg80211 snd" --add-drivers "ext2 ext3"
#fence_kdump_args -p 7410 -f auto -c 0 -i 10
#fence_kdump_nodes node1 node2

Comment 10 Gregory Young 2018-02-14 16:13:34 UTC
Give me a few, I need to go back to an un-patched system and do the kernel upgrade again to grab the other logs you asked for.

Comment 11 Gregory Young 2018-02-14 19:31:10 UTC
[root@localhost ~]# grep dracut /var/log/messages
Feb 14 13:40:06 localhost systemd[1]: Starting dracut cmdline hook...
Feb 14 13:40:06 localhost systemd: Started dracut cmdline hook.
Feb 14 13:40:06 localhost systemd: Starting dracut pre-udev hook...
Feb 14 13:40:06 localhost systemd: Started dracut pre-udev hook.
Feb 14 13:40:06 localhost systemd: Starting dracut initqueue hook...
Feb 14 13:40:07 localhost systemd: Started dracut initqueue hook.
Feb 14 13:40:07 localhost systemd: Starting dracut pre-pivot and cleanup hook...
Feb 14 13:40:07 localhost systemd: Started dracut pre-pivot and cleanup hook.
Feb 14 13:40:07 localhost systemd: Stopped dracut pre-pivot and cleanup hook.
Feb 14 13:40:07 localhost systemd: Stopping dracut pre-pivot and cleanup hook...
Feb 14 13:40:07 localhost systemd: Stopped dracut initqueue hook.
Feb 14 13:40:07 localhost systemd: Stopping dracut initqueue hook...
Feb 14 13:40:07 localhost systemd: Stopped dracut pre-udev hook.
Feb 14 13:40:07 localhost systemd: Stopping dracut pre-udev hook...
Feb 14 13:40:07 localhost systemd: Stopped dracut cmdline hook.
Feb 14 13:40:07 localhost systemd: Stopping dracut cmdline hook...
Feb 14 13:40:20 localhost dracut: dracut-
Feb 14 13:40:20 localhost dracut: Executing: /usr/sbin/dracut --hostonly --hostonly-cmdline --hostonly-i18n -o "plymouth dash resume ifcfg" -f /boot/initramfs-3.10.0-693.el7.x86_64kdump.img 3.10.0-693.el7.x86_64
Feb 14 13:40:21 localhost dracut: dracut module 'modsign' will not be installed, because command 'keyctl' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'ifcfg' will not be installed, because it's in the list to be omitted!
Feb 14 13:40:21 localhost dracut: dracut module 'plymouth' will not be installed, because it's in the list to be omitted!
Feb 14 13:40:21 localhost dracut: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
Feb 14 13:40:21 localhost dracut: 95nfs: Could not find any command of 'rpcbind portmap'!
Feb 14 13:40:21 localhost dracut: dracut module 'resume' will not be installed, because it's in the list to be omitted!
Feb 14 13:40:21 localhost dracut: dracut module 'modsign' will not be installed, because command 'keyctl' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!
Feb 14 13:40:21 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
Feb 14 13:40:22 localhost dracut: 95nfs: Could not find any command of 'rpcbind portmap'!
Feb 14 13:40:22 localhost dracut: *** Including module: bash ***
Feb 14 13:40:22 localhost dracut: *** Including module: nss-softokn ***
Feb 14 13:40:22 localhost dracut: *** Including module: i18n ***
Feb 14 13:40:22 localhost dracut: *** Including module: network ***
Feb 14 13:40:22 localhost dracut: *** Including module: dm ***
Feb 14 13:40:22 localhost dracut: Skipping udev rule: 64-device-mapper.rules
Feb 14 13:40:22 localhost dracut: Skipping udev rule: 60-persistent-storage-dm.rules
Feb 14 13:40:22 localhost dracut: Skipping udev rule: 55-dm.rules
Feb 14 13:40:22 localhost dracut: *** Including module: kernel-modules ***
Feb 14 13:40:27 localhost dracut: *** Including module: lvm ***
Feb 14 13:40:27 localhost dracut: Skipping udev rule: 64-device-mapper.rules
Feb 14 13:40:27 localhost dracut: Skipping udev rule: 56-lvm.rules
Feb 14 13:40:27 localhost dracut: Skipping udev rule: 60-persistent-storage-lvm.rules
Feb 14 13:40:27 localhost dracut: *** Including module: rootfs-block ***
Feb 14 13:40:27 localhost dracut: *** Including module: terminfo ***
Feb 14 13:40:27 localhost dracut: *** Including module: udev-rules ***
Feb 14 13:40:27 localhost dracut: Skipping udev rule: 40-redhat-cpu-hotplug.rules
Feb 14 13:40:27 localhost dracut: Skipping udev rule: 91-permissions.rules
Feb 14 13:40:27 localhost dracut: *** Including module: biosdevname ***
Feb 14 13:40:27 localhost dracut: *** Including module: systemd ***
Feb 14 13:40:28 localhost dracut: *** Including module: usrmount ***
Feb 14 13:40:28 localhost dracut: *** Including module: base ***
Feb 14 13:40:28 localhost dracut: *** Including module: fs-lib ***
Feb 14 13:40:28 localhost dracut: *** Including module: kdumpbase ***
Feb 14 13:40:28 localhost dracut: *** Including module: shutdown ***
Feb 14 13:40:28 localhost dracut: *** Including modules done ***
Feb 14 13:40:28 localhost dracut: *** Installing kernel module dependencies and firmware ***
Feb 14 13:40:28 localhost dracut: *** Installing kernel module dependencies and firmware done ***
Feb 14 13:40:29 localhost dracut: *** Resolving executable dependencies ***
Feb 14 13:40:30 localhost dracut: *** Resolving executable dependencies done***
Feb 14 13:40:30 localhost dracut: *** Hardlinking files ***
Feb 14 13:40:30 localhost dracut: *** Hardlinking files done ***
Feb 14 13:40:30 localhost dracut: *** Stripping files ***
Feb 14 13:40:30 localhost dracut: *** Stripping files done ***
Feb 14 13:40:30 localhost dracut: *** Generating early-microcode cpio image contents ***
Feb 14 13:40:30 localhost dracut: *** Constructing GenuineIntel.bin ****
Feb 14 13:40:30 localhost dracut: *** Store current command line parameters ***
Feb 14 13:40:30 localhost dracut: *** Creating image file ***
Feb 14 13:40:30 localhost dracut: *** Creating microcode section ***
Feb 14 13:40:30 localhost dracut: *** Created microcode section ***
Feb 14 13:40:38 localhost dracut: *** Creating image file done ***
Feb 14 13:40:41 localhost dracut: *** Creating initramfs image file '/boot/initramfs-3.10.0-693.el7.x86_64kdump.img' done ***
Feb 14 14:16:05 localhost dracut: dracut-
Feb 14 14:16:05 localhost dracut: Executing: /sbin/dracut -f /boot/initramfs-3.10.0-693.17.1.el7.x86_64.img 3.10.0-693.17.1.el7.x86_64
Feb 14 14:16:05 localhost dracut: dracut module 'modsign' will not be installed, because command 'keyctl' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
Feb 14 14:16:05 localhost dracut: 95nfs: Could not find any command of 'rpcbind portmap'!
Feb 14 14:16:05 localhost dracut: dracut module 'modsign' will not be installed, because command 'keyctl' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found!
Feb 14 14:16:05 localhost dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found!
Feb 14 14:16:05 localhost dracut: 95nfs: Could not find any command of 'rpcbind portmap'!
Feb 14 14:16:06 localhost dracut: *** Including module: bash ***
Feb 14 14:16:06 localhost dracut: *** Including module: nss-softokn ***
Feb 14 14:16:06 localhost dracut: *** Including module: i18n ***
Feb 14 14:16:06 localhost dracut: *** Including module: network ***
Feb 14 14:16:06 localhost dracut: *** Including module: ifcfg ***
Feb 14 14:16:06 localhost dracut: *** Including module: drm ***
Feb 14 14:16:07 localhost dracut: *** Including module: plymouth ***
Feb 14 14:16:08 localhost dracut: *** Including module: dm ***
Feb 14 14:16:08 localhost dracut: Skipping udev rule: 64-device-mapper.rules
Feb 14 14:16:08 localhost dracut: Skipping udev rule: 60-persistent-storage-dm.rules
Feb 14 14:16:08 localhost dracut: Skipping udev rule: 55-dm.rules
Feb 14 14:16:08 localhost dracut: *** Including module: kernel-modules ***
Feb 14 14:16:11 localhost dracut: *** Including module: lvm ***
Feb 14 14:16:11 localhost dracut: Skipping udev rule: 64-device-mapper.rules
Feb 14 14:16:11 localhost dracut: Skipping udev rule: 56-lvm.rules
Feb 14 14:16:11 localhost dracut: Skipping udev rule: 60-persistent-storage-lvm.rules
Feb 14 14:16:11 localhost dracut: *** Including module: resume ***
Feb 14 14:16:11 localhost dracut: *** Including module: rootfs-block ***
Feb 14 14:16:11 localhost dracut: *** Including module: terminfo ***
Feb 14 14:16:11 localhost dracut: *** Including module: udev-rules ***
Feb 14 14:16:11 localhost dracut: Skipping udev rule: 40-redhat-cpu-hotplug.rules
Feb 14 14:16:12 localhost dracut: Skipping udev rule: 91-permissions.rules
Feb 14 14:16:12 localhost dracut: *** Including module: biosdevname ***
Feb 14 14:16:12 localhost dracut: *** Including module: systemd ***
Feb 14 14:16:12 localhost dracut: *** Including module: usrmount ***
Feb 14 14:16:12 localhost dracut: *** Including module: base ***
Feb 14 14:16:12 localhost dracut: *** Including module: fs-lib ***
Feb 14 14:16:12 localhost dracut: *** Including module: shutdown ***
Feb 14 14:16:12 localhost dracut: *** Including modules done ***
Feb 14 14:16:12 localhost dracut: *** Installing kernel module dependencies and firmware ***
Feb 14 14:16:12 localhost dracut: *** Installing kernel module dependencies and firmware done ***
Feb 14 14:16:12 localhost dracut: *** Resolving executable dependencies ***
Feb 14 14:16:13 localhost dracut: *** Resolving executable dependencies done***
Feb 14 14:16:13 localhost dracut: *** Hardlinking files ***
Feb 14 14:16:13 localhost dracut: *** Hardlinking files done ***
Feb 14 14:16:13 localhost dracut: *** Stripping files ***
Feb 14 14:16:13 localhost dracut: *** Stripping files done ***
Feb 14 14:16:13 localhost dracut: *** Generating early-microcode cpio image contents ***
Feb 14 14:16:13 localhost dracut: *** Constructing GenuineIntel.bin ****
Feb 14 14:16:13 localhost dracut: *** Store current command line parameters ***
Feb 14 14:16:13 localhost dracut: *** Creating image file ***
Feb 14 14:16:13 localhost dracut: *** Creating microcode section ***
Feb 14 14:16:13 localhost dracut: *** Created microcode section ***
Feb 14 14:16:21 localhost dracut: *** Creating image file done ***
Feb 14 14:16:26 localhost dracut: *** Creating initramfs image file '/boot/initramfs-3.10.0-693.17.1.el7.x86_64.img' done ***

Comment 12 Gregory Young 2018-02-14 19:31:54 UTC
Created attachment 1396119 [details]
journalctl -t dracut

Output of "journalctl -t dracut" attached.

Comment 13 Gregory Young 2018-02-14 19:35:19 UTC
And of course it works now.....

OK, really not sure why it was failing in the past, but works now with the 3.10.0-693.17.1.el7.x86_64 kernel...

For sure, adding the uefi-libs module corrected it... Not sure what happened differently this time.

Comment 14 Harald Hoyer 2018-02-15 09:23:10 UTC
If it happens again, post the /var/log/messages and journalctl logs along with all the mentioned configuration files.


Note You need to log in before you can comment on or make changes to this bug.