Open Dyadya-Sasha opened 2 years ago
I was having the same issue. I eventually got things working by using busybox for mkinitcpio instead of systemd. I actually did figure out how to resolve this error message ("Systemd is enabled, but there are no .initramfs files under /etc/systemd/network; exit"), but then I had other issues.
HOOKS=(base udev autodetect modconf block netconf dropbear keyboard keymap consolefont encryptssh lvm2 filesystems resume fsck)
The instructions in the Arch wiki say to put netconf
, dropbear
, and encryptssh
before filesystems
. I found that netconf
, dropbear
, and encryptssh
actually need to go before encrypt
. Otherwise, the encrypt
hook prompts for your disk password and waits, blocking netconf
, dropbear
, and encryptssh
from starting. Also, encryptssh
actually prompts for your disk password locally as well as over SSH, so encrypt
can be removed.
For what it's worth, I also added:
MODULES=(r8169)
Regarding how I resolved the error message: since I couldn't find any documentation about this anywhere, I looked into the source. mkinitcpio-netconf looks for files named *.initramfs
in /etc/systemd/network/
. For each matching file, mkinitcpio-netconf copies the file to /etc/systemd/network/
in the initramfs, but with the trailing .initramfs
removed. For example, if I have /etc/systemd/network/20-wired.network.initramfs
, mkinitcpio-netconf will copy this file to /etc/systemd/network/20-wired.network
in the initramfs.
However, when I did this (and eventually figured out that I needed to move netconf
, dropbear
, and encryptssh
before sd-encrypt
), systemd-networkd failed to start:
Hello everybody! I am trying to set up remote unlocking LUKS root partition (with dropbear) and faced an issue I cannot find the solution for.
What is done: 1) /boot is ordinary, / is encrypted 2)
HOOKS=(base systemd autodetect keyboard sd-vconsole modconf block netconf dropbear encryptssh sd-encrypt filesystems fsck)
3) ip=:::::ens33:dhcp in grub.cfg
4) while making
mkinitcpio -p linux
I got the following
therefore network doesnt work when it is time to unlock encrypted root partition, as I am told
[FAILED] Failed to start Network Configuration.
if I switch to udev, then process doesnt even go to the phase of asking the password and kicks me into rootfsCould anybody give me a hint what and why it does happen?
Thanks in advance.