Red Hat Bugzilla – Bug 210548
[RHEL5 Beta2] anaconda/mkinitrd: difference of driver loading order between installation time and boot time after installation causes name changes.
Last modified: 2009-06-19 05:25:06 EDT
Description of problem:
Loading order of device drivers is different between installation time
and boot time after installation, even if HW configuration is unchanged.
(e.g. In one of our test environment,
at installation, the order is qla2xxx, then mptscsih,
after installation, the order is mptscsih, then qla2xxx.)
The difference causes device name changes, and the name changes
causes some problems.
o System panic occurs during boot if the root filesystem is
on a (dm) multipath device, because (dm) multipath map is
created against specific major:minor combinations during boot.
o /boot/efi partition isn't mounted by default on IA64 systems
during boot, because /boot/efi is mounted by device name
instead of label.
Version-Release number of selected component:
Steps to Reproduce:
1. Install mptscsih SCSI card, SCSI disk, qla2xxx FC card and FC disk
to a IA64 box.
2. Install OS.
At the time, remember the driver loading order and which disk is
which name, and assign /boot/efi on the SCSI disk.
Driver loading order is changed during boot, so device name of
the SCSI disk is changed.
As a result, /boot/efi isn't mounted during boot.
Driver loading order should not be changed as long as
HW configuration is not changed.
There are two bugs listed here. The /boot/efi labeling problem is fixed in
RHEL-5.0 GA. The multipath enumeration problem is a duplicate of 185852.
*** This bug has been marked as a duplicate of 185852 ***