Yes, I've found your bug reports and thread on the mailing lists about the issue you have been having. Very similar but unfortunately, different as you've noticed. Here is the output of the relevant services:
[root@some-server ~]# systemctl status iscsi iscsid remote-fs.target remote-fs-pre.target iscsi.service - Login and scanning of iSCSI devices Loaded: loaded (/usr/lib/systemd/system/iscsi.service; enabled) Active: active (exited) since Tue 2014-12-09 09:37:01 EST; 1 weeks 2 days ago Docs: man:iscsid(8) man:iscsiadm(8) Main PID: 881 (code=exited, status=0/SUCCESS) Dec 09 09:37:00 some-server systemd[1]: Starting Login and scanning of iSCSI devices... Dec 09 09:37:00 some-server iscsi-mark-root-nodes[869]: iscsiadm: No active sessions. Dec 09 09:37:01 some-server iscsiadm[881]: Logging in to [iface: default, target: some-target, portal: 10.174.1.38,3260] (multiple) Dec 09 09:37:01 some-server iscsiadm[881]: Login to [iface: default, target: some-target, portal: 10.174.1.38,3260] successful. Dec 09 09:37:01 some-server systemd[1]: Started Login and scanning of iSCSI devices. iscsid.service - Open-iSCSI Loaded: loaded (/usr/lib/systemd/system/iscsid.service; enabled) Active: active (running) since Tue 2014-12-09 09:37:00 EST; 1 weeks 2 days ago Docs: man:iscsid(8) man:iscsiadm(8) Main PID: 857 (iscsid) CGroup: /system.slice/iscsid.service +-855 /usr/sbin/iscsid +-857 /usr/sbin/iscsid Dec 09 09:37:00 some-server systemd[1]: Starting Open-iSCSI... Dec 09 09:37:00 some-server iscsid[850]: iSCSI logger with pid=855 started! Dec 09 09:37:00 some-server systemd[1]: Failed to read PID from file /var/run/iscsid.pid: Invalid argument Dec 09 09:37:00 some-server systemd[1]: Started Open-iSCSI. Dec 09 09:37:01 some-server iscsid[855]: iSCSI daemon with pid=857 started! Dec 09 09:37:01 some-server iscsid[855]: Connection1:0 to [target: some-target, portal: 10.174.1.38,3260] through [ifac...ational now remote-fs.target - Remote File Systems Loaded: loaded (/usr/lib/systemd/system/remote-fs.target; enabled) Active: active since Tue 2014-12-09 09:37:03 EST; 1 weeks 2 days ago Docs: man:systemd.special(7) Dec 09 09:37:03 some-server systemd[1]: Starting Remote File Systems. Dec 09 09:37:03 some-server systemd[1]: Reached target Remote File Systems. remote-fs-pre.target - Remote File Systems (Pre) Loaded: loaded (/usr/lib/systemd/system/remote-fs-pre.target; static) Active: inactive (dead) Docs: man:systemd.special(7) I also noticed "remote-fs-pre.target" is not active and guessed that it might be an issue but haven't been able to figure out what needs to be changed to correct it from not being active. local-fs-pre.target is active and I would think these two would be have the same way for the most part. I just updated the iscsi.service unit file to include "Wants=remote-fs-pre.target" and it seems to have solved the issue! I'm not sure how I didn't find this myself. I thought I tried just about everything. Also, tried this same thing on RHEL7.1 beta and it seems to be fixed there out of the box (no changes necessary). Just looked at the iscsi.service file on RHEL7.1 and it has "Wants=remote-fs-pre.target". I guess, according to the changelog, https://bugzilla.redhat.com/show_bug.cgi?id=1161417 may have fixed this issue in 6.2.0.873-22? I looked through the patch you uploaded and didn't see this particular change and was for the fstab issue, which again seems pretty different than this. Nothing else in the changelog for iscsi-initiator-utils on RHEL7.1 seems to indicate where this fix might have come from. Thanks for your help. Will this fix get applied to RHEL7.0 eventually? Will that happen after 7.1? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.