Bug 1756735 - Live USB image ofr Fedora 31 beta does not boot on HP Z220
Summary: Live USB image ofr Fedora 31 beta does not boot on HP Z220
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-29 13:24 UTC by Simon
Modified: 2020-11-24 16:58 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 16:58:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Foto of the error (4.79 MB, image/jpeg)
2019-09-29 13:24 UTC, Simon
no flags Details

Description Simon 2019-09-29 13:24:15 UTC
Created attachment 1620776 [details]
Foto of the error

Description of problem:
When I try to start the system with the Fedora 31 beta USB stick the system hangs at the message:
A start job us running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling

This message stays there forever (max time tried: 5:30 min).

What I checked:
- I already executed the selfcheck of the medium: PASS
- On my Laptop the same stick boots.

Version-Release number of selected component (if applicable):
Fedora 31 beta USB stick iso image

How reproducible:
always

Steps to Reproduce:
1. Start HP Z220 Workstation with Fedora 32 beta USB stick
2. Wait...

Actual results:
Hangs forever

Expected results:
Fedora boots into gdm login screen

Additional info:
System configuration:
Intel i7-3770 3.4 Ghz
Radeon RX570
24 Gb RAM

Comment 1 dagunny 2020-04-19 20:27:04 UTC
I had an identical problem on an HP Envy 17t with F32 beta using a GPT UEFI LiveCD. I setup an additional blank flash drive as GPT using Minitool Partition Manager and put it in another USB slot. I then booted the original LiveCD UEFI USB drive (Created by Rufus as GPT from the downloaded LiveCD.iso) with the 2nd GPT blank drive in and it got past the error. The BIOS did have secure boot enabled as well as Intel SGX. The main drive was an Optane32GB/512GB SSD that had Windows 10 on it. I then retried everything and was able to replicate it. My goal was to create a spare USB drive I could boot with linux loaded in case the Windows drive failed.

Comment 2 Ben Cotton 2020-11-03 16:53:30 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-11-24 16:58:35 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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