/openswap_keymount: no filesystem type specified

[7a5c3641e1aa9f98d4df]

My device switched from AHCI to RAID ON and after switching it back it can no longer boot and I’m dropped into an emergency shell.

Boot logs:

mount: /openswap_keymount: no filesystem type specified. 
Device /dev/disk/by-uuid/luks-xxx1 does not exist or access denied. 
umount: can't unmount openswap_keymount: Invalid argument 'xxx1' not found 
mount: /new root: no filesystem type specified.
You are now being dropped into an emergency shell. 
sh: can't access tty: Job control turned off

lsblk

sh: Isblk: not found```

[7a5c3641e1aa9f98d4df]

lsblk -f and ixni --full don’t list the nvme drives on a live USB

[Nachlese]

Only the most necessary things are included in the initial ram disk.

Boot from USB (the installation medium) and investigate from there.
All the tools are there and the GUI too.

That invalid command line argument must have a reason - perhaps an edit that you did?

[MLXQt]

@7a5c3641e1aa9f98d4df
Hi,
try this:

Mount: /openswap_keymount: no filesystem type specified

Hello everyone, I’ve been running Manjaro with the XFCE flavour for over 3 years now. And I’ve been puzzled with this problem. I can’t seem to boot into my OS anymore. I’ve been running a dual boot where I’ve installed each OS on a different SSD. However, it seems if my NVME SSD isn’t being recognised anymore. Both of my drives are encrypted. The windows with Bitlocker and the Manjaro with LUKS. This is the error message I’m getting after selecting to boot into Manjaro from GRUB mount: /ope…

[Mirdarthos]

Hi @7a5c3641e1aa9f98d4df, and welcome!

While I’ve never seen this, I think you’d have to enter a chroot to see what’s up.

How to chroot

1. Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.

2. Write/copy/dd the ISO to a USB thumb drive.

3. When done, boot with the above mentioned USB thumb drive into the live environment.

4. Once booted, open a terminal and enter the following command to enter the chroot encironment:

manjaro-chroot -a

5. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.

From the chroot environment, please provide the output of the following:

cat /etc/fstab

---

Ano0ther option is that I’m completely wrong and, because of this

@7a5c3641e1aa9f98d4df

My device switched from AHCI to RAID ON

…you’ll have to reinstall.

But let’s hope I’m not.

Edit:

See @MLXQt’s answer first!

[7a5c3641e1aa9f98d4df]

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!