Page MenuHomeSolus

multipathd.service fails to start at boot up
Closed, ResolvedPublic


Checking "systemctl list-units" I noticed that "multipathd.service" had failed to load. Searching for this issue I found several bug reports (other Linux OSes), and this in particular refering to the same issue for Solus Budgie, which hasn't been submitted in Phabricator as suggested, so I thought that should be a good idea.

The output of "systemctl status multipathd.service" is

● multipathd.service
   Loaded: not-found (Reason: No such file or directory)
   Active: failed (Result: exit-code) since Tue 2017-08-01 10:39:02 -04; 3h 11min ago
   Main PID: 195 (code=exited, status=1/FAILURE)

The output of "sudo journalctl -u multipathd.service" is something like this,

-- Reboot --
Jul 26 22:53:27 solus multipathd[192]: Jul 27 02:53:27 | Checker 'directio' not found in /lib64/multipath
Jul 26 22:53:27 solus multipathd[192]: Jul 27 02:53:27 | failed to initialize checkers
-- Reboot --
Jul 27 12:57:17 solus multipathd[191]: Jul 27 16:57:17 | Checker 'directio' not found in /lib64/multipath
Jul 27 12:57:17 solus multipathd[191]: Jul 27 16:57:17 | failed to initialize checkers

My version is Solus Budgie "shannon".

I hope it helps.

Event Timeline

rodrum created this task.Aug 1 2017, 6:01 PM
elgrande71 added a subscriber: elgrande71.EditedAug 16 2017, 9:37 AM

All Solus versions and flavours ( Budgie, GNOME and MATE ) are affected : look at this forum subject

To fix it, we have to install multipath-tools ( sudo eopkg it multipath-tools ) and to add the following line to the /etc/multipath.conf file :

multipath_dir "/usr/lib64/multipath"

Relaunch the multipathd service with :

sudo systemctl start multipathd.service

ikey changed the task status from Open to In Progress.Aug 16 2017, 3:35 PM
ikey claimed this task.
ikey triaged this task as Unbreak Now! priority.

So I've fixed multipathd itself which helps when directly starting it. However we actually ship multipath-tools as part of the dracut initrd, which in turn
is built when the kernel is. The systemd unit comes from very early boot. As such I've also patched (and updated) dracut to support the new stateless
location of the config file, which is vendor-fixed/sane. Next step is to issue kernel rebuilds so that the new initrd is in effect and would solve this issue
for all users.

Thank you for theses explanations .

Thanks for the fix :D

ikey closed this task as Resolved.Aug 17 2017, 11:05 PM

Oh right, yeah, this is fixed now. xD

● ironhide
    State: running
     Jobs: 0 queued
   Failed: 0 units