I installed Fedora with a 6.1.7 kernel, however any more recent kernels will not boot. It says
Failed to start systemd-cryptsetup@luks\*.service - Cryptography Setup for luks-*.
See 'systemctl status "systemd-cryptsetup@luks*.service" for details'
I cannot find any more information about this, does anyone know the solution? I cannot access systemctl as I cannot get the computer to boot. I’m still running off a Fedora 37 kernel while installing Fedora 38.
I don’t use luks so cannot speak to the cryptology.
However it is always recommended that one upgrade the system to the latest and reboot before starting an upgrade to the next version.
The 6.1.7 kernel means that you should not try upgrading until the boot issue with the newer kernels is resolved. F38 was released with a 6.2.x kernel and if the newer kernels will not boot then you would potentially have a dead system that would not boot.
The second line you posted suggests to use systemctl to show the status of that service. If you do that and post the results we might be able to assist.
Also use journalctl -b to display messages for the most recent boot and dmesg to display kernel messages from the boot. Both those log media may provide clues as to why the newer kernels are not booting properly.
Thank you, however none of those commands show anything about the necessary boot, seems like the files have not been created.
Do you mean the command dmesg does not give a response? That would be very strange.
If journalctl -b also gives no reponse it would be even more weird.
It gives me a response, but I cannot get an output for failed boots, ones on the 6.2.x kernel line
I tried doing this and the shell never appears. Do I need to reinstall?
I fixed my install, this is how I did it. First, I used a backup drive to decrypt my luks partition. Next, I booted into the dracut shell, mounted my partition and /dev, /proc, etc partitioned. I then chrooted by using the chroot program stored in that chroot. Then, I edited my fstab to replace the old entry with the new one, and rebooted. It booted just fine. Thank you @vgaetera for the dracut link.