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) How reproducible: always Steps to Reproduce: 1. Install RHEL5 on iSCSI volume (using "advanced storage configuration") 2. Press "Ok" on "congratulations" screen Actual results: Root filesystem isn't found Expected results: Normal boot Additional info: No initial RAM disk is created during installation. The reason is that mkinitrd calls "iscsiadm -M <sysfs file>" but iscsiadm (iscsi-iniator-utils 6.2.0.742-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 highly desirable.
The iscsiadm -M <sysfs file> is fixed in iscsi-initiator-utils-6.2.0.742-0.3. And mkinitrd was fixed in 5.1.19.5-1. Here is the bugzilla: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221088 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 success. 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.