From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2 Description of problem: mkinitrd fails to find scsi modules in modules.conf if using probeall instead of alias. The mkinitrd script greps for alias but does not look for probeall: scsimodules=`grep "alias[[:space:]]\+scsi_hostadapter" $modulefile | grep -v '^[ ]*#' | LC_ALL=C sort -u | awk '{ print $3 }'` Recommend mkinitrd look for both alias and probeall entries (as modprobe does) to determine which scsi host adapter modules to load in the initrd. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.enter "probeall scsi_hostadapter cciss" in modules.conf 2.run mkinitrd 3.reboot using new initrd 4.kernel panic unable to locate the rootfs 5.enter "alias scsi_hostadapter cciss" in modules.conf 6.run kninitrd 7.reboot using new initrd 8.no kernel panic Additional info: This occurs when updating the kernel and running the mkinitrd command. Since this causes the system to no longer boot, I will note this as high priority.
This isn't the supported way of doing this. If you need two modules loaded, do (using aha7xxx as an example since I don't know what you've got): alias scsi_hostadapter0 ata7xxx alias scsi_hostadapter1 cciss And both mkinitrd and rc.sysinit will handle them correctly.
Although this may not be the way Red Hat creates their modules.conf files, it is still valid to use probeall in the modules.conf file and is valid for the modprobe command. I am surely not the only user that has made VALID manual updates to the modules.conf file. I do not feel this is an unreasonable request for the mkinitrd command to properly handle valid uses of both alias and probeall in the modprobe.conf file.
*** This bug has been marked as a duplicate of 182008 ***
This is not a duplicate of 182008. This is a separate issue.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you.