Red Hat Bugzilla – Bug 447375
[Netapp 5.3 bug] mkinitrd doesn't provide complete support for SANBoot.(root on multipath iSCSI).
Last modified: 2014-09-08 10:22:55 EDT
Description of problem:
mkinitrd, shipped with RHEL5.2 doesn't support multipathed devices completely.
For multipathed device, the initrd image creates iscsi login to target through
only one path.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run install on iscsi multipathed device (Root on multipath).
2.At the end of installation process anaconda will run mkinitrd to create new
3. Once installation is done, do reboot.
4. During 1st boot you will see that initiator has logged in through only one
During initrd, initiator will be logged in through only one path.
During initrd, iscsi initiator should be logged in to the target through all
Created attachment 305992 [details]
root on multipath(iSCSI) mkinitrd patch
After applying attached patch mkinitrd creates proper initrd, which makes sure
that iscsi initiator will login to target through all configured paths.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Because we're merging the Fedora 9 encryption support into RHEL5.3, the attached
patch may require changes. We'll re-evaluate this one in ~2 weeks, once the
encryption support is in.
Have we included patch (id=305992) comment #1 in 5.3? I don't see any update here.
This support should be present in mkinitrd-184.108.40.206-31 .
mkinitrd is creating proper initrd image. Now we can see initiator is logged in to all the configured paths during boot time.
Thank you for including patch (Comment #1).
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.