Hi Christian,

Apologies, I couldn't get back to you sooner since Friday.

> 1. get your help to recreate the issue - what more than having
multipath devices and rebooting do I need? Any special setup to force it
to be more active in the initramfs?

Not really special setup needed. Actually no multipath devices needed.

On a 17.04 guest with a single virtio scsi disk, apt-get upgrade'd
yesterday, I just install multipath-tools-boot to hit this problem.

It happens in 3 reboots in a row.



No multipath devices required:

        # ls -d /sys/block/sd*
        /sys/block/sda
        # 

Just install multipath-tools-boot and reboot.

I see this error in 3 reboots in a row.

        # apt-get install multipath-tools-boot

        # dpkg -s multipath-tools | grep ^Version
        Version: 0.6.4-3ubuntu2

        # reboot
        <...>
        Begin: Waiting for udev to settle (multipath) ... done.
        done.
        Begin: Will now check root file system ... fsck from util-linux 2.29
        [/sbin/fsck.ext4 (1) -- /dev/sda2] fsck.ext4 -a -C0 /dev/sda2
        /dev/sda2: clean, 251692/8388608 files, 5617803/33552128 blocks
        done.
        [    3.868178] EXT4-fs (sda2): mounted filesystem with ordered data 
mode. Opts: (null)
        done.
        Begin: Running /scripts/local-bottom ... Begin: Stopping multipathd ... 
cat: can't open '/var/run/multipathd.pid': No such file or directory
        Failure: inconsistent PIDs (pidof: '349', multipathd.pid: '')
        done.
        Begin: Running /scripts/init-bottom ... done.

        ...

        Welcome to Ubuntu Zesty Zapus (development branch)!

        [    4.656639] systemd[1]: Set hostname to <ubuntu>.
        [    5.300761] systemd[1]: Listening on udev Kernel Socket.
        [  OK  ] Listening on udev Kernel Socket.
        [    5.301826] systemd[1]: multipathd.socket: Failed to listen on 
sockets: Address already in use
        [    5.302126] systemd[1]: Failed to listen on multipathd control 
socket.
        [FAILED] Failed to listen on multipathd control socket.
        See 'systemctl status multipathd.socket' for details.
        ...
        [FAILED] Failed to start Device-Mapper Multipath Device Controller.
        See 'systemctl status multipathd.service' for details.

        # systemctl status multipathd.socket
        ● multipathd.socket - multipathd control socket
           Loaded: loaded (/lib/systemd/system/multipathd.socket; static; 
vendor preset:
           Active: failed (Result: resources)
           Listen: @/org/kernel/linux/storage/multipathd (Stream)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670811

Title:
  Multipath services fails to start on Ubuntu 17.04 on boot and kdump
  (initramfs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1670811/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to