After further digging it appears this issue is down to misconfiguration from my side - somewhat at least. For my test scenario I have been using Windows Server 2003 SP2. Starwind iSCSI was configured to use a sector size of 4096. However as it turns out Windows Server 2003 does NOT support a sector ...
I have been testing the new final version and seen some of the issues I saw during RC (which was fixed) come back. This setup is running: Starwind 8.0.6784 All LUN are created with 512 MB L1 write-back cache. vSphere 5.5 build 1623386 VM running Windows Server 2003 with SP2 slipstreamed - fully unat...
Maybe I did not sign up the right place, but I did not see anything regarding RC2 being out? I did however receive this e-mail on 30th March 2014: Dear Beta-Team member! You have received this email because you have registered on StarWind Beta-Testing program. We will contact you as soon as new beta...
I have digged a bit more into this, very strange. Same thing happens with new clean LUN that was not expanded. If I create a VM on local storage on the ESXi host and then storage vmotion it to the Starwind iSCSI lun it continues to work fine without any corruption. However if I create a new VM on th...
Hello!, I created a target with 2 devices. Both devices were created as 13 GB thick with 1024 MB L1 cache. I then expanded both devices from 13 GB to 20 GB. In ESXi (5.5) I added the LUNs as individual datastores (VMFS-3) and started creating new virtual machines. Up to the first 13 GB I did not exp...