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.
Bug 1775613 - Laptop install of linux 7.7 failed
Summary: Laptop install of linux 7.7 failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-22 12:22 UTC by Dan
Modified: 2021-05-22 07:30 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-22 07:30:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan 2019-11-22 12:22:43 UTC
Description of problem:
I installed Centos 7 on my laptop. The install went fine and I get to the login screen. I select the user and enter the password and then get these error messages.

[Firmware Bug] the BIOS has corrupted the hw-PMU resources (MSR 38d is b0)
mce: Unable to init device /dev/mcelog (RC: -5)
tmpfs: Bad mount huge
SR 2:0:0:0 [sr0] out of memory
Please enter passphase for disk vggroup00-var

If I enter the passphase it continues for awhile and prints some stuff and then reboots.

It has the latest firmware update and 12GB of memory.
It ran Centos 6 for years and also runs Windows 10 fine.


Version-Release number of selected component (if applicable):


How reproducible:
I have only tried this once.

Actual results:
Bad install, had to reinstall Centos 6


Expected results:
A workable install


Additional info:
This is my disc configuration
[dan@laptop ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/dm-2       145G  6.5G  131G   5% /
tmpfs           5.8G  2.3M  5.8G   1% /dev/shm
/dev/dm-15      413G  388G  3.8G 100% /backup
/dev/sdb1       969M   65M  854M   8% /boot
/dev/dm-12      193G   30G  154G  17% /home
/dev/dm-10      9.5G   23M  9.0G   1% /tmp
/dev/dm-13      9.5G  415M  8.6G   5% /var
/dev/dm-14      4.7G   15M  4.5G   1% /var/log
/dev/dm-16      4.7G   10M  4.5G   1% /var/log/audit
/dev/dm-11      193G   64G  120G  35% /vm
[dan@laptop ~]$

When reinstalling Centos 6 I got a message that a 5GB partition didn't have a filesystem.  This could only be /var/log or /var/log/audit.  Note that the error message: "Please enter the passphase for vggroup00-var" in Centos 7.7.  When installing Centos 7.7 I used allocate space as a standard partition instead of LVM.  This is because I didn't have any spare LVM space and when you select swap it sets the space to 0.  (Also swap was allocated as a standard partition already). You then have to delete swap and add it again. I suspect that it allocated space in LVM even though I said allocate as standard partition and wiped out the LVM volumes formatting swap.  Any way, this is what I think the problem is!

Comment 4 RHEL Program Management 2021-05-22 07:30:41 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.