I was unable to post this to
https://labs.parabola.nu/projects/packages/issues due to "spam filter", so
sending this to mailing list :)

* architecture: x86_64
* is nonsystemd enabled: yes
* is nonprism enabled: yes

* steps to reproduce:
  1) Have a working parabola system with full disk encryption enabled (worked
  and I was able to decrypt it at boot time perfectly fine for several years).
  Kernel parameters (UUID for cryptdevice and device mapper name for root
  partition) are obviously correct since it worked fine for a long time. I
  double-checked those just in case though. For decryption, hooks netconf,
  dropbear and encryptssh are added to mkinitcpio.conf. The issue can be
  reproduced w/o netconf and dropbear and with encrypt instead of encryptssh.

  2) $ pacman -Syu # updates the system, udev should be v257 now

  3) reboot

* expected result:
  Prompt for root device encryption password

* actual result:
  Error messages regarding network device not found (this looks related to
  netconf hook). Then, "Waiting 10 seconds for <cryptdevice UUID>".
  Then, "Waiting 10 seconds for /dev/mapper/cryptroot" for several times. If
  changing device mapper name to decrypted root UUID in kernel cmdline - the
  same issue appears. Obviously, I should be prompted for root device password,
  but I'm not. After several unsuccessful attempts of waiting for decrypted
  root, I'm given a recovery console. **And even the keyboard is not working
  there**. I was able to decrypt the system at boot after downgrading the udev
  package to the previous v255 version (by booting to live-usb and chroot'ing)
  So, it looks like that udev is somehow broken after update to v257.
  Also, note that I have an almost identical setup on another machine with
  artix+runit+full disk encryption, and it works fine with udev v257

Best regards, Daniil
_______________________________________________
Dev mailing list
[email protected]
https://lists.parabola.nu/mailman/listinfo/dev

Reply via email to