Comment 4 for bug 1431107

Revision history for this message
Martin Pitt (pitti) wrote : Re: ordering cycles with early boot images on lvm2.service

Ah, thanks for the journal. That shows that early boot is completely messed up due to dependency cycles. This also affected systemd-tmpfiles-setup.service:

Mar 12 05:56:32 mamarley-laptop systemd[1]: Found ordering cycle on basic.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on sysinit.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on local-fs.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on lvm2.service/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on basic.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with basic.target/start

But the shortest one is

Mar 12 05:56:32 mamarley-laptop systemd[1]: Found ordering cycle on basic.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on sysinit.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on local-fs.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on lvm2.service/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Found dependency on basic.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Breaking ordering cycle by deleting job local-fs.target/start
Mar 12 05:56:32 mamarley-laptop systemd[1]: Job local-fs.target/start deleted to break ordering cycle starting with basic.target/start

Out of that I blame lvm2.service. That's shipped by default, but for some reason on your system it causes trouble. Can you please give me the output of

  systemctl show --no-pager -p Requires,Wants,Before,After lvm2

?