You are not logged in.
After a reboot, it's got stuck at:
:: running early hook [udev]
starting version 239I've tried the fallback kernel - same issue. I've also tried commenting out the `initrd /intel-ucode.img` without luck.
I booted to USB, mounted my FS, and was able to install the LTS kernel, which works:
:: running early hook [udev]
starting version 239
:: running hook [udev]
:: Triggering uevents...
:: running hook [encrypt]
Waiting 10 seconds for device ..
...Switching to sd-encrypt instead of encrypt gets me a little further.
[ OK ] Started Load Kernel Modules.
[ OK ] Reached target System Initialization.
[ OK ] Reached target Basic System.
[ *] A start job is running for dev-mapper-cryptroot.device (30s / 1min 30s)Here's my current HOOKS in mkinitcpio.conf after switching to sd-encrypt:
HOOKS="base systemd autodetect modconf block keyboard sd-encrypt filesystems fsck"My /boot/loader/entries/arch.conf looks like this:
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options ro luks.name=UUID=26cece29-fdb4-4c04-96e9-3747e31de6dd=cryptroot luks.options=timeout=10 root=/devAny ideas?
Offline
you should not have `ro` on the kernel command line.
what kernel is troublesome for you.
otherwise, start in debug mode https://wiki.archlinux.org/index.php/Ge … t_problems
and you should also inspect things if you get thrown out in the initramfs shell
Offline
you should not have `ro` on the kernel command line.
With the systemd hook in use and ro will systemd-fsck not be run once after switch root and fsck will not be called by anything else?
Edit:
misplaced end of quote
Last edited by loqs (2018-10-25 18:14:45)
Offline
The issue was this:
options ro luks.name=UUID=26cece29-fdb4-4c04-96e9-3747e31de6dd=cryptroot luks.options=timeout=10 root=/devI don't know how this has worked for the last 12+ months, but it should have been:
options ro luks.name=26cece29-fdb4-4c04-96e9-3747e31de6dd=cryptroot luks.options=timeout=10 root=/devOffline