#822247 open-iscsi: multipath volumes aren't activated at boot

Package:
open-iscsi
Source:
open-iscsi
Description:
iSCSI initiator tools
Submitter:
Christian Seiler
Date:
2026-08-01 13:49:01 UTC
Severity:
normal
Tags:
#822247#5
Date:
2016-04-22 13:17:18 UTC
From:
To:
Hi there,

FYI: I'm co-maintainer of open-iscsi in Debian, but not
multipath-tools. CC'ing the bugtracker, assigning to open-iscsi for
now, will reassign to multipath-tools later if necessary.

Am 2016-04-22 14:45, schrieb Cédric Bassaget:

Gah. During the freeze of Jessie I encountered some bugs related to the
boot process and I thought we had fixed them all before Jessie was
released. Obviously not... :-(

For current versions (starting with Jessie) of multipath-tools, this
is correct, as the daemon is supposed to be started and then pick up
all of the devices as they appear dynamically.

OTOH, what you're seeing in dmesg is just the modules that are loaded,
which might be due to /etc/modules, /etc/modprobe.d or similar, so
they don't necessarily indicate which is started before.

multipath-tools is still late-boot? That seems wrong to me. May be part
of the problem you're seeing.

Could you give me the output of the following on your system?

systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires
multipath-tools.service
systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires
open-iscsi.service

Also, what does the following command tell you? (After booting, when
the problem appears, but before restarting multipath to fix it.)

journalctl -u open-iscsi.service -u multipath-tools.service

Well, there's probably still some bug in the integration between
open-iscsi and multipath-tools. The output of the commands I requested
will help me narrow down the problem, which will then hopefully give
me enough information to tell you how to fix it on your local system,
and hopefully this can be fixed in 8.5.

Regards,
Christian

#822247#14
Date:
2016-04-22 14:25:32 UTC
From:
To:
Hello,

(CC'ing the bug report I created, dropping debian-user in reply-to.)

Am 2016-04-22 16:10, schrieb BASSAGET Cédric:

Maybe that's the issue? Could you recreate the LVM stuff? That should
also be supported, so maybe this only occurs if LVM is used on top.

But even if it appears to be fixed, could you still copy the output
of the systemctl and journalctl commands I asked for?

systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires
multipath-tools.service
systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires
open-iscsi.service
journalctl -u open-iscsi.service -u multipath-tools.service

Regards,
Christian

#822247#19
Date:
2016-04-22 14:46:48 UTC
From:
To:
Seems that recreating the pv / vg on the multipath device reproduces the pb
:

root@virtm5:~# systemctl show -p
Before,After,WantedBy,Wants,RequiredBy,Requires multipath-tools.service
Requires=basic.target
Wants=system.slice
RequiredBy=
WantedBy=graphical.target multi-user.target
Before=multi-user.target graphical.target shutdown.target
After=systemd-udevd.service local-fs.target remote-fs.target
systemd-journald-dev-log.socket systemd-journald.socket basic.target syst

root@virtm5:~# systemctl show -p
Before,After,WantedBy,Wants,RequiredBy,Requires open-iscsi.service
Requires=
Wants=network-online.target remote-fs-pre.target system.slice
RequiredBy=
WantedBy=sysinit.target
Before=sysinit.target shutdown.target remote-fs-pre.target
multipath-tools.service pve-manager.service
After=network-online.target local-fs.target mountnfs-bootclean.service
systemd-journald.socket system.slice


root@virtm5:~# journalctl -u open-iscsi.service -u multipath-tools.service
-- Logs begin at Fri 2016-04-22 16:44:04 CEST, end at Fri 2016-04-22
16:46:12 CEST. --
Apr 22 16:44:07 virtm5 iscsid[1309]: iSCSI logger with pid=1312 started!
Apr 22 16:44:07 virtm5 open-iscsi[1278]: Starting iSCSI initiator service:
iscsid.
Apr 22 16:44:07 virtm5 open-iscsi[1278]: Setting up iSCSI targets:
Apr 22 16:44:08 virtm5 iscsid[1312]: iSCSI daemon with pid=1313 started!
Apr 22 16:44:09 virtm5 iscsid[1312]: Login authentication failed with
target
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5
Apr 22 16:44:09 virtm5 iscsid[1312]: Login authentication failed with
target
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Logging in to [iface: eth3,
target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] (multiple)
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Logging in to [iface: eth2,
target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] (multiple)
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Login to [iface: eth3, target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] successful.
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Login to [iface: eth2, target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] successful.
Apr 22 16:44:10 virtm5 open-iscsi[1278]: .
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Mounting network filesystems:.
Apr 22 16:44:10 virtm5 open-iscsi[1278]: Enabling network swap devices:.
Apr 22 16:44:10 virtm5 iscsid[1312]: Connection1:0 to [target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] through [iface: eth3] is operational now
Apr 22 16:44:10 virtm5 iscsid[1312]: Connection2:0 to [target:
iqn.2001-05.com.equallogic:4-52aed6-ef76d5a6f-4926f953a505715d-vms-virt5,
portal: 192.168.0.200,3260] through [iface: eth2] is operational now
Apr 22 16:44:10 virtm5 multipath-tools[1526]: Starting multipath daemon:
multipathd.

Regards,
Cédric

2016-04-22 16:25 GMT+02:00 Christian Seiler <christian@iwakd.de>:

#822247#24
Date:
2026-08-01 13:47:56 UTC
From:
To:
multipath-tools got a lot better since jessie, and I hope this class
of problems got fixed with it.