Red Hat Bugzilla – Bug 223221
boot from iSCSI volume fails because iscsiadm doesn't support -M flag
Last modified: 2009-06-19 08:11:29 EDT
Description of problem:
Reboot after installation on iSCSI volume fails.
Version-Release number of selected component (if applicable):
5.1.19-2.1 (RHEL5 RCS 6)
Steps to Reproduce:
1. Install RHEL5 on iSCSI volume (using "advanced storage configuration")
2. Press "Ok" on "congratulations" screen
Root filesystem isn't found
No initial RAM disk is created during installation. The reason is that mkinitrd
calls "iscsiadm -M <sysfs file>" but iscsiadm (iscsi-iniator-utils
220.127.116.112-0.2.el5) doesn't support that flag and exits with an error.
Further remark: The EL5 rescue system apparently has no support for iSCSI
storage, so recovering from this problem is extremely tedious because the whole
iscsi system must be setup by hand. iSCSI support in the rescue system would be
The iscsiadm -M <sysfs file> is fixed in iscsi-initiator-utils-18.104.22.1682-0.3.
And mkinitrd was fixed in 22.214.171.124-1. Here is the bugzilla:
Do we want to keep this bugzilla open for the second part of the BZ asking for
rescue system support?
It's unclear from the comments on this bug - is this issue still a problem?
The bug where -M sysfs_file was not working is fixed. We have testers reporting
The second part of the BZ that requests iscsi support for the rescue system is
still open. Not sure how you want to handle that. Open a new BZ for that request
or use this BZ?
Peter: no, the problem has been solved shortly before RHEL5 GA. Installation on
iSCSI works fine now (see issue tracker #119765, though).
Mike: we haven't tried the rescue system for some time (precisely because the
installations worked well).
Adding beta blocker flag per Sly. This is not really a 5.1 beta blocker.
Closing this bug. Open new bugs for secondary issues. The original issue
stated in the summary has been fixed.