Stuck on boot after LUKS decrypt with systemd

[misty ginkgo]

Description

I was messing around with TLP and Tailscale the other night, I have ultimately disabled Tailscale and configured TLP and started the config. I also installed powertop with bending restart.

After shutting the system down, around 5 hours ago I find out the OS does not boot.
The LUKS decryption spinner suddenly froze and after exiting the LUKS decrypt GUI, the terminal displays that the system hangs at "Reached target nss-lookup.target - Host and Network name Lookups" AND "Started systemd-rfkill.service - Load/Save RF Kill Switch Status"
It does not progress beyond that. I have tried the image previous image with GRUB but that didn't work. What could be the issue?
I have a business grade DELL laptop. I should add the laptop does not respond to CTRL ALT DEL, I can only exit with a force turn off.

*Reproduce

Reboot/boot device
Decrypt

*Expected

Boot

*Actual behavior

No boot

*Image

Unknown, recent, up to date

[misty ginkgo]

It is always different where the systemd check screen stops, I also noticed a few errors:
"[FAILED] Failed to start systemd-remount-fs...mount Root and Kernel filesystems"
also
"systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernek filesystems."

Can I fix this with a recovery image?

[unreal bough]

why are using TLP over tuned?

[unreal bough]

oh wow

[unreal bough]

wait no, this is probably a red herring

[misty ginkgo]

Lack of better judgement?

Am I screwed? Can I salvage anything based on this? I'm in college and I cannot go without a working device for long.

[unreal bough]

i'm not familiar with TLP or how it could impact your system well enough to comment

fedora has been using tuned for some time

[gloomy python]

if it's urgent, you could extract your data with luksOpen from a rescue ISO and start again

[unreal bough]

good idea, @misty ginkgo

[gloomy python]

lmk if this route works out for you - remember that after opening the luks and mounting the top-level btrfs, you'll also need to mount the home (and optionally var) subvolumes

[misty ginkgo]

Thank you for the advice. Is there any way to repair the system as it is? I don't have a storage device to save to. Is the kernel messed up? Can I do some additional checks?

[misty ginkgo]

Why is tuned recommended over tlp?

[gloomy python]

power-profiles-daemon was historically the default on Fedora and is well-integrated

for example, the "Balanced / Power Saving / Performance" modes in gnome correspond to power profiles

fedora then transitioned from ppd to tuned-ppd, so it has that same integration

[unreal bough]

granular profiles, better efficiency, more tunable

[misty ginkgo]

So can anyone confirm there is no was to return the previous state of the OS? There is data I cannot easily move such as browser state and installed app lists, other configs. What does the systemd kernel errors tell? There is no testing I can do?

[gloomy python]

it should be possible to move all of that stuff, since it lives under ~/.config/trivalent and /etc, you should be able to copy it verbatim. installed app lists are in /usr/share/applications and ~/.local/share/applications too. the thing that won't transfer is your layered packages

there isn't really enough information here to know for sure, but if it's failing to remount the root filesystem, then that's not great? royal said it might be a red herring - both TLP and Tailscale don't show up early enough in the boot process to cause that kind of problem

were you using a custom initramfs?

[misty ginkgo]

if by that you mean hardened kargs then yes

[gloomy python]

no, i meant using rpm-ostree initramfs

if not, i don't have any ideas, sorry :(
there's no reason (i can think of) tlp/tailscale would make it impossible to unlock your drive

again, i think you might get more clues if you use something like SystemRescue to try and mount it externally and see if that works