Windows Server 2016 iSCSI initator issues with connectivty to a TrueNAS 12 target

Sameer Sheikh 191 Reputation points
2021-09-19T07:36:48.647+00:00

Hello Everyone,

I'm having an issue with my Windows Server 2016 initiator connecting to my TrueNAS 12 target.

The server connects randomly, and then loses connection when the TrueNAS server reboots. I get the following errors:

iSCSIprt Event ID 1

iSCSIprt Event ID 70

MSiSCSI Event ID 113

iSCSITarget-Service Event ID 10 (I think this may be the core issue)

I've tried rebooting the Win2k16 server, restarting all iSCSI services, deleting all target records from the iSCSI initiator properties, and re-adding them.

Oddly, I have a Win2k12r2 that's acting as an initator as well, which has no issues connecting to the TrueNAS target, and re-establishing connectivity when the TrueNAS target reboots.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,416 questions
Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
640 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sameer Sheikh 191 Reputation points
    2021-09-21T03:24:28.633+00:00

    The issue has been resolved. I'm not sure if this is the case, but I would surmise that you cannot have multiple initiators all communicating with the same port. When I allowed the Win2k16 initiator to communicate on another port, the issue went away.

    Thank you for the links though. I'm going to give them a look, and if they prove to be a better solution, I'll give them a try.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Sameer Sheikh 191 Reputation points
    2021-09-19T08:18:48.82+00:00

    I'm hoping I resolved the issue. I added another port on the target. When I tried to connect the Win2k16 initiator on that port, it seemed to connect right away. I've had very intermittent connectivity between the Win2k16 initiator and the TrueNAS target, so let's see what happens.

    0 comments No comments

  2. Alex Bykovskyi 1,831 Reputation points
    2021-09-19T17:18:01.863+00:00

    Hey,

    Check the information discussed in the following thread. Might be helpful:
    https://learn.microsoft.com/en-us/answers/questions/133982/iscsiprt-event-id-10-login-request-failed.html

    In addition, you can try using StarWind SAN&NAS as an alternative to create an iSCSI storage on top of ZFS-based pools and share it via iSCSI to Windows hosts:
    https://www.starwindsoftware.com/san-and-nas

    SAN&NAS uses the same iSCSI Target as StarWind VSAN, which is certified to use with Windows Server 2012R, 2016, 2019 and 2022.
    https://www.windowsservercatalog.com/item.aspx?idItem=4ad61112-add2-c3f2-64ab-f9a7473bfa25&bCatID=1283

    Cheers,
    Alex Bykovskyi
    StarWind Software
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose

    0 comments No comments