StarWind Software

Hello,

We have a Management Console setup on a 2022 Server machine and have a number of Tape Librarys and drives set up via Fibre and SAS that we can connect via iSCSI with no issues on some Hyper V VM's with Server 2022/2019/2016 and have no problems. As we are testing our software on Server 2025 we needed to connect to our tape librarys though iSCSI the way we always do with a target and connect. We have no issues connecting to the actual Librarys and Tape drives via iSCSI and can see them on the client on our software and also in the device manager, the issue comes when we try to start our service and get some of the following errors in our log:

Unexpected check condition for drive 0 (SCSI tape HP Ultrium 6-SCSI HU1315VDMU). Command LOG SENSE returned sense key 0x06 code 0x29 qualifier 0x07 (I_T nexus loss occurred (the I_T nexus is a relationship between an initiator port and a target port)).

On the Windows System logs at the same time we get the following errors also :
iSCSI discovery via SendTargets failed with error code 0xefff0003 to target portal *10.1.19.13 0003260 ROOT\ISCSIPRT\0000_0 .

Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.

Error occurred when processing iSCSI logon request. The request was not retried. Error status is given in the dump data.


None of this happens on any other windows operating systems, we have tried the same hardware and process on server 2022 with the same starwind management console as the server and have no issues.

The version of starwind management console we are using is 8.0.19551.0


Any help with why we might be getting these errors currently / anyone else with similar issues would be good to know. Any additional information needed please let me know

Thanks

If you can manage StarWind VTL through the GUI, then you might have a TRIAL or commercial key. In both cases, you can get support (for commercial only if you have an active support contract, though).
Please also let me know what drivers you have for the HPE Tape driver
Could you please pull the logs with the StarWind Log collector https://knowledgebase.starwindsoftware. ... collector/? Share them via Google Drive or any other convenient tool alongside the connectivity scheme that showcases how the hosts are connected and what backup software you use.

We have always used the free version so i dont believe we have the posibility to get full support but wanted to see if it was a known 2025 issue or if something we were doing.

For the tape driver:
IBM Corporation 7.0.1.5 03/12/2024

I will also put we have tried this on three different LTO libraries so i would doubt it would be a driver issue as all have seen the same types of errors.

Log below:
https://drive.google.com/file/d/1uv_mw0 ... sp=sharing

For the layout - this is a pretty basic overview of what we have setup, not sure if its the exact information you are looking for but gives an overall idea
https://drive.google.com/file/d/19rjks_ ... sp=sharing

The backup software we are using is Xendata

Thanks for your update! Can you please install the HPE drivers https://www.starwindsoftware.com/resour ... ended%20to ?

yaroslav (staff) wrote: ↑

Tue May 13, 2025 12:26 pm

Thanks for your update! Can you please install the HPE drivers https://www.starwindsoftware.com/resour ... ended%20to ?

Hi Sorry i got mixed up with my event errors and sent the one that was when the other library was attached, the current library plugged in shows this error in our XenData Event Log

Unexpected check condition for drive 1 (SCSI tape IBM ULTRIUM-HH9 11CCB1F05B). Command LOG SENSE returned sense key 0x06 code 0x29 qualifier 0x07 (I_T nexus loss occurred (the I_T nexus is a relationship between an initiator port and a target port)).

This is a qualstar Q40 library and that is the IBM tape drive driver that i referenced above (IBM Corporation 7.0.1.5 03/12/2024)

Sorry for the confusion

No worries.
StarWind VTL requires the specific HPE driver to operate. Could you please try installing it?

yaroslav (staff) wrote: ↑

Tue May 13, 2025 1:39 pm

No worries.
StarWind VTL requires the specific HPE driver to operate. Could you please try installing it?

I believe we are slightly confused, this is probably down to my explanation sorry. We are using Physical librarys , these are not Virtual, our XenData software uses the correct drivers to talk to these, usually we have no issues and its is only moving to 2025 has shown these errors. The part of starwind we are using is the StarWind Tape Redirector part of the product from looking through the website,

Hopefully this clears up any confusion, Thanks

I had discussed your request internally. The tape redirector was not tested with 2025. I will log an internal request and see what can be done about it.

Thats good to hear, at least shows their might be a problem with it on 2025 and was unlikely it was something we had done differently our side and configured something incorrectly. If you could please keep me updated if they do or do not find anything whenever they get around to testing it that would be great, for now will stick with Server 2022. Thanks

Hi,

Sure, I will keep you posted.

Sorry for the delay. My colleagues have finally run the tests for WS 2025 and DPM.
Could you please let me know what type of service/software you use? So we could check it as well.