stable

dracut-053-2.fc34

FEDORA-2021-50707f8501 created by adamwill 3 years ago for Fedora 34

This update backports a change which is reported to fix a bug where systems with certain encrypted LVM storage configurations fail to boot.

Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2021-50707f8501

This update has been submitted for testing by adamwill.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago

This update's test gating status has been changed to 'waiting'.

3 years ago

This update's test gating status has been changed to 'ignored'.

3 years ago
User Icon special provided feedback 3 years ago
karma
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot
User Icon kalvinist provided feedback 3 years ago
karma
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot
User Icon pbrobinson provided feedback 3 years ago
karma
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot

This update has been pushed to testing.

3 years ago

This update can be pushed to stable now if the maintainer wishes

3 years ago

adamwill edited this update.

3 years ago
User Icon tdlrali provided feedback 3 years ago
karma
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot
User Icon scorreia provided feedback 3 years ago
karma
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot

This update has been submitted for stable by bodhi.

3 years ago
User Icon cserpentis commented & provided feedback 3 years ago
karma

works for me

User Icon atim provided feedback 3 years ago
karma
User Icon mmaslano commented & provided feedback 3 years ago

I think I have a problem related to 1946074. This update doesn't fix it for me. I'm not exactly sure if it's fault of dracut. I can boot with kernel 5.11.10-300.fc34.x86_64. Two new kernels are not working for me.

BZ#1945901 boot hang with message [DEPEND] Dependency failed for Cryptography Setup for luks-XXXX...
User Icon scorreia commented & provided feedback 3 years ago

@mmaslano: did you rebuild your initramfs after installing the updated dracut?

This comment has an example on how to do it (you may have to adjust the command slightly depending on the kernel version you have installed): https://bugzilla.redhat.com/show_bug.cgi?id=1946074#c12

This update has been pushed to stable.

3 years ago
User Icon mmaslano commented & provided feedback 3 years ago

@scorreia No :) I did rebuild it now. No luck. I've noticed message: "Cant load kernel modules" which was replaced by hanging on dracut :-/


Please login to add feedback.

Metadata
Type
bugfix
Severity
urgent
Karma
7
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
5
Stable by Time
14 days
Dates
submitted
3 years ago
in testing
3 years ago
in stable
3 years ago
modified
3 years ago
BZ#1945901 boot hang with message [DEPEND] Dependency failed for Cryptography Setup for luks-XXXX...
0
0
BZ#1945950 dracut-053 renders system unbootable
0
0
BZ#1946074 boot failure when LV is a cryptoluks device used as sysroot
0
4

Automated Test Results

Test Cases

0 0 Test Case Dracut live image
0 0 Test Case Dracut root=LABEL
0 0 Test Case Dracut root=nbd
0 0 Test Case Dracut root=nfs
0 0 Test Case Dracut root=partition
0 0 Test Case Dracut switch to host-built ramdisk
0 0 Test Case Dracut switch to locally built ramdisk