Stuck in emergency shell due to incorrect edit of loader.conf

Hey everyone, partner ran an update for their XFCE Cachy OS, after update it would boot, but her NTFS drives would not mount. They edited the loader.conf resulting in incorrect UUID mounts, the root drive is using LUKS.

Inside emergency shell, we can get to the point of unlocking and mounting the drive to browse everything on the root drive, but when loading up loader.conf with ‘vi’ we just see a bunch of ‘~’ and nothing else.

So, my next step was to try boot of a Cachy live USB, however, we end up back in the emergency shell because of LUKS I’m guessing.

Is the image here booting from the live ISO? That seems pretty impossible. The live ISO is a different environment than your system so it should boot fine. Make sure your your boot device order is correct.

No, no USB atm, this is just a straight boot, and trying to access the fstab file or the loader.conf she edited inside Cachy, issue is, even putting the CachyOS live USB in, selecting CachyOS, results in us ending up back at the emergency shell - and trying to open the loader.conf with sudo from here just results in ‘sudo not found’

So the image above is simply trying to access anything at all so we can fix things, the original problem being the loader.conf she must have edited inside cachy

These two quotes contradict each other here and I’m not sure which one is correct. If your friends does have USB with the live ISO then make sure she’s picking the correct boot device. Showing up at the emergency shell is in indication that the wrong boot device has been selected.

Furthermore I just noticed that there was no space in the original image from OP, it should be nano /etc/fstab not nano/etc/fstab