Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
*os-prober* now uses device mapper alias names in the boot loader configuration
The *os-prober* component previously used the numeric device mapper device in the boot loader configuration. After reboot, when the installer disk image was no longer mounted, the number changed, which rendered the boot entry unusable. Consequently, when two instances of Red Hat Enterprise Linux were installed on one machine, one of them failed to boot. To fix this bug, *os-prober* now uses device mapper alias names instead of the direct enumerated device mapper names. Because the alias names are more stable, the boot entry works as expected in the described situation.
Created attachment 1116586[details]
Screenshot zip file
Description of problem:
I have install two RHEL7.2 on one server .The grub has already contain two RHEL7.2 OS (first install the rhel72-1 OS then install the rhel72-2 OS).But when trying to boot from the rhel72-1 OS it will failed to boot up.
Version-Release number of selected component (if applicable):
rhel-server-7.2-x86_64-dvd.iso
How reproducible:
Every time
Steps to Reproduce:
1.Use a bare machine to install the RHEL7.2 OS with below partation:
sda1 500M xfs /boot
sda2 7G lvm rhel-root xfs /
2G lvm rhel-swap swap
2.then use the same machine to install the second RHEL7.2 OS as below partation:
sda3 500M xfs /boot
sda4 1k
sda5 7G lvm rhel00-root xfs /
3.waiting for the installation finished
4.select first install RHEL7.2 OS to boot
Actual results:
boot failed
Expected results:
boot success
Additional info:
The solution is fix the grub list manual :
When see the grub high light the first RHEL7.2 OS then press "e" to edit it find the “root=/dev/dm-2”entry and then fix it into "root=/dev/mapper/rhel-root" then press "Ctrl+x" the first RHEL7.2 OS could boot normal.
I just wondering why the default grub doesn't work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2351.html
Created attachment 1116586 [details] Screenshot zip file Description of problem: I have install two RHEL7.2 on one server .The grub has already contain two RHEL7.2 OS (first install the rhel72-1 OS then install the rhel72-2 OS).But when trying to boot from the rhel72-1 OS it will failed to boot up. Version-Release number of selected component (if applicable): rhel-server-7.2-x86_64-dvd.iso How reproducible: Every time Steps to Reproduce: 1.Use a bare machine to install the RHEL7.2 OS with below partation: sda1 500M xfs /boot sda2 7G lvm rhel-root xfs / 2G lvm rhel-swap swap 2.then use the same machine to install the second RHEL7.2 OS as below partation: sda3 500M xfs /boot sda4 1k sda5 7G lvm rhel00-root xfs / 3.waiting for the installation finished 4.select first install RHEL7.2 OS to boot Actual results: boot failed Expected results: boot success Additional info: The solution is fix the grub list manual : When see the grub high light the first RHEL7.2 OS then press "e" to edit it find the “root=/dev/dm-2”entry and then fix it into "root=/dev/mapper/rhel-root" then press "Ctrl+x" the first RHEL7.2 OS could boot normal. I just wondering why the default grub doesn't work.