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.

Created attachment 1028961 [details]
initial grub.cfg

Dear Red Hat,

Would one of our intrepid heroes please fix this for me?

I am coming from the community: Scientific Linux 7.1

I installed SL-71-x86_64-2015-03-27-LiveDVDgnome.iso into a SL 6.6 KVM virtual machine.  There were a number of error in in /boot/grub2/grub.cfg

On the attached file:

1) Line 89 and 90 are reversed and lines 103 and 104 are reversed.

2) Lines 106 to 119 (menuentry) should be the first menu entry, not the third.  

3) the two MenuEntries for "rescue" are duplicates of each other

4) the menu entry for Nitrogen (line 106-119) causes a kernel panic:
     Failed to access perfctr msr (MSR c1 is 0)
     kernel panic -- not syncing:L VFS: Unable to mount root fs on unknown-block(0,0)

Many thanks,
-T

Additional info:

If I comment out the "linux16" entry from the Nitrogen menuentry, the kernel panic goes away and I can boot normally.

Also, putting the ending bracked ("}") in the right place on the two duplicate rescue menuentries also enables it to boot.

OOps on the linux 16.  I was in Fedora Live.  The line just flash at you when you repeatedly try to select it from the menu if linux16 is commented out

Figured it out.

In the Nitogen menuentry, I made this change (linux16) and addition (initrd16):

#	linux16 /vmlinuz-3.10.0-229.1.2.el7.x86_64 root=/dev/sda2 ro rhgb quiet LANG=en_US.UTF-8
	linux16 /vmlinuz-3.10.0-229.1.2.el7.x86_64 root=/dev/sda2 ro quiet LANG=en_US.UTF-8
	initrd16 /initramfs-3.10.0-229.1.2.el7.x86_64.img


I will upload my corrected grub.cfg

Created attachment 1028976 [details]
corrected grub.cfg

Corrected grub.cfg for use correcting the installer

*** This bug has been marked as a duplicate of bug 1177003 ***