Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1667642

Summary: Getting messages like "systemd-udevd[XXX]: Process '/sbin/modprobe -bv sg' failed with exit code 1." on boot
Product: Red Hat Enterprise Linux 8 Reporter: Jose Castillo <jcastillo>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: bugzilla, dracut-maint-list, dtardon, jdluhos, systemd-maint-list
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-03 17:43:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Possible patch none

Description Jose Castillo 2019-01-19 09:53:43 UTC 
Description of problem:
While booting a RHEL 8 server, the following messages are printed in the logs:

Jan 19 09:05:00 localhost systemd-udevd[368]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[375]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[366]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[368]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[375]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[368]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[366]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[368]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[366]: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Jan 19 09:05:00 localhost systemd-udevd[368]: Process '/sbin/modprobe -bv sg' failed with exit code 1.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 8
systemd-239-10.el8
systemd-udev-239-10.el8

How reproducible:
Always

Steps to Reproduce:
In a system with SCSI devices present, simply check the logs via 'journalctl' and these messages will be there.

Actual results:
modprobe fails to load the 'sg' module during boot.

Expected results:
modprobe doesn't fail and the module 'sg' is loaded as expected.
Comment 1 Jose Castillo 2019-01-19 09:56:16 UTC 
The messages come from the following udev rule:


/usr/lib/udev/rules.d/40-redhat.rules:SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", RUN+="/sbin/modprobe -bv sg"
/usr/lib/udev/rules.d/40-redhat.rules:SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_target", TEST!="[module/sg]", RUN+="/sbin/modprobe -bv sg"
This rule is included in the initramfs image, but the module it tries to load is not:


# lsinitrd /boot/initramfs-`uname -r`.img |grep sg
crw-r--r--   1 root     root       1,  11 Oct 30 08:38 dev/kmsg
-rwxr-xr-x   1 root     root        83640 Oct 30 08:38 usr/bin/dmesg
-rw-r--r--   1 root     root          942 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg-latin1-lk450.map.gz
-rw-r--r--   1 root     root          992 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg-latin1.map.gz
-rw-r--r--   1 root     root          924 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg.map.gz
-rw-r--r--   1 root     root         3161 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg.map.sg-decimal-separator
After using:


# dracut --add-drivers sg /boot/initramfs-`uname -r`.img -v --force
The module is added, and the messages disappear:


# lsinitrd /boot/initramfs-`uname -r`.img |grep sg
Arguments: --add-drivers 'sg' -v --force
crw-r--r--   1 root     root       1,  11 Oct 30 08:38 dev/kmsg
-rwxr-xr-x   1 root     root        83640 Oct 30 08:38 usr/bin/dmesg
-rw-r--r--   1 root     root          942 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg-latin1-lk450.map.gz
-rw-r--r--   1 root     root          992 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg-latin1.map.gz
-rw-r--r--   1 root     root          924 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg.map.gz
-rw-r--r--   1 root     root         3161 Oct 30 08:38 usr/lib/kbd/keymaps/legacy/i386/qwertz/sg.map.sg-decimal-separator
-rw-r--r--   1 root     root        20920 Oct 30 08:38 usr/lib/modules/4.18.0-58.el8.x86_64/kernel/drivers/scsi/sg.ko.xz
Comment 2 Jose Castillo 2019-01-19 10:01:34 UTC 
Changing component from systemd to dracut, since there seems to be the problem. 

Dracut version is dracut-049-8.git20181030.el8.x86_64
Comment 3 Jose Castillo 2019-01-19 10:06:54 UTC 
Created attachment 1521769 [details]
Possible patch

Possible patch, very simple. It just adds the 'sg' (scsi generic) module to the list of modules to be loaded, when the other scsi module are loaded (sd_mod, sr_mod)
Comment 6 David Tardon 2020-08-03 17:43:33 UTC 

*** This bug has been marked as a duplicate of bug 1579763 ***