Boot error after entering LUKs password

Linux Support
, ,
1

I get the the following error message after entering my LUKS password:

Booting `Fedora Linux (6.14.9-300.fc42.x86_64) 42 (Workstation Edition)`

Warning: /dev/disk//byuuid/1405d96c-bd31-4816-a2cd-e137e0f9dd07

Generating "/run/initramfs/rdsosreport.txt"

The problem persists when restarting the device.
I had the same problem on the same computer before and back then I just reinstalled Fedora to fix it, but after a while I have the same error again.
I don’t want to just reinstall again because then it will probably happen a third time.

Would it help to install a different Linux distribution to fix the error and don’t get it again?

In case you need the
“/run/initramfs/rdsosreport.txt”
Can you please tell me how to get it out?

Thanks to everyone who tries to help :slight_smile:

2 Likes
Weekly Forum Summary
2

This usually happens when Fedora’s initramfs can’t find the encrypted root device after you enter the LUKS password. The warning about /dev/disk/by-uuid/… means the UUID Fedora expected doesn’t match the actual UUID on your system.

Also see:

Now this helps.

3 Likes
3

Thank you, but how do I fix it and how do I avoid it in the future?

I checked this links but can’t find a solution for my problem

4

Is the error specific to Fedora?
Would using another Distro like Ubuntu solve this?
Sorry for my stupid questions but I don’t have much technical knowledge and just want to the computer to work again

1 Like
5

Ubuntu wouldn’t really “fix” this because it uses the same underlying initramfs mechanism for unlocking LUKS. The difference is just tooling and defaults, not the core process. If the drive isn’t detected early in the boot stage, any distro with full-disk encryption can hit the same issue.

So switching distros isn’t a guaranteed solution. The root problem is that your initramfs can’t see the encrypted device after you enter the password.

And don’t worry about the questions. This error is confusing for all of us at some point.

A fresh install even of Fedora might be helpful, once you have your files backed up.

1 Like
6

I really would liek what is causing this, so I can avoid it in the future, because this happened twice to this computer, but never to my other computer that is running the exact same distribution and also has LUKS enabled.

I fear that if just reinstall the same distro, on the same device and doing the same things , it will end up with the same result.

7

To add to this, that message usually appears when the system can’t locate the encrypted drive after you enter the password. It often means the boot configuration no longer matches the actual disk.

If there’s nothing important on the install, the safest route is to back up what you need from a live USB and do a clean reinstall. That avoids low-level recovery steps that could make things worse, and I wouldn’t feel comfortable giving those commands here. You’re of course free to troubleshoot it yourself and share any confirmed solution.

If you’d rather try recovering it, the next step is to grab the rdsosreport.txt file from the emergency prompt and post it here. That shows exactly what the system is complaining about without changing anything on the disk.

Reference:

1 Like
Weekly Forum Summary
8

I am ok with reinstalling, but I would like to know what I did wrong to avoid the issue in the future

1 Like
Weekly Forum Summary
9

I am not a Fedora user, but this gives the impression that selecting a previous kernel may help.

Please see the section “How to get the rdsosreport when the system boots to emergency mode/dracut”:

2 Likes
Weekly Forum Summary
10

Thanks, I will try this when I find time next

2 Likes