Hi everyone, * Chris Hofstaedtler <z...@debian.org> [210114 19:20]: > * Heinrich Schuchardt <xypron.g...@gmx.de> [210114 18:52]: > > >> iscsistart: version 2.1.3 > > >> iscsistart: Logging into iqn.2000-01.de.xypron:disk1 > > >> 192.168.0.1:3260,1 > > >> iscsistart: initiator reported error (32 - target likely not > > >> connected) > > >> > > >> I downgraded to open-iscsi and libopeniscsiusr to version 2.1.2-2 and > > >> reinstalled the kernel package. > > Could you try rebuilding 2.1.3-1 with this upstream patch reverted? > https://github.com/open-iscsi/open-iscsi/commit/9258c8eae046d98511d92912983778ca57ba201f > > That seems to have changed timeout behaviour, so maybe that "fixed" > something broken that nevertheless was needed on your system.
Heinrich: here is a proposed source package: https://people.debian.org/~zeha/open-iscsi/ (incl. amd64 binaries, but they are useless to you) I gave this some more tries in my test VM, and from what I can tell there is a race between the iscsi login and the NIC becoming ready. (In my test VM, the NIC is immediately ready - but I can "unplug" it and "plug" it back in in just the right moment to simulate a slow link setup.) The 2.1.2 code gave you just a bit more time (and maybe one retry) to win this race. The 2.1.3 code just flat fails when the NIC is not ready, at iscsi login time. Maybe the old variant is good enough on Heinrich's system. But it looks like this would break on an "enterprise network", where the Ethernet link would take many seconds to come online... Not sure if we can claim "iscsi root is supposed to work" where it would usually be deployed. But I don't know about 2.0.x or earlier. Chris
