donypie wrote:Can you please tell me if this problem is now solved ?

Not yet.

We are working on the feature to be included in a future release of StarWind.

Thank you! From the last log I saw that StarPort repeatedly tried to negotiate its DefaultTime2Wait=5, but the target each time answered with DefaultTime2Wait=2 and so on until StarPort given up its attempts. According to the iSCSI specs the DefaultTime2Wait is a "max number value", so the...

nazarianin wrote:see log1.txt in log1.zip. This is wireshark log filter for port 3260. 192.168.56.1 - my system with windows 7 x32, 192.168.56.2 - remote Sun storage 7000 in virtualbox.

Hi,

Could you upload the logs in the pcap format?

Thank you in advance.

yushang wrote:Thanks . I have found by analyzing the packet that initiator forgot to set the final bit of SCSI Read Command , that's why target didn't respond .

Great!

Yes , that's because I close the initiator . But if I didn't , I can't even get this log and target will keep no responding . BTW , Target can respond to Nop-Out PDU. Could you send me a zipped network dump file generated by Wireshark for a failed session? The corresponding StarWind log file with L...

Hi,
from the partial log data it seems that the initiator dropped the connection before the SCSI command completion.

For debug purposes it is helpful to enable verbose logging in the StarWind service (level 2).

Ok. One more question. Is there any valid reason for starwind not supporting partitions? If the user ensures that the partition will be used by only one Initiator, why cant we have support for partitions? Is there any particular reason why image file targets should be used? Also exporting a whole d...

Hey Valery, I followed your suggestion and modified the .CFG as you said. When I started the initiator on another machine (vista) and added the portal on the "Discovery" tab, the target got automatically listed under the "Targets" tab. The iscsi target was showing as "Inact...

ThomasS,

Could you zip the StarWind Service's logs and send them to my email?

Hi,

The iSCSI quorum disk is the most critical resource of the cluster.
So I'd recommend to use only 2 NICs on the hosts: public and private+iSCSI.
This should remove the problem you described.

The corresponding StarWind's log files could help to understand what's wrong.

Also a Wireshark's dump of network packets on TCP/IP port 3260 for the same test could give some information...

Hi, - can i backup the snapshot files directly with my backup software? My understanding is that when i create a snapshot new ibvd files are created and the old ones are not changing anymore. So these old ibvd files should be ok to backup. Yes. Older snapshots are ready to be backed up. - when I cre...

Hi!

1) To build a 2-way cluster you need the iSCSI target to run on a third machine, not a cluster node!

2) Check it whether you enabled clustering for the shared targets.

Try to change the following parameter in StarWind.cfg and restart the service:
from <iScsiPingPeriod value="0"/>
to <iScsiPingPeriod value="5"/>

This should help.

Hi,

the Imagefile have to be unmounted from StarWind before you create an IBVolume over it.
It is not allowed to use the image file and its child IBVolume as iSCSI targets simultaneously.