Comment # 4 on bug 921570 from Steffen Hau

These messages do net seem to be the cause. When I disable the multipathd
systemd unit and start it manually after a reboot, the messages are also shown:

M��r 10 17:16:34 testhost kernel: device-mapper: multipath: version 1.7.0 loaded
M��r 10 17:16:34 testhost kernel: device-mapper: multipath service-time: version
0.2.0 loaded
M��r 10 17:16:34 testhost kernel: device-mapper: table: 253:0: multipath: error
getting device
M��r 10 17:16:34 testhost kernel: device-mapper: ioctl: error adding target to
table
M��r 10 17:16:34 testhost kernel: device-mapper: table: 253:0: multipath: error
getting device
M��r 10 17:16:34 testhost kernel: device-mapper: ioctl: error adding target to
table

But the devices are avalable:
testhost:~ # multipath -ll
360050768018085377800000000000084 dm-0 IBM,2145
size=1000G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 1:0:6:0 sdd 8:48 active ready running
| `- 2:0:6:0 sdf 8:80 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
  |- 1:0:1:0 sdc 8:32 active ready running
  `- 2:0:0:0 sde 8:64 active ready running
testhost:~ # dmsetup ls --tree
360050768018085377800000000000084-part1 (253:1)
 ������360050768018085377800000000000084 (253:0)
    ������ (8:64)
    ������ (8:32)
    ������ (8:80)
    ������ (8:48)


I can see the device-mapper lines an all systems (also 13.1), were multipathd
is enabled, so they look harmless to me.