On Mon, Sep 24, 2012 at 11:54:17AM +0200, Lennart Poettering wrote: > On Sun, 23.09.12 18:20, Ali Lown ([email protected]) wrote: > > > > > I responded too early, mdadm has caused its own set of problems: > > > > - During the boot process, the mdXpX.device don't get marked as active > > automatically causing X.mount based on those devices to fail. > > Once I get to the emergency shell, simply calling 'systemctl > > daemon-reload' reloads the mdXpX.device items which are now marked as > > active (why?). > > Hmm, might be related to 44b5651f19b60a84dbfdbb0ea13196b784080c8b? Are > you running a version with this, or without? OP said that he tested with f6c2e2 and v189. Both are later.
Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
