Arch Linux

flegma

Member

From: Romania

Registered: 2013-09-08

Posts: 2

Wrong hook order/missing hooks - encrypted /

I just installed arch on a USB flash drive and it refuses to boot properly, mainly because the encrypt hook is ran directly after the udev hook and before all others, thus resulting in no disks being created in /dev and an unbootable system.

[root@archiso /]# grep HOOKS /etc/mkinitcpio.conf
HOOKS="base udev autodetect modconf block keyboard encrypt filesystems fsck"
[root@archiso /]#

[root@archiso /]# lsinitcpio -a /boot/initramfs-linux.img
...
==> Hook run order:
  udev
  encrypt

...

Also, I don't understand why only two hooks are listed on the run order and not all of them

Edit: After trying to boot, waiting for 10 seconds for /dev/sdXX appears after which the system falls to the emergency shell. /proc/partitions is empty, there are no devices (sdXX) in /dev and also /dev/disk/* directories are all empty

Thanks!

Last edited by flegma (2017-06-03 12:54:54)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,425

Re: Wrong hook order/missing hooks - encrypted /

Does it work w/o the autodetect hook? Then it's just missing modules.

fsckd

Forum Fellow

Registered: 2009-06-15

Posts: 4,173

Re: Wrong hook order/missing hooks - encrypted /

The hook run order list from lsinitcpio seems fine. Are you using /dev/sdXX or UUID to tell the kernel which partition to decrypt? Share the kernel command line from your bootloader's config and your fstab.

---

aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: Wrong hook order/missing hooks - encrypted /

You're making assumptions about hooks that simply aren't true. Not all hooks have runtime components. In particular, hooks such as block and filesystems are strictly compile-time.

---

blog | ±github