broken LUKS after latest update

MetaNorm

Hi guys! Latest update broke my LUKS. Entering the passphrase after rebooting my machine leads to the following ouput. Can you help me pleas or tell me what to do?

ReillyBrogan

Can you boot an older kernel?

MetaNorm

Unfortunately not. The first prompt after the BIOS bootscreen is to enter the passphrase. I don't know how to display the typical additional boot-options for Solus shown on my Laptop for example.

528491

MetaNorm I don't know how to display the typical additional boot-options for Solus

I think you just have to repeatedly hit any key while booting. Try the spacebar.

MetaNorm

The spacebar did it. I could choose three versions including the LTS Kernel but without success. Everytime the emergency mode appears.

presianbg

MetaNorm are you on unstable or shannon repo ?
I was planing to test the unstable updates, because there will be no sync today, but after reading this... I do not dare to break my LUKS 🙁

ReillyBrogan

Next time hit e on the boot entry and then delete quiet and systemd.show_status=false. This should hopefully give you some better logs.

MetaNorm

I'm on shannon.

MetaNorm

This appears after typing e on the selected boot option.
I can give you certain entrys of the journalctl if it would be helpful. Just tell me...

ReillyBrogan

MetaNorm you can go left and right there with your keyboard keys. Find the two arguments I said in my previous comment and delete them. Then hit enter to boot

MetaNorm

Ok, thats what I get after deleting the mentioned arguments.

MetaNorm

Maybe it's important to share this info as well:

Immediately before the reboot, the flatpaks update refused to install a package. I think it was something with GNOME 44, if I remember correctly. On the second try it worked. Then Firefox crashed, Handbrake stopped working and I couldn't delete the half-finished file. It seemed to me that the system was suddenly read-only. So I rebooted with the known problem.

Axios

Is this system mission critical and has a current backup

MetaNorm

What does critical mean? It's just my private desktop. I don't have any critical or super-private data there. But the installation is old and I have a lot of bookmarks and chat histories there that I would lose if I reinstall. That's what you were getting at, right? Reinstalling and reconfiguring everything would also be extremely annoying. I'm honestly still hoping for another way.

Axios

MetaNorm Thats exactly what I wanted to know
I dont want to suggest the possible fix because it being a luks volume I have never done it with one those
and not sure if the procedure is the same.
If not done properly not sure what would happen maybe one the dev will chime in.
Is this gnome or budgie

MetaNorm

Axios Is this gnome or budgie

It's GNOME

clauded

You should follow onscreen instructions and share the output of systemctl... and journalctl... It looks like a corrupt or full root fs
You can also boot with the ISO, unlock your luks volume and try to repair root with fsck

MetaNorm

clauded Ok, journalctl shows estimated more than 1000 lines. I can't possibly post all of that. What exactly should I look for to show relevant information?

The tip to boot the ISO probably won't work because the AM5 platform is too new for the kernel it contains. I swapped my AM4 motherboard for an AM5 in January and then just booted from my old hard drive. Worked smoothly until the crash.

Axios

Yes it appears to be a file issue but being luks and a boot drive not sure how it should be handled
Just my two cents

Axios

MetaNorm Gnome likes trashin file system after updates sometimes
(In my experience)
I have grown to notice when it happened just like you described and it will make it read only to prevent damage
But usually just a file repair is all thats needed and your good to go
The question is the procedure maybe its the same for non and encrypted that I dont know!!!!
You could use fedora iso I always used the simple gnome disks (on non encrypted you can check and repair with it) and it fixed things like a champ
Thats why I asked if it was mission critical earlier in case it got trashed.
I try to be as careful with others data as would mine when I answer posts