Playing with this more, I think I see what you mean now. Indeed there appear to be bugs.
Martin, Could you please take a look at all the systemd units and init scripts, and how they intervene with each other? * /etc/init.d/multipath-tools-boot - this one works fine * /etc/init.d/multipath-tools - this one is enabled by default, and starts up without loading dm-multipath first * /lib/systemd/system/multipathd.service - a trap, that is easy to shoot oneself in the foot. - has alias Alias=multipath-tools.service but doesn't appear to properly be enabled in maintainer scripts, and doesn't seem to be masking multipath-tools-boot initscript at all. - does not appear to be operational properly. - references non-existant units - deamon fails to create socket... yet unit declares that socket activation is to be used. Could you please dig further into these units and check what needs fixing? ** Changed in: multipath-tools (Ubuntu) Status: New => Confirmed ** No longer affects: ubuntu-z-systems ** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: multipath-tools (Ubuntu) Importance: Undecided => High ** Also affects: multipath-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: multipath-tools (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583563 Title: System will not start with multipathd enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1583563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs