Systems with FIPS enabled producing dracut modprobe errors at boot

Solution Verified - Updated -

Issue

  • We have just built our first RHEL7.3 system in our test lab. This system is essentially an uncustomized, vanilla build which runs in FIPS compliance mode. During testing, the following errors occur on boot.
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'camellia_aesni_avx_x86_64': No such device
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'camellia_aesni_avx2': No such device
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'cast6_avx_x86_64': No such device
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'serpent_avx_x86_64': No such device
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'serpent_avx2': No such device
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: FATAL: Module sha1 not found.
<Month> <Day> <Time> <hostname> dracut-pre-trigger[252]: modprobe: ERROR: could not insert 'twofish_avx_x86_64': No such device

Environment

  • Red Hat Enterprise Linux 7
  • FIPS compliance mode

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.