Reconnecting to iSCSI target: "Login request failed"

Marcus Büttemeyer 376 Reputation points
2021-01-11T13:18:04.257+00:00

I'm trying to migrate my Windows Backup from external hard disks to an iSCSI target. The idea was to have the NAS (target) power itself on right before the backup and then power off after a certain time. This basically works but after a couple of days the iSCSI initiator on Server 2019 / Win10 20H2 fails to reconnect to the target. The event log display an error ID 10 from iScsiPrt which states "Login request failed". If I reconnect the target manually it works.
Does anybody have any ideas what is happening here?

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,486 questions
Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,278 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Xiaowei He 9,876 Reputation points
    2021-01-12T06:41:58.013+00:00

    Hi,

    I troubleshot a similar issue before, the ISCSI target does not reconnect automatically after the server restarted, while manually reconnect works, however, after a period of time of troubleshooting, still not find out the cause of that case.

    As it needs to collect logs, such as process monitor log, network traffic log to do troubleshoot, and forum has limited to collect these logs, if you want to find the root cause, I would recommend you open a case with MS directly. If you just want to get some voice on this issue, then as a workaround, I would suggest you just manually reconnect it.

    Below is the link to open a case with MS:

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

    Thanks for your time!
    Best Regards,
    Anne

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Alex Bykovskyi 1,831 Reputation points
    2021-01-17T20:03:42.683+00:00

    Hi,

    As mentioned, you should check the logs to identify what's causing the issue. Check on both initiator (Windows Server) and target sides.
    As an alternative, you can automate the connection process and use PowerShell to connect to iSCSI target on a certain event. The following article might help:
    https://www.starwindsoftware.com/blog/dont-break-your-fingers-with-hundreds-of-clicks-automate-windows-iscsi-connections

    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