Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • So were you prompted for password or anything to unlock the drive before the errors was shown? Sounds like your bootloader config has somehow gone bad and doesn't pass anything as the "crypt device" to the early init? Commented Aug 5 at 8:32
  • 1
    Btw, anyone on Arch (or even in general) should keep (regularly updated) installation medium with them, which can be used for investigation / rescue purpose on broken system. Commented Aug 5 at 8:38
  • @TomYan : thank you! how would i do create an installation medium? as a normal archlinux user i've never stumbled over this subject -- untul now d-: Commented Aug 5 at 8:51
  • @TomYan : no, i'm thrown out of the booting process before entering the decription password. Commented Aug 5 at 8:52
  • 1
    Make sure that you are checking the right location (your installation mounted on e.g. /mnt instead of the live environment), especially if you haven't chrooted yet. Also make sure you have everything mounted in proper order (the root filesystem first, and /boot and other filesystems, if any). And if it's really wrong, arch-chroot and have it fixed, and run mkinitcpio -P to regen the initramfs. (Again, make sure you have /boot mounted beforehand if it has a dedicated filesystem. Be aware of the "location difference / change" of things before and after chroot.) Commented Aug 5 at 13:51