What did i told you? Not to remove filesystems from the hooks line … either you still did that, or based on how you deal with the code, you did this
instead of this
You see? In your code you missed " at the end, so you probably did the same on /etc/mkinitcpio.conf file.
You will need a USB with the Live Installer and chroot into your installed system and fix it.
At this point i will make this public, so maybe someone else will help you out more.
Merged this because people that will help you out should know the context.
Ok I will try to figure it out then 
Yes, it is.
It would be much better to create your own thread for your own issue, btw.
two places to look at:
there is an “encrypt” HOOK in /etc/mkinitcio.conf
and
there is a setting in /etc/default/grub
dealing with encrypted root file systems -it is aptly named
So you actually did change it - no? 
Too complex now to quickly figure this out.
I will be back - in a few hours.
Is your first time posting here so nobody recommended you to do anything previously.
What is the exact system issue you had? Please see
In case you are @rogerR - please see Forum Rules - Manjaro
That is against the Forum Rules as mentioned above. Use the I forgot my password link and reset your password.
Hello,
please pardon that I broke the rules. I use a password manager which which I couldn’t access from the live USB. I’m not writing from my windows partition. I’ll change the password here to something simpler, and later will log in from the live USB into this account.
Shall I also delete the post that I made with the other account (“ghostroger”). This won’t happen again, I promise. 
BTW
When booting this time around I noticed that something changed in the screen where I decrypt the harddrive. Before trying the fix today it said “hd0, gpt9” and now it “hd1,gpt9”.
does not matter much to me, as long as I know that I’m talking to the same person
It is, however, easy to recover your password (or set a new one) via the way that @Yochanan mentioned.
Easy.
To address the issue:
we should start by getting a picture of the situation
boot from USB
open a terminal
issue:
lsblk -f
post the result
I think it is a fully encrypted system - but we’ll see whether that is actually so.
Okay,
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/miso/sfs/livefs
loop1
squash 4.0 0 100% /run/miso/sfs/mhwdfs
loop2
squash 4.0 0 100% /run/miso/sfs/desktopfs
loop3
squash 4.0 0 100% /run/miso/sfs/rootfs
sda iso966 Jolie MANJARO_GNOME_2137
2022-08-16-12-53-59-00 0 100% /run/miso/bootmnt
├─sda1
│ iso966 Jolie MANJARO_GNOME_2137
│ 2022-08-16-12-53-59-00
└─sda2
vfat FAT12 MISO_EFI
CA66-9EA7
nvme0n1
├─nvme0n1p1
│ vfat FAT32 ESP 1404-B4AC
├─nvme0n1p2
│
├─nvme0n1p3
│ BitLoc 2
├─nvme0n1p4
│ ntfs WINRETOOLS
│ 22B80C19B80BE9DD
├─nvme0n1p5
│ ntfs Image 3CC60E59C60E1434
├─nvme0n1p6
│ ntfs DELLSUPPORT
│ D230105A301047BD
├─nvme0n1p7
│ vfat FAT32 9D5A-92DF
├─nvme0n1p8
│ swap 1 97f9ff6f-27bf-448f-9544-8744a7ad79e7
├─nvme0n1p9
│ crypto 1 3ef5d5a5-7e9f-412e-b0fa-a9c8625930c0
└─nvme0n1p10
crypto 1 df0c6b01-8f49-466a-b8ee-c16ee3407d03
Meanwhile I learned a bit from these links:
I think, based upon your previous posts, this is the / (root) partition of your encrypted system
I do not know what the other one is:
Do you know?
It looks like …p10 is the document folder, including pictures, downloads etc.
(And p9 the system folders)
you probably mean - in “proper” linux terms:
this is your $HOME partition?
You set up a separate $HOME partition?
… it’s not really relevant to get the system booted … but would be good to know
Yes it is the $HOME partition. I don’t know exactly (anymore) why they’re seperate… but I set this up (somehow 
)
Maybe this (fdisk -l) also helps?
Disk /dev/nvme0n1: 238,47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: PM981 NVMe Samsung 256GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4EA88B3E-9780-4EC1-A689-4A6577662A83
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1026047 1024000 500M EFI System
/dev/nvme0n1p2 1026048 1288191 262144 128M Microsoft reserved
/dev/nvme0n1p3 1288192 351981567 350693376 167,2G Microsoft basic data
/dev/nvme0n1p4 474861568 476889087 2027520 990M Windows recovery environmen
/dev/nvme0n1p5 476889088 497860607 20971520 10G Windows recovery environmen
/dev/nvme0n1p6 497860608 500092927 2232320 1,1G Windows recovery environmen
/dev/nvme0n1p7 351981568 353030143 1048576 512M Microsoft basic data
/dev/nvme0n1p8 353030144 357224447 4194304 2G Linux swap
/dev/nvme0n1p9 357224448 408424447 51200000 24,4G Linux filesystem
/dev/nvme0n1p10 408424448 474861567 66437120 31,7G Linux filesystem
so:
(this is now to the start of how to chroot into that encrypted system)
boot from the USB again - or maybe you are still there …
and issue
sudo cryptsetup open /dev/nvme0n1p9 encryptedroot
(this should prompt you for the password to decrypt that partition - and open it)
also:
the “encryptedroot” is just a word I chose - you can use any word you like. It’s just a name … not important what it is, but some word needs to be there
and then run
lsblk -f
again
see what you get
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0 0 100% /run/miso/sfs/livefs
loop1
squash 4.0 0 100% /run/miso/sfs/mhwdfs
loop2
squash 4.0 0 100% /run/miso/sfs/desktopfs
loop3
squash 4.0 0 100% /run/miso/sfs/rootfs
sda iso966 Jolie MANJARO_GNOME_2137
2022-08-16-12-53-59-00 0 100% /run/miso/bootmnt
├─sda1
│ iso966 Jolie MANJARO_GNOME_2137
│ 2022-08-16-12-53-59-00
└─sda2
vfat FAT12 MISO_EFI
CA66-9EA7
nvme0n1
├─nvme0n1p1
│ vfat FAT32 ESP 1404-B4AC
├─nvme0n1p2
│
├─nvme0n1p3
│ BitLoc 2
├─nvme0n1p4
│ ntfs WINRETOOLS
│ 22B80C19B80BE9DD
├─nvme0n1p5
│ ntfs Image 3CC60E59C60E1434
├─nvme0n1p6
│ ntfs DELLSUPPORT
│ D230105A301047BD
├─nvme0n1p7
│ vfat FAT32 9D5A-92DF
├─nvme0n1p8
│ swap 1 97f9ff6f-27bf-448f-9544-8744a7ad79e7
├─nvme0n1p9
│ crypto 1 3ef5d5a5-7e9f-412e-b0fa-a9c8625930c0
│ └─encryptedroot
│ ext4 1.0 078e24b2-846f-4627-ba86-08ac5dcb55a5 6,9G 66% /run/media/manjaro/078e24b2-846f-4627-ba86-08ac5dcb55a5
└─nvme0n1p10
crypto 1 df0c6b01-8f49-466a-b8ee-c16ee3407d03
You can now mount what is referred to as “encryptedroot”
to somewhere - usually to /mnt
sudo mount /dev/mapper/encryptedroot /mnt
and then call “manjaro-chroot”
manjaro-chroot -a
to change root into your encrypted system - and perform whatever repair is needed
The prompt you see should change.
And you are now in your, now decrypted, systems file system
(sans the /home/user data - this is separate and not available as of now - but also not needed)
It would help, at this stage, if you had a terminal file manager installed.
… to move around, look around, and also more easily view and change contents of files
as is probably needed
sudo pacman -S mc
will install that for you
you open it by typing: mc and enter
more easy than to rely on only terminal commands - but that works just as well, of course
needs some getting used to - reminicent of the good old days … but works a treat
I get an error message when trying to manjaro-chroot -a:
rub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> ERROR: No Linux partitions detected!
try just:
manjaro-chroot /mnt /bin/bash
instead
which means:
chroot to whatever is mounted to /mnt and run the bash shell as a shell there
I could not look it up easily (but you could have)
because it is on the live media, but not on an already installed system.
manjaro-chroot -h
Thanks very much that work. I can hardly ask anymore of you.
Though I really don’t know how to fix the initial question:
mount:/new root: no filesystem type specified
[...] emergency shell
sh: can't access tty: job control turned off
Maybe someone else will have an answer to this.
Have a nice evening and thanks againg for your patience and help.