Hi,
this is not an error, just a warning that the optional INQUIRY VPD page 0x86 is not supported by the device.

As I've already said, the problem is that the Linux initiator drops iSCSI sessions because of too short timeout setting somewhere in the Linux iSCSI or SCSI data path.

Hi,

It's not a StarWind's issue, from the logs we can see that the Linux initiator uses too short timeouts.

Please ask your question about the Linux iSCSI timeout settings at a Linux forum.

Hi, According the logs the iSCSI pings could lead to the problem. So please try to turn off iSCSI pings by setting: node.conn[0].timeo.noop_out_interval = 0 node.conn[0].timeo.noop_out_timeout = 0 node.session.timeo.replacement_timeout = 120 Also it's better to use separate targets for the tape and ...

sidecar wrote:Thanks but the credit goes to my boss boxcar for being the first. I found and changed that setting to 360 - rebooted - request to mount a tape fails just as fast. Please let me know if you need the latest log or any other information.

Yes, I'd like to look at the StarWind log and the iscsid.conf.

Hi, sidecar! It seems you are the first person at the forum who using the Starwind Tape Redirector with Linux clients. But according to http://www.open-iscsi.org/docs/README the node.session.timeo.replacement_timeout parameter of iscsid.conf is the one to be tuned. Please look at the parameter at is...

The target emulates native 4K drives for 8T and 16T.

But MS supports native 4K drives only since WIndows 7 SP1.

If you need to use the target with Vista/Server 2008 - try to find a way to switch the target to emulate 512e drives.

Thanks!
What is the Windows version of the initiator host?

If the MS initiator works OK, why do you need to use StarPort?

The target seems to have some issues in the iSCSI/SCSI protocols' implementations.
If the MS initiator does not work with it - it's because of the target which should be fixed.

Thank you! From the log file I could see that the initiator completed a Descovery session with success. Then it established a Normal session, but did not send any SCSI requests to the target, only periodical iSCSI pings. It's a strange behavior of the initiator. Does the MS iSCSI initiator work well...

Hi Felipe,

could you send us Wireshark dumps of the network packets for cases when the iSCSI initiators try to mount the target?

This should shed some light on the problem...

k1_ wrote:It was working before with the old version of TapeRedirector with the same setup.

Any suggestions?

If it worked well for you with the older TapeRedirector, the first idea is to try it now to be sure it's the new TapeRedirector build's problem and not a hardware related issue...

Anton, Valery can it be anybody in the storage stack who has connection to tape drive and basically receives "media changed" ASC/ASCQ from tape drive instead of a customer whom we're supposed to send that over iSCSI? According to the logs I've seen StarWind receives the "media changed...

I'm getting the same problem using DPM 2012 R2 UR4. It happens after a while from 10-40Gb of written data to the Tape. Is this the same problem as with BackupExec? I have been wating the server for hardware faults and hardware disconnect but there is no problem there. I'm running Windows Server 201...

Hi! Hello, we have a problem with Tape Redirector and an Hyper-V VM with DPM 2012 installed. The problem is that through Tape redirector we have shared an HP Autoloader G2 1760 connected on a machine and is normally recognized by DPM. The problem is that when we try to inventory or to clean all the ...

When i Try to do Drvinst.exe -install root/stariscsi D:\openoffice\iSCSI Initiator> DrvInst.exe -install [root\stariscsi] "D:\openoffi ce\iSCSI Initiator\iscsi.reg" DrvInstDriverInstallOrUpdate failed (3758096640) ! What could be the issue that it does not work on cmd line but works while...

Hi,

According to the AoE specification each AoE disk connected to a separate Ethernet segment must have its unique "major.minor" id.
Othewise disks with the same ids will look the same for initiators and that may lead to data corruption, so the device ids are very important.