Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1948193 - Kernel 5.11.12 & 5.11.13 fail at "Reached target local encrypted volumes"
Summary: Kernel 5.11.12 & 5.11.13 fail at "Reached target local encrypted volumes"
Keywords:
Status: CLOSED DUPLICATE of bug 1945950
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
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: 2021-04-10 16:38 UTC by tla2k15
Modified: 2021-04-14 13:42 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-14 13:42:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Successful boot of kernel 5.11.10 (125.05 KB, text/plain)
2021-04-10 16:38 UTC, tla2k15
no flags Details

Description tla2k15 2021-04-10 16:38:32 UTC
Created attachment 1771005 [details]
Successful boot of kernel 5.11.10

1. Please describe the problem:

System boot fails to get past "Reached target local encrypted volumes"

2. What is the Version-Release number of the kernel:

5.11.11 or 5.11.12 have the issue.

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

First appeared 5.11.11.
Issue also present in 5.11.12.
Last working version 5.11.10.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Boot the system normally
Enter the encrypted volume passphrase
Boot stalls at "Reached target local encrypted volumes"

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes. fedora-repos-rawhide-34-0.14.noarch is already installed

6. Are you running any modules that not shipped with directly Fedora's kernel?:

RPM Fusion: nvidia_drm, nvidia_modeset, nvidia
Issue still present when running nouveau only

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

The boot does not proceed far enough to create a boot dmesg.
Attached the boot log for the last working kernel 5.11.10.

Comment 1 Justin M. Forbes 2021-04-14 13:42:45 UTC
This was a dracut bug fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2021-50707f8501

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


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