Are you sure your system is up to date? You shouldn't have to enable bootlogd to get this log, it should be created for you by plymouth via /etc/init/plymouth-log.conf.
Is /etc/init/cryptdisks-udev.conf present on your system? There's no mention in the log of this job being started by upstart, but it should have been.
Are you sure your system is up to date? You shouldn't have to enable bootlogd to get this log, it should be created for you by plymouth via /etc/init/ plymouth- log.conf.
Is /etc/init/ cryptdisks- udev.conf present on your system? There's no mention in the log of this job being started by upstart, but it should have been.