Fedora will not boot: LUKS

Ask Fedora
1

After successfully installing Fedora 43 on a love USB. I attempted to install it on my Thinkpad. After completing the set up, and choosing to encrypt my SSD.

After restarting, and entering the correct LUKS passphrase, it will load continuously, I have waited hours at some point. I have entered the live USB and done the cryptsetup command, and see that the drive is not corrupted. I have even reinstalled fedora and the problem persists. I editted grub and where it says rhgb splash I editted it to say nomodeset, and the issue was still happening.

I then reinstalled it again, and it is still broken, and I thought it could be my USB that is the issue. I installed Fedora 43 on an older Thinkpad, about 20 years old, and it works perfectly fine with LUKS. I have no idea what is the problem and I am exhausted trying to find a solution.

Can anyone here help provide what is going on?

2

Hit ESC while the spinner is spinning to see the boot messages and report back where it’s hanging.

1 Like
3

I will do this now. One moment.

4

Hello. I have gotten the following issues, all slowly came up after one another:

/O Error (sct 0x2 / sc 0x81)
critical medium error, dev nvme0n1, sector 10395800 op 0x0: (READ) flags 0x84700 phys_seg 1 prio class 2

nvme0n1: I/0 Cd(0x2) @ LBA 10396056, 184 blocks, I/0 Error (sct- 0x2 / sc 0x81)

critical medium error, dev nvmeon1, sector 10396056 op 0x0: (READ) flags, 0x80700

systemd[1]: Failed to fork off sandboxing environment for executing generators: Protocol error

[!!!] Failed to start up manager.

systemd[1]: Freezing execution.

nvme nvme0: Device not ready; aborting reset CSTS-0x1.

nvme@n1: 1/0 Cmd(0x2) @ LBA 17064808, 32 blocks, I/0 Error (sct 0x3! sc 0x71)

I/O error, dev nvme@n1, sector 17064808 op 0x0: (READ) flags 0x80700 phys_seg 4 prio class 2

nvme nvme0: Device, not ready; aborting reset, CSTS=0x1.

nvme nvme0: Device not ready; aborting reset, CSTS=0x1

BTRFS error (device dm-0):bdev/dev/mapper/luks-4c567c78-6432-11ec-bf63-0242ac130002

5

This looks like a physical hardware failure of your NVMe SSD. The error codes you’re seeing point toward the drive’s internal controller struggling to communicate with the NAND flash memory.
Boot a live system and run a smart test.

1 Like
6

I will do this soon. However I should note that this machine had Fedora 42 installed on it within the last year, and worked fine, but I forgot the LUKS passphrase so I did a fresh install of Fedora 43 over it, and with my much older computer being able to run Fedora 43. I did run the “live test” before and it did fail something, but all my other machines have before but still worked.

Just thought that all this information might be helpful. I’ll do another test and paste it here soon.

7

Perform a S.M.A.R.T. test of all your hard drives from a f42 or f43 live media and let us know the results.

2 Likes
8

I did a test run of the USB and here were is what failed:

It is not reccommended to use this media.
[FAILED] Failed
to start checkisond80deu-sda.seruice - Media check on /dev/sda.
11.0781701 dracut-initqueuel794]: Job for checkisomd6edeu-sda.service failed because the control process exited with error code.
11.078294] dracut-initqueue[794]: See
“systemctl status checkisomd5adeu-sda.service” and
11.0788991 dracut-initqueuel739]: Warning: Media check failed? We do not recomend using this media. System will halt in 12 hours

9

Did the media test succeed on the systems where the installer worked? USB keys are not durable, so either the USB or the computer has a problem. If the USB key tests OK on the other systems, try to run the standalone memtest86+ on the problem machine.

10

The “USB test” did not pass the test when I installed it on my much older computer, but it still boots perfectly fine with LUKS. After this, I don’t think it’s my USB stick.