Hello,
There could be a race condition between:
If I read correctly, the iscsid.service from the initiator (client) took six seconds to connect to the iscsi target (server).Q2: What is the status for open-iscsi.service and iscsid.service when mount fails after boot ?
Answer: sudo journalctl -u iscsid.service --since todayCode:
Dec 09 00:01:45 PC1 iscsid[874]: connection-1:0 cannot make a connection to 192.168.x.x:3260 (-1,101) << Tries every 03 seconds until 00:02:42Dec 09 00:02:42 PC1 iscsid[874]: connection-1:0 cannot make a connection to 192.168.x.x:3260 (-1,101)Dec 09 00:02:45 PC1 iscsid[874]: connection-1:0 cannot make a connection to 192.168.x.x:3260 (-1,101)Dec 09 00:02:48 PC1 iscsid[874]: connection-1:0 cannot make a connection to 192.168.x.x:3260 (-1,101)Dec 09 00:02:51 PC1 iscsid[873]: Connection1:0 to [target: iqn.2004-04.com.ENDPOINT, portal: 192.168.x.x,3260] through [iface: default] is operational now
There could be a race condition between:
- the service that make the iscsi disk available as device in the client through the iscsi initiator
- the service that mounts the partitions of the iscsi device in /etc/fstab
Statistics: Posted by Aki — 2024-12-11 15:07