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
Bug 1945440 - Kernels 5.11.10, 5.11.11, 5.12.0 won't boot: stuck mounting volumes
Summary: Kernels 5.11.10, 5.11.11, 5.12.0 won't boot: stuck mounting volumes
Status: CLOSED DUPLICATE of bug 1945530
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-03-31 23:21 UTC by Dima Ryazanov
Modified: 2021-04-01 23:52 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-04-01 23:52:30 UTC
Type: Bug

Attachments (Terms of Use)
Photo (1.85 MB, image/jpeg)
2021-03-31 23:21 UTC, Dima Ryazanov
no flags Details

Description Dima Ryazanov 2021-03-31 23:21:00 UTC
Created attachment 1768181 [details]

1. Please describe the problem:

Cannot boot anymore after installing the latest kernels. Getting stuck at:
``A start job is running for /dev/mapper/fedora_localhost--live-swap``

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

5.11.10-300, 5.11.11-300, 5.12.0-0.rc5

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at :

First happened in 5.11.10. Everything works fine with 5.11.8. (Not sure about 5.11.9; I can try it if needed.)

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

Install the newest kernel and reboot.

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``:


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


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.

Not sure how to get it, since it won't boot.

Comment 1 Justin M. Forbes 2021-04-01 23:52:30 UTC

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

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