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 1024858 - dracut: adding kernel option "rd.iscsi.firmware" to iSCSI boot causes installation to fail
Summary: dracut: adding kernel option "rd.iscsi.firmware" to iSCSI boot causes install...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: dracut-maint
QA Contact: Bruno Goncalves
URL:
Whiteboard:
: 1014463 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-30 14:08 UTC by Bruno Goncalves
Modified: 2014-06-18 03:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:36:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
serial console log with rd.debug (349.09 KB, text/plain)
2013-10-30 17:43 UTC, Jeff Burke 		no flags Details
View All

Description Bruno Goncalves 2013-10-30 14:08:52 UTC 
Description of problem:
Trying to install a server using "rd.iscsi.firmware" in the kernel options command line causes installation to fail.

sysroot.mount mount process exited, code=exited status=32  
[      
FAILED   
] Failed to mount /sysroot.  
See 'systemctl status sysroot.mount' for details.  
[      
DEPEND   
] Dependency failed for Initrd Root File System.  
[      
DEPEND   
] Dependency failed for Reload Configuration from the Real Root.


Version-Release number of selected component (if applicable):
dracut-033-26.el7

How reproducible:
100%

Steps to Reproduce:
1.Try to install a iSCSI boot system and add "rd.iscsi.firmware" to installation kernel command line.

2.Check error when mounting device on serial port.
Comment 3 Harald Hoyer 2013-10-30 14:14:38 UTC 
Note: only happens, when there is no "root=..." parameter
Comment 4 Harald Hoyer 2013-10-30 16:58:37 UTC 
*** Bug 1014463 has been marked as a duplicate of this bug. ***
Comment 5 Jeff Burke 2013-10-30 17:43:52 UTC 
Created attachment 817550 [details]
serial console log with rd.debug

(In reply to Harald Hoyer from comment #3)
> Note: only happens, when there is no "root=..." parameter

This happens during install. I am not sure who/when that option is added during install. I believe Anaconda adds it to the 'kernel command line' with a grubby command.

In my configuration. I have a iBFT entry and a local disk. Once the install is complete, I review which disks were used. It never even tried to use the iSCSI disk. It was like Anaconda was unaware that I wanted to use iSCSI.

If I reinstall, modify the pxe entry and add in rd.iscsi.firmware=1 then run my install I ge this during install.

---------------<snip>----------------
dracut-initqueue[663]: iscsistart: version 6.2.0.873-14  
dracut-initqueue[663]: iscsistart: initiator reported error (15 - session exists)  
[    
  OK     
] Started dracut initqueue hook.  
         Starting dracut pre-mount hook...  
[    
  OK     
] Started dracut pre-mount hook.  
         Mounting /sysroot...  
[      
FAILED   
] Failed to mount /sysroot.  
See 'systemctl status sysroot.mount' for details.  
[      
DEPEND   
] Dependency failed for Initrd Root File System.  
[   18.872695] systemd[1]: Starting Emergency Shell... 
[   18.873761] systemd[1]: Stopped Device-Mapper Multipath Device Controller. 
[   18.873869] systemd[1]: Starting Journal Service... 
[   18.875578] systemd-journald[100]: Received SIGTERM 
[   18.876390] systemd[1]: Starting Journal Service... 
[   18.876631] systemd[1]: Started Journal Service. 
[   18.878102] systemd-journald[925]: Vacuuming done, freed 0 bytes 
[      
DEPEND   
] Dependency failed for Reload Configuration from the Real Root.  
 
Generating "/run/initramfs/rdsosreport.txt" 
  
Entering emergency mode. Exit the shell to continue. 
Type "journalctl" to view system logs. 
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot 
after mounting them and attach it to a bug report. 
:/# 
---------------</snip>----------------
Comment 7 Bruno Goncalves 2013-11-01 11:56:13 UTC 
Verified, tried adding rd.iscsi.firmware to kernel command line when installing the OS and iSCSI session got established.

dracut-033-39.el7.
Comment 9 Bruno Goncalves 2013-11-01 11:57:45 UTC 
Should kernel option "rd.iscsi.firmware" be added to all iSCSI boot servers that have the iSCSI configuration stored on BIOS?
Comment 10 Ludek Smid 2014-06-13 10:36:51 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.