On Mon, 27.04.15 11:47, aaron_wri...@selinc.com (aaron_wri...@selinc.com) wrote:
> I applied commit 628c89cc68ab96fce2de7ebba5933725d147aecc - core: rework > device state logic, but now I'm left with a random chance to boot or not. > > Some boots it comes up with "/var mounted" and lots of nice colored "[ OK > ]"s. > > Some boots it comes up with "Unit var.mount is bound to inactive unit > /dev/mapper/<name>. Stopping, too." and no colored "[ OK ]"s and about > half the logs; only the "systemd[1]" messages, and it just hangs at some > point; it never reaches the default target. > > I create /dev/mapper/<name> in initrd with cryptsetup, and then mount it > to /newroot/var before switching root to /newroot and running systemd. I > don't use systemd in initrd. Make sure to apply 496068a8288084ab3ecf8b179a8403ecff1a6be8 and f62009410a72f5a89bfb8fdd7e48d9d472a6887b. Also make sure you have LVM/DM compiled with proper udev support. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel