Swap partition errors on startup luks (wrong fs type, bad option, bad superblock)

[anon89812132]

@MeowMeow

mount: /openswap_keymount: no filesystem specified

Have you tried forum search related to that?

/openswap_keymount: no filesystem type specified

Good news, I went back to step 1 and it turns out that the BIOS settings update did not do anything and it was still in RAID ON. After switching it again the live USB was able to detect the drives and I was able to boot normally. Thanks!

Mount: /openswap_keymount: no filesystem type specified

I was able to resolve the issue. Somehow my BIOS decided to change my SATA operation to RAID ON from AHCI. Due to this, the NVMe SSD wasn’t being read during load, which meant the path to the LUKS container wasn’t there. Props to this post for nudging me in that direction: LUKS encrypted drive is missing. “cryptsetup: lvm is not available” Hopefully this might help someone else encountering this issue in the future

Solution to access my encrypted Manjaro

You mount the decrypted partition, inside the encrypted container, on /mnt, but you generate a new /boot/grub/grub.cfg which is not inside the /mnt Plus you won’t get any different outcome unless you change the /etc/default/grub INSIDE /mnt and chroot into /mnt before you give the command to regenerate your grub config… Thus you need to in sequence: Open the encrypted container Mount the @ subvolume inside the container at /mnt chroot into /mnt Change /etc/default/grub from within…

None of those helped?