It sounds like an initramfs screw up. There are no other reports and this ticket is severely lacking in detail:

- what kind of initramfs (mkinitcpio, dracut, booster)?
- how is the initramfs configured, what hooks, etc?
- root volume details/setup/luks?
- bootloader used?
- hardware details, bios/uefi, etc, etc?

For booting issues like this, it is recommended to visit the support channels (forum/IRC/mailing lists/Reddit/etc) as your first port of call to seek help in debugging. If an Arch packaging bug is identified, *then* file a bug report here with as much detail as possible.

1. mkinitcpio 35.2-1
2. ==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-zen1-1-zen'
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [sd-vconsole]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-zen1-1-zen'
-> Running build hook: [base]
-> Running build hook: [systemd]
-> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [sd-vconsole]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen-fallback.img'
==> Image generation successful

3. # /dev/nvme1n1p2
UUID=a931209a-b0cd-4978-ab65-dc2edc4d47aa / ext4 rw,relatime 0 1

# /dev/nvme1n1p1
UUID=1525-35D1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2

LABEL=OTHER /mnt/OTHER auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=othernvme /mnt/othernvme auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=GAMEZ /mnt/GAMEZ auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=123 /mnt/123 auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=otherinternalhdd /mnt/otherinternalhdd auto nosuid,nodev,nofail,x-gvfs-show 0 0

4. systemd bootctl

5. amd ryzen 5 5700x, rx 6700xt, samsung 1tb ssd boot drive, uefi security disabled

Thanks for the additional info. Unfortunately it's still not enough to determine what's wrong. I'm trying to understand why device-mapper and/or lvm2 matter here. Do you have a dm-crypt vol and/or are you using LVM? Please post (as an attachment) the output of

# lsblk -fp

Please can you also do the following:

- update again to the latest device-mapper and lvm2 pkgs
- immediately afterwards, rebuild your initramfs (just for good measure e.g. sudo mkinitcpio -p linux-zen)
- post the output of: lsinitcpio -c /boot/initramfs-linux-zen.img | sed 's/#.*$//;/^$/d'
- also post the output of: lsinitcpio -a /boot/initramfs-linux-zen.img
- then reboot to confirm it still fails.

Additionally, what kernel parameters are you passing to the kernel via the bootloader?

1. as far as i know im not using lvm, i used archinstall and formatted my root device as 1 ext4 volume and mounted it to /
2. I loose control of my keyboard after it reboots so i cant type anything into the emergency prompt. I have to reboot into fallback mode to get anything

Ok, so something definitely went wrong during initramfs creation. If/when this happens again, please use the support channels as indicated...as reporting non-bugs here is super unproductive.