Hi, I debugged a similar problem just yesterday. The problem was that systemd correctly unlocked the encrypted partition but did not activate the logical volumes on it and thus local-fs.target never completed.
Are you using LVM? If so, can you try the following please? Add /lib/systemd/system/storage-after-cryptsetup.service with the following contents: [Unit] Description=Restart storage after cryptsetup DefaultDependencies=no After=cryptsetup.target Wants=cryptsetup.target Before=local-fs.target Before=shutdown.target [Service] RemainAfterExit=true Type=oneshot TimeoutSec=0 ExecStart=/bin/systemctl restart lvm2.service Then, create the following symlink: ln -s /lib/systemd/system/storage-after-cryptsetup.service /lib/systemd/system/local-fs.target.wants/storage-after-cryptsetup.service And try to boot your system with systemd again. Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
